What's new

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.