What's new

Pale messages in the corner were easy to miss, and a failed save often said only "Not saved" without the reason. Each message is now a bordered sheet that names its level in a word, gives the reason on a second line, and offers Retry when the connection dropped during an edit. Repeats count up instead of stacking, F8 jumps to the newest, and Recent messages in the command palette keeps the last 20.

The faded suggestion that appeared while you wrote a punch response was slow to arrive and rarely said what you meant. The response box on the punch list and in the Comment Response Log is now a plain editor that shows only what you type.

Picking a date saved the moment you touched the calendar, and typing a year saved after its first digit, so the picker closed before you had the date you wanted. Dates on RFIs, change orders, the Submittal Log, project settings and the whiteboard now save once you leave the field or press Enter. Escape puts the saved date back.

Closing a comment or recording its acceptance in the Comment Response Log moved it out of the filter you were in, and it vanished before you had set its other fields. The comment you are working on now stays open in its place, showing where it moved, until you close it or open another.

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 AI run 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 AI work.

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 AI tool 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 AI spent the short reply's room thinking first. Those drafts now answer directly. If the AI provider stops responding, 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 AI 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 AI 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 2014 editions (40 90 00 through 40 97 00) and that a 2016 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.

A background job you had just started could claim it had been waiting for weeks, because a re-run kept the clock from its first attempt. The queued and working readouts now restart with each attempt, and a genuinely long run reads as "2h 5m" instead of a wall of minutes.

A submittal of the exact parts the spec named came back mostly blank, with false not-mets on the specified modules. Now a product the section names satisfies its own article's rows, the datasheet values already extracted answer temperature, humidity, voltage and I/O in code, and ranges are compared as numbers, so "0 to 60" meets "0 to 40". The check reads the pages each requirement actually needs, a filed part is always judged, and equipment files itself from its own name. The matrix lists what needs you first, and a not-met you stand behind takes a declared deviation that prints with its reason in the package.

A PLC section against a sixty-part panel came back as sixty columns of not confirmed, because every requirement was asked of every part. Under the matrix each subject nobody answers to now asks which entry it is, File equipment walks the register once, and a requirement is checked only against the entry filed as its subject. A catalog number the section names is matched against the part itself, so a FortiSwitch submitted where the book says Stratix reads not met before a datasheet is opened. Feature requirements are rows again.

An item you add from the catalog is now called what the manufacturer calls it, and it stays that way as the catalog learns more names. The ordering code sits beside it as a chip rather than standing in for it, so a register, a submittal workspace or a search result tells you what the thing is before it tells you how to order it. Name a piece of equipment yourself and that name is yours; clear the field and it goes back to following the part.

Compiled manuals carry it too. The contents page prints the product name with the catalog number beside it, and the Equipment Schedule swaps its Equipment and Description columns for one Product column with room to print a full name, so nothing truncates. Issued Revisions are untouched.

Submittal rows are almost half as tall, because the description no longer needs a line of its own.

A catalog number like 5W5B3H meant nothing until you looked it up, and a spec that asked for an "Endress+Hauser ProMag W 500" never matched the part you actually had. Parts now carry the manufacturer's product name: it is read off the datasheet you attach, fills in for older parts with a one-time pass, shows up wherever the catalog number does, and new equipment lands in your register under its real name. Compliance checks see the name too, so a requirement that names a product can finally be met by it.

Starting an RFI used to land on a bare form: no breadcrumb, no title, and two identical-looking buttons for writing an RFI or uploading one you received. The page now opens like every other page, with the breadcrumb trail and a header that carries Preview and Mark sent. A clear "New RFI / Upload RFI" switch replaces the old buttons, the recipient comes from your project directory instead of a typed address, and the sign-off block only asks for the names that matter while drafting.

The Field Guides page was one flat list, so finding the guide for the phase you were in meant scanning every title. Guides now group the way a job runs: reading the spec, assembling the package, surviving review, then closeout. The landing page also answers the four questions that decide a trial before they become an email (time to first package, who sees your projects, what happens when you leave, portal workflows), and links shared from the site now unfurl with a proper title and picture instead of a bare address.

Picking from a dropdown inside a log's detail panel — a change order's "grew out of RFI", a punch item's classification — opened the option list somewhere else on the page entirely, and it would not always go away. The list now opens directly beneath the field you clicked, everywhere in the app, and closes the moment you pick, press Escape, or click away.

