List the narrative claims
Read the scope narrative and copy each claim that could create cost. Include inclusions, exclusions, alternates, allowances, and any phrase that assigns work to another party. Write one claim per row, using the narrative wording rather than a paraphrase.
The list should be short enough to review and specific enough to test. Mark the claims that use broad words such as complete, all, or as required. Those words often hide a scope decision that the specifications resolve in a different direction.
For each broad claim, write the specific work it implies. A claim that cannot be made specific is a question for the design team, not a number for the estimate. Add the claims that describe a boundary between packages.
Electrical work by others, owner-furnished equipment, and a contractor-provided connection point are boundaries that change both scope and cost. The cost estimator page describes the review support this cross-check fits, and the allowance record guide shows how to keep a disputed decision visible. The AACE recommended practices call for a documented estimate basis that includes the scope boundary.
Map claims to specification sections
For each narrative claim, write the specification section that should describe it. A claim about roof drainage should point to the roofing and plumbing sections that carry the drains and leaders. A claim about temporary power should point to the temporary facilities section.
If no section supports the claim, mark it as unsupported and keep it visible. Check the reverse direction as well. Skim the section list for sections that do not appear in the narrative.
Firestopping, commissioning, and closeout requirements are common examples of work that can sit in the specifications without a narrative mention. Add each to the matrix and decide whether it is in scope. Use the same section numbers that appear in the specifications.
Do not invent a grouping that only the estimator understands, because the reviewer and the design team need to trace the row back to the source. A shared numbering system makes the matrix usable outside the estimating department. Add the specification title beside the number so a reader can recognize the scope without opening the file.
Flag sections that are referenced by another section but not issued. A specification can call for a product or a test that lives in a section the design team forgot to publish.
The reference is evidence that the work exists even when the section is absent. Put those rows at the top of the review list because they often carry a real cost.
Test the boundaries
Read the by others and not in contract phrases with care. A phrase can exclude a scope from one package while the specification still requires a connection or a coordination duty. Test each boundary with a simple question.
Who supplies the item, who installs it, and who makes the final connection. If the narrative and the section disagree, record the conflict. Check the alternates against the base scope.
An alternate that adds a system may also add a specification section that the base estimate did not include. Add the section to the alternate column and cost it separately. Mixing the alternate into the base is the most common way a boundary disappears.
Test the allowances the same way. An allowance may cover a material upgrade that the specification lists as an option, or it may leave the installation cost with the contractor.
Read the allowance language beside the section that governs the product. If the two do not match, write the question and carry the difference explicitly.
Resolve and record the gaps
Send the unsupported claims and the unmatched sections to the design team in one list. Include the narrative page, the section number, and the specific question. A short list gets a faster answer than a long narrative email.
Record the answer and the date in the estimate file, then update the matrix. If the answer does not arrive before the bid, carry the work as a qualified item with a stated assumption. Do not bury it in a contingency line without a note.
The reviewer should be able to see the unresolved question and the assumption used to cost it. That visibility is the difference between a risk and a surprise. Set a date to revisit every open matrix row, even if the bid is still weeks away.
A question that sits open for a month often becomes a last-minute change. The revisit date gives the design team a reason to answer and the estimator a reason to follow up. Put the date in the same calendar as the estimate review.
Keep the matrix for the next review
Save the completed matrix with the estimate and use it in the post-bid review. Compare the claims that changed with the questions that were asked. The pattern often shows which parts of the narrative are reliable and which sections tend to hide scope.
That pattern is useful for the next bid from the same design team. Update the template when a new type of gap appears. Add the section group, the boundary question, and the owner.
A matrix that grows with real examples is more useful than a generic checklist. Over time, it becomes a record of how the team reads scope, not just a form.
| Narrative claim | Governing section | Status |
|---|---|---|
| Roof drainage included | Div 07 and Div 22 sections | Supported |
| Temporary power by others | Div 01 temporary facilities | Boundary question |
| Firestopping not mentioned | Div 07 firestopping section | Added to scope |
| Alternate adds a system | Alternate section list | Priced separately |