What's new in September 2026

Clicking a name in the Submittal Log left the log for the submittal page, so checking one entry's review history meant finding your place again. A row click now opens the entry's details beside the log, like the RFI and Change Order logs. The submittal's name at the top of the details still takes you to the submittal.

Bookmarks you added to a control narrative or drawing set disappeared when the package compiled, so a reviewer lost the map you built. Uploaded documents, manuals, and drawings now keep their bookmarks in the compiled PDF, nested under the document's name, or directly under its section when it is the only document there.

Acrobat's comment list showed every datasheet highlight as a blank entry, so finding the one you wanted meant opening each page. Every highlight and strikethrough in a compiled package now carries the words it covers as its comment, so the list reads as the catalog numbers and options you marked.

The bookmarks in a compiled package started at the first section, and a part's long datasheet sat between you and its manual. The Cover, Transmittal, and Table of Contents now lead the bookmark list, and a part with several documents lists each one under its own bookmark, the same way in submittals and O&M manuals.

A part number like OM1LCSTDX never appears whole on a fiber patch cable datasheet, so highlighting came back empty and the options went unmarked by hand. Highlighting now reads the number as its options and marks each chosen value in the options table, in the right column. Each one is checked like a catalog-number highlight and listed by the words it marks.

The import review said four items would be removed without naming them, and Replace or Sync on a submittal with subgroups landed the new list beside the old one. The review now names every entry Replace deletes, every shared group it takes out, and every Sync update with its old and new value. Sync updates parts inside subgroups where they sit. An empty submittal just shows Import.

Every package opened its sections with the same gray divider and printed the same footer, whatever your cover looked like. Settings > Package design now edits all three together. Draw your own section page with the section title, number, and tab, and set the footer's left, center, and right text, such as "Page 3 of 48". The list shows each design's cover and section page side by side. The editor fills the window, with a zoom and one panel for layers and properties. Package layout is now Package contents.

A long project name printed on top of the line below it, and the Color band heading did the same at any length. Cover text now shrinks to fit its box, and a name too long even at the smallest size ends in "...". In the editor you can drag a text box taller, and designs you made earlier keep their text sizes without a resize. The Color band prints your package type instead of an O&M title on every package. Saving a cover recompiles every project that uses it. The built-ins are now Left aligned, Centered, and Color band.

Your covers could carry your logo and nothing else. Now each project can hold a photo, such as the building you outfitted, and every built-in design prints it below the title. Set it in the project's settings drawer. In Settings > Package design, place an image on any cover or section page, either that project photo or one picture that prints on every project.

When Submittal Kit shipped an update, every open tab reloaded within about a minute and a half and took whatever you were typing with it. Your page now stays put, and the update loads the next time you move to another page. A record whose refresh fails for a moment keeps what you were reading, with Could not refresh and Try again, instead of saying it is gone. A reviewer's page keeps their typed response through a dropped connection.

A compile or a document read that was working when we shipped an update could fail with nothing wrong in your submittal, and you had to start it again. Work that is already running now gets time to finish before the update takes over: two minutes for a compile, which is several times the slowest one, and five for everything else.

An Undo toast vanished after five seconds, often before you could tab to it. It now stays ten seconds and holds while your pointer or focus is on it. Search previews for a part list its documents by name again. Selecting text in a dialog no longer closes it when you release over the backdrop. Building the sample project says it is building, and the mobile menu and an entry's Move menu close on Escape.

Clicking Monthly or Annual on Billing ended on an error page, so no one could subscribe. Checkout now opens Stripe, and coming back says "Your subscription is active" instead of the old trial. Subscribing mid-trial keeps the days you have left, annual shows the founding price while spots remain, monthly plans can switch to annual, and a failed checkout says why right on the page.

A forwarded invite used to sign its holder in for a year, and a removed member could rejoin with bob+1@ at your domain. Invite links now last 7 days, sending a new one cancels the old, and removal covers every plus alias of the address. Reviewers on a share link can add up to 10 colleagues, 5 an hour. Signup marks each field that needs fixing, and the connect screen for an assistant names the site it sends your access to before the name the tool gave itself.