Reloading a page, or opening the package layout or cover page editor, used to white out the whole window for a moment while everything loaded again from scratch. The sidebar is now part of the page itself, so it is there the instant the window paints, and Submittal Kit remembers your workspace between loads instead of asking before it can draw anything. Opening an editor no longer reloads the app at all: it opens in place, the way moving between tabs does.

Checking a part against the specification used to read its whole datasheet, every page, for every requirement. The check now finds the handful of pages likely to answer the section's requirements and reads those, so a three-hundred-page manual costs no more than a cut sheet. Reading a part's datasheet for its description and attributes works the same way, and scanned datasheets are read through OCR instead of coming back empty. Verdicts still quote the datasheet word for word, with the page to turn to.

A section demands things of kinds of component: the CPU module's catalog number, the switch's operating temperature, and a few things of every part. Each requirement now sits under that subject, and the subject bar says which part categories it covers. The compliance check runs a requirement only against those parts, so a terminal block is never asked about the PLC's catalog number, and a subject with nothing on the register says so instead of costing a call.

Uploading a PDF used to wait while its text was read in the request, and a long manual could hold the page for a while. The upload now lands right away, the file is read in the background, and a look-alike offer shows on the document's row once the read finishes, with a way to keep the existing file or keep both.

A section that asked for twelve things offered twelve submittals, most of them procedures and notifications no datasheet answers. The pane now lists what describes the equipment, plus the O&M, and holds the rest under More suggested submittals, where they keep every answer they had. An O&M or a procedure no longer carries a compliance band or a matrix it has nothing to put in.

A curated section sets aside more requirements than it keeps, and every one of them sat in the list struck through, so the page was twice as long as the half worth reading. They now wait under Set aside, closed, with their reasons and their Restore intact. Read it again is the same button in the same place on the scope document, the requirements and the demand list.

Opening a section on the Specifications tab pulled the whole book out of storage every time, and a section with two hundred requirements sent six megabytes of page to draw a list. Neither happens now: a section opens in a few tens of milliseconds, and a requirement's checks and controls arrive the first time you open that row. Lines on the Scope tab load their edit form and section finder the same way.

An instrument section came back with 146 requirements for four instruments, a third of them from Part 1 articles specifying accessories nobody was buying. Reading a section now takes a blanket Part 1 rule but leaves the accessory specifications alone, keeps each row at the size a datasheet has a line for rather than one per screw, and cites a real article or none at all instead of writing "article number not shown". The same section now reads 89.

A scope document, a section's requirements and a section's demands can each be read again from what is already uploaded, instead of deleting the file and starting over. The list is cleared and rebuilt rather than added to, so a second read under better reading actually improves it. Anything you decided is kept: lines you typed, requirements you accepted, declined or judged, and demands you answered with a submittal.

A read, a compile, or an import used to report in on a timer, and every tick could close the step list you had just opened or drop you to the bottom of the Scope tab. Screens now hear about a change the moment it lands and refresh only what moved. Disclosures stay open, the page keeps its place, and answering one line of your scope repaints that line.

A section could be read again and come back with every requirement kept, even the ones the trimming pass had plainly decided to drop. The verdicts named rows by their article reference instead of the row itself, so none of them matched and each unmatched row quietly defaulted to being kept. Rows now carry a label an article number cannot be confused with, and a response that names rows we never sent is treated as a failed pass rather than as approval of everything.

Sending an RFI used to wait while the PDF was drawn, its attachments merged and the file stored. The record is now numbered and marked sent at once and the PDF is built behind it; the page shows Preparing the PDF until it is there. If the build fails, the record says why and offers Build PDF again.

A section like PRIMARY SENSORS AND FIELD INSTRUMENTS specifies every instrument a plant could carry, and you are buying four of them. Trimming its requirements now sees only the lines filed under that section instead of the whole project's scope, so requirements about equipment you are not furnishing drop out. And a section that specifies equipment but asks for no submittal of its own now says which section does ask, instead of showing an empty list.

Rows arrived that nobody could check: "Automatic zeroing" whose value was "automatic zeroing feature", "Transmitter construction" whose value was "solid state construction". A requirement now has to be something two datasheets could differ on, so those are gone and the ones that hid a real number came back with it: the low-flow cutoff reads "below 0.5 percent", the damping "1 to 25 seconds", and an output that was one row is now its signal, its action and its load.

