Project Write-Offs: The Cost You Stop Measuring

Your team finished the project. The client signed off on every deliverable. But when the project manager submits the final timesheet reconciliation, there’s a problem: 140 hours of legitimate work that nobody can bill. The project was fixed-fee, the scope stayed (mostly) within bounds, and the estimate was simply wrong. Those hours become a project write-off, and the margin drops from 28% to 9%.

This happens more often than most services firms admit. Write-offs get treated as one-off events rather than a systemic signal, partly because nobody tracks them consistently enough to see the pattern.

What Counts as a Project Write-Off?

A project write-off occurs when a services firm absorbs billable work that will never generate revenue. It takes several forms:

Time write-offs. Hours worked on client deliverables that get written off because they exceed the budget, weren’t pre-approved, or fall outside the contracted scope
Rate write-offs. Work billed at a lower rate than the resource’s standard rate, either through discounting or because a senior person did work that was scoped for a junior
Invoice write-downs. Reducing the final invoice because the client disputes the hours, questions the value, or because the project manager decides the overage “wasn’t worth the fight”
Bad debt write-offs. Invoiced work that the client never pays, eventually written off as uncollectable

Each type has different root causes and different solutions. Most firms lump them all into a single line item, if they track them at all.

How Much Do Write-Offs Actually Cost?

The SPI Research 2026 Professional Services Maturity Benchmark reveals a striking gap: average project margins reached 37.2% (a five-year high), yet industry EBITDA dropped to 9.9%, down from a 13.8% five-year average. That 27-point spread between project-level margins and firm-level profitability includes several factors, but write-offs are one of the largest contributors that firms fail to isolate.

Consider a mid-size consultancy with $8 million in annual revenue and 50 consultants. If the firm writes off an average of 4 hours per consultant per week (a figure that many managing directors would consider conservative), the math looks like this:

50 consultants x 4 hours/week x 48 working weeks = 9,600 hours
At an average bill rate of $175/hour, that’s $1.68 million in annual write-offs
On $8M revenue, that’s 21% of top-line capacity that never converts to revenue

The hours still cost you. Salaries, benefits, and overhead don’t disappear because the time didn’t get billed. Write-offs are pure margin destruction.

Why Do Services Firms Stop Tracking Write-Offs?

If the financial impact is this severe, why don’t firms measure it rigorously? Three patterns come up repeatedly when working with mid-size services businesses.

Write-offs happen at the wrong moment

The decision to write off time typically happens during invoicing or project close, when the project manager is focused on moving to the next engagement. There’s pressure to close the books, send the invoice, and avoid a client conflict. The write-off decision gets made quickly, documented poorly (if at all), and forgotten by the next sprint planning meeting.

No clear ownership

Finance sees write-offs as a delivery problem. Delivery sees them as a scoping problem. Sales sees them as a pricing problem. When accountability is diffuse, nobody builds the reporting or the process to systematically track, categorize, and learn from write-offs.

The data lives in different systems

Time gets logged in one tool, invoices go out from another, and the write-off decision happens in a conversation or an email thread. Reconciling what was worked, what was billed, and what was absorbed requires pulling data from multiple sources. Most firms do this analysis quarterly at best, by which point the lessons are stale.

What Triggers the Write-Off Decision?

Understanding the root causes helps you intervene earlier. The most common triggers, ranked by frequency:

Estimation errors. The original scope or LOE (level of effort) was wrong. The project needed 600 hours but was sold at 400. This is the single largest category in most firms, and it connects directly to how estimates go wrong
Scope absorption. Small additions that individually seem too minor to trigger a change order, but collectively add 15-25% to the project. This is a form of scope creep that flies under the formal change control threshold
Resource misallocation. A senior architect does work that was scoped for a mid-level developer because the mid-level wasn’t available, the senior could do it faster, or nobody was tracking who was doing what. The hours are within budget, but the cost is higher than planned
Rework and quality issues. Deliverables that need to be redone because requirements were misunderstood, technical approaches failed, or client feedback wasn’t incorporated correctly the first time
Client relationship preservation. The PM decides that billing for the overage would damage the relationship, trigger a dispute, or jeopardize future work. The write-off gets framed as a “strategic investment” in the account

Each trigger has a different intervention point. Estimation errors require better scoping processes. Scope absorption requires clearer change order thresholds. Resource misallocation requires real-time visibility into who’s doing what and at what cost.

How Do You Measure Write-Offs Effectively?

The goal isn’t to eliminate write-offs entirely. Some projects will always have overruns, and sometimes absorbing a cost is genuinely the right business decision. The goal is to make write-offs visible, intentional, and declining over time.

Track write-offs as a distinct metric

Create a write-off rate: total hours written off divided by total hours worked, expressed as a percentage. In our experience working with mid-size services firms, the best-run organizations keep this number below 3%. The industry average is harder to pin down because most firms don’t track it consistently, but 8-10% is a reasonable baseline for firms that do measure.

Categorize every write-off

When time is written off, require a reason code. At minimum, distinguish between:

Estimation error (project was under-scoped)
Scope change (work was out of original scope but not formally changed)
Efficiency issue (rework, learning curve, technical debt)
Relationship decision (deliberate absorption for strategic reasons)
Administrative (timesheet corrections, misallocated entries)

The categories tell you where to invest in prevention. If 60% of your write-offs are estimation errors, improving your scoping process will have more impact than tightening change order controls.

