The short answer
A retainer burndown shows how many of a retainer's hours are left, week by week, against a straight line that would use them up exactly at month end. If your actual line sits above the straight line, you are using hours more slowly than the month is passing. If it sits below, you are on course to run out early. It answers the one question an account lead needs every Monday: will the hours last?
The idea is borrowed from project teams, who burn down remaining work over a sprint. A retainer is simpler, because the starting point is a number the client already bought.
What a burndown shows
- Start. The hours available for the month: the monthly allowance plus anything carried in from last month.
- Actual line. Hours available minus the hours logged so far, at the end of each week.
- Ideal line. Hours available times the share of the month still to come. It falls in a straight line from the full amount to zero. The ideal line is a yardstick, not a plan: real work arrives in lumps.
- Gap. Actual minus ideal. A positive gap means unused hours compared with an even pace. A negative gap means you are ahead of an even pace, and need to decide whether that is a launch week or a problem.
A burn-up is the same data drawn the other way: hours used, rising towards the allowance. Use whichever your clients read more easily. This guide uses the burndown.
How to work it out
- Hours available = monthly allowance + hours carried in.
- Hours used by the end of the week = every hour logged on the retainer from the 1st to that day.
- Actual remaining = hours available - hours used.
- Ideal remaining = hours available x (days in the month - days gone) / days in the month. Use calendar days: it keeps the line honest across weekends and is the same in every month.
- Gap = actual remaining - ideal remaining.
A worked month, week by week
An example retainer: 30 hours a month, with 4 hours carried in, so 34 available in March 2027 (31 days). Weeks run in blocks of seven days from the 1st. The figures are illustrative.
| Week ends | Days gone | Hours that week | Used so far | Actual left | Ideal left | Gap |
|---|---|---|---|---|---|---|
| 7 March | 7 | 8 | 8 | 26.0 | 26.3 | -0.3 |
| 14 March | 14 | 9 | 17 | 17.0 | 18.6 | -1.6 |
| 21 March | 21 | 7 | 24 | 10.0 | 11.0 | -1.0 |
| 28 March | 28 | 6 | 30 | 4.0 | 3.3 | +0.7 |
| 31 March | 31 | 0 | 30 | 4.0 | 0.0 | +4.0 |
Reading it, week by week:
- Weeks 1 to 3. The gap stays within 2 hours of the line. The account is slightly ahead of an even pace. Nothing to do except note that a launch is planned.
- Week 4. Only 6 hours were logged, and the gap flips to +0.7. The launch took less time than planned.
- Month end. 4 hours are left, and the gap is simply those 4 hours. What happens to them depends on the rollover rule: under a cap of 10 hours, all 4 carry into April. Under no rollover, they lapse, and that is a conversation to have in week 3, not on 31 March.
Three shapes to watch for
- Falling faster than the ideal line. The month will run out early. Decide in time whether to reprioritise, ask for approval to go over, or pause lower-value work. See overage.
- A flat line for two weeks. Either the work is waiting on the client, or hours are being logged somewhere else. Check both before the report goes out.
- A cliff at the end. A line that is nearly level for three weeks and then drops is a month where the team left everything to the last week. That is a delivery habit, not a client problem, and it makes overruns invisible until it is too late.
Drawing the chart
You do not need a charting tool. Put the "Actual left" and "Ideal left" columns from the table in a spreadsheet and insert a line chart. Our free retainer hours tracker has a Weeks sheet that fills in those columns from your time log, so only the chart is left to add. For a quick check partway through a month, the retainer hours calculator projects where the month will end.
Common mistakes
- Starting from the allowance when hours carry in. If 4 hours came in, the burndown starts at 34, not 30. Otherwise a carried balance looks like an overrun.
- Treating the ideal line as a target. Work is lumpy. Use the gap to ask a question, not to blame the team.
- Counting weekends as no time. If you use working days for the ideal line, use them for every month and say so on the report.
- Showing the client a line with no context. Add one sentence: what drove the hours, and what is planned next.