Reading a section again for what it asks you to submit cleared the list and then sat silent for the whole minute the read takes, which looked exactly like a button that deleted your work and stopped. The section now says it is reading, how long it has been going, and how many sections are still to come.

"6.3 GHz to 26 GHz" was read as article 6.3 of Part 2, which cut the radar level transmitter's specification in half and left every requirement from it citing an article the book does not contain. An article of Part 2 is numbered 2-something, and that now settles it. A bare "7.5" in an equipment section was doing the same thing.

Reading a section used to hand you every restatement and every installation step as its own row, and you declined your way down to the ten that matter. The read now merges duplicates, sets aside anything a manufacturer's datasheet does not actually carry (lab test acceptance criteria, resin chemistry, jacket print legends), and lands the keepers on your list directly. Every removed row stays visible with a one-line reason and a Restore beside it, and anything you decided yourself is never touched.

Reading a scope document now shows its four steps with the finished ones ticked, instead of one sentence for the whole three minutes. The project's setup checklist keeps up on its own while those reads run, and says which one is running, so a page that used to need a refresh to notice a step was done no longer does.

You no longer have to open a drawer to find out whether a package answers the spec, or guess whether the matrix will reach the PDF. The submittal page now carries a compliance matrix panel with the counts on its own line and a switch that says, in words, whether the compiled submittal includes the table. The matrix is scoped to the sections that submittal is linked to, so a package stops claiming requirements nobody checked it against. Both bands on the page now start collapsed and remember what you opened.

You had to scroll past every section to reach the sharing panel, and it sat there greyed out on packages that were not compiled yet. Share now sits in the submittal header beside Settings and opens a window with the same recipient list, activity, and one-time-code links. On a package with nothing to send yet, the window says why instead of the page carrying a dead panel.

A supply line that never landed on a section had nothing you could press: the read had already run, and adding the line by hand did not start another one. The Scope tab now offers Match unfiled lines whenever any are waiting. Uploading another volume also re-reads the scope against a book whose earlier volume did not finish, instead of leaving those sections unmatched for good.

You were answering the same question twice: once on the Submittals tab and once beside the section that asked for it. Now you answer it once, on Specifications, where the section's own words are in front of you. The Submittals tab says how many are waiting and links across, and says nothing when none are. Two answers moved with it: you can point a demand at a submittal you already made, which links that section to it, and you can reopen any demand you have answered without touching the submittal.

A long list of checks before a submittal goes out used to push the sections halfway down the page. The band now collapses to one line, and opening it shows every check in a compact table that scrolls in place, with the kind of check called out beside each one. It remembers whether you left it open, and the count on an equipment row still jumps you straight to the list. Checks still never block a submittal.

Run check on a submittal reads each piece of equipment's datasheet against the accepted requirements for the sections it answers, and records met or not met with the datasheet's own words quoted as evidence; anything the datasheet does not prove lands as not confirmed. Verdicts land on the requirements panel with nothing to accept: each stays marked as suggested until you confirm it, and you can override or remove any of them. Anything not met shows up in the checks band before the package goes out, and if a requirement or a datasheet changes after a check, the affected answers are flagged as checked against older facts.

Matching your scope against the specification can only answer one question: is what you said you supply specified here. It cannot tell you what is in the book that you should have said, and those are the sections most often missed. All sections now sweeps the whole book for controls work, by section number where the numbering says so and by title where it does not, and lists anything you have not decided on yet. Work that only touches controls, raceway and grounding and surge, is listed apart from controls work itself, because who owns it is usually worth an RFI rather than an assumption.

Claiming a project used to mean answering "is this section yours?" over and over about a book that covers every trade on the job. A new Scope tab turns it around: tick what you provide from a list of control-system deliverables, paste your scope, or upload it, and each line comes back with the section that specifies it beside it. Sections nothing you supply reaches are never put in front of you, every line stays editable for the life of the project, and each one shows the submittals covering it, however many batches you sent it in. The old "Is this yours?" queue on the Specifications tab is gone; claiming lives in one place now.

Reading a dense section for what the equipment must be used to take one long call, and a section with a hundred requirements in it hit the answer size limit and came back empty three attempts running. Sections are now read a few articles at a time, so the requirements appear on the panel as each part is read instead of all at once at the end, and the panel says which part it is on. If one part does not come back the rest still do, and the panel tells you the list is incomplete rather than letting it look finished.

