10 construction reference sources for GC prebid review
Find the right construction reference authority, verify the cited edition and track how an issued requirement affects trade scope and your project estimate.
Author
Ido Gedanken, CEOPublished

Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.
Book a demo- Type
- Guide
- Read
- 5 min
- Published
On this page
- 1. CSI standards: organize the work
- 2. AIA Contract Documents: review the issued conditions
- 3. ConsensusDocs: identify the form architecture
- 4. AACE recommended practices: describe the estimate basis
- 5. ASTM International: identify material and test references
- 6. NFPA: verify the applicable fire and life-safety edition
- 7. International Code Council: distinguish model code from adoption
- 8. WBDG UFGS: start from the issued specification
- 9. OSHA: identify safety scope and cost owners
- 10. SMACNA: review sheet-metal interfaces
- Build a reference-to-carry register
- Connect issued requirements to trade scopes
When a specification cites an external standard, the estimator's first job is to establish why it applies, which edition controls and who owns the resulting work. A publisher's current edition is not automatically the edition adopted by the jurisdiction or incorporated into the contract.
Piper selected these ten authorities and publishers for questions that arise during commercial and industrial prebid review. They serve different purposes: classification, forms, guidance, standards, model codes, guide specifications and regulations. This is an editorial reading order, not a ranking. Consult the applicable issued documents, amendments and qualified reviewers before deciding what to carry.
| Reference type | Question it helps answer | Review action |
|---|---|---|
| Classification | Where is work organized? | Assign actual package responsibility separately |
| Contract form | What allocation does the issued agreement establish? | Read amendments and supplementary conditions |
| Standard or code | What technical reference is cited or adopted? | Verify designation, edition and applicability |
| Guide specification | What might a designer use as a starting point? | Price the edited project section |
| Regulation | What safety rules may apply? | Verify jurisdiction and project conditions |
1. CSI standards: organize the work
CSI's standards overview describes Dynamic Standards, including MasterFormat, UniFormat and OmniClass. Classification helps reviewers navigate work results and project information. It does not itself decide which subcontractor owns an interface. Check the project-specified edition and access terms; full standards require licensed access, while limited number and title lookup is available. See MasterFormat and trade-package responsibility for the allocation step.
2. AIA Contract Documents: review the issued conditions
AIA's A201-2017 summary describes general conditions addressing owner, contractor and architect relationships and responsibilities. Use the actual issued agreement, its modifications and supplementary conditions to identify the project allocation and ask the appropriate contract reviewer about ambiguities. A publisher's template or summary is not the signed agreement; document access is subject to licensing.
3. ConsensusDocs: identify the form architecture
The ConsensusDocs catalog describes its owner-constructor agreement and related forms, including change-order and RFI documents. Use the catalog to understand what kind of form a bid package references, then find the actual version and project modifications. Do not assume that a common form is incorporated merely because it appears in a catalog. The distinction between contract conditions and project requirements helps route the review.
4. AACE recommended practices: describe the estimate basis
AACE's estimate-classification guide identifies RP 56R-08 for building and general construction and describes its scope. Use the relevant guidance to communicate estimate maturity and basis to decision makers, while documenting actual design information and exclusions. A recommended practice is not automatically a project contract requirement, and a class label is not a guarantee of a particular outcome. Obtain the applicable practice through the publisher and check its scope.
5. ASTM International: identify material and test references
ASTM's construction standards catalog covers materials, systems and test methods. When a specification cites a standard, record the full designation and edition and identify the affected material, testing or installation obligation. Review the properly licensed reference where needed and assign the work to an estimator or trade reviewer. Do not substitute a similarly named current standard without checking the issued documents.
6. NFPA: verify the applicable fire and life-safety edition
NFPA offers free online read-only access to selectable editions with sign-in; its viewer is not a downloadable or printable copy. Establish the adopted or contract-referenced edition and any amendments before using a requirement in a fire or life-safety scope review. The newest publisher edition does not, by itself, establish local applicability.
7. International Code Council: distinguish model code from adoption
ICC describes the I-Codes as coordinated model building-safety codes used by adopting jurisdictions. A GC reviewing a facility must establish the jurisdiction, effective code edition and amendments for the project. Ask a qualified reviewer or authority as appropriate when the applicability is unresolved. The model-code catalog alone cannot decide that question. The code applicability guide sets out the project review.
8. WBDG UFGS: start from the issued specification
WBDG's Department of Defense program hosts Unified Facilities Guide Specifications and criteria developed by participating agencies. Guide masters are starting points, not automatically the project requirements. An Army Corps specification rule describes designer notes, tailoring and editing masters for a project. Review and price the issued edited section; this agency guidance does not impose UFGS on private work generally.
9. OSHA: identify safety scope and cost owners
OSHA's construction standards index organizes 29 CFR Part 1926 by subject, including scaffolds, fall protection and excavation. Identify relevant work methods and possible temporary measures, training or staffing for review by the project safety lead. Verify federal or applicable state-plan requirements and actual conditions. An index and estimating checklist do not constitute a complete safety plan.
10. SMACNA: review sheet-metal interfaces
SMACNA's HVAC duct construction standards page identifies duct construction guidance and editions. Where the issued project documents refer to SMACNA, check the cited publication and edition and ask how duct pressure, reinforcement, supports and any specified testing or balancing affect the packages. Confirm whether related manuals and licensed access are needed. The reference alone does not assign every item to a particular subcontractor.
Build a reference-to-carry register
For each item, record the issued requirement and section; cited source and edition; evidence of adoption or incorporation; affected trade or interface; quantity, testing or administrative obligation; responsible reviewer; unresolved question; and estimate disposition. Keep the source location with the carry, exclusion, allowance or RFI so the team can revisit it after an addendum.
Illustrative duct and TAB review: A mechanical specification cites a duct standard and separately describes testing, adjusting and balancing. Record both issued sections and cited editions, then ask whether leakage testing, access and TAB are included in the mechanical and balancing proposals. If the package boundaries conflict or remain unclear, route an RFI and document the interim carry. The external source helps identify potential requirements; the project specification and design clarification establish the actual work.
Connect issued requirements to trade scopes
After checking authority and edition, the GC still has to assign the project requirements to packages. Piper Scope Generation turns project requirements into trade scopes with source-linked findings for review. Use authorized project documents and resolve applicability with the appropriate reviewers; this workflow does not replace a standards publisher or an authority having jurisdiction. For the next step, turn requirements into trade scopes and keep project revisions under review.
Related reading
Construction specifications and MasterFormat: section numbers do not define trade scope
MasterFormat organizes project information; it does not assign work to a bidder. A method for turning specification requirements into trade packages.

Construction code requirements: confirm the applicable basis before assigning scope
A model-code reference is not a project applicability decision. Review connecting adopted requirements, issued design information, trade scope and pricing.

General conditions vs. general requirements: separate the contract from the cost plan
General conditions can mean contract terms or job costs. A GC review for separating that language from Division 01 requirements and package pricing assumptions.

Piper removes manual review from the critical path and brings project data, company knowledge, and expert checks into every preconstruction decision and workflow
See Piper on your project
Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.