Make MSP Time Tracking Reflect the Work You Deliver

Record the Work Before Deciding What to Bill

Cohost Nick describes a technician recording less project time than he worked because he expected the task to take less time. Nick argues for recording actual work and asking for help, with the business deciding the billing treatment. That's his reported experience and advice, not a measure of how often technicians do it.

The useful distinction is between labor consumed and money charged. A fixed-fee agreement can include the work without making the labor disappear. A project write-off can change the invoice without changing the cost of delivering it.

Tell staff to record actual work against the right client and task. Have the authorized billing reviewer decide whether it is included, separately billable, waived, or disputed. Keep that decision visible without rewriting the original work into a more flattering number.

If the estimate is being exceeded, ask the technician to raise it with the project owner while the work is still underway. The owner can review scope, access, assumptions, and approvals. Time tracking should reveal that decision early enough to make it.

Put the Entry Against the Right Work

Give technicians a clear place to record managed support, project delivery, internal work, and other duties. Use work types and agreements your PSA actually supports. Keep the choices distinct enough to report on, and remove labels the team can't consistently tell apart.

Picture a technician helping with a deployment and then answering an unrelated support request from the same client. Those activities need their own task records and time treatment. The client name alone doesn't tell finance which delivery work consumed the hours.

The model costs service work through burdened labor and utilization. It also separates project engineers from the desk. Mixing their work into a common undifferentiated bucket would make the resulting comparison hard to interpret.

Have the lead publish worked examples from your own agreements: an included support task, an approved project task, and internal documentation work. Use those to explain the categories. Don't ask each technician to invent a billing policy while closing a ticket.

Count Labor Rather Than the Ticket Clock

An open ticket measures elapsed time until closure. A labor entry records a person's work. Waiting for a client reply isn't automatically continuous labor, and closing a ticket doesn't establish how much time it consumed.

Record the work performed during a waiting period, such as investigation or follow-up, against the appropriate task. Describe it. Have the lead review entries that appear to cover an uninterrupted stretch of waiting without a corresponding activity.

Check overlapping entries for the same technician. Resolve the actual work sequence rather than automatically adding every running timer. When several technicians work together, each records their own labor, so the task's total labor can differ from its elapsed duration.

Choose how the team captures time from the tools and working arrangements you have. A timer can help capture a stretch of work, but leaving it running doesn't establish what happened. The record still needs the person's check before it is submitted.

Write a Note the Next Technician Can Use

Require enough detail to connect the time to an action and result. A useful note says what the technician worked on, what they found or changed, what happened, and what remains. Keep sensitive information in its approved place rather than pasting it into a general work note.

For unresolved work, add the next action and who owns it. For a completed task, record the result that supports closing it. A note saying Worked on issue leaves both the next technician and the billing reviewer to reconstruct the work.

I'd have technicians check the entry when they finish the task or hand it over, while the details are available. If work interrupts that check, give the lead a way to see what remains unsubmitted. Don't treat an incomplete note as a reason to make up a precise duration later.

Where a record needs correction, preserve what was changed and why through the PSA's available history or your documented correction process. A tidy report assembled from unmarked guesses is still a guess.

Have the Lead Check the Record Before Using It

The review belongs to the lead, with billing decisions going to the authorized reviewer. Keep their checks short enough to perform and specific enough to change the record.

• The technician confirms actual labor, the correct task, and a note explaining the work before submitting the entry.
• The team lead checks missing, overlapping, unusually long, or misclassified entries with the technician and records agreed corrections.
• The project owner reviews work exceeding the estimate and decides whether scope, method, or approval needs to change.
• The billing reviewer applies the agreement and approval record, preserving actual labor when changing the charge.
• The owner or finance lead confirms the reporting definitions before using utilization or client costs to make staffing and pricing decisions.

A discrepancy needs investigation. It doesn't tell you whether the cause was a timer, a category, an estimate, or the work itself. Ask about the entry before using it to judge the person.

Compare Utilization on the Same Basis

Utilization is productive work divided by the available hours used for the calculation. The model's 70% service assumption uses its 1,660 annual available-hour basis. Keep that basis visible when comparing your records with the plan.

Don't compare a report based on paid calendar hours with the model figure as though their denominators were identical. Have finance reconcile the available hours and have the lead confirm which activities count as productive work. Record any differences before interpreting a gap.

Nor is every productive hour separately billable. Included managed support still consumes delivery capacity. Use the work classification and agreement treatment to answer the billing question separately.

Start with the entries your lead can't explain today. Correct their categories and notes, then show the team the recording rule using those examples. The next utilization report will be more useful when it can be traced to work the desk recognizes.