Structured specification processing
Detect CSI sections and rebuild document hierarchy so a requirement keeps its heading and parent context.
Submittal register software
Submittal register software that starts with the project manual.
SubmittalsHQ does the first pass through the specifications, organizes the findings, and keeps the evidence beside each register item so your team can review—not retype.
Less searching. Less cleanup. Better evidence.
Actionable register entries
Turn requirements into clear action titles, submittal types, categories, and responsible-party suggestions.
Source-linked review
Open the page and paragraph behind an item. Confirm, edit, merge, split, or suppress before export.
Designed around the review
Handle the obvious items automatically. Put judgment where it matters.
High-confidence requirements can move quickly. Ambiguous language, missing actions, and grouping decisions are surfaced for targeted review. That keeps automation from hiding uncertainty.
- Filter by section, type, confidence, and review status
- Edit titles and responsibility without losing source evidence
- Review suggested merges, splits, and suppressions
- Export a clean working register
From PDF project manual to reviewed register
Upload the project manual
Start with the specification issue your team is actually using. SubmittalsHQ identifies CSI sections and prepares the document for structured review.
Rebuild document hierarchy
PDF extraction often flattens headings, lead-in paragraphs, and numbered children. The system reconstructs those relationships so requirements are interpreted with their context.
Identify potential requirements
Explicit directives and likely deliverables are collected from applicable articles—not only a section labeled “Submittals.”
Create useful register entries
Findings are organized into specific action titles with likely submittal types, categories, parties, source pages, and paragraph references.
Review the exceptions
Your reviewer validates uncertain items and considers suggestions to edit, merge, split, or suppress entries.
Export the approved working list
After review, export the register for scheduling, responsibility assignment, coordination, or import into the team’s established platform.
A better unit of work
A requirement is not always the same thing as a register row.
Specifications may repeat the same deliverable, break one package into several nested bullets, or list multiple independently prepared items under one directive. Software that converts every text match into a row simply moves the cleanup downstream.
SubmittalsHQ presents grouping decisions for review. Related requirements can be merged when they form one coordinated package. A broad requirement can be split when separate parties, timing, or review paths make that more useful.
Example: one heading, three decisions
A “Shop Drawings” paragraph may require a door schedule, elevations, and wiring diagrams. Those could be one coordinated package or separate actions depending on responsibility and sequence. The source hierarchy is preserved so the reviewer can make that decision intentionally.
The information behind a defensible entry
FieldWhy it matters
Action titleDescribes the deliverable in language the project team can understand and assign.
Section and titleConnects the action to its technical scope.
Type and categorySeparates product data, shop drawings, samples, qualifications, reports, and closeout records.
Source page and paragraphLets a reviewer return directly to the supporting requirement.
Evidence textShows the directive and context used to create the item.
Confidence and review statusDistinguishes a clear requirement from an item that needs judgment.
Responsible partyProvides a starting suggestion that the project team can confirm or edit.
Where register software saves time
The most obvious savings come from searching and data entry, but the larger benefit is reduced rework. A concise title, consistent classification, and source link mean another person does not need to reconstruct the original reviewer’s reasoning.
This is especially valuable on document-heavy projects, projects with multiple specification volumes, and teams that must create a useful register during a short preconstruction or startup window.
Where human knowledge still matters
Software cannot decide project strategy by itself. Teams still determine scope ownership, packaging, contractual interpretation, and schedule dates. They also decide how alternates, substitutions, deferred approvals, and design-assist obligations affect the register.
SubmittalsHQ is built to support those decisions with better organized evidence.
Submittal register software questions
Is this the same as submittal tracking software?
Not exactly. Tracking software usually follows packages after they are created. SubmittalsHQ concentrates on finding the requirements and producing the register that tracking begins with.
Can I edit generated entries?
Yes. Reviewers can correct titles, classifications, responsibility, and grouping while retaining the underlying source evidence.
Will it find closeout submittals?
The specification-processing workflow can identify closeout-oriented requirements as well as preconstruction and product submittals. The reviewer decides how those items should be categorized and managed.
What if the specification PDF has poor formatting?
SubmittalsHQ is designed around the hierarchy problems common in extracted project manuals. Results still require review, particularly when the underlying PDF is scanned, incomplete, or unusually structured.
See it on a real project manual
Get accessBuild a register your team can verify.
What the project team does after processing completes
The reviewer begins with the project-manual structure and the draft register. Clear requirements can be confirmed in batches by section or type. Entries marked for attention are examined individually with their source language and hierarchy visible.
For a possible duplicate, the reviewer compares both evidence locations and decides whether they describe one package. For a vague child paragraph, the reviewer confirms whether the parent supplies the missing action. For a suggested responsible party, the reviewer compares the technical scope with the project’s actual buyout. Every accepted change improves the working register without disconnecting it from the source.
Once the content is credible, the team can add project-specific responsibility and dates. That sequencing matters. Scheduling a noisy or duplicated register simply creates more administrative work.
Good fit for SubmittalsHQ
- Large or multi-volume project manuals
- Short startup windows for register preparation
- Teams that need source evidence during review
- Registers requiring significant cleanup after keyword searches
- GC or trade reviews organized by CSI scope
When a manual process may be sufficient
A small, familiar project with a short manual and a disciplined reviewer may be handled effectively in Excel. Our free template supports that approach. Software becomes more useful when document volume, authoring inconsistency, repetition, or review handoffs make the manual process difficult to control.