Scope reconciliation: the monthly check that found 230 hours before they reached an invoice
A scope-reconciliation workbook compares, line by line, what the client approved with what the team actually did, before the invoice goes out. It is the simplest margin control I know, and on one programme it surfaced more than 230 hours of unapproved work while there was still time to decide what to do about it.
Why invoices get disputed
Most invoice disputes are not about the rate. They are about surprise. The client sees a number that does not match the picture in their head, and the delivery team cannot quickly show where the hours went. By the time the conversation happens, the work is weeks old, nobody remembers who asked for what, and the easiest way out is a discount.
Scope reconciliation removes the surprise. Every month, before anything is invoiced, delivery and the client look at the same sheet: approved scope on one side, actual effort on the other, and every difference explained.
The workbook: seven columns
The format matters less than the discipline, but this is the layout I use. One row per piece of work, grouped by workstream.
Swipe the table sideways to see every column →
| Column | What goes in it | Why it matters |
|---|---|---|
| Item | Ticket, feature or task, in the client's language | The client must recognise every row |
| Source | SOW line, change request number or "not approved" | Makes unapproved work visible at a glance |
| Approved hours | From the SOW or signed change request | The baseline the client agreed to |
| Actual hours | From timesheets, by person | The real cost of the row |
| Variance | Actual minus approved | Where margin is leaking |
| Reason | One sentence: defect, clarification, new request, estimate miss | Separates our mistakes from new asks |
| Decision | Bill, absorb or defer | Every variance ends with a choice |
The monthly routine
The workbook only works if it is boring and regular. The rhythm I run is simple.
- Week 1: team leads tag every timesheet entry to a workbook row. Anything that cannot be tagged is a finding in itself.
- Week 2: the delivery lead reviews variances and writes the reason for each one. Estimate misses on our side are marked honestly.
- Week 3: a 30-minute review with the client owner. We walk the variances, not the whole sheet.
- Week 4: decisions are recorded and the invoice is raised from the agreed sheet, so there is nothing left to dispute.
Bill, absorb or defer
Not every variance should be billed. If the extra hours came from our own estimate miss or a defect we introduced, we absorb them and say so. If they came from a genuine new request, we raise a change request, or we agree to defer the item into the next phase where it can be priced properly. Sometimes we absorb a small new request on purpose, because the relationship is worth more than the hours. The point is that it becomes a decision someone made, not a leak nobody noticed.
On the multi-brand Adobe Commerce programme, the first few reconciliations surfaced more than 230 hours of work that had never been approved. Some of it was billed, some absorbed, and a large part was moved into a new workstream the client funded. The same discipline later supported the business case for continued investment, because every hour on the account could be explained.
How to start next month
You do not need a new tool. Export last month's timesheets, list the approved scope from the SOW and any signed change requests, and match them up in a spreadsheet. The first attempt will be messy. The second will be faster, and by the third the team will start tagging their time properly because they know the question is coming.
Frequently asked questions
- What is scope reconciliation in project delivery?
- It is a regular comparison of approved scope and hours with actual hours worked, line by line, before invoicing. Each variance gets a reason and a decision to bill, absorb or defer it, so invoices match what the client agreed.
- How often should scope reconciliation be done?
- Monthly, before each invoice, for time-and-materials and retainer work. On fixed-price programmes, run it at every milestone so change requests are raised while the work is still fresh.
- How do you stop scope creep without damaging the client relationship?
- Make every change visible early and give the client a choice: pay for it now, defer it to a later phase, or have it absorbed deliberately. Clients rarely object to a clear record; they object to surprises on an invoice.
If you are building or fixing a delivery organisation and want someone who has run one as a business, book 20 minutes.
Book a 20-minute intro call