CMAR early-release packages: reconcile the bought scope with the later GMP

Trace an early equipment purchase into the later GMP and identify installation interfaces still to buy without counting included scope twice.

Guide6 min read

Published

Tower crane above steel reinforcement

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
On this page
  1. A procurement commitment is one scope boundary
  2. Follow a fictional package from release to GMP
  3. Build the bought and not-bought reconciliation
  4. Separate scope gaps from contingency decisions
  5. Freeze the approved basis for the next handoff
  6. Compare proposals against the installed-scope baseline

For a CM at risk preparing a GMP after an early equipment release, the purchase order is the starting boundary, not proof that the complete installed system is bought. Reconcile the authorized purchase and its revisions against the later design, the installation proposals and the GMP estimate. Carry each required activity once, identify who is expected to perform it, and leave an explicit gap where coverage is unconfirmed.

The decision is whether the remaining buyout and GMP basis cover the installed scope on the current documents. A purchase order is not necessarily the project GMP, and early-release authority and treatment depend on the actual agreements. This review identifies scope and pricing questions; it does not determine liability or entitlement to contingency.

A procurement commitment is one scope boundary

An early release can secure equipment while design and other trade packages continue to develop. The useful record is not merely the equipment price. It is the authorization, the exact scope committed, the document and proposal revisions incorporated, qualifications, delivery terms and the subsequent changes that affect interfaces. A PO for equipment supply may leave unloading, rigging, controls connections or on-site startup to a separate party, depending on its terms.

The Construction Management Association of America's undated member communication on CM at-risk discusses how GMP assumptions, design development and unclear contingency terms can produce different expectations. It also identifies risk when a GMP is established before trade buyout or design completion. The communication is general industry guidance, not a determination of a particular contract's allocation. The reconciliation below is an estimating method, not a CMAA-prescribed register.

For the larger delivery-method context, see estimating workflows for hard bid, CMAR and design-build. For the complete proposal basis, use the GMP estimate review alongside this package-level check.

Follow a fictional package from release to GMP

Assume a fictional CMAR project releases air-handling equipment before the later GMP. The owner's written authorization permits a $400,000 purchase on a specified early design and supplier offer. The executed PO incorporates the offer and a revision that includes factory-mounted controls hardware, delivery to the site and one remote startup session. It excludes unloading, setting, field controls integration and on-site startup.

The later design revision identifies the installed equipment and its controls interfaces. The mechanical installation bid is $180,000 and includes unloading, rigging and setting, but excludes field controls integration and supplier on-site attendance. The controls proposal is $25,000 for field integration and participation in startup. The supplier offers an on-site startup visit for $8,000 if the project requires it. All excerpts, figures and scope boundaries in this example are fictional; they are a review fixture, not market pricing or a recommended technical scope.

The team confirms with the project requirements that one on-site supplier visit is required. Its illustrative package carry is $613,000: the committed $400,000 purchase, $180,000 installation, $25,000 controls and $8,000 visit. The remote session and factory-mounted hardware remain within the $400,000 PO. Adding a separate allowance for either would duplicate a supplier inclusion. If the supplier's offered on-site visit is instead accepted as a PO amendment, transfer the $8,000 into the revised commitment and remove the separate carry. Preserve the original baseline and the amendment so the transfer is visible.

The important interaction is between the later controls interface and the early PO qualification. The presence of factory-mounted hardware in the purchase does not by itself establish that field integration is bought. The $25,000 controls proposal may cover that interface, but only after the estimator checks its scope and current revision against the later design. If the proposal excludes a required connection, record and price that gap rather than assuming the equipment PO or mechanical bid covers it.

The same discipline applies to rigging. Here it is in the installation bid, so do not leave a second rigging allowance in the GMP. If the installation proposal is conditional on a crane being supplied by others, however, the estimator must compare that condition with the GC's actual crane carry. The number may need an adjustment or clarification, but the existence of a rigging line alone does not establish complete coverage.

Build the bought and not-bought reconciliation

Start with the installed-scope baseline on the documents selected for the GMP. Break it into activities at the interfaces where responsibility can change. For each activity, keep a row with:

  • Requirement and basis: description, drawing or specification reference, revision and any approved design assumption.
  • Early authorization: the authority to release the package, scope and amount authorized, and any stated conditions.
  • Commitment: executed PO and amendments, supplier offer revision, included amount and relevant qualification or exclusion.
  • Remaining buyout: installation or controls bidder, proposal revision, included or excluded work, and whether the price is a quote, allowance or commitment.
  • Decision and evidence: bought, proposed but not committed, gap or overlap; carry amount, owner, open clarification and source reference.

A row can be partly bought. In the example, the PO buys factory-mounted hardware and remote support; the controls proposal addresses a separate field interface. Keep those as distinct activities rather than marking the whole controls system bought. Conversely, if two documents both include the same clearly defined work, resolve the overlap and carry it once. Do not simply subtract a guessed duplicate without confirming each bidder's scope.

Tie each amount to the estimate line and its status. A supplier's executed PO, a subcontractor's unaccepted proposal and a GC allowance are not interchangeable commitments. A proposed amount can support a carry while still needing buyout. Avoid adding a generic percentage over a line that already includes the same cost.

Separate scope gaps from contingency decisions

A gap in the register answers a practical question: what required work is not yet covered by an identified commitment or accepted proposal? It does not answer whether the gap is design development, a change, an omission or a cost payable from a particular contingency. Those classifications depend on the agreements, authorized basis, later documents and project-specific facts.

Maintain a separate decision record for disputed treatment. Link it to the affected scope row, the estimate amount, relevant communications and the person responsible for resolution. Identify CM and owner contingency provisions separately in the actual contract. Until the authorized parties decide, show the cost and its unresolved treatment rather than burying it in contingency or asserting that either party must pay.

For example, if the later design calls for the $8,000 on-site visit but the early documents are unclear about it, carry the identified cost in the package scenario and flag the basis question. Do not label it automatically as a change order. If a later decision removes the requirement or reallocates the cost, update both the estimate and the register with the source for the decision.

Freeze the approved basis for the next handoff

Before GMP approval, issue a reconciliation snapshot showing document dates and revisions, signed authorization, current PO and amendments, proposal status, open qualifications and the estimate lines that carry each amount. The chief estimator and project team should resolve material gaps or explicitly present assumptions for decision. A snapshot is a record of the proposed basis, not evidence that an unexecuted buyout has been awarded.

After approval, hand the register to buyout and project management with a named owner for each open item. When an installation subcontract is executed, replace the proposal status with the commitment and reconcile its value against the carry. If the PO changes, record the amendment and check whether a separate allowance now duplicates it. Preserve the prior snapshot so the team can explain what moved between the GMP and buyout.

For related interface questions, see owner-furnished equipment bid leveling. Ownership and contract terms differ.

Compare proposals against the installed-scope baseline

Piper bid leveling compares subcontractor bids against project scope with source-linked findings. The estimator can review the later requirements alongside proposal coverage and qualifications, then decide the carry and clarifications. The project team remains responsible for approving the GMP basis, contract interpretation and buyout decisions.

ShareLinkedInX

Related reading

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.