A spec book that was mostly digital but carried a stretch of scanned pages, such as a scanned addendum, kept those pages out of search and out of the register read, so their sections went missing. Now any document with ten or more pages that have no text gets those pages read, however long the book is.

Searching inside your library's documents could take a second or two in a large library, and a long spec book or manual could be missed by searches that match on meaning. Content search now reads an index instead of every page, and long documents are indexed in full. A document that fails to index no longer holds up the others waiting behind it.

Cloning equipment from another submittal deleted the shop drawings you had already uploaded, and a BOM Replace on a project with a punch list failed or cut punch items loose from their equipment. Clone now keeps each upload in its section, and Replace keeps any entry a punch item points at and names it on the review. Uploading an outside RFI works while a draft is open, a stalled RFI PDF no longer hides Rebuild, and stamps and completion dates use your day, not the server's.

Drafting a cover note or a punch response sometimes failed and asked you to type it yourself, because the drafter spent the short reply's room on its own notes first. Those drafts now answer directly. If drafting stalls, the draft gives up after about 20 seconds instead of holding the page.

Dropping a BOM onto a submittal that already listed equipment said "Reading the BOM" and then showed nothing, leaving the import waiting on the Equipment Register. The review now opens right there on the submittal, and starting a second import asks before it replaces the one in progress.

Deleting a project that had never been issued failed once anyone had moved a milestone on its schedule or started a BOM import into it, so test and duplicate projects stayed on the list. Delete now removes the project with its schedule history and imports.

A datasheet shared by several parts showed a row of equipment names printed over the vendor's header, so a reviewer couldn't tell which highlight belonged to which part. Every highlighted page now opens with a legend band: each highlight color beside its part number and tags. The vendor page sits below the band rather than under it, and the colors stay distinct for color-blind readers.

A group's BOM export read like the whole project's: no group name in the title and its own parts under no heading. It now names the group and heads every table, and re-imports as that group. A submittal's equipment list gains Export BOM beside Import BOM, and its source documents ZIP opens with the same workbook, so the parts list travels with the datasheets.

A spec check asked you to look at requirements the datasheet answered plainly, when the answer was one number in a table with a column for each model, such as "Local I/O modules, max" of 16. Those rows now land as Meets or Doesn't meet, with the page quoted like any other.

Importing a punch list from a CSV showed your rows, then added nothing. A CSV import now adds every row, the same as a spreadsheet. A row whose status your company does not use starts at your default status, the one a newly logged item takes, instead of whichever status happens to be first in your list.

Owners want an Asset Table and a Maintenance Plan at closeout, and filling them in meant retyping every tag and task. Turn on Closeout fields in the Equipment Register to give each tag a line number, serial, process and in- service date, then download both sheets in one workbook. Maintenance tasks now belong to each part, with frequency, materials, skill and hours you can edit on the part's page.

Product names, descriptions and part numbers no longer end in "..." in a compiled package. The Bill of Materials, Equipment Schedule, Maintenance Schedule and Table of Contents wrap long text, and each item's full configuration prints on its own line. The Bill of Materials follows your Register's groups and lists each item's tags. An Equipment Schedule row counts only its own tag, so a pair of sensors no longer reads as four. The O&M's Table of Contents lists each product once, with no separate rows for its manuals.

When Find Documents could not save a document it found, that link was treated as rejected and never offered again, even on a later search. A link that failed to save is now left out of that search only, and your next search tries it again.

Some owners want an O&M Manual with manuals only, and leaving datasheets out meant rerouting them by hand. In Configure sections, the equipment row now shows Datasheets, Manuals and Configuration summaries as toggles with their counts. Click one to leave that kind out, and it stops counting as missing. The Cover, Transmittal and Table of Contents now sit locked at the top, where they always print.

Clicking an upload zone, or its browse files link, did nothing, so the only way to add a file was to drag it in. Both open your system's file picker again, on every upload zone in the app.