Deleting a specification removed the file and left every section it had been read into standing on the project, with nothing behind them and no way to take them off. All sections now has a tick beside each division and each section and a Remove button, so you can clear a division or a handful of sections; deleting an upload offers to take its sections with it, ticked by default; and if any sections are already stranded the tab says how many and clears them in one press. Removing a section drops its claim, its requirements and its register entries, but lines of your scope of supply are kept and go back to unmatched.

Every section of a specification was read one after another, so a project with a dozen claimed sections waited for the sum of all of them. They share nothing, so they now run several at a time and the wait is closer to the slowest section than to the total. A long scope document's pages overlap the same way. If every pass fails, the import names the failure instead of calling it too large. Background workers can pick up any kind of work now, so a burst of reading no longer queues behind itself while other workers sit idle.

Bringing a section into scope, by claiming it or by importing your scope, now reads it for what it demands you submit and what the equipment must be. Neither read has to be asked for, and the results appear as they arrive instead of after a manual refresh. The Specifications tab also keeps your place: reload and you are back on the section you were reading rather than the first one in the list. When your scope matches more than one section, each choice now says what that section is and why it was offered, instead of showing bare numbers.

Deciding which of two thousand sections are yours used to mean matching your scope against a table of contents, so "Fiber Conversion Panels" never reached the section that says "media converters". The import now reads the sections themselves and searches by meaning as well as by word, quoting the line behind every call, and it keeps what the contract actually said including work you supply but somebody else installs. It is reachable on a project that has never used it, reports every stage while it runs, and drops citations your book has no section for instead of claiming them.

Three cells printed the wrong thing: PROJECT # printed the project's name, PROJECT NAME printed its description, and the job number a reviewer files the package by appeared nowhere on the sheet. Each cell now prints what its label asks for, and PROJECT #, SUBMITTAL #, SPECIFICATION # and CONTRACT NO. all print the value when the project has one and otherwise leave a line to write on. The submittal date now comes from the same place the cover page and the comment response log read it from.

You write VFD, the engineer writes "variable frequency drive", and the search that should have found both found neither. Type either one now and you reach both, across spec sections, library PDFs and the palette; shorthand that means two things, like LS for a level switch and for a lift station, looks for both readings. The same vocabulary reads equipment tags back in plain English, so VFD-101 on a register somebody else built tells you what it is.

A package can be complete and still come back, because the panelboard's rating is below the available fault current or the transformer's temperature rise was never stated. Read a claimed section and it returns the characteristics it demands, each quoted with the article it sits at; accept the ones that apply, mark each Met, Not met or Not confirmed, and point at the page that proves it. Add a Compliance Matrix section to a submittal and all of it prints inside the package, so the reviewer audits your checking instead of repeating it.

Finding anything on the Specifications tab meant reading past everything else on it: an endless queue, panels counting how many sections had been read, and three drawers to open four levels deep. The tab now shows the sections you own down the left and one section, whole, on the right: its pages, what it asks you to submit in the spec's own words, and anything that has changed it. A section that names nine deliverables can be answered in one press rather than nine.

You watched a reader work, then watched the progress bar sit there long after it had finished and saved everything it found. Reads now turn the page over the moment they land, whether that is an uploaded RFI, comments pulled from a returned document, or a scope import. Previews open where you clicked them instead of reporting that the site refused to connect, and a specification you scanned rather than exported now reads from the text recovered on upload.

The Table of Contents no longer doubles its rules, and an empty section gets its tab number on the contents page instead of numbering that runs 01, 02, nothing, 04. The Compliance Matrix prints landscape with wrapping cells, so a required value lifted from the specification arrives whole rather than cut off mid-number. Divider pages stay portrait behind a turned section, and a long project name on the Transmittal stops at its own column instead of running under the ITEM # label.

Thirteen field guides are now up at /learn: what goes in a submittal package, how to read a spec section, what Approved as Noted obligates you to do, numbering schemes that survive long jobs, the closeout checklist, and what our own submittal logs say about real resubmittal rates. Written from the founder's own project experience, useful whether or not you use Submittal Kit, and each one is plain markdown at its address plus .md if you want to hand it to your assistant.

When an imported parts list spells a manufacturer differently than your library does, you used to work through every unrecognized name by hand. Now the review screen comes pre-filled. Names that look like one of your existing manufacturers arrive already pointed at it, marked Suggested, with the alias checkbox ready so the spelling is remembered next time. You still confirm every row, and a name with no good match is left exactly as before.

