Clients want to know how you spend your time, and how you word it matters.
On your timesheet entries, there are a few rules you should follow on how to best explain the value you have created for the client:
Use past tense. E.g. 'Built', 'Investigated', 'Resolved', 'Enhanced', 'Created', 'Optimized', 'Experimented with', 'Improved' or 'Fixed'.
Use the word 'bug' only if it fits the definition of a bug.
The term 'Investigated and changed' is better than 'Fixed bug'. The word 'bug' gives the impression that the problem was solely the developer's fault, when often most fixes are to do with changes as a result of unspecified work (extra validation, extra testing or gold plating).
Fix Bug on customer form.
❌ Figure: Bad example - Vague work description
Investigated and improved the validation on customer form to enable saving when Customer Name is over 100 characters.
✅ Figure: Good example - Clear description of the work completed
Use a capital letter for proper nouns, such as names, brands, and product names.
For example, “Adam Cogan,” “SQL Server,” and “Toyota” should be capitalized. Common nouns, such as “website,” should not be capitalized unless they start a sentence.
This makes the timesheet easier to read. However, don't go overboard and use half a page for a single timesheet entry.
Avoid abbreviations unless they are widely understood, as they can make content harder to read and understand.
E.g. Use 'version' rather than 'ver'.
Apply changes as per Tony's request for FRDCAPP
❌ Figure: Bad example - This is an example of a bad timesheet note
'CaterPRO! Version 8.3 - Fixed Sales Reports (Sales Dashboard)
✅ Figure: Good example - Informative timesheet note
If you do any work related to a client that you would not usually bill for, such as attending an initial meeting or travelling within Sydney, you should still enter the time under that client.
When it comes to invoicing, the rate for this time will be set to zero. However, the time will still appear on the invoice, giving the client a complete record of all the time spent on their project.
Tip: Use TimePro to avoid doubling up by using Azure DevOps commit messages that flow through to timesheets.