When one datasheet covers a whole product line, a part's suggested product name used to come back as the family title, so a CM444 read as Liquiline CM442/CM444/CM448. Describe now names the model the catalog number orders, such as Liquiline CM444 Multichannel Transmitter, using only words the datasheet prints. Regenerate a part's description to pick up the new name.

After a parts import, most manuals still had to be linked by hand, and a few suggestions named the wrong product. Accept all now links each part's first datasheet and first manual. A document that prints the part's whole catalog number is offered first, with the page it prints it on. Matching ignores a distributor code such as the A/ on A/AFS-460, reads ACI as Automation Components, Inc., and handles placeholders like AF..24-SR. A short prefix such as FS no longer suggests a document naming another manufacturer.

A manual reused from another job still printed that job's name on every page. Draw a Redact box over a header, footer or stamp, from the document page or the part's annotate editor, and every package compiles without it. The text and images under the box are removed, not covered, and the library keeps the original file. As compiled shows the result before you ship.

Owners ask for a table of every maintenance task and how often it is due, and building one meant reading every manual by hand. Each manual you add is now read once for its maintenance tasks, intervals and page references. New O&M Manuals include a Maintenance Schedule section built from the manuals in the package. Download it as a spreadsheet for the owner's maintenance system, and fix any task on the manual's library page.

An O&M printed your equipment three times: in the schedule, the BOM, and a table of contents with one line per station, so a switch at five stations took five lines. The contents now list each product once with its tags, and section dividers show totals instead of a cut-off list. New O&M Manuals start leaner: one Bill of Materials by station with manufacturer contacts, no transmittal page since the contractor sends its own, and no empty Overview or Studies sections.

A vendor's datasheets usually arrive as a folder, sometimes one folder per manufacturer, and an upload zone would only take loose files. Drop the folder itself now: every file inside it uploads, subfolders included, and files the zone doesn't take are skipped.

Cleaning up a library after an import meant deleting one row at a time. Check rows in Parts or Documents, or take the whole page, then select every row your search and filters match. Delete shows what it will skip first: parts still on a register, quote or purchase order stay, and linked documents stay unless you choose to unlink them.

Picking a firm on a new RFI slid the form up under your cursor. It now holds still. The Submittal Log names each section a revision added or dropped, and a linked spec section reads as linked before its first check. The Budget calls a change order CO-004, as the log does. The Dashboard stops offering to issue a package you already sent. A redline no longer reads Not started, and a compiled package no longer expires by itself. Evening covers and created dates stop showing tomorrow.

Deciding what to buy meant trusting a vendor's own comparison, and every one of them ends the same way. The new Compare page sorts the field by the problem you actually have: routing approvals, building the package, or drawing the panel. It names Procore, Autodesk, Bluebeam, eSUB, Trimble, EPLAN and the rest, says which of them beats us and when, and carries a section on when Submittal Kit is the wrong choice. Linked from the footer.

Seeing how Rev 0 came back, or recording that it did, meant leaving the submittal for the Submittal Log. Each row in the submittal's Revisions and reviews list now shows what was sent on the left and how the review went on the right: the outcome, the return date, the returned document and the comment count. The newest revision opens to the full record, so the outcome, dates, notes and returned document are recorded right there. The log's drawer shows the same record.

Expanding a punch item in the comment log, or posting a comment beside one, could take the whole submittal page down to an error stamp. The response box now waits out the moment its editor is being replaced instead of reading one that is already gone. A load that met the server mid-restart also gave up on the first try; it now tries twice more over the next few seconds before reporting.

A brochure whose sections all read as one bulletin number, "1492-" six times over, pre-checked every unlinked 1492 part in your library onto the first section, breakers onto a terminal-block sheet. A section that cannot tell its own parts from a sibling's now keeps only the parts already linked to it, and a part's suggestions come only from the most specific family in your library. A sheet whose families all sit on the same pages no longer offers to split into one datasheet, which was the sheet itself; it offers the links. Brochures are read again with the change.

A part with no manual waited for someone to find one, and a part's datasheet suggestions showed only on its library page. Manuals are now read for the families they cover like datasheets, so a part missing one is offered the manuals that match, each row saying which it is. The suggestions now show on the equipment entry page and inside the submittal equipment drawer as well, and Link works from any of them.