A change proposal or a G703 continuation sheet arriving as a PDF used to mean retyping every field by hand. The New Change Order page and the Budget tab now take the PDF itself. Drop it and the form or the line table fills in, with the numbers, dates and headings pulled straight from the document. You check every row before anything is logged, and if the file can't be read you get the ordinary form exactly as before.

After uploading an RFI you used to hunt for what the reader had filled in, behind a collapsed form and a pop-up demanding the sent date. The record now leads with one card, "What the PDF said": every field the reader filled, next to the line on the PDF it came from, and one "Looks right" folds it away. Two fixes went with it, a dropped PDF actually starts the read now, and the sent date you record sticks the first time.

Searching document contents used to be literal to a fault: "brackets" missed the page that says "bracket", and a scanned datasheet was a dead end with no text layer to index. Search now matches word forms and puts the pages carrying all your terms first, and pages that turn out to be images are read individually and indexed like any other upload. Catalog numbers and ratings still match exactly as typed.

What does hand-assembling packages actually cost you a year? The new worksheet at /roi does the arithmetic with your numbers: your package count, your hours, your rate, your resubmittal share. No industry averages baked in anywhere. The defaults are a worked example drawn from real project submittal logs, and every one of them is yours to change. Share it with whoever signs off on tooling.

Answering a page of review comments means writing the same kind of sentence over and over. Pause while typing and a grey draft of the next words appears, written from the comment itself and the way you have answered similar ones on this project; press Tab to keep it, or keep typing and it steps aside. Nothing is saved until you accept it, so your log only ever holds words you chose.

The transmittal always printed an empty NOTES block, so what a package contains and what changed since the last revision got typed into an email or nowhere at all. The transmittal section now has a cover note. Type it once and it prints on the next compile, and Draft note suggests a starting paragraph from the files that changed and the review responses the package carries. Issued revisions are records and stay exactly as they went out.

A recent update tucked Download PDF, Preview, Recompile and the source document export behind a "..." menu on the submittal page. They are visible buttons again, right where they used to be. The "Pending issued package" box is gone too, because the confirmation you get when you Mark as Submitted already names exactly what will be issued.

Filtering the Contact List and changing a role, expanding a firm, or keeping a punch candidate used to redraw the whole page. Your filter snapped back and open panels shut while your search text still sat in the box. Each of those now touches only the rows it changed, so your filter, your scroll position and your half-typed edits stay put. A rejected save hands your typing back too, so fixing a near-miss is an edit, not a do-over.

Getting a compiled package to the reviewing engineer used to mean attaching a 40 MB PDF and hoping their server took it. A submittal now has a Share panel: pick a contact or type an email, and each recipient gets their own link to a transmittal page with a download button. The link is bound to their address and opens only after a one-time code, and you see per-recipient views and downloads, with a revoke that works the moment you click it.

Hard to argue for a tool when the value it returns is invisible. Settings > Billing now shows your numbers: packages issued, hours recovered, labor recovered, and your subscription cost with the return multiple, with a compact version on the dashboard. The two assumptions behind the math, hours saved per package and your loaded rate, sit right next to the figures and are yours to edit, so the numbers stay honest to how your shop actually works.

A corrupted or oversized file used to fail somewhere mid-import, or grind the page trying. Every spreadsheet import now checks a file's real size before parsing it and tells you exactly what is wrong, and PDF and image uploads are checked the moment they arrive. The SOV import no longer reads legacy .xls files, so re-save as .xlsx or .csv before uploading.

Finding a phone number used to take two steps: pick a firm from a narrow list, then read its detail pane. Firms & Contacts is now one table with people, projects, phone and email in columns, and clicking a firm expands its team right in place. Delete only appears on records nothing references yet; everything else deactivates, so history keeps its names.

Kick off the wrong compile or point a scan at the wrong datasheet, and until now your only option was to watch it finish. Every progress surface now carries a plain Stop: datasheet scans, compiles, source exports, part descriptions, BOM imports, punch extraction, scope parsing, document finding, RFI reads, and MOF exports. A stopped job lands in a clear stopped state and stays there until you choose to run it again; nothing requeues behind your back. This also fixes the datasheet scan that could sit at "Looking for this catalog number on the page" for hours. A stuck handoff kept recycling the same work forever, and scans now run to a real finish.

