The version that was submitted
is the version the AHJ sees.
The submittal package, the AHJ markup, the RFI, the as-built, the commissioning record, the DSP file, the rack elevation — one document plate per project, every artifact version-controlled, every change attributable.
The pains the founder built it against.
- 01.The fire-alarm panel that failed inspection because the as-built didn't match the submitted plan. The submission lived in one folder, the as-built in another, and the difference cost a Tuesday.
- 02.The AV install where the next integrator inherited a rack with no wiring diagram, no DSP file, no version history. The previous integrator left a spreadsheet. The customer paid twice for the same documentation.
- 03.The submittal package that took three weeks because the utility wanted a stamped single-line, and the operator's CAD tool, panel-schedule tool, and structural-letter tool didn't talk to each other.
- 04.The RFI thread buried in someone's email — three operators on the project, four versions of the answer, and the GC's RFI log out of sync with all of them.
The tools that ship together.
Single-line, panel schedule, NEC calcs, equipment cuts, structural letters — generated from the project's data, packaged in the format the AHJ asked for. The submission is one PDF; the source artifacts are individually addressable.
AHJ comments and conditions ride alongside the submitted document, not in a parallel email thread. The next revision shows what changed, who changed it, when, and why — auditable inside the same plate.
As-built captured in the field via Hyperion scan or operator markup. Variance from the submitted plan flagged automatically. The as-built is the version the AHJ sees on inspection day; the submitted plan is the version the AHJ saw on review day. Both are preserved.
RFIs initiate from the project, reference the submitted document, route to the responsible party, and resolve with a timestamped answer. The GC's RFI log syncs in.
Rack elevations, cable schedules, Q-SYS / Symetrix / BSS DSP configurations as first-class artifacts attached to the project. The next integrator picks up where the last one left off.
Commissioning records — test results, sign-offs, training receipts, warranty start dates — packaged as a turnover binder. The customer receives one document; the chest preserves every input.
On the menu.
The honest answers,
without the sales gloss.
Plate is purpose-built for commercial installation contractors and federates with the rest of the chest. D-Tools imports and exports work for AV operators staying on D-Tools; Bluebeam markup imports for operators continuing to use Bluebeam upstream of Plate; Procore reads via the open API. Charter operators usually consolidate to Plate because the document and the data share an architecture; the choice is the operator's, not the platform's.
Yes. Q-SYS, Symetrix, and BSS configurations attach as first-class artifacts. Rack elevations import from D-Tools or are drawn natively. The next integrator picks up the project without playing email archaeologist.
Yes. Submittal packages generate as a single PDF that an AHJ can review without a Forge account. For repeat-AHJ relationships, a read-only AHJ link can be issued per project; the AHJ sees the version submitted, the comments thread, and the as-built when filed. The audit trail is preserved on the operator's side.
The plate exports as a portable archive — PDFs of every submittal and as-built, source artifacts in their native formats where licensable, the complete RFI and commissioning record. The covenant runs both ways: the operator's documents are the operator's, on entry and on exit.
Master tier gets the chest. Every tool. Forever.
The day we ship it to ourselves, we ship it to you.