A file saved as legacy .xls or as an Excel template used to bounce off an import with a request to re-save it. The SOV, BOM, punch list, comment log, change order log and schedule imports, and quote intake, now read both alongside .xlsx and .csv. Formats that can carry macros (.xlsm, .xlsb) are still refused, re-save those as .xlsx first.

A part's suggested product name could come back as the whole ordering-table specification line, semicolons and all, which is no name for an equipment schedule. Describe now asks for the short name the manufacturer prints on the cover, such as 1279 Duragauge Pressure Gauge, and drops anything longer than a few words. Regenerate a part's description to pick up the new name.

Loading a master parts list meant importing it into a project register and living with the equipment entries that came along. The Parts page now has an Import button. Drop a CSV or Excel file, place any manufacturer names the library does not know, and the review shows which rows are new, which are already in your library, and which the file repeats. Import creates the new parts and leaves everything else as it was.

A 132-page selection guide used to ship whole or one page, and every imported part waited for someone to find and link its sheet. A datasheet now records which product families it covers. A brochure covering several offers to split into one datasheet per family, moving the parts that match. Any part with no datasheet is offered the documents that cover its family, on its page and on the import summary, and Link does the rest.

Finding the parts that share a catalog number, or the uploads that read the same as a file already in the library, meant paging through every row for the Duplicate chip. Both libraries now have a Possible duplicate filter. On Parts it keeps the parts whose catalog number matches another part's after ignoring case and punctuation. On Documents it keeps the uploads still carrying a look-alike offer, so you can keep the original or keep both from one list.

Once you had read a notification there was no way to get it off the list, so the feed only ever grew. Every row now has an X at its right edge: press it and the row leaves your feed and your count for good, with Undo in the toast for a few seconds. Clear all empties the tab you are on. A clear is yours alone; coworkers keep the row, and it comes back for everyone if something new happens on that item.

When several people follow a project, nobody knows what a coworker or a reviewer did since they last looked, and two people end up filing the same response. Notifications, under Workspace, lists every event on the projects you follow: a reviewer responded, an RFI was answered, a coworker issued or closed something. Each row shows who has already opened it and lets one person say "I've got it", which also shows on the Submittal Log and RFI log rows. Your own actions never notify you.

The purple "Finish & send" chip sat next to blue links and read as one more thing to click, not as something waiting on you. Anything on your desk now fills warm: apricot when it is your open work, deeper orange when a reviewer has sent it back, red when it is blocked. Cool blue and green still mean it is out of your hands or done. Every chip and badge across the logs, the register, settings and the changelog now prints its label in the same dark ink at the same size, so a status reads at a glance for anyone whose colour vision does not separate the tints.

Most of the office knows a job as "Dunedin", not by its number or its forty-word title, so the board's job numbers meant little and the line under them ended up carrying the name by hand. A project now has a short name, set once in its settings or from the whiteboard, and every cell, block and TV row prints it. A line on a person's row is now a project, a note, or both: pick the project and leave the note blank, or type what they are doing on it underneath. Nothing truncates.

A long project name or job number made one person's row ragged against the next, and a fourth item hid behind "+1 more" even with room to show it. Items now sit in equal cells, three to a line, with the job number above the label, and the person's position reads under their name. In the app a row wraps to show everything; the TV still keeps to one line.

Scanning the board for which projects are moving meant reading every person's row and adding it up. By project, at the top of the whiteboard, turns the rows round: one block per project with everyone on it, headed by the job number, name, phase and a one-line note that says who set it and when. Tap the block to set the phase or note; every open board and TV for the branch updates as you do. Each paired TV picks its grouping on the Branch Locations page: by person, by project, or both in turn.

A reviewer's stamp came back as a scan and their comments as an email you retyped. Now the share link opens the package in a viewer where they mark the exact spot each comment is about, state the outcome, attach their PDF, and send. It waits in the revision's drawer until you accept it, which files the PDF, their marks and their comments in one click. After the next revision they see your answers and close or re-raise each one. RFIs share the same link, with a typed answer and what it does to the work.

