What actually drives the count
The register size is set by how many spec sections the project carries and how demanding each one is. The multipliers that push counts up:
- MEP intensity: hospitals and labs carry huge Division 21-28 scopes — equipment, controls, med-gas, low voltage — each with data, drawings, and closeout lines
- Finish variety: every flooring type, tile, and paint system adds product data plus samples
- Delegated design: sprinklers, curtain wall, trusses, and anchorage each add engineered packages and often AHJ legs
- Owner standards: institutional owners add informational submittals (warranties, training, spare parts) per section
- Sustainability programs: LEED documentation adds a line to most product submittals
- Public work: agencies commonly require submittals on items private jobs would wave through, including mix designs and certifications for commodity materials
Benchmarks by project type
Rules of thumb that hold up reasonably well in practice:
- Tenant fit-out / small commercial: 30-75 register lines
- Mid-size office, retail, multifamily: 200-500
- K-12 school or mid-size municipal building: 400-900
- Full-service hospital, laboratory, airport terminal: 1,500-4,000+
- Add 30-50% to any of these for total review events once resubmittals are counted
Why the count matters before day one
The register size sets the review pipeline load, and the pipeline has a fixed width: a design team that comfortably turns 20 packages a week drowns when 80 arrive in week three. That is why sequencing beats volume — long-lead procurement items first, finishes later — and why the submittal schedule required by Division 01 is worth building honestly instead of copying from the last job. For subs, the count is also a staffing signal: a 600-line register hitting three of your trades means someone owns package production as a real job for two months, not as evenings.
Managing volume without drowning
Volume is a logistics problem, and logistics automate. Submittal.App generates the register from spec sections, assembles packages from schedules in minutes, and keeps statuses current as a side effect of sending and receiving — so a 500-line register is a dashboard, not a part-time job. The teams that struggle with submittal volume are almost never short on knowledge; they are short on hours, and hours are what assembly automation returns.
One more sizing note for subs quoting a new project: count your sections before you price the general conditions. The gap between a 12-section scope and a 30-section scope is hundreds of hours of documentation labor across submittals, resubmittals, and closeout — real cost that belongs in the number, not absorbed as overtime later, and a line worth defending when the GC questions it.