Consultant time tracking: from work sessions to billing records
Create a routine for customers, projects, activities and review, separating recorded time from approved billing input.
Time records are useful when someone can understand what was done, for whom and how it should be handled. A monthly total rarely answers a customer’s question about the work.
This guide concerns recording and review workflows, rather than accounting, tax rules or statutory invoice requirements.
Separate three different concepts
Time worked is what you record. Billable time is work that may be charged under the assignment’s terms. Processed billing input is what has actually moved into invoicing.
These need not match. You may track fixed-price work internally without adding every hour to the agreed price. Decide the treatment for each project and resolve uncertainty before invoicing.
Use a few clear fields
Include date, customer, project, activity, duration and billing treatment, with a short useful description. Avoid unnecessary personal or sensitive information.
| Date | Customer/project | Activity | Time | Treatment |
|---|---|---|---|---|
| Example day | Example customer / website | Review page structure | 1.5 hours | Review against agreement |
| Example day | Internal | Improve project template | 0.5 hours | Internal time |
| Example day | Example customer / website | Correct an issue | 0.75 hours | Assess under contract |
These fictional rows do not establish that any item can be invoiced. They show why activity and treatment are separate.
Agree when and how to record
Use a timer or manual entry close to the work. Colleagues need shared definitions and a way to correct mistakes. Agree how meetings, travel, planning and support are labelled. Keep assignment-specific terms available to the reviewer; software does not replace the customer agreement.
Review before closing the period
Assign regular review. Check missing projects, unclear descriptions, duplicate entries and undecided billing treatment. Ask for clarification while the work is fresh.
Distinguish reviewed rows from those awaiting a decision. If the tool has no dedicated approval state, agree another explicit routine. Do not hide uncertainty in a total.
Check the handover to invoicing
Define how records are transferred and how processed items are recognised. The recipient must trace customer, project, period and approved rows. Test corrections after handover too.
Fixed prices, hourly work and capped budgets may need different decision points. Define these before automating transfers. Confirm export and integration requirements with the supplier.
Try a small example first
Record fictional internal and customer work, correct a mistake and pass a limited set to the recipient. Can they understand it and avoid processing the same row twice? Record unclear steps and decide whether fields or responsibilities need changing.
Glomiva’s time tracking page describes timers, manual entry and customer/project links. Verify review, correction and integration needs in a walkthrough. If customer information is scattered, start with our small business CRM guide.
Keep reading
CRM, projects & time · 3 min read
Small business CRM: when a spreadsheet is enough and when to change
Evaluate follow-up, ownership and handover with a simple customer record template and a complete CRM test journey.
CRM, projects & time · 3 min read
Project tools for small teams: choose with a real workflow
Use a project template, a simple internal scoring method and a limited pilot to compare tools your team can use.
CRM, projects & time · 3 min read
Moving customer records to a CRM: an import checklist
Prepare field mapping, customer identifiers and duplicate decisions, then test a small import before migrating the full register.