Giving someone a whiteboard group without a branch put them on no board while the roster still showed the group as if they were listed. The roster now says "Not on a board: no branch" until a branch is set. When your company has a single branch, adding a person starts them on it, so picking a group is all it takes to put them on the board.

A reviewer's response from the share link, or the comments read from a returned PDF, used to sit inside the Submittal Log drawer until someone happened to open it. Now the Submittal Log link on the project page, the log row and the top of the submittal page all wear a ↩ mark while an entry needs you: a review to accept, comments to file, or an outcome to record. The submittal page lists each one with its action beside it, so you act from where you already are.

If the worker behind a spec check stopped partway, the band kept counting up for hours and Stop answered that nothing was running. A check that has gone quiet for fifteen minutes now reads as failed, says the worker stopped before it finished, and offers Run again.

A PDF dropped into Shop Drawings, As-Built Redlines, or any section other than a custom uploads one counted in the header but never appeared below the drop zone, so it could not be opened or removed. Every section that takes uploads now lists its files with a delete control. The drop zone also says PDFs only, which is what these sections accept.

When a page failed to load, all you got was a bare "Something went wrong" box with a status code in it. A page that cannot open now comes back stamped the way a submittal does: not found, no access, or rejected, with a line that says what happened, Try again and Go back, and a Copy details button that gives support the reference to find it by. Nothing internal is shown.

Deleting an entry from a submittal failed with a bad request whenever that entry had been scoped in from the register or shared from another submittal, even though the row sat right there in the workspace. The only way out was the Equipment tab. Delete from the row, the selection, or a quantity of 0 now reaches every row the submittal shows.

Removing one entry from a submittal meant opening its settings and finding the button at the bottom, and the confirmation for a selection had its text jammed against the edge. Now the row's own drawer has Delete next to Edit entry, setting a quantity to 0 asks the same question, and the confirmation reads like the rest of the app: what else the entry feeds, which documents it carries, and a clear Cancel.

Who is on what lived on a wall and in a group text, so the shop floor and the field never saw the same board the office did. Now each branch has a whiteboard: people from your Personnel roster, grouped Office, Shop and Field, each row listing what they have on their plate with the project and how long it has been there. Edit it from your phone; it updates everywhere at once. On the shop TV open submittalkit.com/tv, press Pair a TV on the branch, and type the six character code. No sign-in, nothing long to type.

A review or RFI response that slipped past its expected date only showed up if you opened the dashboard that week. Now the morning after it goes overdue, you get one email listing every late item across the projects you follow, then a weekly reminder until it comes back. Turn it off under Settings > Account without unfollowing anything.

A prospect could read one Pro price in the help centre, another in the trial reminder, and a third at checkout. Every surface now says the same thing: $299 per month or $2,990 per year, with no per-package or per-seat cap. The billing article also says plainly that Spec Check waits for a plan, so a dark button during the trial reads as policy, not a defect.

An agent connected by someone who later left your company could keep its token until it expired. Removing a member now revokes every agent they connected, and a deleted company revokes its whole team's. Your Account page lists what each connected agent was granted, so you can see at a glance what it may read.

A very large file dropped on an RFI, a submittal section, an equipment entry, a revision, a redline, a scope document or a schedule import was read whole before anything checked its size, which could tie up the server for everyone. Those uploads now stop at a stated limit: 100 MB for attachments, the same the library already holds you to, 20 MB for imports and 250 MB for scope documents. An oversized file is refused with the limit named and nothing is stored.

From a submittal page, jumping to the project's Punch List or Budget meant going back to the project and finding the row in the records band. With a project open, the command palette now lists its Equipment, Submittals, Scope and Specifications tabs and its Schedule, Submittal Log, RFI Log, Punch List, Change Orders, Contacts, Procurement and Budget records. Type the page name and go.

The Terms of Service told you an administrator had to approve a workspace request and that a card would be charged when the trial ended. Neither has been true since signup went self-serve. The Terms now say what happens: you sign up, confirm your email, and a 14-day trial starts with no card. The Privacy Policy now covers the equipment lists you send through the sample package form, how long they are kept, and how to have them deleted, and it names Sentry, the error monitoring service, among the providers we use.