A library document can back parts across many projects, and editing its category or Always Full Sheet setting used to apply everywhere silently. When the file is shared, the edit now tells you first exactly how far it reaches, with live counts of the parts and projects linked to it, the same warning the part page already gave. A document used in one place still edits without ceremony. Also new: What's new lives in the help menu when you're signed in, opens as a quick panel instead of leaving your page, and shows a dot when something shipped since your last look.

After a reviewer returned a package, two questions had no answer on screen: what did this revision actually change, and did anyone go through the returned document? Each revision's drawer now answers both. A changes-since line states what the package added, replaced, or removed compared to the revision before it, with the full list one click away. Under the returned document, a summary shows the outcome, the reviewer, the date, and any pages the reading could not cover, so you know at a glance whether the response still needs your eyes.

Running several jobs meant answering "what's late, everywhere?" by opening each project and checking five surfaces one at a time. A part twelve days past its order-by date, a slipping FAT, a change order waiting in a customer's inbox: none of it reached the dashboard. Now it all does. A schedule rail lists every dated item across your projects in time order, broken dates first, then the next thirty days. Below it, your open work splits into "In your court" and "Out of your hands", each row tagged with the register it came from, so the next action is always one click away.

Figuring out a corner of Submittal Kit used to mean poking around or emailing support. Now every feature has a written guide with screenshots at /help, public and shareable. Search the guides with Cmd+K on the help site, and matching guides now appear in the app's own search under a Help group. Your Help & feedback menu links straight there, and any guide is plain markdown at its address plus .md, easy to hand to your assistant.

Opening the site while signed in now lands on your dashboard directly instead of taking a redirect hop first. Logos, icons, and fonts are cached by the browser for the long term rather than being re-downloaded, and the Part Library page trimmed redundant counting work. The difference is most noticeable on company laptops whose security software slows every request.

Milestones were ten loose dates you pushed around one at a time. Now each one can carry a duration, follow another milestone with an optional lag, and the dates work themselves out: slip FAT and Ship, Materials on Site, and everything after move with it. A timeline above the table draws the plan as bars you can drag and resize, with week, month, and quarter views and a today line. An empty schedule can start from the standard sequence, Kickoff through Substantial Completion already chained with typical spacing, so the first draft takes one date and one click. Recording an actual date pins that milestone where it really landed, and the rest of the plan flows from it. Procurement's need-by dates and the Submittal Log's proposal hint read from the same schedule, so there is one plan, not three.

The schedule also works the way a schedule is used. Durations and lags count working days, so weekends stop hiding inside "10 days of fabrication". Every change that ripples shows an Undo, and a history keeps who moved what, when. The chain that decides the finish date gets a heavier outline, milestones that drive purchasing say so on their row, and dragging a bar shows the date it will land on. Dragging a dependent bar slides its lag behind its predecessor, so the whole chain stays honest. Project followers hear about it when one edit moves the finish date a week or more, and the whole timeline exports as a PDF Gantt or a spreadsheet.

Submittals put together by hand, outside the application, had nowhere to live: the log could note that a revision went out, but not keep the document that actually went. Drop that PDF into a submittal's Revisions section, fill in the revision number, dates, and what came back, and it becomes a real revision on the Submittal Log, marked as recorded so it reads apart from one the application compiled. The next revision is built here as usual and continues the numbering.

The Revisions list on a Submittal only offered a download, so checking what went out in an earlier revision meant saving the file and opening it yourself. Each revision now opens in the same preview window the rest of the application uses, with the download still there beside it.

A recorded revision is typed in after the fact, so the usual mistake is the wrong file or the wrong date rather than a bad build. You can now correct one: change its number or dates, drop in a replacement PDF without re-entering everything around it, or remove it entirely, even when it is not the newest. All of that stops once the reviewer's returned document is attached, at which point the revision is part of the permanent record like any other.

Importing a BOM could stop with an error when a part was already in your Part Library under the manufacturer's saved spelling and the spreadsheet shouted it in capitals. The import now files the row against the part you already have instead of trying to create a second copy of it.

The importer is also better at reading a workbook. It matches column headings by whole words rather than stray letters, so "Manufacture", "Part #" and "PartNumber" are all understood and a column like "Finished Water QMS" is no longer mistaken for a quantity. It reads the rows underneath a heading before deciding, so a leftovers tab loses to the live parts table and a column that simply counts 1, 2, 3 is never taken for a part number. When one sheet is the clear winner, the import skips the mapping step entirely.

