Define the purpose of the categories
Decide what the team needs to learn. If the question is whether client delivery leaves enough room for support and review, categorize those activities explicitly. If the question is whether an invoice is ready, keep billing eligibility and approval status visible rather than using a general internal-work label.
Use a short shared definition for each category. A person should be able to classify an ordinary entry without asking which label makes the report look better. Publish examples, a route for corrections, and who decides an ambiguous case.
Start with a small set of meaningful categories
An illustrative starting set is:
- **Internal operations:** maintaining the team's own systems and administrative processes.
- **Learning and capability:** training, documentation practice, and skills development.
- **Business development:** proposals, discovery conversations, and prospect work.
- **Client coordination pending billing review:** project-related work whose billing treatment still needs a decision.
- **Internal planning and quality review:** capacity planning, peer review, and process improvement.
- **Unclassified or awaiting correction:** an entry whose purpose is not yet understood.
Leave and other unavailable capacity should remain distinct from worked hours. Whether you subtract leave from available capacity is a denominator choice that must be stated. Do not quietly count it once as unavailable time and again as an internal task.
These categories are examples, not a universal chart of accounts. The actual billing treatment of client work depends on the applicable agreement and the authorized review, which this guide does not establish.
Keep billing status separate from activity type
A meeting is an activity type. Whether that meeting is billable is a separate question. The same is true for research, review, and support. Where the workflow permits it, record the project, activity, and billing decision separately.
For example, a project review can be linked to a client project while remaining pending billing approval. Classifying it as “internal” solely because the invoice has not been approved loses information about what the work supported.
If a record is missing, preserve that uncertainty. An unclassified hour is not confirmed business development, and a missing hour is not a confirmed zero. Give the owner a clear way to correct the record without rewriting the history invisibly.
Use the same period and people in comparisons
Consider an illustrative week with 40 scheduled hours, 24 billable hours, 8 hours of internal work, and 8 hours of approved leave. With scheduled capacity as the denominator, utilization is 24 divided by 40, or 60%. With capacity adjusted for that leave, it is 24 divided by 32, or 75%.
Both figures can describe the same record, but they answer different questions. State the basis before comparing teams or periods. The utilization calculator keeps that basis next to the inputs and exported result.
Do not use the remaining capacity as an automatic label of idle time. It may include work the billing classification excludes or records that still need review.
Review categories with the people using them
Pilot the definitions with a small group. Look for repeated ambiguity, duplicate labels, and entries that people cannot classify honestly. Combine categories that lead to the same review decision and split a category only when doing so answers a real operational question.
The time-tracking rollout guide covers purpose, transparency, corrections, and a small initial pilot. Avoid changing the rules midway through a comparison without documenting the change.
Turn the report into a practical decision
At the weekly capacity review, ask which internal activities support upcoming commitments, which client entries need approval, and which records need correction. Name the next action and owner for each unresolved item.
Use Colabio to connect the categories to the team's projects and time records. The useful outcome is a clearer planning conversation, not a score that treats every non-billable hour as a failure.