Time entry descriptions that hold up on an invoice
“Design changes” says little when finance reviews an invoice weeks later. These fictional before-and-after examples show how to describe work accurately without copying private conversations or overstating completion.
Product claims checked against the ABH truth sheet on 14 October 2026. Examples are fictional and illustrative. Operational guidance only, not legal, tax or accounting advice.
Short answer
Write the action, the deliverable or context, and the result or next state. Keep duration in its own record and avoid confidential details. The examples below are writing guidance, not ABH templates, automated suggestions or proof that an activity is chargeable.
Review current plans for the time and invoicing workflow. Client funds are received outside ABH and recorded manually.
What a useful description contains
A useful entry says what you did, what it concerned and what changed or remains to do. The date, duration and assignment provide the surrounding record; the description supplies meaning. “Client work” repeats the project label without explaining the activity. A reviewer should be able to distinguish research from revisions and a finished task from an unresolved investigation without interviewing the contributor again.
Write for someone who was not in the meeting, while keeping confidential detail out. Use a deliverable name or approved task reference rather than copying a private message. ABH ties time to clients, projects and tasks, and proof-backed invoice lines can trace to logged work. These editorial examples are not description templates or automated suggestions inside ABH.
Weak versus strong examples: design
Weak: “Design changes.” Stronger: “Revised the landing page hero layout following the approved second-round feedback; exported the desktop preview for review.” The stronger entry identifies the asset, basis for the change and resulting state. It does not need every spacing adjustment or the client's private comments. Keep the time amount in the duration field rather than repeating it in the sentence.
Weak: “Worked on branding.” Stronger: “Compared two approved logo lockups at small sizes and prepared a legibility sheet for the selection meeting.” This describes exploration without claiming a final logo was delivered. If a design remains unfinished, name the remaining decision. Do not turn an honest progress note into a completion claim merely to make it look more invoice-ready.
Weak versus strong examples: development
Weak: “Fixed bugs.” Stronger: “Reproduced the contact form validation error, corrected the empty-message check and verified the agreed test cases.” Name the affected behavior and the verification performed. Avoid credentials, customer payloads or security-sensitive implementation detail in a description that could become billing evidence. Keep detailed debugging notes in the appropriate restricted technical record instead.
Weak: “Deployment.” Stronger: “Prepared the release checklist and tested the booking flow in staging; production approval remains open.” This distinction prevents a reviewer from assuming the live release happened. Similarly, “Investigated the checkout failure and isolated a browser-specific reproduction” describes useful work without claiming a fix. The result can be a diagnosis, provided the description says so clearly.
Weak versus strong examples: marketing and account work
Weak: “Campaign work.” Stronger: “Reviewed the agreed search campaign terms and drafted exclusion recommendations for client review.” That entry names the channel, activity and next state without inventing a performance outcome. Do not attach unsupported claims about revenue, conversion gains or campaign success to a time note. A work record should explain the task performed, not become a sales testimonial.
Weak: “Client call.” Stronger: “Reviewed the October content calendar with the client and recorded owners for the three outstanding approvals.” Weak: “Emails.” Stronger: “Consolidated the client's revision requests into the approved brief and sent the scope questions to the engagement owner.” These are fictional wording examples. None implies that calls or correspondence are automatically billable; the agreement still determines eligibility.
A one line format
Use this one line format: action + deliverable or context + result or next state. For example, “Mapped the onboarding form fields to the approved data list; two retention questions await the client.” Replace vague verbs with the actual activity, but avoid stacking jargon. If two unrelated tasks need different review or authorization, use separate records rather than one sentence that hides the distinction.
For internal work, apply the same clarity: “Updated the reusable kickoff checklist after the team review and assigned the remaining documentation task.” Label and handle that work according to your agency process, without charging it to a client by default. Read billable versus non-billable hours for eligibility and team tracking habits for teaching the format consistently.
Review descriptions before approval
Before approving an entry, compare its description with the assignment and supporting task. Check whether “completed” is accurate, whether a revision was authorized and whether the wording can safely appear in client evidence. Return a specific request when a note is unclear. Let the contributor clarify what happened rather than having finance invent a polished explanation after the fact. Keep the underlying duration accurate.
ABH supports single and bulk time approval, not an invoice approval workflow. Use the timesheet approval checklist, proof-of-work checklist and time-to-invoice guide for the wider review. The agency billing process connects that review with invoice issue. If a client questions a line, follow dispute handling using the original evidence rather than rewriting history.
Frequently asked questions
Do these examples come built into ABH?
No. They are editorial examples to adapt to your own work. No in-product description template or suggestion feature is claimed.
Does every entry need to describe a finished deliverable?
No. Investigation and work in progress are valid activities. State the actual result or next step without implying completion.
Can I copy a private client message into a time note?
Use a neutral reference or short factual summary instead. Review who may see the description and avoid unnecessary personal or confidential information.
Make the work understandable.
Review current plans for the time and invoicing workflow. Client funds are received outside ABH and recorded manually.