)
)
How to spot at-risk projects before margin goes: summary & key takeaways
At-risk definition: A project is at margin risk when its cost budget burns faster than its work gets delivered.
Four leading signals: Watch burn against progress, forecast margin against target, unpriced scope and rate mix, each with an amber and a red threshold.
Weekly screen: A 30-minute review between finance and delivery each week catches drift before repricing, rescoping or restaffing gets expensive.
Signal-specific fix: Each red signal has its own first move, such as a change order for extra scope or restaffing junior-rate tasks.
Knowing how to spot at-risk projects before margin goes comes down to one weekly check: what each project has spent against what it has delivered. Before I joined Teamwork.com, I worked agency-side, where clients kept asking for more inside the same retainer and nothing in our process recovered the cost.
The lesson stuck: by the time a report said overspent, the decision behind it was long past cheap to fix. This guide gives you four leading signals with thresholds, a worked example and the fix for each.
A project is at margin risk when spend outruns progress
An at-risk project is one where the share of its cost budget used runs ahead of the share of work delivered. Budget used on its own tells you very little. Say a project has used 50% of its budget: that looks healthy until you learn it's 30% done.
Portfolio views make it harder to see, because a blended margin can hit target while one fixed-fee project loses money every week. A budget that finally reaches 100% only confirms a loss that started much earlier.
In my agency years, the resourcing spreadsheets showed workloads that averaged out fine while the same few people stayed late. Averages hid that imbalance, and portfolio margin hides a sinking project the same way. Screen projects one at a time.
If you're the person asked to explain a write-off on a project you never ran, it's a frustrating seat. You own the number but none of the decisions that produced it.
Our guide to margin erosion in professional services covers the causes behind that loss. The case for watching margin as work happens sits in live margin control, and wider delivery risks are in the project risk guide.
The weekly margin risk screen: four signals and their thresholds
The weekly margin risk screen splits spend against progress into four numbers you can check in one meeting. Each signal gets an amber line, where you ask questions, and a red line, where someone owns a fix by the next review. Treat these thresholds as illustrative starting points, and tune them after a quarter of reviews against your own project history.
Margin risk screen: signals, thresholds and first fix
Signal
Run the screen as a 30-minute meeting between the finance lead and the delivery lead. The inputs are time and costs logged up to the end of the previous week, plus percent complete from the delivery lead. Take red projects first, so the time goes where margin is moving.
Data check (5 minutes): Confirm every project has time and costs logged through last week, and flag any with missing timesheets.
Red projects (10 minutes): Agree the first fix for each red signal, with one owner and a date.
Amber projects (10 minutes): Ask what's behind each amber, and decide whether it's likely to turn red next week.
Actions recap (5 minutes): Read back owners and dates, and note any forecast change finance needs for invoice planning.
Burn running ahead of progress
Burn gap is the share of the cost budget used minus the share of work complete, in percentage points. Amber starts at a 10-point gap and red at 20.
The number is only as honest as percent complete. If your team measures progress as hours spent against hours estimated, the gap is zero by construction, and every overrun disappears. Measure progress by deliverables or milestones the client has accepted, weighted by their share of the estimate.
Expect some gap early on projects with heavy setup work. A gap that widens two reviews running matters more than one bad week.
Forecast margin below target
Forecast margin at completion is what the project will earn if the remaining work runs at the cost efficiency seen so far. It takes two steps: project the total cost, then compare it with the fee.
Amber is 5 points below the quoted margin and red is 10 points below. Compare this trend forecast with the delivery lead's own estimate of effort to finish. When the two disagree, the gap between them is your first question.
Scope growing without a price
Unpriced scope is the cost of hours spent on requests outside the SOW that have no change order behind them. Measure it as a share of the cost budget, with amber at 3% and red at 5%.
The 5% red line borrows from a broader warning about change across a whole project. Lee A. Peters' 2010 PMI Global Congress paper on warning signs notes that "many times changes greater than 5% of the total can overwhelm a project."
A red here means the project you're delivering is no longer the one you priced. Most of the scope creep I dealt with in agency life started at the pitch, when we underbid to win the business. So a red is a lesson for the next quote as much as a conversation about this one.
Rate mix drifting senior
Rate mix drift is the gap between the actual cost per hour logged and the blended cost rate you planned at quote. Amber is 10% above plan and red is 15% above. It usually means senior people are doing work you priced at junior rates, often because they were free when the request came in.
Before you restaff, check where the senior hours would go instead. The billable utilization rate calculator shows how much of each person's time is invoiceable. Moving a senior person off junior work only lifts margin if their freed hours land on billable work.
Worked example: recomputing margin on a project halfway through
Run the four signals on one illustrative project and the thresholds turn into a clear verdict by week 6. Assume a $120,000 fixed-fee project over 12 weeks, quoted at a 40% margin, which sets a cost budget of $72,000.
At week 6, the delivery lead reports 40% of the work accepted, and $43,200 of cost has been logged. That's 60% of the cost budget, so the burn gap is 20 points: red. At that rate of spend, the forecast cost at completion is $108,000.
Forecast margin drops to 10%, which is 30 points below the 40% target and well past the red line. In dollars, that's $12,000 of profit against the $48,000 you quoted.
Of the cost logged, 70 hours went on extras the client asked for outside the SOW. At a $90 cost rate, that's $6,300.
That $6,300 is 8.75% of the cost budget, red against the 5% line. Assume the rate mix matches the plan, so the fourth signal is green.
Strip the extras out and cost to date is $36,900, or 51.25% of the cost budget. The burn gap is still 11.25 points, amber, so scope explains part of the slide and the original estimate explains the rest. On the screen itself, the whole diagnosis fits on one line anyone in the meeting can read.
Week 6 margin risk row
| Project | Weeks elapsed | Work complete | Cost budget used | Burn gap (points) | Forecast margin at completion | Unpriced scope (% of cost budget) | Rate mix vs. plan | Overall status |
|---|---|---|---|---|---|---|---|---|
| Illustrative fixed-fee project ($120,000 fee) | 6 of 12 | 40% | 60% | 20 (red) | 10% (red, 30 points below target) | 8.75% (red) | On plan (green) | Red |
Three reds in one row put this project at the top of the next agenda, with a named owner for each fix.
Which fix to reach for once a project turns red
Each red signal points to its own first fix, so the example project needs three separate actions in a set order. Work through them cheapest first, because stopping new loss comes before reforecasting.
Unpriced scope is red: Raise a change order for the extras before more hours go in, and pause them until the client signs.
Rate mix is red: Move junior-rate tasks back to junior-rate people, and make sure the freed senior hours go to billable work.
Burn gap is red but the bottom-up forecast holds: Check percent complete deliverable by deliverable, since an optimistic progress number hides overruns.
Forecast margin stays red: Reset the forecast with the delivery lead, update invoice planning and book a write-off provision before close.
In the worked example, the change order covers the $6,300 of extras, but the 11.25-point gap that remains is an estimate problem. That leftover is what the forecast reset has to absorb. It's also a pricing lesson for the next comparable quote.
If pulling these numbers together eats half a day, I'd fix that before tuning a single threshold. Slow reporting means you're also blind between reviews.
For the client conversation, our guide to managing scope creep covers how to raise extras before they pile up. After close, a project profitability variance analysis shows which cause cost the most, and financial project reports set out the metrics worth keeping.
Where the screen gives false alarms
The fix rules assume each signal is accurate, but the screen misfires in four predictable cases you can learn to spot. Front-loaded projects burn early by design, since setup and design phases spend heavily before much gets accepted. Compare their burn against a phased budget for each stage instead of a straight line.
Short projects rarely justify a weekly screen, so check them at each milestone instead. Retainers reset each period, so screen them against that period's budget and carry any overspend forward on purpose.
Stale time data breaks every signal at once. Data readiness tracks with margin in SPI Research's 2026 Impact of AI on Professional Services report. In SPI's survey, firms with highly ready data report project margins of 43.6%, versus 35.2% for firms whose data is not ready or fragmented.
For your screen, the lesson is practical. If timesheets arrive a week late, every signal describes last week's project, so fix logging discipline before you tune any threshold.
How Teamwork.com runs the margin risk screen with you
Teamwork.com is the agentic PSA (professional services automation platform) that runs this screen from the time, costs and rates your team already logs. Budgets, delivery and margin sit in one place, so burn gap, forecast margin and rate mix update as work happens. Your finance system keeps invoicing and the ledger, and your CRM keeps the pipeline.
Catch burn before it outruns delivery: an overspend usually surfaces once the budget is gone, too late to reprice. Budgeting & Profitability tracks fixed-fee, time-and-materials and retainer budgets against logged time and expenses, costed at the team rates you set. Add a notification at a spend threshold you choose and a profit margin target per project, and the amber warning reaches you between reviews.
)
See every project's margin in one weekly view: the screen falls apart when someone builds it by hand before each meeting. The Project Health Report and Profitability Report track budget burn against plan, plus revenue, cost and margin by project. They also flag unbilled time or over-servicing, which feeds the unpriced-scope signal, so your 30-minute agenda starts from a ready-made list.
)
OIC Advisors moved budget reporting, portfolio dashboards and time tracking into Teamwork.com, replacing a set of disconnected tools. The firm gained 360° visibility across all active projects and spends 100% less time manually generating reports.
)
Fix the rate mix before it's baked in: drift starts when whoever is free picks up the next request, whatever their cost. The Workload Planner shows who's booked on each project against capacity, so you see which senior people carry junior-rate tasks. The AI Utilization Summary flags who's overloaded and who has room for your review, so you restaff the week the signal turns amber.
)
Spend against progress, checked every week, is the whole screen, and Teamwork.com keeps both numbers next to the work that moves them.
)
)
)
)
)
)
)