How to Track Retainer Burn in an Agency (2026)

Agencies track retainer burn by dividing actual hours worked on each client by the hours the retainer was scoped for, and comparing that against how much of the period has elapsed. A retainer priced for 100 hours a month that has consumed 60 by day 15 is burning at 120% of pace. Most agencies discover the overrun at renewal, when the account manager says "we're doing way more than we scoped" and nobody can prove by how much. The fix is not a better spreadsheet — it is accurate hours, captured automatically and reported by client and department, so over-servicing shows up mid-period instead of after the margin is gone.

Quick Answer

Track retainer burn monthly per client with one ratio: hours used ÷ scoped hours, checked against percent of period elapsed. Above 100% of pace, the retainer is underwater. Below 70%, it is a churn risk. The report only works with complete hours, which is why the input has to be automatic time capture rather than manual timesheets.

What Is Retainer Burn?

Retainer burn is the rate at which a team consumes the hours or budget a retainer was scoped against, relative to the period elapsed.

Retainers are priced off a staffing plan: a blended rate multiplied by estimated hours per department. Burn tracking compares the plan to reality. When reality consistently exceeds the plan, the agency is over-serving — delivering more than the fee covers — and the gap comes straight out of margin. For how over-servicing hides, read the agency over-servicing guide.

Two numbers, updated continuously:

Burn % = (actual hours worked ÷ scoped hours) × 100, compared against % of period elapsed.

Burn $ = actual hours × each person's fully-loaded cost rate, compared against the retainer fee.

Hours are easy to count. The cost side needs loaded rates — salary plus benefits, payroll tax, and overhead per person — or you get a burn number that flatters the account. Employer Social Security and Medicare tax alone adds 7.65% on top of wages, according to the IRS (Topic 751). A senior-heavy month on a fixed-fee retainer costs far more than the same hours from juniors, and flat "hours remaining" views miss that entirely.

A Worked Example: Burn % vs Burn $

A retainer can look fine on burn % and lose money on burn $ when the over-delivered hours come from expensive staff.

Take a $9,000 monthly retainer scoped for 60 hours: 30 hours of design at $110 loaded cost, 20 of copy at $85, 10 of account time at $140. Scoped delivery cost is $6,400, so the account is priced for a 29% margin. Mid-month, tracked hours sit at 30 — 50% burn against 50% of the period elapsed. On pace, the retainer looks perfectly healthy.

Look at who worked the hours. Instead of the staffing plan's mix, the month ran heavy on senior design: 18 hours of senior design at $130, 5 of copy, 7 of partner-level account time. Delivery cost so far is $3,745 — 59% of the scoped cost budget against 50% of the scoped hours. Run that mix to 60 hours and delivery cost lands around $7,490, leaving $1,510 of profit: a 17% margin, not 29%. Burn % said fine; burn $ caught it. That is why the cost-rate column is in the report template below.

How Do Agencies Track Retainer Burn by Client Each Month?

Agencies track retainer burn each month by exporting actual hours per client, dividing by scoped hours, and ranking clients by burn against the period elapsed — a report the resourcing or operations manager owns.

That is how it works in practice at real agencies. On Rize sales calls, resourcing leads describe the same cadence: clients ask for monthly burns so they can see how the engagement is going, and the burn report doubles as the trigger for a scope addendum when the account runs hot. They also describe the same constraint — the report lands in week one or two depending on whether people did their timesheets. The report is only as fast as the timesheets behind it.

A monthly burn report needs six columns per client. This is the template most agencies converge on:

The "action" column is what turns the report from bookkeeping into management. Every client over 110% gets a named response: a re-scope, a change order, or a repricing conversation. Every client under 70% gets a different one — a check on whether under-delivery is about to cost you the renewal.

Run the same report by department and the picture sharpens. Over-burn is rarely spread evenly; it concentrates in one pod. Unlimited revisions in design or a client who booked two extra status calls a week shows up as a departmental number, which tells you what to cut.

Why Do Manual Timesheets Break the Burn Report?

Manual timesheets understate retainer burn because the work that causes over-burn — small, unscoped tasks — is the work people forget to log.

A Harvard Business Review analysis of timesheet accuracy found that people who fill in time weekly produce records roughly two-thirds accurate at best, and estimated unrecorded work costs the U.S. economy about $7.4 billion per workday. The missing third is not random: it is the quick revision, the "while I'm in here" fix, the five-minute client call that never got a timer.

The result is systematic understatement in one direction. The burn report says 85% at month-end; the real number is 110%. The agency learns the truth only in aggregate, at the P&L level, with no way to attribute the loss to a client. That is the gap between a burn report and reality, and no spreadsheet fixes it — the input has to change.

Timesheets also cost time on the producing side. Asana's Anatomy of Work Index reports workers spend 58% of their day on "work about work" — status updates, chasing approvals, logging activities — and manual time entry is a recurring item on that list. The agency pays twice: once in unlogged delivery hours, once in the hours spent logging.

When Should an Agency Raise Retainer Prices Based on Tracked Time?

An agency should raise a retainer when tracked hours run above scope for two or three consecutive periods, or when the account's effective hourly rate drops below the rate it was priced at.

One heavy month usually has a cause the client already knows about — a launch, a campaign, an extra revision round. Three heavy months mean the scope assumption behind the price was wrong. The trigger thresholds most agencies use:

Burn above 110% for two or more periods. A 50-hour retainer landing at 55+ hours twice running is structural, not noise.

