Is this fixed-fee project going over? A mid-project check
A fixed-fee project is going over when the share of hours used runs ahead of the share of work done. Weight milestones at kickoff, compare the two at the midpoint, then project the final contribution two ways.
You are halfway through a fixed-fee website. The hours feel high, but the fee is set and the client has seen nothing wrong. Will the project still leave what you quoted when it ends?
This guide gives you a check to run at the midpoint. It sets the share of hours used against the share of work done, then projects the final contribution two ways. A fictional studio works through every step.
Hours used mean little without work done
Say 70% of the budgeted hours are gone. That is a warning if 40% of the work is done. It is fine if 80% is done. So you need two numbers:
Percent spent = hours used ÷ budgeted hours
Percent done = hours earned ÷ budgeted hours
Hours used come from your time log. Hours earned are the budgeted hours of the work that is finished. The next section shows how to count them.
The U.S. Government Accountability Office (GAO) makes the same comparison in its cost guide for government programs. It says a program is overrunning its budget when the share spent runs well ahead of the share complete. The method is called earned value management. This guide scales it down to one project at a small agency.
A retainer resets each month, so retainer burn compares hours used with the share of the month that has passed. A fixed-fee project never resets. The measure is the work finished, not the days gone.
Agree milestone weights before you start
"Percent done" is where this check goes wrong. Set by feel, it is a guess. Set it by rule, before the work starts:
- Split the project into 6 to 10 milestones. Each ends in something you can check: a client approval, a page on staging, a set of content loaded.
- Weight each milestone by its budgeted hours divided by the project's budgeted hours. A 48-hour milestone in a 240-hour project is 20%.
- Write the done test for each one. A milestone counts when its test passes, and not before. There is no partial credit.
GAO's guide calls this the weighted milestone method. It says the measure of done should be set before work starts and be objective. It adds that the method works best when at least one milestone closes in each reporting period. If you check every two weeks, size the milestones so one closes in each.
Three more rules keep the check honest:
- Weight by hours, not by invoices. A 50% deposit is not 50% done.
- Spread project management across the milestones. GAO calls credit that follows the calendar "level of effort". It is subjective, and GAO says to use it sparingly. Build meetings and management hours into each milestone's budget.
- Run the check the day a milestone closes. Hours on unfinished work earn nothing yet. A check taken mid-milestone reads worse than the project is.
How to run the check
Step 1: Add up the hours used
Total every delivery hour logged to the project so far, including your own. Use hours, not dollars, so one cost rate covers the project. Keep outside costs apart: stock images, licenses and any contractor who invoices you. Add what you have paid and what is still due.
Step 2: Add up the hours earned
Add the budgeted hours of every finished milestone. Divide by the budgeted hours to get percent done.
Step 3: Read the cost performance
Cost performance = hours earned ÷ hours used
At 1.00, finished work took exactly its budget. Below 1.00, it took more. GAO calls this the cost performance index. At 0.80, each budgeted hour took 1.25 hours.
Step 4: Project the final hours two ways
At the pace so far = hours used ÷ percent done
At the original estimate = hours used + budgeted hours × (1 − percent done)
The first case assumes the rest of the project runs like the first part. The second assumes the rest runs exactly to plan, even though the first part did not. Call it the hopeful case. GAO's guide says it is best practice to work out more than one estimate and to look at the range.
Both are one formula, the generic one in GAO's guide: final hours = hours used + hours left ÷ efficiency. Hours left are the budgeted hours less the hours earned. Efficiency is the cost performance in the first case and 1.00 in the second.
Then price the hours:
Final contribution = fee − outside costs − final hours × internal hourly cost
Final margin = final contribution ÷ fee
Your internal hourly cost is what an hour of delivery costs you, not what you charge. How to set an internal hourly cost rate shows how to find it. Contribution here is before overhead. Client profitability: contribution before overhead explains it with a worked month.
Step 5: Test the hopeful case
How much better than so far would the rest have to run to land on the original estimate?
Efficiency needed = hours left ÷ (projected final hours − hours used)
GAO gives a rule of thumb. An estimate that needs efficiency more than 5 percentage points above the record so far is too optimistic.
A worked example (fictional)
Fictional example. Fernhollow Studio is not a real business. The figures are illustrative and are not a customer result.
Fernhollow is a four-person design and web studio. It quoted a fixed fee of US$24,000 for a ten-week website for a dental group. The quote budgets 240 hours. Fernhollow's internal hourly cost is US$55, and the job has no outside costs. The plan:
- Delivery cost: 240 × US$55 = US$13,200.
- Contribution: US$24,000 − US$13,200 = US$10,800.
- Margin: US$10,800 ÷ US$24,000 = 45.0%.
At kickoff, Fernhollow split the job into eight milestones and weighted them by hours. The check below ran the day milestone 4 closed, after five weeks, so no hours sit on unfinished work.
| Milestone | Weight | Budget hours | Status | Hours used | Over |
|---|---|---|---|---|---|
| 1. Kickoff and content audit | 5% | 12 | Done | 16 | +4 |
| 2. Sitemap and wireframes approved | 10% | 24 | Done | 36 | +12 |
| 3. Home and template designs approved | 20% | 48 | Done | 66 | +18 |
| 4. Page templates built | 10% | 24 | Done | 50 | +26 |
| 5. CMS and forms built | 15% | 36 | Open | 0 | — |
| 6. Content loaded and checked | 20% | 48 | Open | 0 | — |
| 7. Testing and fixes | 10% | 24 | Open | 0 | — |
| 8. Go-live and handover | 10% | 24 | Open | 0 | — |
| Finished (1 to 4) | 45% | 108 | — | 168 | +60 |
| Whole project | 100% | 240 | — | — | — |
The check:
- Percent spent: 168 ÷ 240 = 70.0%.
- Hours earned: 12 + 24 + 48 + 24 = 108.
- Percent done: 108 ÷ 240 = 45.0%. That is also 5% + 10% + 20% + 10%.
- The gap is 70.0% − 45.0% = 25.0 points.
- Cost performance: 108 ÷ 168 = 0.64.
Finished work took 168 ÷ 108 = 1.56 hours for each budgeted hour.
The two projections:
- At the pace so far: 168 ÷ 0.45 = 373.33 hours. Cost: 373.33 × US$55 = US$20,533. Contribution: US$24,000 − US$20,533 = US$3,467.
- At the original estimate: 168 + 240 × (1 − 0.45) = 168 + 132 = 300 hours. Cost: 300 × US$55 = US$16,500. Contribution: US$24,000 − US$16,500 = US$7,500.
| Case | Final hours | Delivery cost | Contribution | Margin | Per hour |
|---|---|---|---|---|---|
| Plan | 240 | US$13,200 | US$10,800 | 45.0% | US$45.00 |
| At the original estimate | 300 | US$16,500 | US$7,500 | 31.3% | US$25.00 |
| At the pace so far | 373.33 | US$20,533 | US$3,467 | 14.4% | US$9.29 |
Each margin is the contribution ÷ US$24,000. Each per-hour figure is the contribution ÷ the final hours, for example US$3,467 ÷ 373.33 = US$9.29.
Now test the hopeful case. Hours left in the plan are 240 − 108 = 132. To land on 300 hours, the rest has to run at 132 ÷ (300 − 168) = 1.00. Fernhollow's record is 0.64. That is 36 points better than the first half, which fails GAO's 5-point rule of thumb. To finish on the budgeted 240 hours, the rest would need 132 ÷ (240 − 168) = 1.83.
Where did the 60 extra hours go?
- Templates, +26. The client added an events page type after design approval. It is not in the scope lines, and 14 of the 26 hours went on it.
- Design, +18. The estimate assumed four page layouts. The approved designs have six.
- Wireframes and kickoff, +16. Review loops ran long.
Reading the result
Fernhollow's contribution would end between US$3,467 and US$7,500, against US$10,800 planned. Even the hopeful case gives up US$3,300 (US$10,800 − US$7,500).
Which case to plan on. Plan on the pace case. GAO's guide says research has shown that once a program is 20 percent complete, its cumulative cost performance varies by less than 10 percent. It most often gets worse as completion nears. Change that only if you can name why the rest should run faster, such as repeat work. GAO's programs are far larger than a website, so treat this as a reason to check early, not as a law.
Set your floor before you look. Your floor is the margin you need to cover overhead, or zero. Fernhollow's floor is 30%.
| The two cases | What to do |
|---|---|
| Both above your floor | Carry on. Check again when the next milestone closes. |
| Only the original-estimate case is above your floor | Act now, while open milestones can still change. |
| Both below | Act now, and tell the client. |
Fernhollow's original-estimate case is 31.3% and its pace case is 14.4%. It acts now.
The two cases meet as the project ends. Suppose milestone 5 closes on its budgeted 36 hours. Hours used reach 168 + 36 = 204 and percent done reaches 45% + 15% = 60%. The original-estimate case stays at 300 hours. The pace case falls to 204 ÷ 0.60 = 340 hours, a cost of US$18,700 and a contribution of US$5,300 (22.1%). A milestone on budget narrows the range. It does not repair the first half. So run the check at every milestone.
What to do at the checkpoint
You have four moves. Fernhollow's pace case stands at US$3,467.
Raise a change request. The 14 hours on the events page type are outside the scope lines. At the quote's own rate, US$24,000 ÷ 240 = US$100 an hour, they are worth US$1,400. What scope creep and overservicing cost, per client shows how to tag that time as you log it. If the client approves it, the change goes into the baseline. Add it in three places:
- Budgeted hours: 240 + 14 = 254.
- Fee: US$24,000 + US$1,400 = US$25,400.
- Hours earned: 108 + 14 = 122, because the work is finished.
Percent done is 122 ÷ 254 = 48.0%. The pace case becomes 168 × 254 ÷ 122 = 349.77 hours. Cost: 349.77 × US$55 = US$19,237. Contribution: US$25,400 − US$19,237 = US$6,163, a margin of 24.3%.
Rescope. Agree with the client to drop 24 budgeted hours of open work, for the same fee. Budgeted hours become 216 and percent done becomes 108 ÷ 216 = 50.0%. The pace case becomes 168 ÷ 0.50 = 336 hours. Cost: 336 × US$55 = US$18,480. Contribution: US$24,000 − US$18,480 = US$5,520, a margin of 23.0%.
Restaff. Moving open milestones to someone with a lower internal hourly cost lowers the cost of each hour, not the number of hours. Count only hours that person would really do, and allow for the handover.
Absorb it, knowingly. Write the figure down. Fernhollow's pace case ends at US$3,467 (14.4%), which is US$10,800 − US$3,467 = US$7,333 below plan. Some clients are worth keeping at a low margin. Decide at this checkpoint, with the number, and not when the last invoice goes out.
Close the loop for the next quote
Record the hours used for each milestone beside the hours you budgeted. Fernhollow's four finished milestones took 168 hours against 108 budgeted. Design took 66 hours, not 48. Templates took 50, not 24. Use those figures in the next quote. How to price a project so it still pays after delivery shows how to build scope lines and compare a finished project with its quote.
What this method doesn't do
- It is only as honest as the done tests. A milestone called done too early flatters the result.
- It uses one internal hourly cost. If the rest of the work falls to your most expensive people, the real cost is higher than the projection.
- It projects in a straight line. Real projects change pace, and GAO's research covers government programs, not studio projects.
- It projects hours, not outside costs. Add what you have paid and what is still due.
- It does not show cash. When the client pays is a separate question.
- What you can bill for a change depends on your contract. Ask a lawyer before you rely on a change clause.
- It is management arithmetic, not your accounts. How a fixed-fee project is recorded in your books, and any tax question, are for your accountant.
Where the tracker fits
The Client Profitability Tracker records fees, credits, delivery hours and delivery costs for each client project by month. It calculates contribution before overhead, margin and contribution per delivery hour. For this check, add up a project's rows to get its hours so far. It holds no budget, milestone weights or projection, so you work those out by hand with the formulas above.
The Project Quote Calculator prices a project from hours, rates and direct costs. It holds each scope line's hours by role and has ready-made rows to paste into the tracker. The budget you check against is then the one you quoted. It does not track hours while a project runs.
Entry is manual in both, both are tested in Excel 365 for Windows desktop, and the tracker stops before overhead. The formulas above work in any spreadsheet.
Independence
Metricvalley is independent. This guide isn't affiliated with, or endorsed by, the U.S. Government Accountability Office. Nothing in this guide is financial, tax or legal advice.
Sources and method
Every figure in the worked example is fictional (Fernhollow Studio). The method is the earned value comparison in the GAO guide below, scaled down from government programs to one fixed-fee project. It uses weighted milestones set before work starts (chapter 18, Table 21, p. 231), time-based credit called level of effort (p. 232), the share spent against the share complete (chapter 19, p. 259), the cost performance index (Table 23, p. 257), the 5-point test for an optimistic estimate (p. 258), more than one estimate at completion (p. 265) and the 20 percent point (pp. 266 to 267).
In GAO's terms, hours used are the actual cost of work performed. Hours earned are the budgeted cost of work performed, or earned value. Budgeted hours are the budget at completion, and final hours are the estimate at completion. Page numbers are those printed in the full-report PDF. The guide is written for government programs, so its 20 percent point and 5-point test are borrowed here as rules of thumb. They have not been tested on agency projects.
- U.S. Government Accountability Office, Cost Estimating and Assessment Guide: Best Practices for Developing and Managing Program Costs (GAO-20-195G) (published Mar 12, 2020; chapters 18 and 19 read in the full-report PDF), read Nov 3, 2026.
Common questions
How do you work out percent complete on a fixed-fee project?
Before work starts, split the project into milestones. Weight each by its budgeted hours divided by the project's budgeted hours. A milestone counts only when it passes a test you wrote down, with no partial credit. Percent complete is the weights of the finished milestones added up. Don't use the invoice schedule, because a deposit isn't progress.
How early can you trust a mid-project projection?
From about 20 percent done, with care. GAO's cost guide says research has shown that once a program is 20 percent complete, its cumulative cost performance varies by less than 10 percent and most often gets worse. A small project is different, so re-run the check each time a milestone closes and plan on the pace figure.
What does a cost performance below 1.00 tell you?
It tells you finished work took more hours than the plan allowed. At 0.80, each budgeted hour took 1.25 hours. It doesn't say whether the fee still covers the cost. Project the final contribution both ways, then compare it with the floor you need.
How we research, check and update these guides. Found an error? Email [email protected] and we’ll correct it and note the change here.