Searching for how to write a transmittal, how to answer review comments, or what 01 78 23 demands of an O&M manual used to turn up one sentence inside a bigger guide. Ten new field guides on /learn take each on its own: transmittals, shop drawings versus product data, sequencing against lead times, UL 508A, I/O lists and loop drawings, substitution requests, answering review comments, the comment that is really a change order, reading 01 78 23, and punch list to retainage. Written from real spec books, useful whether or not you use Submittal Kit.

Reading a help article from the keyboard meant tabbing through the nav and every article in the sidebar, around fifty links, before reaching the text. The help centre, guides, feature pages, changelog, ROI worksheet and legal pages now open with a Skip to main content link. It stays hidden until you press Tab, then one Enter lands you on the page body.

Forgot your password, signed in by email link, and the password page still asked for the one you forgot. After a link sign-in the page now skips the current password once, so you can set a new one and go back to signing in directly. A password sign-in still asks for the current one.

A scope import refused for a used-up allowance stored a note about the company's budget and the mechanism behind it, and a spec check refused for the same reason said only that something was unavailable. Both now name the help that stopped and the next step: the reading allowance is used up, nothing was imported, try again once it resets.

A few links landed you on an address built from the project's internal id instead of its job number: the punch-list link from a log entry's comments, the RFI a change order grew out of, the projects a library document is used in, and the equipment register's rows. The address bar, breadcrumbs and recents then disagreed with every other page in the project, and a pasted link looked like a different project. Those links now name the project by its job number, as the rest of the app does.

A screen reader user had no signal when a compile, register read, document fetch or spec check started or stopped; the progress row was silent. The row now announces its sentence when a job is queued, starts working, finishes or fails, and stays quiet through the ticks in between.

Tabbing through Procurement landed on the open view and skipped Purchase orders and Quotes, so without a mouse there was no way to reach them. The left and right arrow keys now move between Coverage, Purchase orders and Quotes, Home and End jump to either end, and focus follows the view you picked.

Setting up the company's standard Product Data package meant working out Package layout by trial. The help centre now has a Package Layouts article: built-ins and your own library, Clone, one default per type, editing sections and document requirements, custom submittal types, and why a layout is copied at creation. The ? on the Package layout page opens it. Configure sections now covers the transmittal's cover note and Draft note, and the cover page article names the {cover_note} token.

Any member could change the company logo or brand colors, and a colour change sent every compiled submittal in the company back for a recompile. Both now follow the company name: admins change them under Settings, Identity & brand, and members see the current logo and colors on the brand proof card without the controls. The server refuses a member's change even when the page is bypassed.

A project name with a quote, a dash or a non-Latin letter made the RFI log, change order log, punch list and punch record downloads land with a garbled name and no file extension. Those exports now download under a clean filename built from the project name, the way the submittal log and schedule exports already did.

A long read kept the lamp blinking and the rail sweeping for as long as it ran, and on a high-refresh display that cost a fan's worth of GPU for a compile or a returned-document read. The lamp now holds its fill and a read with no count parks a short segment at the start of the rail. The sentence and the clock still change as the job moves, and Stop is where it was.

Typing a button label into help search, such as Mark as Submitted, Run spec check or Import BOM, came back empty because search only read article titles, summaries and section headings. It now reads the whole article, so a word that only appears in the body, like transmittal, ball in court or xlsx, finds every guide that covers it. Title and heading matches still rank first. This applies to the help centre's search and to the Help group in the command palette.

The founding counter on the pricing page dropped a seat for every paid company, including monthly and Enterprise plans that never took the founding terms, so it could close the window with fewer than 20 founding members. It now counts only annual Pro subscriptions, the ones the founder discount applies to.

A screen reader landing on the Add Item form, the submittal quick-add row, the parts library search, the move-to-group menu, personnel and contact fields, or the markup page box heard only "edit text". Each of those fields now carries its label, so the reader says what the field is for and keeps saying it after the placeholder disappears.

