MasterFormat in two minutes
MasterFormat (CSI/CSC, 2004 edition onward) organizes construction information into 50 divisions, of which about 35 are actively used in buildings. The six-digit section number reads as division (2 digits) + heading levels: 23 73 13 is Division 23 (HVAC), 73 (indoor central-station AHUs), 13 (the specific type). For submittal purposes you rarely need the deep levels — what matters is that every submittal belongs to exactly one section, the section defines what must be submitted, and the register sorts by that number.
The pre-2004 16-division format (electrical was Division 16, not 26) still appears on renovation specs and in the muscle memory of older estimators; if a spec says 15000-series mechanical, you are looking at the old system.
The divisions that carry the submittal load
Where the register lines concentrate on a typical commercial job:
- Div 01 — General Requirements: the submittal procedures themselves (01 33 00), plus schedules, closeout (01 78 00)
- Div 03-05 — Concrete, masonry, steel: mix designs, rebar and steel shop drawings
- Div 07-08 — Thermal/moisture and openings: roofing assemblies, glazing, doors and hardware (hardware schedules are notorious line-item generators)
- Div 09 — Finishes: the sample-heavy division — drywall, tile, flooring, paint
- Div 21-23 — Fire suppression, plumbing, HVAC: equipment data, shop drawings, delegated design
- Div 26-28 — Electrical, communications, security: gear drawings, fixture packages, device-heavy low-voltage scopes
- Div 31-33 — Earthwork, exterior improvements, utilities: civil and landscape submittals
Why numbering by section matters in practice
The section-based convention (26 51 00-001, revision R1) is not bureaucratic decoration. It routes review automatically — the architect knows a 23-series package goes to the mechanical engineer without reading it. It sorts the register into procurement-meaningful groups. And it prevents the classic failure of description-based logs, where 'light fixtures' and 'lighting package' turn out to be the same submittal logged twice. One section, one sequence, one history per item.
Reading a section number you've never seen
When an unfamiliar section lands in your scope, decode it left to right: the first pair is the division (what kind of work), the second pair the broad category, the third the specific type. 08 71 00 is Division 08 (openings), 71 (door hardware), 00 (general). You don't need the full MasterFormat book on your desk — the pattern plus the section's own title carries you, and the division tells you instantly which reviewer will see the package and which of your suppliers owes you the data. That instinct is worth building because scope-gap disputes between subs are usually arguments about which section number owns an item.
How Submittal.App uses MasterFormat
Submittal.App organizes projects and packages by spec section natively: the AI Builder reads section numbers off your specs, files each assembled package under the right section with convention-correct numbering, and keeps the register sorted the way reviewers and procurement both expect. You think in sections; the software does the clerical part.