An estimate review should test whether the scope, delivery plan and price tell the same story. Before a fixed-fee commitment, check completeness, role effort, capacity, rate basis, cost rules, uncertainty and approval. The 15 questions below turn the review into specific decisions rather than a quick glance at the margin percentage.
Terms used in this guide. fee: the amount charged to the client; cost: the expense included in the stated project model; margin: revenue left after the included costs; margin percentage = that amount / revenue × 100; baseline: the approved original plan kept for comparison.
In plain words
An estimate review is a short, structured check before you send a fixed price. A second person asks the same questions about scope, hours, rates, risks and margin every time. It does not guarantee the estimate is right, but it catches the mistakes that are easy to see from outside.
Who this helps: Presales consultants, project managers and finance staff who approve prices.
Questions this guide answers:
- What should you check in a project estimate?
- What is an estimate review checklist?
- How do you review a fixed-price estimate before sending it?
How does a missed cost change the margin?
Included cost = labor + nonlabor costs + applicable cost rules
Margin % = (approved fee − included cost) / approved fee × 100
Check the selected margin layer, final fee and rule bases. A labor-only figure does not establish an after-cost target.
Scope and estimating basis: questions 1–5
- 1. Which exact deliverables and scope version does the estimate cover?
- 2. Are acceptance criteria clear enough to estimate completion?
- 3. Which method and evidence support the effort: comparable actuals, work packages or another basis?
- 4. Are testing, coordination, release and handover included without overlap?
- 5. Are assumptions, exclusions and client responsibilities consistent with promised outcomes?
Ask the reviewer to trace one deliverable end to end, as in the scenario below. If key acceptance criteria are unavailable, record the open decision rather than calling the review complete.
Use the first five questions to establish the boundary of the decision. The reviewer needs the scope version, intended outcome, estimating method and acceptance evidence before examining the arithmetic. A correct spreadsheet can still price the wrong deliverable.
Ask for a trace rather than a yes-or-no assurance. Choose one user journey and identify its analysis, implementation, error handling, acceptance and handover work. Where a task is excluded, confirm that the exclusion is consistent with the promised outcome. This reveals omissions that a total-hours review can miss.
For an early estimate, state which evidence is provisional. For a fixed-fee commitment, decide whether unresolved high-impact assumptions can be accepted, need discovery or require a different scope. The checklist should support that decision rather than merely record that a question was asked.
Resources and costs: questions 6–10
- 6. Do role-hour totals reconcile to the work-package rollup?
- 7. Can the proposed roles be available in the required weeks or stages?
- 8. Are cost rates current, approved and appropriate to the role and location?
- 9. Are licenses, travel and other nonlabor costs included with correct units?
- 10. Are labor-based charges, revenue-based charges and overhead allocations distinct and counted once?
Resource availability is part of estimate credibility. A low-cost plan relying on an unavailable specialist is not an approved alternative until delivery can support it. Review the planning-rate version and cost boundary, especially when comparing scenarios created at different times.
Reconcile work-package totals to role totals and period allocations. A duplicated package can inflate cost; a missing QA role can understate it. Check the approved planning rates, working-hour assumptions and currency against the chosen resource profiles.
Confirm capacity separately from cost. A role's rate being present does not show that the firm can staff it in the required week. Identify scarce specialists and the point at which their availability must be confirmed. If substitutions are likely, include a relevant mix sensitivity.
Review licenses, travel and duration-based charges with units and coverage. A monthly license for three months is different from a one-time purchase. A per-person charge needs the applicable quantity. The rate-card guide explains the governed input basis.
Risk and commercial approval: questions 11–15
- 11. Which unresolved risks change effort, cost or the delivery date, and who owns them?
- 12. Is contingency based on the residual exposure after base-work and calibration adjustments?
- 13. Does the fee meet the approved margin definition after discounts, commissions and credits?
- 14. What happens if client dependencies change or scope is added?
- 15. Who approves the commitment, and which version becomes the delivery baseline?
Assign each unresolved answer an owner and a decision date. Reviewers should be able to approve, reject or approve with a specific condition. “Looks fine” is not a useful decision record if the plan depends on access that nobody has confirmed.
Ask which costs the target margin includes. A quote can satisfy labor-only margin and fail the after-cost target because of commission or overhead. Check fee concessions, free work and credits using the final proposed revenue, not the earlier reference quote.
Treat residual risk after correcting known omissions. A contingency percentage should not compensate for a missing release package or invalid rate. Record what the reserve covers and what has already been included in effort scenarios or calibration.
Give every unresolved condition an owner and decision point. A review outcome might be approved, declined, rework required or conditional on a named access test. A conditional decision needs clarity about whether the team may issue a firm offer or start work before the condition is satisfied.
Scenario: Yusuf traces one deliverable through the estimate
A good reviewer does not accept a yes-or-no assurance. Yusuf, a delivery lead, reviews a colleague's fixed-price estimate for a customer portal by tracing one user journey from end to end.
- He picks “customer uploads a document” and asks for its analysis, build, error handling, acceptance and handover work.
- He finds analysis, build and acceptance hours, but nothing for the failed-upload path or for scanning.
- He checks the exclusions list: scanning is not excluded, so the estimate silently promises it.
- He records two options: add the hours, or exclude scanning and say so. The author chooses the first, and the cost increases before the quote is sent.
A total-hours review would have passed this estimate. Tracing a deliverable catches the omission because it follows the work, not the arithmetic. Check the scope version, the estimating method and the acceptance evidence first, because a correct spreadsheet can still price the wrong deliverable. For an early estimate, state which evidence is provisional; for a fixed fee, decide whether unresolved high-impact assumptions are accepted, need discovery or need a different scope.
How does this checklist catch a pricing error?
Suppose a USD 60,000 fee is shown against USD 36,000 labor cost as 40% margin. The review finds USD 4,000 licenses and 5% revenue-based commission. With these included, margin is (60,000 − 36,000 − 4,000 − 3,000) / 60,000 = 28.33%. The displayed labor-only margin is a different measure, not evidence that the fee meets a 35% project target.
If a further USD 5,000 delivery credit is promised, recognized project fee under the example becomes USD 55,000. Recalculate the charges and margin on the actual commercial arrangement. Every concession should enter the same approval calculation instead of remaining in a separate sales note.
Reproduce the corrected calculation in four steps: fee USD 60,000; labor USD 36,000; license USD 4,000; commission 0.05 × 60,000 = USD 3,000. Contribution is USD 17,000, and margin 17,000 / 60,000 = 28.33%. This is below a 35% after-cost target even though the labor-only figure is 40%.
With a USD 5,000 credit, revenue becomes USD 55,000. Assuming commission is still 5% of that net fee, commission becomes USD 2,750 and contribution USD 12,250. Margin is approximately 22.27%. State the commission base explicitly, since a different compensation rule can change the result.
What should you keep after the estimate review?
A review that leaves no record cannot be learned from. Keep six things together.
| Keep this | Why |
|---|---|
| Approved scope and estimate version | So everyone prices and delivers the same thing |
| Assumptions register | So a failed assumption can be traced to its owner |
| Cost-policy version | So the margin can be reproduced later |
| Chosen scenario and rejected options | So the decision can be explained |
| Decision record with conditions | So conditions on approval are not forgotten |
| Evidence required before work starts | So starting is a decision, not an accident |
Use it again later
- At handover, the project manager reads it to understand what the firm accepted and why.
- When a condition changes, show the affected scope, effort or fee and follow the agreed approval path.
- After the project, compare the assumptions with what happened. That is how the next estimate gets better.
Real example: a delivery lead reviews a colleague’s estimate
An illustrative story with invented figures, to show how the idea works in a real office.
Yusuf, a delivery lead, reviews a USD 95,000 fixed-price estimate using the checklist. Question 6: do role hours add up to the work package hours? They do not: the roles total 640 hours, the packages 700.
He finds that 60 hours of testing were in the packages but not in any role. At USD 50 an hour that is USD 3,000 of cost missing from the estimate, so the real margin is about three points lower than the one on the page.
The estimator corrects it and adds the finding to the record. Without the checklist the error would have reached the client.
When do you review an estimate, and who should do it?
| Stage | Owner | Checkpoint |
|---|---|---|
| Draft complete | Author (presales consultant) | Self-check against the fifteen questions |
| Independent review | A delivery lead or peer who did not write it | One deliverable is traced end to end; resources, rates and availability are checked |
| Commercial review | Presales lead and finance | Margin layer, rule bases and the approval fee reconcile |
| Decision | Final approver | Open assumptions are accepted, investigated or removed; the review record is kept |
| After the project | Project manager | Findings from the review are compared with what actually went wrong |
Checklist, peer review or review board: which should you use?
Estimate quality can be assured in several ways.
| Approach | Use it when | Watch for |
|---|---|---|
| Structured checklist (this guide) | Any fixed-fee estimate | Box-ticking |
| Independent peer review | High-value or unusual work | Cost and delay |
| Calibration against history | You have comparable projects | Small samples |
| Formal estimate review board | Very large commitments | Slow |
Use the checklist for every fixed-fee estimate and add peer review for high value or unfamiliar scope. Add history-based checks as data accumulates.
Estimate review: frequently asked questions
Who should perform an estimate review?
Choose reviewers who can assess scope and delivery, governed costs and commercial exposure. For material uncertainty, independent input can reveal assumptions the estimator has overlooked. The accountable approver needs the relevant evidence rather than only a margin total.
Should every unanswered question block a ROM?
Match the standard to the decision. A planning estimate can retain clearly described unknowns. A firm commitment needs explicit treatment of material unresolved conditions and the appropriate approval. Minor open design details need not prevent every early affordability discussion.
Who should review an estimate?
Someone who did not build it, with delivery and finance perspective where the value justifies it.
What is an estimate review checklist?
A short list of questions an independent reviewer answers before an estimate is sent: scope and method, resources and costs, and risk and commercial approval. Fifteen questions in three groups is enough to catch most missing work, double-counted costs and unsupported assumptions.
How do you review an estimate in Managed Margin?
Open the proposed strategy with its scope assumptions and resource plan available to reviewers. Reproduce the checklist example's USD 36,000 labor, USD 4,000 license, USD 60,000 fee and 5% revenue commission. The after-cost margin should be 28.33% under that boundary, not the 40% labor-only figure.
Use the review to validate roles, working-hour assumptions, costs and difficult-case alternatives. Keep unresolved conditions and approvals in the decision record. Once authorized, finalize the selected strategy as the baseline and carry its scope version into handover. A calculation passing input validation is necessary evidence; it is not proof that scope or staffing is complete.
Explore the pricing and estimation workflow or review the delivery margin workflow.
Background reading: the sales-to-delivery handoff: preserving the pricing baseline and protecting margin on a fixed-price project.
Continue the sequence: guides to read next
- Assumptions and Exclusions in an Estimate: 40 IT Examples: the assumptions to review
- From ROM to Fixed Price: What Evidence You Need First: the move this review protects
- How to Calculate Project Margin (Formula + Example): checking the margin arithmetic
- How to Manage Fixed-Fee Project Margins in Consulting: why fixed-fee estimates need this review
- Resource-Based Estimating: How to Estimate Project Cost: estimating cost from roles, hours and rates
- How to Audit a Project Margin Spreadsheet: how to audit a project margin spreadsheet
- Project Estimation: Process, Methods and What to Consider: five estimation methods and how to choose between them
Sources and methodology
The worked figures are original educational illustrations. The linked references provide background for the estimating and management concepts; they do not establish the example rates or guarantee the outcomes. Product instructions describe the current implementation and are separate from methods the reader performs outside the application.
The examples, templates and calculations are original editorial illustrations, not market benchmarks or customer results. Monetary amounts are in USD, exclude tax unless stated, and use the cost boundaries defined in the article. Validate assumptions against your own delivery history before quoting.
Further background: US NPS: estimate quality review. The worked arithmetic and scenarios above are original; this reference provides context and is not a source for market rates or the stated example amounts.
The application walkthrough was checked against the current stage, pricing, cost-rule and delivery calculation code on 13 October 2026. Forecasts describe recorded actuals plus the remaining plan, not predicted customer outcomes.