Record each controlled issue

List the document number, title, revision, issue date, received date, source, and status. Include specifications, addenda, formal clarifications, bulletins, and approved sketches that affect estimating.

A folder modified date is not a reliable substitute for an issue record. Connect the register to the preconstruction document control process so the estimator and document controller use the same current-set decision.

Compare new issues against the estimate basis

When a document arrives, identify what it supersedes and which estimate areas may be affected. Assign the review by discipline or package. Do not mark the issue reviewed merely because it was downloaded or distributed.

AACE guidance on the basis of estimate supports recording the information that underlies an estimate. The document register supplies the exact project references for that record.

Document issue register fields
FieldReview use
IdentityNumber, title, revision, date
RelationshipSupersedes or supplements
ImpactAffected estimate package
StatusReviewer, action, and closure

Freeze the set used for release

At each estimate milestone, export or tag the controlling register and preserve exceptions. Identify late documents not incorporated, pending revisions, and information used only as an assumption. The approver should see these limits before accepting the estimate.

Reconcile changed documents through the drawing revision log. Keep review status, estimate action, owner, and closure evidence separate so unfinished cost work remains visible.

Frequently asked questions

Is a shared folder a document register?

No. The register records identity, revision relationships, review, and estimate action.

When is a new issue reviewed?

After its estimate effect is assessed, not when the file is downloaded.

What should be frozen at release?

Preserve the controlling issue list and every document exception.

Document ControlConstruction EstimatingCost Support