Map estimate detail to value lines

Start from the approved estimate version and controlling contract scope. Create a mapping from estimate codes to each proposed value line.

Preserve labor, material, equipment, subcontract, allowances, alternates, and indirect costs according to contractor policy and contract requirements. Use the estimate handoff checklist to transfer the basis, approvals, and open exceptions with the numbers.

Reconcile without hiding scope

Confirm that mapped values sum to the approved contract basis and explain every adjustment. Watch for duplicated general conditions, omitted buyout gaps, taxes, bonds, contingency, retained alternates, and costs spread across several lines. Do not force an unexplained plug merely to match the total.

AACE guidance on the basis of estimate emphasizes documenting scope, assumptions, exclusions, and pricing basis. Keep that context available when estimate codes are rolled into broader value lines.

Review billing and risk interfaces

Ask the authorized project and commercial reviewers to check contract line requirements, stored materials, mobilization, retainage treatment, and owner formatting. The estimator supplies traceability, not legal interpretation or billing approval.

Carry unresolved allowances and scope boundaries into the weather risk estimate. Retain the approved mapping, revision history, and reconciliation with the handoff package.

Value mapping controls
ControlRequired evidence
SourceApproved estimate revision
MappingEstimate codes to value lines
ReconciliationAdjustments and total match
ExceptionsAllowances, risk, pending decisions

Frequently asked questions

Should the schedule of values be built from a working estimate?

No. Use the approved controlling estimate version.

Can a balancing plug be used?

Only with transparent explanation and authorized approval.

What context should follow rolled-up values?

Preserve scope, assumptions, exclusions, risk notes, and mapping evidence.

Estimate ManagementConstruction EstimatingCost Support