Effective rate below target. A $9,000 retainer worked at 75 hours earns $120 an hour. If it was priced at $150, every month gives away $30 per hour.

Loaded costs rose and the fee did not. Compensation climbs every year — the U.S. Bureau of Labor Statistics Employment Cost Index tracks that change quarterly — so a fee held flat for two years buys less delivery than it did.

Holding the price has a real cost, and the market data says most agencies hold anyway. The Promethean Research Digital Agency Industry Report found only about one in five agencies raised rates in 2026, down from 28% in 2025 — and its 2025 State of Digital Services survey reported 8% average growth for agencies that raised rates versus 4% for agencies that kept them flat.

For the pricing math and the exact pitch — worked example, option framing, notice period — read how to justify a retainer price increase with time tracking data.

What to Do When a Client Burns Under

A client consistently burning under 70% of scope is a churn risk, not a margin win — the fix is more visible delivery, not silence.

Under-burn feels safe because margin looks great. It is not: the client is paying for hours they are not getting, and they will figure that out before the renewal conversation does. Options, in order:

Deliver the missing scope visibly. Front-load the deferred deliverables and tell the client they are coming. Under-delivery survivable by data is not survivable by silence.

Re-scope down at renewal. Offer a smaller retainer before they ask. A client paying $9,000 for work worth $5,000 will eventually find a cheaper agency; a client right-sized to $6,000 stays.

Check the data before acting. Under-burn sometimes means hours are landing in the wrong client bucket — a tagging problem, not a delivery problem. Verify the client's tracked work against the deliverables that actually shipped before you concede the gap.

How to Set Up Retainer Burn Tracking

Retainer burn tracking takes four steps: convert each retainer to scoped hours, capture actual hours automatically, report by client and department, and review weekly so over-burn is caught mid-period.

1. Define the scope unit. Convert each retainer to hours-per-period by department. If the retainer was priced in dollars only, back into hours with the blended rate it was quoted at.

2. Capture actual hours automatically. Manual logging at scale is the failure mode — remember, the burn report can only move as fast as timesheets arrive, and a week of lag means the over-burn client already ran another week over. Automatic capture tools like Rize record every work session in the background and categorize it to the right client, so the report is complete from day one instead of waiting for timesheet compliance.

3. Report burn by client and department. A single agency-level number hides the problem. Burn reports need to split creative, strategy, social, and media separately, because over-servicing is almost always departmental — unlimited revisions in one pod, not uniformly distributed goodwill.

4. Review weekly, act monthly. Weekly review catches a retainer running 130% of pace in week two, when there is still time to re-scope. Monthly reviews only document losses. The agency profitability dashboards in Rize surface this continuously rather than at report time.

5. Take the report to the client. Burn data converts an awkward reprice conversation into a scope conversation. "Here is where the hours went" is evidence a client can engage with; "we need more money" is not. Some clients even ask for the report themselves; at agencies where that happens, monthly burn becomes a client-facing deliverable.

Burn Rate Benchmarks

A healthy retainer burn lands at 85-100% of scoped hours by period end; above 115% is over-servicing, and below 70% is under-delivery that invites churn.

85-100% of scoped hours — healthy. The client gets what they paid for and the margin holds.

100-115% — watch zone. One month here is noise; three consecutive months is a scope problem.

Above 115% — over-servicing. Re-scope or reprice at the next touchpoint; do not wait for renewal.

Below 70% — under-delivery risk. The client will notice the drop in output before your report does, and the renewal conversation goes the other direction.

For context on where the whole industry sits: SPI Research's Professional Services Maturity Benchmark puts average billable utilization across professional services firms around 68-72%, and reports firms above 70% utilization average net margins of 18-22% versus 8-12% for firms below 60%. Burn discipline is how you get to the top of that band without burning the team out.

Common Mistakes

Tracking hours without cost rates. 100 hours of senior time and 100 hours of junior time cost different amounts. Burn in dollars, not just hours.

Reporting at the account level only. Agency-wide utilization looks fine while two clients eat the entire overrun. Burn has to resolve to the client, and ideally the department, to be actionable.

Reviewing at renewal. Burn found at renewal is a post-mortem. The point of tracking is to catch the overrun while the period is still open.

Treating over-servicing as free goodwill. Some over-service is deliberate investment. Fine — but it should be a decision made with numbers, not a default discovered at year end.

Waiting on timesheets. If the burn report lands in week two "depending on if people do their time sheets," every over-burned client got a free week. The cadence problem is a capture problem.

How Rize Produces the Hours

Rize is an automatic time tracker that captures every work session in the background and assigns it to the right client and project, so retainer burn reports use real hours instead of remembered ones.

The desktop app records which apps, documents, and sites the team works in and categorizes the time to clients and projects. Nobody starts a timer, and Rize does not need screenshots or keystroke logging to do it — each person reviews their own time before it is shared, and admins can turn auto-approve off if they want a longer review window. That privacy model is why teams adopt it instead of working around it.

Rize is native for ClickUp, Asana, and Linear, so the client and project structure your PM tool already has becomes the structure of the burn report — no manual mapping spreadsheet. From there, hours and margin per client are live in the Rize for agencies dashboards, and automatic time tracking is what makes them trustworthy.

The agencies that fix retainer burn do it with data, not discipline. If your burn reports depend on people remembering to log time, the reports are already wrong. See how Rize compares to Float for burn reporting, run the numbers in the profitability calculator, or read the agency profitability tracking guide.