Quick overview: construction estimate assumptions log
An assumptions log is a controlled list of judgments used to complete an estimate when drawings, specifications, schedules, procurement decisions, or site information leave a gap. Each entry should be specific enough for another person to test. The log is useful only when it identifies the affected estimate area and the action needed to confirm or replace the assumption.
Keep the log with the estimate package and update it during review. The estimate may still need a concise note beside an affected cost line, but the central log gives the team one place to sort open, confirmed, rejected, and superseded items. The log also supports a clear construction basis of estimate.
The basis explains the estimate as a whole. The assumptions log gives reviewers a working record of the unresolved conditions inside that basis.
Separate ground rules from assumptions
A ground rule is confirmed direction or a baseline condition accepted for the estimate. An assumption is a judgment used where that direction is missing. Mixing the two makes review harder because the reader cannot tell which condition came from the project team and which one still needs confirmation.
The AACE basis of estimate practice lists ground rules and assumptions among the information commonly included in a basis of estimate. It distinguishes project ground rules from assumptions made by the estimator, which gives reviewers a useful way to separate direction from unresolved judgment. Write a ground rule with its source, such as an approved milestone or issued design criterion.
Write an assumption with its rationale and review path. If the project team later confirms the assumed condition, update its status and point to the confirming source rather than silently deleting the history.
What every assumptions log entry should contain
Give every item a stable identifier. Record the assumption in a complete sentence, then name the scope area, estimate line, or work package it affects. Add the reason it was necessary and the project information reviewed before the judgment was made.
Assign an owner who can obtain or approve the missing information. The owner is not automatically the estimator. A design question may belong to the architect or engineer, a logistics condition may belong to operations, and a procurement decision may belong to the project manager.
The estimator should track the effect without claiming authority over another discipline's decision. Include the date opened, target review date, current status, resolution, and the estimate revision that reflects the resolution.
Describe cost impact qualitatively unless the estimate contains a traceable calculation. Labels such as low, medium, or high need a documented meaning if the team uses them.
Assumptions log review checklist
Reviewers need more than a list of vague caveats. The table below provides a practical check for each entry. A useful record connects the missing information to the estimate, assigns a next action, and preserves the result.
Read the log beside the drawings, scope notes, quote comparisons, and estimate summary. If an assumption affects several trades, identify each affected area rather than placing the entire consequence under a general project note.
| Log field | What to record | Review question |
|---|---|---|
| Identifier and statement | Stable ID and one testable condition | Can another reviewer understand the judgment? |
| Reason and source | Information gap and documents reviewed | Why was the assumption necessary? |
| Affected area | Scope, work package, quantity, rate, or allowance | Where does the estimate use it? |
| Potential effect | Traceable calculation or defined qualitative effect | What changes if it is wrong? |
| Owner and date | Person responsible and target review date | Who can resolve it and when? |
| Status and resolution | Open, confirmed, rejected, or superseded | What evidence supports the current status? |
| Revision reference | Estimate version that reflects the decision | Was the result carried into the estimate? |
How to manage assumptions through estimate revisions
Start the log during the first scope review. Add an entry when the estimator must choose a temporary condition to keep working. Do not wait until the estimate is ready for approval, because late documentation loses the discussion and source context behind the decision.
At each estimate review, sort open entries by affected scope and urgency. Confirm whether new drawings, addenda, owner direction, vendor information, or schedule decisions resolve them. When an assumption changes, revise the affected quantities, rates, allowances, or notes and identify the estimate version where the change appears.
Close an item only when the confirming information is recorded and the estimate reflects it. If the team decides to retain the condition as direction, mark that decision and its approver. If the assumption is rejected, record the replacement and the affected estimate areas.
A short audit trail prevents the same question from returning during the next review. A remote project cost analyst can maintain identifiers, source references, review dates, status changes, and revision evidence. Scope judgment, commercial strategy, risk ownership, and final estimate approval should remain with the responsible project leaders.
Set a review cadence that matches the estimate
The review rhythm should follow information releases and estimate milestones. A live bid may need checks whenever an addendum or major quote arrives. An early budget may use scheduled design reviews.
The point is to review assumptions when the underlying information can change, not to update a register on an arbitrary calendar. Bring the most consequential open items into the estimate review agenda. Ask whether the assumption remains reasonable, whether its effect is represented, and whether someone can resolve it before issue.
Escalate assumptions that could change the scope boundary, procurement plan, schedule basis, or a major cost area. Keep closed and superseded entries in the record.
Filtering them out of the active view is fine, but deleting them removes useful revision history. The next estimator or reviewer should be able to see why the earlier estimate used a different condition.
A practical assumptions review tip
Pro tip: test each open entry with two questions. What part of the estimate changes if this assumption is wrong, and who can provide the answer?
If the entry cannot answer both, rewrite it before the review. This exposes harmless background notes and important unresolved decisions that were written too vaguely.
Common assumptions log mistakes
Do not use broad statements such as 'normal conditions assumed.' Name the working hours, access condition, scope boundary, material choice, design state, or schedule condition that the estimate actually uses. Do not hide missing scope inside an assumption. If the documents conflict or omit a required decision, record the question, temporary treatment, owner, and resolution date.
The assumption lets work continue, but it does not settle responsibility. Do not close an entry because someone discussed it in a meeting. Point to the revised document, written direction, approved decision, or estimate revision that resolves it.
A status without evidence will not help a later reviewer. Do not let the log become a second risk register. An assumption states a condition accepted for estimating.
A risk record evaluates uncertain events and responses. The two can refer to each other when an assumption creates material uncertainty, but they serve different review tasks.
Key takeaway
A construction estimate assumptions log should make unresolved judgment visible and actionable. Record the condition, rationale, affected estimate area, source, owner, dates, status, and resolution. Review the log when project information changes, update the estimate when an assumption changes, and preserve closed entries so later reviewers can follow the decision history.