Set write-off approval thresholds

Not every write-off should require executive approval. But write-offs above a certain threshold (5% of project value, for example) should require documentation and sign-off from someone other than the project manager who’s absorbing the cost. This isn’t bureaucracy. It’s making the cost visible to someone with the authority and incentive to ask: “Why did this happen, and how do we prevent it next time?”

Review write-offs monthly, not quarterly

A quarterly review means you’re always looking at stale data. Monthly write-off reviews, connected to your financial close process, surface patterns while they’re still actionable. If three projects from the same practice area all had estimation overruns in the same month, that’s a signal you can act on. Three months later, it’s just history.

The Early Warning Signs That Predict a Write-Off

Write-offs don’t appear from nowhere. They build over weeks or months before the formal decision to absorb the cost. Here’s what to watch:

Budget consumption outpacing delivery. If a project is 40% complete but has burned 60% of budget, a write-off is likely unless something changes. This requires real-time tracking, not end-of-project reconciliation
Senior resources doing junior work. When your most expensive people are executing tasks below their rate card, the project is accumulating hidden cost overruns even if the hours look on-track
Change requests that never become change orders. Every “quick addition” absorbed without adjusting the contract is a future write-off being born
Time entries that spike late in the project. A sudden increase in hours during the final 20% of a project usually means earlier work was underreported, or late-stage rework is consuming more effort than anyone expected
Project managers who stop updating forecasts. When the EAC (estimate at completion) stops getting revised upward, it often means the PM knows the project is over-budget but hasn’t yet formalized the write-off

Building a Write-Off Prevention Culture

The firms that maintain write-off rates below 3% don’t do it through better tools alone. They treat write-offs as learning opportunities rather than failures to bury.

Normalize the conversation. Write-offs are not shameful. Every services firm has them. What’s unacceptable is writing off time without understanding why, without documenting it, and without feeding the lesson back into future estimates.

Connect write-offs to estimation improvement. Every write-off caused by an estimation error should trigger a comparison: what did we estimate, what did we actually spend, and what did we miss? Over time, this builds an institutional database of estimation accuracy that makes every future estimate better.

Reward early escalation. If a PM raises a flag at week 3 that the project is trending toward a 15% overrun, the firm can intervene: adjust scope with the client, bring in different resources, or make a deliberate decision to absorb the cost for relationship reasons. If the PM waits until week 12 to surface the same problem, the only option is a write-off. Make early warnings safe.

Tie write-offs to compensation. Not as a punitive measure, but as an accountability signal. If project margins (net of write-offs) are part of how PMs are evaluated, they’ll track them more carefully. If partner bonuses factor in the write-off rate of their practice area, partners will invest in better scoping and estimation.

Frequently Asked Questions

What is a project write-off in professional services?

A project write-off occurs when a services firm absorbs the cost of billable work that will never be invoiced to the client. This includes hours that exceed the project budget, work done at rates higher than billed, invoice reductions to avoid disputes, and uncollectable receivables. The cost is borne entirely by the firm’s margins.

What is a normal write-off rate for services firms?

Top-performing professional services firms typically maintain write-off rates below 3% of total hours worked. The industry average sits closer to 8-10%, though many firms don’t track it formally. For a firm billing $150-200 per hour, every percentage point of write-offs represents significant annual revenue loss.

How do you reduce project write-offs?

Reducing write-offs requires addressing root causes, not symptoms. Start by categorizing write-offs by type (estimation error, scope absorption, rework, relationship decisions). Then invest in the highest-impact category first. For most firms, this means improving estimation accuracy through historical data analysis and requiring formal change orders for any scope additions.

What is the difference between a write-off and unbilled work?

Unbilled work is broader. It includes any time worked that doesn’t generate an invoice, including internal projects, business development, and administrative tasks. A write-off specifically refers to client-facing billable work that was performed but will not be invoiced. All write-offs are unbilled work, but not all unbilled work is a write-off.

How often should firms review project write-offs?

Monthly reviews are the minimum cadence for actionable insights. Quarterly reviews produce stale data that’s difficult to act on because the context around the write-off decision has faded. Best-in-class firms review write-offs as part of their monthly financial close, categorize each one, and feed findings back into estimation and scoping processes within the same month.

How Tier2 Keel Tracks Project Margins in Real Time

The early-warning signals described above require one thing that most services firms lack: real-time visibility into the gap between planned and actual project economics.

Tier2 Keel tracks project costs from the moment work begins. As your team logs time, the system calculates actual cost against the project budget and updates margin projections automatically. When a project hits a budget threshold (say, 70% of hours consumed at 50% completion), the variance surfaces before it becomes a write-off.

The project lifecycle in Keel connects estimation to execution to invoicing in a single system. The gap between what you quoted and what you delivered isn’t something you discover during billing reconciliation. It’s visible throughout the engagement, giving project managers the data they need to escalate early, adjust scope, or make deliberate decisions about cost absorption.

See how Keel handles project financials or book a walkthrough with our team.

Moving Forward

The next time your finance team reports quarterly write-offs as a single line item, ask for the breakdown. What percentage was estimation error? What was scope absorption? What was a deliberate relationship investment? The answers will tell you whether you have a process problem, a pricing problem, or a visibility problem. Each has a different fix, and none of them require accepting write-offs as an inevitable cost of doing business.