A field guide ended with a bold disclosure heading and a button to the price list, so a reader who finished the highlighting guide had no path to the highlighting feature. Each guide now closes on the disclosure as a plain paragraph and links to where its topic lives: the feature page and the help article, right under the previous and next links.

The field guides speak in the first person, but nothing on the page said who was talking. Each guide now names Jeremy under the title, and the page metadata carries the author, the date it was first published, and the share image, so search results and link previews show the same thing.

The CSI divisions guide sent you to 40 61 through 40 79 for process control, and a 2010-era book has nothing there. The guide now says where that scope sits in 2004 through 2012 editions (40 90 00 through 40 97 00) and that a 2014 or later book reuses 40 90 00 for control valves and drives. The resubmittal rates article corrects one job's age, and the three closeout guides stop repeating each other's passages when you page through them.

A change order row with a problem, a skipped BOM line, a pending scope step and a revoked share link were faded to the point of being hard to read, right where you had to read them. Those rows now use a darker secondary ink instead of a fade, and the change order import spells out the unrecognised status in the row instead of hiding it in a hover. The Annotate layer now opens as a true dialog: Tab stays inside it, Done hands focus back to the button that opened it, and Escape still returns the editor to the select tool.

Marking a clean package as submitted ended on a button that read Submit anyway, as if you were overriding a problem that was not there. The button now says Mark as Submitted, and says Submit anyway only when a check or a missing required document is listed above it. Withdrawing a revision from the Revisions list asked with a button that read Delete; it now reads Withdraw, the same as the Submittal Log.

Answering a returned review's comments was the one resubmittal job the help centre did not explain. The new Comment Response Log article covers reading the rows, the three ball-in-court states, Next unanswered, answering in place with the draft that appears while you type, leaving a comment out and bringing it back, and how the log prints. A ? beside Next unanswered opens it from the submittal page.

The Billing and Plans help article and the trial ending email quoted a Pro price half of what checkout charges, so an admin about to subscribe saw one number in the article and another on the Billing page. Both now state $299 per month or $2,990 per year, the same figures checkout and the pricing page show.

Removing someone from Team & access dropped them from the roster, but a fresh sign-in with their password or a sign-in link put them straight back in, because any address at your domain joins on sign-in. Removal now deactivates the account: their sessions, passwords, sign-in links and agent tokens stop working until an admin invites them again from the same page.

A spec check, register read, scope import or description showed one sentence and a clock for the whole call, so a long think looked like a stall. The job row now says whether the call is waiting, reading or producing, and counts what has landed: rows judged, demands or equipment listed. Spec check rows appear in the panel as they land, marked not final, until the findings replace them. Stop reaches a call in flight within a second, keeps what was read, and records only what was spent. The returned document read and the library search gain a Stop.

Both panels on the Submittal page were small to read and fiddly to click. The spec check now arrives folded, lists only the products the filter keeps, each with its counts and one whole-product control on its header, shows what the datasheet said on each row, and marks a row in place. The Comment Response Log shows what they said and whether you have answered on each row, opens in place to write the response, and sets status, severity, category, source and acceptance without leaving the page. Configure sections is a plain button on the sections' own line.

A submittal tied to a spec section can now be checked against it. Press Run spec check and the section's requirements are read once and kept on its workbench pane; then every datasheet on the submittal is judged against the rows that apply to its part's category, a few datasheets at a time, with the job row counting them down and a Stop that keeps what has been read. Each requirement comes back as Meets, Does not meet, or Look at this, with the value the datasheet states, the page it is on, and what to do next. The panel opens on the worst verdict's tab, folds rows under their datasheet, and shows a row's evidence beneath it. Mark any row yourself, or every row on a product at once, and the mark survives re-runs. Available on paid plans.

The requirement lists on the specification workbench, the compliance matrix on the submittal and the printed matrix section are gone, along with the check that judged a datasheet against them. They asked too much filing for what they answered. What a section demands you submit, the register, is untouched, and so are your claimed sections, your scope of supply and the spec links on each submittal. A rebuilt spec check follows.