Identify applicable sections
Work from assigned CSI sections and related requirements instead of relying on a generic contractor log.
For subcontractors
Find the submittal requirements tied to your scope.
SubmittalsHQ helps trade partners isolate relevant requirements and review them against the specification before procurement and submittal planning begin.
Focus the manual on your scope.
Understand the actual deliverable
Separate the item description from its type and retain the source language behind it.
Prepare scope questions early
Flag unclear responsibility, cross-references, and requirements that may affect suppliers or fabrication.
Useful before the register arrives
Trade partners can review their own scope early, compare it with the general contractor’s register, and raise omissions or responsibility questions while there is still time to act.
Review your own specifications
The contractor’s register is a coordination tool, not a substitute for reading the subcontract documents. A scope-focused review helps you identify requirements tied to your suppliers, fabricators, installers, testing providers, and delegated-design professionals.
Retaining the page and paragraph makes it easier to discuss a questioned item with the contractor and to pass the correct requirement to the party preparing it.
Look beyond product data and shop drawings
- Installer and manufacturer qualifications
- Engineering calculations and professional seals
- Selection and verification samples
- Mockup, testing, and field-report documentation
- Coordination drawings and interface details
- Warranties, training, maintenance data, and spare materials
Questions to resolve before preparation starts
QuestionWhy it matters
Who prepares the item?A supplier may provide product data, a fabricator may prepare drawings, and an engineer may be required for delegated design.
What must be coordinated?Dimensions, openings, supports, power, controls, finishes, and adjacent work can depend on other trades.
What must be selected?Colors, finishes, accessories, options, and performance characteristics may need project-team or design-team decisions.
When is it needed?The package must support approval, procurement, fabrication, delivery, and installation—not simply meet a generic due date.
What evidence is required?Certificates, qualifications, test results, calculations, or samples may need to accompany the primary product submission.
Compare the GC register with the source
If a requirement is missing, provide the section and paragraph when raising it. If a row appears outside your scope, identify the supporting language and the contractual basis for your question. Source-based discussions are clearer than disagreements over a spreadsheet label.
Send usable requirements downstream
Suppliers and detailers work more effectively when they receive specific deliverables and supporting paragraphs rather than an entire project manual with a generic request to “provide all submittals.”
Questions from subcontractors
Does the specification determine subcontract scope?
Not by itself. The subcontract, scope exhibits, drawings, addenda, and other incorporated documents control. Specification requirements are essential evidence, but responsibility must be confirmed contractually.
Can I build a register for only my CSI sections?
Yes. A focused register can support internal planning and comparison with the GC’s project-wide log. Include related and cross-referenced sections where they affect your work.
Should supplier submittals be entered separately?
Separate entries when different suppliers, timing, or review paths make that useful. Combine related items when they will form one coordinated package.
Reviewing a controls subcontract before the GC log is final
A controls subcontractor receives Division 23 specifications containing product data, control diagrams, points lists, sequences, qualifications, demonstration requirements, and closeout records. Some requirements sit in the controls section; others are cross-referenced from equipment sections or commissioning requirements.
A scope-focused register identifies each deliverable and retains the source. The subcontractor can separate supplier literature from project-specific shop drawings, flag information needed from the mechanical and electrical trades, identify any delegated-design responsibility, and plan training and closeout requirements before the end of the project.
When the GC register arrives, the subcontractor compares lists. Missing requirements can be raised with paragraph references. Items assigned incorrectly can be discussed against the subcontract and source rather than accepted or rejected based on a generic row title.
Use the register with suppliers and detailers
HandoffInformation to provide
ManufacturerSpecific product-data subjects, selected options, compliance evidence, and required certificates.
Fabricator or detailerShop-drawing scope, dimensions, interfaces, design criteria, related sections, and required calculations.
Testing providerRequired qualifications, procedures, report content, timing, and distribution.
Field teamApproved information, required mockups, reports, demonstrations, and records generated during execution.
Closeout teamWarranties, O&M data, record documents, training, spare materials, and outstanding turnover evidence.