How should the checklist be used?
Apply it at takeoff setup, before pricing review and after each material addendum. A checked control means the evidence exists, not merely that someone remembers doing it.
| Stage | Evidence | Decision |
|---|---|---|
| Setup | Document register and work breakdown | Ready to measure |
| Reconciliation | Quantity and scope exceptions | Ready for inputs |
| Bid review | Approved rates, quotes and assumptions | Ready for submission review |
What references sit behind the checklist?
CSI identifies Division 26 as Electrical. NFPA 70 is the National Electrical Code. TIA-942 addresses data center infrastructure including power. Use the editions and requirements named by the project, not a generic checklist as a design basis.
Sources: Construction Specifications Institute: MasterFormat 2026, National Fire Protection Association: NFPA 70, National Electrical Code, Telecommunications Industry Association: TIA-942 Telecommunications Infrastructure Standard for Data Centers
What can still go wrong?
A checklist cannot resolve conflicting drawings, approve a design assumption or validate an unverified rate. Keep those items open for the responsible reviewer.
Common questions
What else should the bid team know?
Does the CSV contain quantities?
No. It records takeoff controls. Quantities must be measured from the tender documents.
Can this replace the project estimate review?
No. It helps structure the review but does not replace authorized technical and commercial approval.
Should it be rerun after addenda?
Yes. Recheck every control affected by changed drawings, specifications or bid instructions.
Primary sources
- MasterFormat 2026Construction Specifications Institute
- NFPA 70, National Electrical CodeNational Fire Protection Association
- TIA-942 Telecommunications Infrastructure Standard for Data CentersTelecommunications Industry Association
- Tier Standard: TopologyUptime Institute