submittals

Open Dashboards in any project's sidebar to see where the project stands this week. Each section starts with four dashboards: Project status (what is overdue, what was approved, and who holds the open work), Submittal tracker (ball in court, closures per week, spec divisions, and submittals at risk of holding up the work), RFI tracker (age, managers, and cost or schedule impact), and Design review issues (severity, discipline, and reviewer feedback). The organization's Dashboards adds a Portfolio overview of every project, most overdue first. Each dashboard reads your data as you, so people see only the records they can already open.

Every number leads to its records. Click a tile such as Overdue RFIs, a bar for a manager or a week, or View all under a table, and the Submittals, RFIs or Issues list opens with exactly those filters applied. Long tables show 10 rows with a Show more button.

The RFI and submittal lists gained the filters these links use, so you can apply them yourself too: Overdue, RFI cost or schedule impact and created dates, and submittal spec division and closed dates.

Want something else on screen? Click New dashboard and describe it. The agent builds it as a draft, and Managers and Admins publish it to the section. See Dashboards.

Stop redrawing the marks you make on every review. Select a check mark, a note, a revision cloud, or a group of marks in the PDF viewer, then choose Save markup, the bookmark icon in the menu that appears beside your selection. Give it a name, and it's ready for any page of any document, including Annotate & Download on submittals.

To use one, choose Apply markup in the viewer toolbar and pick a card. A faint copy follows your cursor; click where it belongs to place it. It lands at its saved size as a regular markup, so you can still move, resize, or delete it, and Undo takes it back. Press Esc to cancel.

Saved markups are yours alone until you share them. Turn on Share with your team when you save or edit one, and everyone in your organization can apply it, including people who aren't on the project you saved it from. Markups your teammates share appear under Your team with their initials. Use the pencil on your own cards to rename one or change its sharing; organization managers and admins can also remove shared markups.

Finish your markup and record your review response in the same step. Under Org Settings → Stamps, add or edit a stamp and choose its Submittal approver status, such as Approved or Revise and Resubmit. Existing stamps can be mapped without uploading them again.

Apply the stamp from a submittal's Annotate & Download view. The placement preview shows an enabled switch to update the approver status, with a reviewer selector when needed. After the stamped PDF saves, Specset records the response, fills an empty returned date, and updates the submittal's overall approval status based on its reviewers' responses.

Turn off the switch to place the stamp without changing a response. Stamps without a mapped status continue to work as before.

Read more in Submittal review.

Until now, review findings traveled as hoverable popups on each mark. That works in a viewer, but a flattened or printed package loses the hover, and the recipient sees marks with no visible comment. Turn on Show comments on the page and every issue also gets a red-pen style callout written on the sheet, with a leader arrow pointing at its mark.

Callouts are built to stay readable on real drawings:

• One note per issue per page. An issue with several highlights gets a single condensed callout, not a duplicate per mark.
• Whitespace-aware placement. Each callout is placed in nearby clear space, sized to the sheet. On dense pages the review skips a callout rather than stamp text over content, and busy pages are capped at a few callouts so the sheet never turns into red-text soup.
• Fully editable. Callouts are regular annotations in the Annotate & Download surface. Drag one to a better spot or delete it before the package goes out, and the change sticks.
• Popups stay. The callout carries the short correction; the complete finding remains in the annotation popup and the review record.

Enable it per project under Project Settings, Submittals, or flip the switch for a single review in the Annotate & Download sidebar, right next to the table of contents toggle. It works on existing reviews without re-reviewing; newly reviewed submittals get sharper, shorter callout text written for the sheet.

Read more in Submittal review.

Submittal reviews check a package against hundreds of spec requirements, and a review that casts a net that wide will inevitably flag some things that turn out to be fine. Until now, sorting those out was your job. Every issue a review files is now re-checked by a second, independent AI before it enters your issue list.

The verifier goes back to the package and actively tries to disprove the finding. It searches the attachments for content the review called missing, checks the submittal register for a separate package that covers the deliverable, looks for an RFI or addendum that supersedes the requirement, and reads the governing spec section for or-equal language that already permits the submitted product.

Findings that do not survive are dismissed automatically with the reason recorded, so they never cost you a click. Open a dismissed issue and hover its AI rejected badge to read exactly what disproved the finding, with citations that jump straight to the submittal page or drawing schedule the verifier used. Nothing is hidden: rejected issues stay in the Dismissed list, and one click re-opens any of them if you disagree. Issues that survive carry an AI confirmed verdict on the issue itself, with the verification evidence a hover away.

Read more in Submittal review.

Submittal reviews now cross-check every submitted product against your conformed specifications. When a product shows up in the submittal but not in the spec, the review flags it.

That catches the cases that are easiest to miss under deadline pressure: unapproved substitutions, items from a different spec section, and products that were value-engineered out but never left the submittal package. Each flag cites the spec sections that were checked, so verifying it takes one click.

Read more in Submittal review.

Submittal reviews now produce a package you can send back as-is. The new Annotate & Download action stamps every review finding onto the submittal pages and exports the annotated PDF in one step.

Reviewers stay in control of what ships:

• Editable issue marks. Move, reword, or remove any annotation before export. Edits sync back into the compiled review, so the record and the package always match.
• Review-scoped marks. Marks belong to the review that created them, so re-reviews start clean instead of inheriting stale annotations.

Read more in Submittal review.

Reviewers can now finish a review the way they always have: with the firm's own stamp on the page.

• Bring your existing stamps. Upload the same dynamic stamp PDFs you use in Bluebeam under Org Settings. Specset reads the stamp's form fields and figures out which is the date, the reviewer, the project, and which need manual input.
• One-click placement. In the document viewer, choose Apply stamp, pick a stamp, and the date and reviewer fill in automatically. Anything left gets a quick prompt.
• Stays with the document. Placed stamps persist with the document's annotations and come along in downloads.

Read more in Submittal review.

Submittal review has been rebuilt from the ground up. Instead of walking a generic checklist, the review now starts from the submittal itself: it reads what was actually submitted and generates review checks from that content, then verifies each one against your specifications, drawings, and RFIs.

• Submittal-first checks. Because checks come from the submittal's own pages, the review covers everything that was actually submitted, not just what a spec-driven checklist expects to find.
• A citation behind every verdict. A finding is only allowed to stand if it cites the governing requirement, whether that's a spec paragraph, a schedule value on a drawing, or an RFI response. Click any finding to see exactly what it was checked against.
• One review workflow. Findings consolidate into issues on a single Overview page. Step through them in the review flyout, dismiss what doesn't apply, and reopen anything later.
• Ready-to-send exports. Download the review as a marked-up PDF package with a clickable issue table of contents, or as a spreadsheet.

Read more in Submittal review.