The three-part section format, read as a contractor
Every CSI-format section follows the same skeleton, and each part has a submittal job:
- Part 1 — General: the 'Submittals' article is your checklist (action vs. informational items, samples, certifications); also read quality-assurance (installer qualifications, mock-ups) and warranty articles — they generate submittal lines people miss
- Part 2 — Products: the acceptable manufacturers, the performance values your product data must meet, and the fabrication requirements your shop drawings must show
- Part 3 — Execution: installation and testing requirements that become field submittals — test reports, TAB, commissioning documentation
The submittal answers the section, item for item
A strong package is a mirror of the section's Part 1 article: each required item present, in order, labeled, nothing extra. Reviewers literally check the article against the package — a missing installer certification listed in ¶1.5.C is a returned package regardless of how good the cut sheets are. Two practical habits follow. Build the package from the section, not from the distributor's quote, because the quote was built to win a price, not to answer a spec. And when the section conflicts with the drawings (a scheduled model that doesn't meet the specified performance), resolve it by RFI before submitting — a submittal cannot fix a document conflict, only inherit it.
Numbering and the register connection
The spec section number is the submittal's address: packages are numbered section-plus-sequence (07 54 00-001), routed to reviewers by division, and logged by section in the register. One section can require many submittals (data, drawings, samples, closeout items on separate lines), but a submittal should answer exactly one section. When your product genuinely spans sections — electrified hardware across 08 and 28 — submit where specified and cross-reference the companion section on the transmittal, so both reviewers see the whole picture and neither assumes the other covered it.
From section to package automatically
This mapping is mechanical, which makes it automatable: Submittal.App reads the spec section, extracts what Part 1 requires and what Part 2 constrains, matches products from its indexed cut-sheet library, and assembles a package organized the way the section demands — with the register line created in the same motion. The PM's job becomes confirming the answer, not transcribing the question.
The habit worth keeping either way: before any package goes out, reread the section's Part 1 article one last time against the finished PDF. It takes four minutes, and it catches the missing warranty letter or sample requirement that would otherwise cost a three-week review cycle and a schedule conversation nobody enjoys.