Skip to content

Build the submittal register the specifications actually require.

Specset builds a cited, editable submittal register from the project specifications. Review the draft, then create the records your team will manage in Specset, Procore, or Autodesk Forma Build (formerly Autodesk Build / ACC).

Book a demo →See the workflow
A reviewable register first. Project records only after your team approves it.
From the specifications

How to generate a submittal log from specifications

Specset reads the project manual and writes a cited draft. Your team reviews it before any project record is created.

  1. 01

    Read the project manual

    Specset scans each assigned section in context, follows requirements that span pages, and confirms a submission is explicitly required before it writes a row.

  2. 02

    Group practical packages

    Related requirements consolidate into packages a project team can review, with the section and paragraph citation kept on every row. Plain-language instructions set scan scope, packaging, numbering, and the level of detail.

  3. 03

    Start from a register you already have

    Import an owner or contractor register when you have one. Specset preserves its authoritative fields, enriches its entries from the specifications, and adds the required packages the register missed.

  4. 04

    Approve the draft, then create records

    Edit, remove, or export entries before anything becomes a project record. Approved entries can be created in Specset, or pushed to Procore or Autodesk Forma Build (formerly Autodesk Build / ACC) when that connection is configured.

Register and log

Submittal register vs submittal log

Most teams use submittal register and submittal log for the same list. Specset builds that cited list from the project specifications as a reviewable draft. Project records are created only after your team approves the draft. An owner or contractor list you already have can be imported, kept, enriched from the specifications, and filled in where it missed a required package.

01 · Reasoning-based

It reads requirements, not keywords.

The agent follows paragraphs across pages and distinguishes an actual submission requirement from a passing reference.

02 · Package-aware

Built the way reviewers receive the work.

Related requirements consolidate while product data, shop drawings, samples, and closeout packages stay distinct.

03 · Reviewer-controlled

A draft before project records.

Edit, remove, export, or select entries in the draft before approved rows become project records.

Trusted by the teams delivering federal and public work
HNTBTriton Marine ConstructionGuardian ConstructionPacific Tech ConstructionTurnagain Marine ConstructionGhirardelli AssociatesDCS Marine Services
“The log that used to take a week of reading came back the same afternoon, with the governing paragraph behind every row.”
Project Engineer · General contractor · Federal courthouse renovation
31K+Spec sections conformed, Caltrans and UFGS included
14K+Submittals managed and reviewed on Specset
01 · Specification reasoning

It reads the section before it writes the log.

Specset scans every assigned section in context, verifies that a submission is explicitly required, then turns the requirements into packages a real project team can review.

01
Requirements can span pages.

The agent keeps the surrounding section in view.

02
Grouping requires construction judgment.

One practical package can draw from several paragraphs.

03
Every row retains its basis.

Section and paragraph citations stay with the register.

02 · Your conventions

Tell the agent how your team wants the register built.

Use plain-language instructions to control scan scope, packaging, numbering, and the level of detail. The agent applies them while it reads, not after the spreadsheet is finished.

01Scan selected sections or divisions
02Split or consolidate package types
03Follow the project numbering convention
The project convention becomes an instruction, not a spreadsheet cleanup exercise.
03 · Existing register

Start with what exists. Find what is missing.

Import an owner or contractor register first. Specset preserves its authoritative fields, enriches its entries from the specifications, and adds required packages the register missed.

Register authority stays intact. Specification gaps become visible.
04 · Register handoff

Approve the draft. Put the register into the workflow.

Select the entries you want, create the project submittals, and let the configured Procore or Autodesk Forma Build connection keep the working records synchronized.

Editable before creationExportable to ExcelBidirectional project sync
Common questions

What teams ask about the submittal log.

01How to generate a submittal log from specifications

Specset reads the project manual, confirms a submission is explicitly required, and groups practical packages with a section and paragraph citation on every row. Review the draft before anything becomes a project record.

02Submittal register vs submittal log

Most teams use submittal register and submittal log for the same list. Specset builds that cited list from the project specifications as a reviewable draft. Project records are created only after your team approves the draft. An owner or contractor list you already have can be imported, kept, enriched from the specifications, and filled in where it missed a required package.

03Is this just a search for the word "submittal"?

No. The agent reads each assigned section in context, follows requirements that span pages, and confirms a submission is explicitly required before it writes a row. Every entry keeps the section and paragraph citation that justifies it.

04Can it start from the register we already have?

Yes. Import an owner or contractor register first and Specset preserves its authoritative fields, enriches its entries from the specifications, and adds the required packages the register missed. You see what came from where before anything is created.

05Can we control how packages are grouped and numbered?

Yes. Packaging, numbering, scan scope, and level of detail are set with plain-language instructions, and the agent applies them while it reads. Controls diagrams, points lists, and sequences can land in one package if that is how your reviewers want to receive them.

06Where do the records end up?

Wherever your team manages submittals. Approve the draft and create records in Specset, or push them to Procore or Autodesk Forma Build and let the connection keep the working records synchronized.

07What specification formats does it handle?

MasterFormat project manuals, plus non-standard formats like Caltrans, WSDOT, FDOT, UFGS, and BNSF, including special provisions amended into standard sections. The log is built from the conformed record, so amendments are already applied.

08How editable is the draft?

Fully. Every entry can be edited, removed, or exported before creation, and nothing becomes a project record until your team approves it. The draft is the starting point, not the decision.

Related workflows
All use cases →
07Any phase

Spec intelligence

Merge the base spec, every addendum, and the special provisions into one conformed text per section. Search it, scan it, and cite it to the paragraph.

Manual + addendaConformed, cited set
Explore spec intelligence
08Bidding

Bid screening

Extract every opportunity from bid boards and notices, then read the full invitation. Damages, bonding, set-asides, and schedule risks come back cited before the go / no-go.

Invitation + noticesCited risk screen
Explore bid screening
09Preconstruction

Contract review

Work the agreement, conditions, and special provisions through a systematic checklist. A severity-flagged review table puts the contractor-unfavorable clauses on the table, cited.

Contract setFlagged review table
Explore contract review
Start with a project manual

Build the register before procurement starts.

Give Specset a recent project manual and your packaging conventions. We'll show you the cited, editable register it produces.

Get in touch →Book a demo