Guaranteed maximum price: review the estimate basis before agreeing to the ceiling
A guaranteed maximum price needs a reviewable scope and cost basis. A GC checklist for reconciling documents, trade coverage, allowances and unresolved design.
Author
Ido Gedanken, CEOPublished

Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.
Book a demo- Type
- Guide
- Read
- 5 min
- Published
On this page
- Define the commercial structure before comparing totals
- Freeze a document and assumption baseline for the review
- Review the selected carry against the package that must be delivered
- Keep allowances and contingency from absorbing undefined scope silently
- Reconcile schedule assumptions with the cost basis
- Give the approval team a short list of consequential decisions
- Review the GMP against the same project understanding used for scope
A guaranteed maximum price, or GMP, generally sets a ceiling on reimbursable construction cost plus the contractor's fee, subject to the agreement's adjustment provisions. It is different from simply naming a lump-sum price. The executed contract governs allowable costs, changes, contingency, savings and the parties' responsibilities.
For a chief estimator or VP of preconstruction, the approval question is more specific than whether the total fits the budget: can the team explain the work and assumptions behind the proposed ceiling? A GMP assembled while design is developing needs a visible basis for what is included, what is qualified and what still needs a decision.
Define the commercial structure before comparing totals
AIA's explanation of GMP contracts describes a cost-plus structure with a maximum price and contract-specific adjustments. Review the actual agreement rather than importing rules about savings or overrun responsibility from a different project.
Identify the treatment of cost of the work, fee, general conditions, allowances and contingency. Confirm which qualifications belong in the proposal and how they are incorporated. Two totals are not comparable when the same obligation sits inside one contractor's number and outside another's stated basis.
The delivery-method comparison provides context for how the review changes across contracting arrangements. The useful distinction here is the pricing commitment, not a claim that every CM-at-risk project uses identical terms.
Freeze a document and assumption baseline for the review
Record the drawings, specifications, narratives, exhibits, addenda and other issued information used to prepare the estimate. Identify referenced documents that are missing. Name the design decisions that remain open and the assumptions used to carry them.
Do not make “design development” a single blanket qualification. A reviewer needs to know which package depends on which unresolved decision. The incomplete-drawing estimating guide explains why design intent and a complete trade scope are different things.
An illustrative mechanical package might have a defined performance requirement but an unresolved equipment selection. The estimate should distinguish what was carried for the equipment, which related work was assumed, and who must confirm the selection. Those are separate questions even when they appear on one worksheet line.
Review the selected carry against the package that must be delivered
For each material trade package, connect the intended scope to the quotation or other basis supporting the carry. Check inclusions, exclusions, qualifications, revision acknowledgments and work-window assumptions. Keep shared obligations visible across packages.
A low quote does not close a coverage gap. An acknowledged drawing revision does not prove that its consequence is priced. Use a named treatment for an unresolved item, with an owner and a decision date, rather than silently moving it into a reserve.
The carry-number guide separates a selected estimate basis from a convenient placeholder. That distinction matters when the team is committing to a ceiling rather than preparing another internal budget iteration.
Keep allowances and contingency from absorbing undefined scope silently
Use the definitions and controls in the agreement. An allowance is not automatically interchangeable with contingency, and neither label tells a reviewer whether the package is complete.
A practical approval register can make those differences visible.
| Estimate item | Basis the reviewer should see | Open decision to preserve |
|---|---|---|
| Defined trade carry | Current package scope and pricing support | Remaining exclusions or qualifications |
| Allowance | Described item and the amount or quantity basis used | Selection or reconciliation still required |
| Contingency | Stated purpose and governing contract treatment | Authority and conditions for its use |
| General conditions | Staffing and duration assumptions | Consequences of unresolved sequence or access |
| Design assumption | Specific requirement and the treatment carried | Who confirms it and when |
This is an illustrative review structure. It does not assign contractual rights or prescribe a universal contingency percentage.
Reconcile schedule assumptions with the cost basis
Review the duration and work calendar supporting supervision, temporary facilities, logistics and other time-related costs. Identify the milestones, occupancy restrictions and procurement assumptions that materially affect those amounts.
Do not approve a general-conditions duration using one sequence while the trade proposals assume another. If the sequence changes, reopen the affected package and estimate treatment. A schedule assumption should have a traceable consequence, not just a footnote.
After the baseline is accepted, keep a later instruction separate from the treatment agreed for its cost and time. The change-directive and change-order comparison explains that distinction within the governing contract process.
Give the approval team a short list of consequential decisions
Before agreement, summarize what has been reconciled, what remains qualified and which unresolved items require a decision. Preserve the basis accepted at approval so later design or scope changes can be compared against it.
The final bid review playbook helps structure that approval. The point is not to eliminate uncertainty from a developing project. It is to make the commitment and its basis understandable to the people accepting it.
Review the GMP against the same project understanding used for scope
Piper's Final Bid Review checks the estimate against project documents, trade scopes and subcontractor proposals, with findings linked to their sources. The review builds on the project understanding used in earlier scope work rather than treating the number as an isolated file.
That can support a team preparing a GMP proposal. The team still establishes the commercial terms, approves allowances and risk treatment, resolves findings and decides whether to commit. Piper does not set the contractual ceiling or guarantee a project's final cost.
For a municipal fleet facility, the Highway School operating brief shows which owner decisions should be recorded before a garage concept becomes a dependable estimate basis.
For an owner discussion before the GMP review, bring the unresolved choices rather than only the total. The Bisnow New York construction conference question plan records the design gap, owner decision, temporary estimate basis and trigger for another review.
An existing-building conversion adds an evidence question to that baseline: which conditions have actually been verified? The Bisnow conversion due-diligence guide maps investigations, authorization and design review to the assumption that must be reopened when new evidence arrives.
A public Central Elementary alternate-budget comparison illustrates another decision to preserve beside the number: whether an option is considered alone or reached through a cumulative acceptance sequence. The scenario remains conditional until the approved order and issued terms establish the commitment.
Where this fits in Piper
Final Bid Review
Review the estimate against the project behind it and focus senior attention on what still deserves judgment.
Related reading
Hard-bid vs CMAR vs design-build: estimating workflows for GC estimators
Compare how estimating unfolds under hard-bid (DBB), CMAR/GMP, and design-build (solicitation, scope, leveling, carry, and closeout) with checkpoints and checklists for each method.

Design intent is what estimators price when the drawings stop talking
Review implied assemblies and ambiguous interfaces, document the source and decision owner, and keep assumptions visible even when the drawing set appears complete.

How to set a carry number you can defend
The method for getting from a submitted subcontractor bid to the number that actually goes in the estimate, including evaluated cost, expected-value risk pricing, and the duplicate-contingency trap.

Final bid review: a QA/QC playbook for general contractors
The pre-submission gate between a working estimate and a price you are prepared to submit, explain, contract around, and build. Workflow, checklists, review lanes, delivery-method playbooks, and the KPIs worth tracking.

Piper removes manual review from the critical path and brings project data, company knowledge, and expert checks into every preconstruction decision and workflow
See Piper on your project
Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.