For control system integrators
The manual shouldn't take longer than the panel.
Import the BOM, hit compile, and send a highlighted, submittal-ready package the same afternoon. Every revision tracked from first transmittal to final stamp.
Two submittals. One parts library behind both.
Every project ends the same way: the submittal package the engineer stamps, and the O&M manual the operator keeps for twenty years. Build both from the same parts, datasheets, and highlights, entered once.
Submittal A
Site O&M Manual
A complete operations & maintenance manual per site (lift station, treatment plant, process skid), assembled from its panels.
- ▸Cover page with your company logo
- ▸Clickable table of contents, numbered sections
- ▸Station Bill of Materials, per panel
- ▸Panel drawings + component datasheets
- ▸Configurable sections: site record, demo test, arc flash study, or your own uploads
Submittal B
Project Submittal Package
The review package the engineer stamps. Configurable sections, tagged items, and shared datasheets handled the way reviewers expect.
- ▸Items pulled straight from the parts library
- ▸Shared datasheets included once, each item's highlights in its own color
- ▸Per-item tags and configuration summaries
- ▸Spec document and custom upload sections
- ▸Source-file ZIP export alongside the compiled PDF
Upload a datasheet once. Never hunt for it again.
You know the folder. Datasheets_FINAL_v3(2). A decade of PDFs named by whoever saved them last. Stop digging.
F-01
Shared Parts Library
Your whole company pulls from one library. Upload a datasheet once and every project, panel, and teammate reuses it. No more emailing PDFs around or re-downloading from the manufacturer.
F-02
BOM Import
Forty line items on the panel? They're in the library before your coffee cools. Drop in CSV or Excel: QTY / CATALOG / MFG / DESC columns match however your CAD package spells them.
F-03
Catalog-Number Highlighting
Reviewers want to see exactly which model you're supplying. The compiler highlights the catalog number on every datasheet automatically, and where detection isn't enough, draw your own. Manual always wins.
F-04
Smart Datasheet Grouping
Ten transmitters off the same datasheet? It appears once, with each item's highlights in its own color. Nobody reviews (or prints) a 400-page package of repeats.
F-05
BOM & Parts-List Exports
Need the parts list in Excel? One click, at every level: panel, site, or whole project, always in lockstep with what compiles. No side spreadsheet drifting out of date.
F-06
One-Click Compile
Hit compile and watch the package build: cover, TOC, drawings, datasheets, highlights. Working copies expire after an hour; the revisions you actually submit are kept forever.
From BOM to stamped package in five steps.
-
01
Model the job
Create the project, add its sites and panels, the same structure you deliver.
-
02
Import the BOM
Upload the bill of materials per panel. Parts auto-match to your library.
-
03
Attach & annotate
Add datasheets to new parts, review the auto-highlights, mark up where needed.
-
04
Configure & compile
Enable the sections each submittal needs, then compile with live progress.
-
05
Submit & track
Submitting mints Rev 1 and snapshots exactly what you sent. Track the review to its stamp.
Real screen, demo project. Every submission and every returned review, on one page.
"What did we send them in Rev 2?"
Answered, permanently. Every submission of a submittal or site O&M manual becomes a numbered Revision with an immutable snapshot of the exact compiled package that went out. The record and the sent file can't diverge: the download comes from the revision.
- ▸Log the engineer's response, response date, and notes per revision
- ▸Attach the returned, marked-up documents to the revision they answer
- ▸The log survives deleted submittals and sites; the record outlives its parents
- ▸Export the full submittal log as a PDF for project closeout
Review statuses · the engineer's stamp, on the record
The review itself happens wherever it happens: email, the engineer's own portal. The log is your company's record of it: who sent what, when, and what came back.
Hand off the chasing.
Eleven parts still have no datasheet and the package goes out Friday. Connect Claude, or any MCP-compatible assistant, to your account and put it on the hunt: ask your spec a question and get the section cited back, find every part missing a document, send it looking, compile the package, read back the log.
You get the hours back. You still review what it brings, and you still sign the record, because the limits below are not settings anyone can turn off.
Endpoint: submittalkit.com/mcp
· Approve the connection once from your account page, revoke it there any time.
- Item 1 Find a datasheet for every part missing one 11 held for your review
- Item 2 Compile Lift Station 31, Rev 2 Ready · 128 pp
- Item 3 What does the spec say about surge protection? Answered · 26 05 33, 2.4
Restrictions · not grantable
- ✗Cannot delete or overwrite anything you own
- ✗Cannot accept its own finds into your library
- ✗Cannot issue a revision or send a transmittal
- ✗Cannot reach another company's projects, ever
New enough to still ask why. Advised by people who aren't.
I'm about a year and a half into the integrator side of this business. Long enough to have spent my own nights printing datasheets, marking catalog numbers, fighting the copier, and wondering which version actually went out the door. Not long enough to think I have it all figured out.
So every decision in here got checked against people with decades on the job: what a reviewer actually wants to see, what belongs in a turnover package, why the log outlives the package it came from. You're getting their judgement with my nights and weekends attached.
And there's no ticket queue behind the curtain. If something breaks, or a reviewer wants the package formatted some way it can't do yet, email [email protected] and the person who wrote the code answers. Tell me what your reviewer sent back and it goes to the top of the list.
Jeremy · builder, and the entire support department
Simple pricing. Fourteen days free.
One subscription covers your whole company, and every plan starts with 14 days free, no credit card.
Plan A
Pro
$149/mo
$1,490/yr · two months free
- ▸Unlimited projects
- ▸Submittal packages & O&M manuals
- ▸Shared parts library
- ▸Unlimited team members
- ▸As-built redlines
- ▸Revision history
- ▸AI agent access (MCP)
Plan B
Enterprise
Custom
Quoted per company: how many of your forms get rebuilt, and how much of my time you want on call.
- ▸Everything in Pro
- ▸Controlled Documents: your approved forms, rebuilt field for field
- ▸Every RFI issues off the controlled version, so no stale copies drift
- ▸Update a form once and the old one retires everywhere at the same moment
- ▸Custom manual & submittal sections
- ▸Tailored onboarding
- ▸Priority support
Secure checkout by Stripe. Cancel anytime. Your data stays yours.
Bring your next project.
Your workspace is scoped to your company's email domain, so your projects, parts, and revision history stay yours. Start a free trial for your company, or if your company's already here, ask your admin for an invite.
14-day free trial, no credit card required. Password sign-in, with magic-link recovery by email.