Write comments that can be answered

Identify the estimate revision, code or page, source document, observed issue, and decision needed. Separate a question from a required correction.

If the comment covers several estimate areas, split it so owners and closure evidence remain clear. Use the estimate peer review to define review scope, sampling method, and escalation before comments begin.

Record the response and estimate action

The owner should answer the comment, identify changed estimate lines or retained treatment, and attach the supporting source. A response such as "noted" is not closure. If the reviewer recommendation is rejected, record the reason and approving authority.

ASPE provides resources for professional estimators. The project review record still needs direct evidence from its own estimate and documents.

Review comment resolution fields
FieldClosure evidence
CommentLocation, issue, and decision
ResponseOwner explanation
Estimate actionChanged lines or retained treatment
VerificationReviewer, revision, and status

Verify closure against the current revision

A reviewer other than the response author should confirm material changes in the current estimate file. Reopen comments when a later revision reverses the fix or changes the underlying scope. Preserve superseded responses for history.

Summarize open and high-impact items in the estimate review meeting. Do not release the estimate until every required comment is closed or accepted as a named exception.

Frequently asked questions

Is "noted" a valid comment response?

No. State the estimate action or the approved reason for retaining the treatment.

Who should verify closure?

A reviewer other than the response author should check material changes.

Can open comments remain at release?

Only when a named authority accepts them as explicit exceptions.

Quality ReviewConstruction EstimatingCost Support