Submittal preparation that starts at the drawings.

What the work actually covers

A submittal package proves that what you intend to buy matches what the drawings and the specification asked for. Preparing one means reading both documents, listing every product that has to be submitted, finding manufacturer data for each, checking that data against the requirements written into the spec, and assembling the result in the order the reviewer expects to see it.

Written out, that reads like five clerical steps. In practice four of them are search and formatting, and one of them decides whether the package is right.

Scoping is the step that gets skipped

Finding a cut sheet for a product you already know about is a search problem, and it is not where packages fail. Packages fail on the products nobody listed.

The list is spread across the documents rather than written down in one place:

• Fixture, panel and equipment schedules carry the bulk of it, usually with an exact catalog string.
• The legend carries device types the schedules never repeat.
• Keyed notes on individual sheets add items that appear nowhere else in the set.
• Part 2 of each spec section names products the drawings assume you already knew about.
• Rough-in that no schedule mentions rides along with the devices that do get scheduled.

An item missed at this stage does not surface during review. It surfaces at delivery, where it is a change order rather than a revision.

How it gets handled today

In-house, by a project manager

The common answer. A PM works through the set with the spec book open, builds the product list by hand, emails reps for cut sheets, waits, then assembles the package in whatever tool is nearby. It works, and it costs several days of the person who can least afford to lose them. The accuracy of the whole package depends on how tired that person was by page 60.

Software that starts after you already know

Some tools read the specification and produce a list of submittal requirements, then hand it back for you to fill. Others take a finished package and grade it against the spec before the engineer sees it. Both are useful, and both begin at a point you have to reach on your own, because each one assumes the scope is already settled.

What we do differently

We start at the drawing set. Legend first, then every schedule, keyed note and detail sheet, checked against the spec book. Every product you have to submit gets listed and scoped by spec section, including the rough-in a schedule never names, grouped under the device it belongs to.

Each item then gets candidate cut sheets from our library of 5,754 sheets across 279 manufacturers, checked against the constraints lifted out of that item's own spec section. Voltage, listing, finish, mounting and the accepted-manufacturers clause each get a pass, review or fail verdict, traced back to the paragraph it came from.

Where the documents are silent or disagree, the item is flagged for your decision instead of filled in with a guess. A person who has worked the trade checks the book before it reaches you.

What you get back

• Every scoped product, organised by spec section, under your cover sheet and table of contents.
• Candidate cut sheets against each item, narrowed to the pages that cover your product.
• A verdict on every spec constraint, with the page it came from.
• Flagged items carrying the reason, so the call stays yours.
• The same package split by vendor instead of by spec section, so each supplier gets one clean list.

You make the final marks in your portal, download the finished book, and send it under your own company name. We never send a submittal to a general contractor, an architect, or anyone else. You are the submitter, every time.

What it costs you to try

Your first package is free, on a real job rather than a demo set. If it is not better than what you would have built, you have spent one set of drawings and an email address. Run your own numbers on what the waiting currently costs, or read the 12 reasons packages get bounced before you decide.