Ignoring Division 01
The register can list the right deliverables but miss the rules governing when and how they must be submitted.
Division 01 guide
Division 01 tells you how. Technical sections tell you what.
A sound register respects both. Division 01 establishes procedures, timing, formats, and responsibilities; individual sections define the actual deliverables.
The role of Division 01
Division 01 coordinates administrative requirements across the project. It may define the submittal schedule, electronic formats, contractor review stamps, deviation statements, resubmittal procedures, and required lead time for design review.
Avoid the two common mistakes
Turning every procedure into a row
The register becomes crowded with administrative instructions instead of usable deliverables.
How to apply it
Extract Division 01 requirements into a short project-level checklist. Then build detailed rows from the applicable technical sections. Apply the checklist consistently during review and scheduling.
Examples of project-level rules
- Submit a coordinated submittal schedule within the specified period.
- Show deviations from the contract documents clearly.
- Complete the contractor’s review before forwarding an item.
- Allow the specified review duration in the project schedule.
Division 01 topics that shape submittal planning
Substitution procedures
Defines timing, supporting information, comparison requirements, and conditions for proposing products that differ from the basis of design.
Project management and coordination
May establish coordination drawings, meetings, scheduling responsibilities, and administrative records.
Submittal procedures
Typically governs the schedule, contractor review, transmittal, format, deviations, review time, and resubmittal process.
Quality requirements
Can define testing agencies, qualifications, mockups, certificates, and documentation applicable across technical sections.
Closeout submittals
Often coordinates record documents, warranties, operation data, maintenance materials, training records, and turnover procedures.
Project-specific requirements
Commissioning, sustainability, delegated design, electronic documentation, and owner standards may be located in other Division 01 sections.
Project rules versus register rows
A project rule applies broadly. For example, “identify deviations from the contract documents” affects every applicable package. Repeating that instruction as a separate row under every section would add noise.
A register row represents a specific deliverable: “Door hardware schedule,” “Concrete mixture design,” or “Controls wiring diagrams.” The team should be able to prepare, assign, schedule, and ultimately close that item.
A useful Division 01 output
Create a one-page review checklist covering format, contractor approval, deviation statements, review durations, resubmittal requirements, schedule updates, and closeout expectations. Apply it to the technical-section rows rather than burying the rules in the register.
How Division 01 affects schedule dates
Technical sections identify what is required. Division 01 often defines the administrative durations and prerequisites that determine when it must move.
RequirementSchedule effect
Initial submittal scheduleSets the deadline and format for presenting the project’s planned submission sequence.
Contractor reviewRequires time for completeness, coordination, field measurement, and internal approval before forwarding.
Design-team review periodEstablishes the minimum planned duration; complex or delegated-design items may need additional coordination.
ResubmittalsRequires contingency between first submission and final approval rather than assuming every item is approved initially.
Sequential reviewMay require one related item to be approved before another can be completed or evaluated.
Schedule updatesCreates an ongoing obligation to revise projected dates as procurement and construction conditions change.
Deviations from the contract documents
Division 01 may require deviations to be identified expressly. Product data with dozens of pages does not satisfy that responsibility by itself. The project team needs a process for marking selections, exceptions, and substitutions so the reviewer understands what is proposed.
Contractor review before submission
The contractor’s review typically addresses completeness, coordination, field dimensions, quantities, installation requirements, and consistency with the work. A software-generated register supports planning but does not perform that package-level review.
Meaning of the design professional’s review
Submittal review generally evaluates conformance with design intent as described by the contract documents. It does not transfer responsibility for means, methods, safety, fabrication processes, or coordination unless the contract says otherwise. The register should not imply that approval resolves every obligation.
Delegated-design procedures
Delegated-design requirements may involve calculations, drawings, design criteria, professional seals, coordination information, and a defined review sequence. Identify these items early because responsibility and duration often extend beyond a typical product-data submission.
Division 01 FAQs
Does Division 01 contain every submittal?
No. It generally establishes project-wide procedures. Detailed deliverables are usually found in the applicable technical sections.
Should Division 01 be reviewed before the technical sections?
Yes. Understanding the project’s rules first helps the reviewer interpret, classify, and schedule the detailed requirements consistently.
Are Division 01 requirements the same on every project?
No. Section numbering may be familiar, but content, review periods, digital formats, owner procedures, and closeout expectations are project-specific.
Turning Section 01 33 00 into project controls
Assume the section requires a submittal schedule within 15 days of notice to proceed, contractor review before forwarding, identification of deviations, a 10-business-day design review period, and resubmittals that respond to every prior comment. These requirements should not become five repeated rows under every technical section.
Instead, create a project-level procedure checklist. Add the initial submittal schedule as a specific administrative deliverable if the contract requires it. Configure planning assumptions to allow the stated review duration. Require preparation teams to identify selections and deviations. Confirm that the contractor’s review step occurs before routing. When a package is returned, use the resubmittal rule to check that prior comments are addressed and changes are identified.
Now consider a technical requirement for a curtain-wall mockup. Division 01 supplies the general process, while the curtain-wall section defines the mockup’s size, components, testing, and acceptance criteria. The register entry should point to the technical requirement and retain related Division 01 procedures without duplicating the same administrative rows.
Coordinate related Division 01 sections
Submittal procedures rarely operate alone. Quality requirements may govern testing documentation. Product requirements may govern substitutions. Project-management sections may govern coordination drawings. Closeout sections may establish turnover formats. Build one coordinated checklist rather than reading 01 33 00 in isolation.
Do not assume familiar numbering means familiar content
MasterFormat numbers help navigation, but the project’s actual language controls. Review periods, electronic platforms, copy requirements, stamp language, and owner approval procedures can vary substantially between projects using the same section number.