Adding a section to a submittal updated the section list, but the button you added it with kept offering to add it again and the section itself did not appear further down the page until you reloaded. All three now update together, as do renaming, deleting, and reordering.

The Submittal page shows every comment on the project along with the review or site visit that raised it. It used to look that source up one comment at a time, so a project with a long comment list spent longer and longer loading the page. The page now collects all of that in a single pass, and its loading time no longer grows with the number of comments.

Progress used to look different depending on where you were: a yellow-striped band on imports, spinning circles under some drop zones, and a "Background work" box that popped up in the corner of the screen. All of that is now one quiet design. When you choose a file, the drop zone becomes a small card with the file's name and size, a thin blue progress bar, and one line saying what is happening right now, with the real percentage when we know it, the step count when the work moves in steps, or how long it has been running. When a job keeps going after the upload, the same line tells you that you can leave the page. Finished work turns the bar green with a plain-words receipt; failures turn it red and say what actually went wrong, with the file still attached so Try again means try again. The corner box is gone, progress stays where you started the work, and it is waiting there when you come back.

Pressing Compile used to sit for five to ten seconds before anything changed on screen. Behind the button, the server was re-downloading every source PDF in the submittal just to double-check nothing had changed, on every compile, every download, and every submit. Those checks now use the record the app already keeps, which answers in a blink, and the heavy file work happens only inside the background compile job where it belongs. The submittal page also stopped running a specification search on every visit; it now runs only when you open the settings drawer where those suggestions appear.

Uploading a file you already had could add a second copy of it, so one datasheet appeared twice and each copy could be linked to different parts. Re-uploading the exact same file now always lands on the entry you already have. A vendor datasheet downloaded a second time is harder, because the file differs even when the document does not, so those uploads still finish as before and the library and part pages tell you when a new file reads the same as one you already have. They show what it matched, when it was added, and a link to open both, since two sheets in a product line can read alike and differ only in a photo. One click links the part to the file already in your library and drops the copy, or you can keep both.

Compiling a submittal could fail with an error page when one of its source documents could not be read, with nothing on the page explaining which document was at fault. The compile button now tells you what needs fixing before it starts, and the same documents are flagged on the submittal itself instead of looking ready. Clearing the Submitted date on a log entry also failed instead of saving, and now reports the problem inline. Compiling is substantially faster, most of all on the packages that took longest: drawing-heavy manuals, and any submittal that covers part of a large project. A package now pulls only the documents it actually contains rather than everything in the project, and documents it has compiled before are reused instead of fetched again. The Purchase Orders tab also stays quick as a project's order history grows.

With the sidebar collapsed, the help and account menus opened underneath the page behind them, so log rows and other content showed straight through the menu. Both menus now sit above the page wherever they open.

Finding the spec paragraph or RFI answer you half-remember used to mean opening page after page. Search (Ctrl/Cmd K) now reads the text inside RFIs, punch responses, change orders, equipment notes, and recorded spec requirements, shows the matched line with a preview beside the results, and pressing Enter on a spec section opens its pages right there, at the matched page. Your search sticks around if you close and reopen, and the empty search remembers where you have been: press Enter to jump back to your previous spot.

Someone joining a company mid-project used to land on a dashboard listing every package the whole company owed, under a heading saying only they could move it. Now their first dashboard asks which projects are theirs, showing what is out for review and what has come back on each so the names mean something, and it turns into their real board the moment they pick. Admins can put a new teammate on their projects right from the invite form, and the invitation email names those projects. On the Team and Personnel rosters, the amber flag on a name now reads "Name is a guess" and explains that the name came from the person's email address and is what an Emergency Contacts page prints. Setting your name on your Account page finally corrects the roster too, which it never did before, so the flag clears and documents stop printing the guess.

A dropdown opened near the bottom of a scrolling panel could be cut off, leaving the last option impossible to pick. Every dropdown in the app now opens over whatever it sits inside, with the full list reachable.

