Submittal reads the project manual, writes one register row for every required item, groups the rows into numbered packages, routes them through GC and design team review and keeps every revision, stamp and file until the job is closed out. Below is each part of the product as it works in the browser today, on desktop and tablet, with no install.
Drop in the full project manual as a PDF, a single division or one section at a time. Submittal finds every MasterFormat section number and title, such as 08 71 00 Door Hardware or 23 05 93 Testing, Adjusting and Balancing, and reads the Part 1 articles that call for submittals, including Action Submittals, Informational Submittals and Closeout Submittals. Scanned spec books go through text recognition first, so an older manual printed and rescanned by the owner is read the same way as a native PDF.
The AI register builder writes a row for each item the spec asks for: spec section, paragraph reference such as 1.4.B, submittal type, description quoted from the spec, responsible company, reviewer, required-by date and a lead time field. Each row links to the exact paragraph it came from, so checking the register against the spec takes a click instead of a page hunt. The full method is on the construction specification software page.
Merge two rows when the spec repeats the same requirement in 1.4.A and 1.4.C, split a row when one paragraph covers both hardware schedule and keying schedule, and assign rows to subcontractors in bulk. Set reviewers and due dates for a whole division at once. Every edit is recorded, so the submittal register keeps a clear line from the spec to what the team decided to track.
Projects already under way start from their existing log. Import from Excel or CSV, map your columns to the register fields and keep your own item numbers. Rows imported this way sit next to rows built from the spec, and you can run the spec import afterwards to see which required items the old log never captured.
A package bundles the rows a subcontractor submits together, for example the door hardware schedule, product data for locksets and closers and the keying schedule under 08 71 00. Attach product data sheets, shop drawings and sample photos to the package, not to loose emails. The transmittal is generated from the package, with every attachment and its revision listed.
Packages follow the section, sequence and revision pattern, for example 087100-002-R1 for the first resubmittal of the second door hardware package. On Team and above, custom numbering lets you match the format written into the general conditions or the owner's standard. Subcontractor portal links on Team and above let each sub upload into its own packages without a paid seat. See how numbering fits a submittal log.
A package goes to GC review first, then to the architect and the consultants named on the row, such as the MEP engineer for 23 05 93. Reviewers comment and mark up each page in the browser and return one of five stamps: Approved, Approved as noted, Revise and resubmit, Rejected or For record only. Informational items like test reports usually go straight to For record only.
Revise and resubmit creates the next revision of the package with the previous comments attached, so the sub sees exactly what to fix and the reviewer sees what changed. External reviewers and subcontractors join a paid project at no cost on every plan. The full sequence of stamps is laid out in the construction submittal process guide, and design firm reviewers have their own page for architectural submittal work.
Enter the date the material has to be on site and Submittal works back through fabrication lead time and review time to the date the package has to be submitted. On Team and above, lead-time tracking keeps the quoted lead time on each row and flags packages whose review cycle no longer fits before the delivery date.
Email reminders go to whoever holds the package right now, the sub preparing it or the reviewer stamping it, and the overdue list shows every package past its date with days late. Notifications arrive by email for new packages, returned stamps, comments and resubmittals, so nobody has to log in to find out they owe something. Status views are covered in depth on the submittal tracking software page.
Every revision, stamp, comment and file stays in the log. Open 087100-002 and you see R0 with its Revise and resubmit stamp and markups, then R1 with Approved as noted, each with the date and the person who returned it. That record answers the question that comes up during installation and again at closeout: which version was approved.
Each project holds companies (the GC, the subs, the design team) and people with roles: admin, project engineer, subcontractor, reviewer and viewer. Internal members are 5 on Starter, 25 on Team and unlimited on Business and Enterprise. Business and Enterprise add SSO, an audit log, API access and priority email support, and Enterprise adds US data residency, custom retention and an SLA. Details on how data is handled are on the submittal software security page, and plan prices are on submittal management software pricing.
Yes. Starter, Team, Business and Enterprise all include the register builder, packages, the review workflow, reminders, version history and exports. Plans differ in active projects, spec pages read per month, internal members and the added features listed above.
Yes. Subcontractors and external reviewers join a paid project at no cost on every plan. On Team and above they get portal links that open only their own packages.
Every row shows the paragraph it came from, so gaps are visible when you read a section next to its rows. Add a row by hand, merge duplicates or split a combined item, and the edit is recorded in the history.
No. Submittal runs in the browser on desktop and tablet, and notifications arrive by email.
Save this submittal log and open the full register.