Submittal Desk / Div 21 Desk
FIRE PROTECTION SUBMITTAL REVIEW
Fire Protection Submittal Review: Division 21 Packages Checked Against the Spec First
The preaction package goes out without every data sheet the spec's Submittals article lists. It comes back for one missing sheet, and the review clock starts over on the whole package.
The Div 21 Desk reads your Division 21 sections first, builds the fire protection submittal log, and pre-checks every package before it goes to the GC. Same four parts and same five checks as every Submittal Desk; your PE signs off on every package.
Request a sample runSee what a sample run returns
Last updated
Div 21 Desk
What the Div 21 Desk reads first
These are the sections the desk opens first. It reads every Division 21 section in your spec book, and any other section your scope covers.
| Spec section | What the pre-check matches |
|---|---|
| 21 13 13 Wet-Pipe Sprinkler Systems | Listed components, sprinkler types, pipe material, and the drawings and calculations the spec requires. |
| 21 13 19 Preaction Sprinkler Systems | The system type the spec names, valve and trim, listed components, and required data sheets. |
| 21 22 00 Clean-Agent Fire-Extinguishing Systems | The agent the spec names, listed components, and the required calculations and data sheets. |
| 21 30 00 Fire Pumps | Rated flow and pressure, driver type, controller, and listed components. |
Same four parts on every desk
How the Div 21 Desk works
01Spec Log
Every submittal your spec book requires, one line per spec section and paragraph, with its type and status, in a log you own.
Check: every Submittals article in the spec book has a line in the log.
02Pre-Check
Each package read against its spec section before it leaves your office: manufacturer, ratings, dimensions and missing items, each finding tied to a page.
Check: every finding cites the spec paragraph and the package page.
03Compliance Matrix
One row per requirement: spec value, submitted value, comply, deviate, missing or needs PE, and the page. The deviation list and cover sheet come from it.
Check: every row cites a spec paragraph and a data sheet page, or says not read.
04RFI Match
Answered RFIs on your RFI log are placed next to the spec requirement they touch, so the package is checked against the answer, not only the original spec.
Check: every RFI answer shown cites its RFI number and the requirement it touches.
What correct looks like
What correct looks like, in writing
Named owner of mistakes: Mike Rodgers. Every value your PE marks wrong is counted in the monthly report, the check behind it is fixed, and the affected packages are checked again before the next batch goes out.
- The manufacturer and model are named in the spec, or an approved substitution is on the log.
- Every item the spec's Submittals article asks for is in the package: shop drawings, product data, samples, O&M data, warranties.
- Every rating and dimension the spec states is matched to a page in the package, with units, and every mismatch is listed as a deviation on the cover sheet.
- Anything code cannot compare is marked needs PE and decided by your project engineer. No model decides comply, deviate or missing.
- Every finding cites the spec paragraph and the package page it came from. A value that cannot be read is marked not read, never guessed.
What stays with you
What your people still own
- Your project engineer approves every package and every compliance matrix before it leaves your office.
- Your PM decides every substitution and every deviation you are willing to carry.
- Your team sends everything to the GC. The desk has no send function and never contacts your GC, architect, engineer or owner.
- The engineer of record makes the compliance call. The desk checks; it does not stamp, sign or certify anything.
Not included
- Not a submission service. The desk never sends a package or contacts your GC, architect, engineer or owner.
- No engineering judgment, stamps or signatures. The engineer of record makes the compliance call.
- No deviation or substitution requests on your behalf, no shop drawing production, and no RFI drafting.
- No closeout manuals or O&M binders yet.
- Never writes into Procore or any other platform. Output comes back as a CSV in your log's column order.
- Not a code review. The desk checks against your project spec, not the NEC, plumbing code or NFPA standards.
Straight answers
Fire protection submittal questions.
- Do you review hydraulic calculations?
- The desk checks that the calculations and drawings the spec asks for are in the package and labelled to the right section. It does not redo or approve them; that stays with your licensed designer and the engineer of record.
- Does the Div 21 Desk cover clean agent systems in data halls?
- Yes, where your spec includes a clean agent section such as 21 22 00: the named agent, listed components and required data sheets are checked like every other package.
- Is this an NFPA or fire code review?
- No. The desk checks the package against your project spec, not against NFPA standards or the fire code. That stays with your designer, the engineer of record and the authority having jurisdiction.
Start with one job
Request a sample run.
The sample run report is yours to keep whether or not you go further. Sign setup within 30 days of the report and the $1,500 comes off setup in full.
Sample run $1,500. Setup $5,000. Then $1,200 a month per active project.
The sample run is a fixed price, returned 10 business days after your documents arrive. Setup takes 4 weeks, including 2 weeks running beside your PE on live packages. The monthly fee covers up to 60 packages a month per active project, month to month with 30 days notice.