Every project now keeps a Change Order log beside its RFI Log and Punch List: numbered records with status, dollar amount, and the RFI each change grew out of. Open a record right in the log and it edits in place, saving each field as you leave it, marking one approved, rejected or void without the page moving, and taking several quotes or markups at once dropped straight onto the record. Bring your existing log in by dropping the spreadsheet on the page: it reads layouts that aren't laid out like ours, including headers split over two lines and the Pending / Approved / Rejected columns a lot of PCO logs use instead of a status column, picks up the day each change order came back whether your sheet calls it a response date, a return date or a decision date, and leaves the subtotal at the bottom out of the log. Anything already logged is spotted by number, or by matching title and amount, and you decide row by row in a window over the log whether to skip it, bring it in again, or update the record from the sheet. When something lands wrong, correct a change order's dates or its number on the record, or delete it outright.

Procurement now lives beside the equipment it covers. Drop a vendor quote on a project and the line items are read from the document, matched against your parts, and priced. Build purchase orders from the quotes you accept, then see at a glance what has been ordered, acknowledged, and received.

Every part now shows its full price history across projects, the quotes behind it, and what is on order, right on its page. Duplicate parts (a quote's full ordering code next to your catalog number) are spotted automatically, and cleaning them up is two clicks: move the quote line to the right part, then delete the empty one. The Parts and Document Libraries share a faster table layout with last-quoted prices and linked-parts columns.

Exporting the MOF failed with a generic error when a Part Category name contained a character Excel does not allow in sheet tabs, such as a slash. Those characters are now replaced in the tab name, and the export reports its real progress instead of failing immediately.

The dates that drive your submittal schedule (order-by, ship, FAT) now live on the project itself instead of a spreadsheet on someone's desktop. The milestones strip shows what is coming due across the work you follow.

Merging two parts failed with an error when the duplicate had quote pricing or purchase order lines recorded against it. The merge now carries that pricing history over to the surviving part.

If the equipment register changes after you compile a submittal, the submittal page now tells you before you issue. No more finding out the register moved after the reviewer already has the PDF.

A performance pass across the app. Big equipment registers, the submittal log, and project pages all respond noticeably faster, especially on projects with hundreds of register entries.

The Specifications tab is no longer a filing cabinet. Claim the spec sections a submittal answers and the log shows what each section actually requires, so what you owe on a project is read from the book instead of remembered.

Press Cmd+K (Ctrl+K on Windows) on any page and type a job number, part, submittal, or RFI to go straight there. It also understands identifiers: paste a spec section or submittal number and it takes you to the thing that number names.

Every field in Settings now saves as you change it. The Save button you could forget to click is gone, and so is losing ten minutes of edits to a missed click.

Creating an RFI and recording what came back now happen on one page, with real formatting (bold, lists, links) instead of a single plain text block. RFIs you sent outside the app can be logged after the fact without renumbering anything.

Track punch list items the same way you track RFIs: one numbered log per project with categories and status. When it is time to hand the list to the customer, it renders as a clean controlled form instead of a screenshot of a spreadsheet.

Exporting an equipment register and importing it back into another project used to trip over its own column headers. Any BOM file now goes through the same mapping and confirm screen, and you choose Replace or Sync with a preview of exactly what will change before anything does.

Projects are now identified by job number first, the way your shop already talks about them. Search by number, create by number, and set a default office per person so new projects land where you work.

The industry says submittal, so the app does too. Every page, email, and compiled document now uses the word your customers use, and old bookmarks and links still land where they should.

Mark up drawings in the app and issue them like any other submittal. Redline shapes use the same markup tools as datasheet highlighting, so a markup stays editable data instead of ink baked into a scan.

Instead of counting tiles, the dashboard now leads with what is waiting on you and what is out with reviewers, so the first thing you see in the morning is the thing to do next.

Companies with more than one office can now pick which office speaks for a project. That office's address and letterhead flow onto compiled covers automatically instead of being edited by hand per package.

The old site and panel folders are gone. A project keeps one Equipment Register that feeds every submittal, so a part corrected once is corrected everywhere it appears, and a package can never quietly disagree with the register behind it.

Cover templates are no longer fixed layouts. Drag your logo, titles, and project fields anywhere on the page, with smart guides to keep things lined up, and every compiled package wears the cover you designed.

Ask a question on a project's Specifications tab and get an answer drawn from the uploaded spec, with the sections it came from cited so you can verify it yourself. Find Documents also checks your shared library first before hunting for a datasheet.

Manuals now build in the background with an inline preview, the same way submittal packages do, so assembling a turnover package no longer means babysitting a progress bar or re-uploading sections that were already there.