Submittal Desk / Div 26 Desk
ELECTRICAL SUBMITTAL REVIEW
Electrical Submittal Review: Division 26 Packages Checked Against the Spec First
The panelboard shop drawings go out before the short circuit and coordination study is approved, and the spec says drawings sent early are returned without review. That rule is paragraph 1.2.C of the public LAWA panelboard section 26 24 16. Medium voltage switchgear averages 22 months of lead time on 2026 orders (Archdesk, 2026-04-16), so a returned package costs more than a week.
The Div 26 Desk reads your Division 26 sections first, builds the electrical 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 26 Desk
What the Div 26 Desk reads first
These are the sections the desk opens first. It reads every Division 26 section in your spec book, and any other section your scope covers.
| Spec section | What the pre-check matches |
|---|---|
| 26 24 13 Switchboards | Short circuit rating against the value the spec states, fully rated versus series rated, bus material and ampacity, enclosure dimensions. |
| 26 24 16 Panelboards | Named manufacturers, voltage and short circuit rating, breaker type, box depth and width, keying, and the coordination study condition. |
| 26 32 13 Engine Generators | Rating at the conditions the spec states, voltage, fuel system, enclosure and sound level, and the emissions and test documents the spec lists. |
| 26 33 53 Static UPS | Rating, battery type and runtime at the stated load, efficiency, bypass arrangement, and the factory test the spec requires. |
Same four parts on every desk
How the Div 26 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
Electrical submittal questions.
- Do you check short circuit ratings against the study?
- The desk matches every rating in the package to the value the spec states, and flags any rating the spec ties to the approved short circuit and coordination study so your PE can confirm it against the study. It does not run or approve the study.
- Does the Div 26 Desk cover switchgear and UPS packages on data center jobs?
- Yes. Switchboards (26 24 13), panelboards (26 24 16), engine generators (26 32 13) and static UPS (26 33 53) are the sections it reads first. Archdesk puts UPS and PDU lead times at 30 to 50 weeks (2026-04-16), which is where a clean first submittal matters most.
- Is this an NEC code review?
- No. The desk checks the package against your project spec, not against the NEC. Code compliance stays with your team and the engineer of record.
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.