Skip to main content

Submittal Package Software

The package compiles itself. You review it.

You know the afternoon. Forty datasheets in a folder, a highlighter, a bookmark panel, and a deadline. Submittal Kit turns that afternoon into a compile: the register feeds the package, and the package comes out bound, bookmarked, and ready to review.

Configuring sections: the compile order, with sections that build themselves and sections that collect documents
A Controllers and Network product data submittal stamped Approved as Noted, its sections listed in compile order: cover, transmittal, table of contents, equipment schedule, then the datasheet sections fed from the register.

From equipment register to bound PDF

Every package draws from one Equipment Register per project. Enter a part once and every submittal that touches it routes the same datasheet, the same description, the same tag.

  • Cover page with your logo and branch identity, then transmittal, then a clickable table of contents
  • Datasheets grouped by part and included once, no matter how many tags share them
  • Spec document and custom upload sections wherever the recipe calls for them
  • A source-file ZIP export alongside the compiled PDF

Highlighting the reviewer trusts

The catalog number for each item is found and marked on its datasheet automatically, each item in its own color, and you review the marks before anything ships. A shared datasheet carries every item's highlights side by side, so the reviewer never has to guess which variant belongs to which tag.

A recipe, not a folder

A submittal is an ordered list of sections: generated ones like the equipment schedule, routed ones fed from the register, and your own uploads. When scope changes, adjust the recipe and recompile with live progress. When it goes out, Mark as submitted records a numbered submission whose bytes are kept forever.

Caught before the reviewer catches it

The Checks tab lists what a reviewer usually bounces, before you issue: an item with no document, an entry still waiting for a part, a catalog number the highlighter could not find on its datasheet, an empty section. Each finding opens the thing to fix.

Tie the submittal to a spec section and the spec check reads every datasheet against it, one row per requirement per part: Meets, Does not meet, Look at this, or Not stated, with the line and page it found. Add a Spec Check Results section and the package prints the table for the engineer.

Upload it anywhere

The compiled PDF is the file you upload to Procore, Autodesk Build, or the engineer's portal. When a reviewer wants the files loose, the source ZIP carries every document with its BOM. Edit the register after a compile and the submittal says the package is out of date, so an old PDF never goes out by mistake.

Questions integrators ask

RFI logSubmittal Package Software
RFI-01

What is a submittal package?

The document set a contractor sends the engineer of record to show that the equipment it will install meets the specification: a cover and transmittal, then product data for every item, usually with the supplied catalog number marked on each datasheet. For a control panel it often adds shop drawings and a bill of materials.

RFI-02

Does it replace Procore or Autodesk Build?

No. Those route the package for review. Submittal Kit builds the PDF you upload to them, and keeps its own record of what you sent and what came back.

RFI-03

What if the BOM changes after I compile?

Change the register and the submittal shows its package is out of date. Compile again and the datasheets, bookmarks and highlights rebuild from the current list. Issued submissions never change, so the version the engineer reviewed stays on the record.

RFI-04

Can I add my own drawings and documents?

Yes. Add an upload section anywhere in the recipe for panel drawings, a spec excerpt, or a cut sheet that lives outside the library, and it compiles in its place in the package.