It reads requirements, not keywords.
The agent follows paragraphs across pages and distinguishes an actual submission requirement from a passing reference.
Build the submittal register the specifications actually require.
Specset reads the project manual, interprets each requirement, and groups practical packages with citations. Review the draft, then create the records your team will manage in Specset, Procore, or Autodesk Build.
Submittal logAI analysis
ExportCreate selected
✦
Project manual scan complete
Ready to reviewSeparate product data from shop drawings. Group controls diagrams, points lists, and sequences into one controls package.
Submittal #Section · paragraphTitleSourceType
✓03 30 00-00103 30 00 §1.5.AConcrete mix designsSpecificationProduct data
✓08 71 00-00108 71 00 §1.4.ADoor hardware scheduleRegisterShop drawings
✓23 09 00-00123 09 00 §1.3.BControls diagrams, points list, and sequencesSpecificationShop drawings
23 36 00-00123 36 00 §1.3.AAir terminal product dataSpecificationProduct data
23 36 00-00223 36 00 §1.3.BAir terminal shop drawingsSpecificationShop drawings
26 05 00-00126 05 00 §1.7.CElectrical closeout documentationSpecificationCloseout
3 selectedDescriptions and citations remain editable
Built the way reviewers receive the work.
Related requirements consolidate while product data, shop drawings, samples, and closeout packages stay distinct.
A draft before project records.
Edit, remove, export, or select entries before the approved log becomes the working register.
Trusted by the teams delivering public work
“The log that used to take a week of reading came back the same afternoon, with the governing paragraph behind every row.”
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.
Specification sourceSECTION 23 36 00AIR TERMINAL UNITS
1.3.A
Product Data: Rated capacities, performance, sound power, and accessories for each type.
1.3.B
Shop Drawings: Air-terminal schedule, room locations, sizes, and accessories.
1.5
Closeout submittals include operation and maintenance data.
Agent reasoning
READInterpret the whole sectionNot a search for the word “submittal”
- 01 Follow requirements across pages
- 02 Confirm the submission is explicit
- 03 Group work reviewed together
- 04 Cite the governing paragraph
Practical packages01 02 03
Air terminal product data23 36 00 §1.3.A · Product data
Air terminal shop drawings23 36 00 §1.3.B · Shop drawings
Air terminal O&M data23 36 00 §1.5 · Closeout
Separate lifecycle packages. Consolidate related requirements.
Requirements can span pages.
The agent keeps the surrounding section in view.
Grouping requires construction judgment.
One practical package can draw from several paragraphs.
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
Submittal Log AgentRidgeview CenterRunning
Scan scope
SpecificationsDivision 23
InstructionsKeep product data and shop drawings separate. Group controls diagrams, points lists, and sequences together. Create separate closeout packages. Follow our section-based numbering.
Natural-language project conventionBreak out samples separatelyScan only Divisions 08 and 09Preserve the owner's numbering
Draft registerApplying project instructions
Live artifact01
Controls diagrams, points list, and sequences23 09 00-001
Grouped02
Air terminal product data23 36 00-001
Separate03
Air terminal shop drawings23 36 00-002
Grouped04
Air terminal O&M data23 36 00-003
Separate03 · 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 reconciliationExisting register + specification scanNo duplicates
Existing registerPreserve
→Numbers, titles, dates, status, and revisions remain authoritative.
Specification verificationEnrich + complete
→Add descriptions and citations. Identify required packages not logged.
Reviewable resultOne clean draft
Every row shows where it came from before anything is created.
Submittal #PackageReconciliationSource
08 71 00-001Door hardware scheduleCitation added · §1.4.ARegister
23 36 00-001Air terminal product dataDescription enrichedRegister
23 36 00-002Air terminal shop drawingsRequired package foundSpecification
23 36 00-003Air terminal O&M dataRequired package foundSpecification
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 Build connection keep the working records synchronized.
Reviewed draftSubmittal log
✓
Air terminal product data23 36 00-001 · cited
✓
Air terminal shop drawings23 36 00-002 · cited
✓
Air terminal O&M data23 36 00-003 · cited
Create selected submittals →
ReviewCreate
S
Project recordSpecset submittalsEditable records, source citations, dates, types, and status.
SyncUpdate
ProcoreConnected project
Autodesk BuildConnected project
Editable before creationExportable to ExcelBidirectional project sync
Common questions
What teams ask about the submittal log.
01Is 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.
02Can 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.
03Can 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.
04Where 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 Build and let the connection keep the working records synchronized.
05What 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.
06How 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.
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.