What Got Shipped Today - 8/10/26 - Drawings from a notice straight into the register, subcontracts you can sign before the SOV is done, and an invoice inbox that sorts itself by project

8 October 2026 Features Register a notice's drawings as the next revision, straight from the notice User story As a contract administrator receiving revised drawings on a CI or RFI, I want to put them into the Document Register as the next revision without downloading and re-uploading, so the register stays current and I can always see where each revision came from. Before A notice's own attachments only offered Preview, Download and Save to Explorer. Getting a revised drawing into the register meant downloading it, opening Upload revisions and matching it by hand, and the register had no record of which notice it arrived on. After Every attachment on a notice now has one icon: Add to Explorer or the Document Register. It opens Upload revisions with the file already loaded, KAI matches the drawing to its register entry, and you choose to file it as the next revision, register it as a new document, or save it to Explorer only. The Document Register gains Source and Received columns, so each revision links back to the notice (or the reply or email) it came from, with the date it arrived. Impact Drawings issued on a notice reach the register in a couple of clicks, and every revision carries its paper trail. (1) Each notice attachment has a single "Add to Explorer or the Document Register" action, which replaces the old Save to Explorer button. Known limitations Submittal notices are not included yet. Client portal users only see the action when their portal role includes document control. Execute a subcontract now, complete the Schedule of Values after User story As a contract administrator, I know the contract sum at award but the breakdown takes time, so I want to send the subcontract for execution now and build the SOV once it is signed. Before A subcontract could not be executed until its SOV was fully built (lines, quantities, rates and cost codes). Once approved, the SOV was locked, and changing it meant reverting to Draft and signing again. After With the workspace setting Complete SOV after execution switched on, a subcontract with an empty SOV gets a single placeholder line equal to the contract sum when it is submitted for approval. The placeholder carries the commitment into the Budget Register exactly like a normal SOV, shows a "SOV pending" badge, and stays editable after execution until the first claim, as long as the SOV still adds up to the contract sum. Every change after execution is recorded on the Timeline. The generated subcontract agreement prints the Subcontract Sum and notes that the Schedule of Values will be issued after execution, rather than printing a placeholder line. Impact Contracts go out for signature the day they are awarded, and the cost breakdown follows without re-signing anything. (1) Add Placeholder in the SOV Builder creates a single line for the contract sum. (2) The line is flagged Placeholder, and Convert to SOV line turns it into a normal line once the breakdown is ready. (3) The SOV still matches the contract sum, so the subcontract can go for approval now. Known limitations The setting is off by default. Claims cannot be made against a subcontract until the placeholder has been broken down. Invoice Inbox: see the invoices for your project, and the ones nobody has matched User story As one of several contract administrators sharing an inbox of hundreds of invoices a month, I want to see only the invoices that affect my project, and the ones that have not been matched to any project, so I am not scanning everything. Before The Invoice Inbox was one shared queue. Every CA scrolled through every invoice to find their own, and invoices with no project sat mixed in with the rest. After Each invoice now shows its likely project, worked out from the purchase order or subcontract it matches. A project filter at the top of the inbox narrows the list to one project, and Could not match to project gathers the invoices that still need someone to own them. A likely project can be confirmed with one click. Impact Each CA works their own queue, and nothing unmatched slips through. (1) Filter the inbox to one project, or to "Could not match to project". (2) Each invoice shows the project it most likely belongs to. Bid packages show which subbies have viewed and downloaded the tender User story As an estimator chasing prices, I want to know whether a subbie has actually opened the tender and downloaded the drawings before I send a reminder. Before A bid package's email history only showed that invitations had been sent. A subbie who had not looked and a subbie quietly pricing the job looked exactly the same. After The bid package Status snapshot now counts Viewed and Downloaded alongside Invited, Accepted, Declined, Submitted and Awaiting, and an Activity log records each subbie's views and downloads, the same way transmittals already do. Impact Reminders go to the subbies who have not opened the tender, and you can tell early when a trade is going quiet. (1) Viewed and Downloaded counters on the Status snapshot. (2) Activity opens the per-subbie log. Known limitations Views and downloads are a signal, not proof. A forwarded email or a printed set will not register. Improvements Upload revisions: see the sheet, sort by drawing number, and settle duplicates User story As a contract administrator uploading a 50-sheet consent set, I need to read each title block while I match, find drawings by number, and know what to do when two sheets share a number. Before The new sheet only showed as a thumbnail while matching, so revision dates could not be read off the title block. Both lists were in upload order, split sheets were labelled p001, p002, and two sheets with the same drawing number in one upload were a dead end. After The new sheet opens in the same viewer as Promote to Register, with zoom and pan. Both lists now sort by drawing number. When two sheets in one upload share a drawing number, you choose to keep one or stack them all as revisions in order. Impact Large drawing sets go into the register in one sitting. (1) The new sheet opens in the Promote to Register viewer, with zoom, pan and a Title block shortcut. (2) The revision date on the title block is readable while you match. (3) Both lists sort by drawing number. (4) When two sheets in one upload share a drawing number, use one as the revision or stack them all in order. Formatting in notice comments and notice templates User story As a contract administrator, I want my replies and my standard notice wording to keep their headings, lists and emphasis, the same as the notice itself. Before The notice composer had a formatting toolbar, but the comment box on a notice and the starting text in Notice Templates were plain text. After The Reply, comment, or @mention box now has the composer's toolbar (styles, bold, italic, underline, lists, indent and tables) plus an expand option that remembers your choice. Formatting shows on the timeline and in comment emails. The starting text in Notice Templates uses the same editor, so a new notice of that type opens with the formatting already in place. Both work for builders and in the client portal. Impact Longer replies and standard notices read the way you wrote them. (1) The comment box on a notice now has the same formatting toolbar as the composer. Head contract Schedule of Values preview split into three sections User story As a commercial manager, I want variations and provisional sums shown separately from the original contract, the same way they appear on the claim. Before The Schedule of Values preview on a head contract mixed base lines, variations and provisional sums in one list. After The preview is now split into Original Contract Values, Variations and Provisional Sums, each with its own subtotal, and the total is labelled Revised Contract Value. Pending variations are tagged and left out of the totals. Impact The contract value reconciles at a glance, and it matches how the client sees the claim. (1) Variations carry their own subtotal. (2) Provisional Sums sit in their own section. (3) The total is the Revised Contract Value. User Directory explains each project permission User story As a workspace manager adding a client or subbie to a project, I want to know exactly what each permission box gives them before I tick it. Before Manager, Collaborator, Viewer and Cost User had no explanation, so it was easy to give someone outside the business access to commercial data. After Each permission box in Add New User and Manage Project Access now has a tooltip, there is a "What do these mean?" link to the permissions guide, and you are warned when Cost User is ticked for someone outside your own company. Impact The right people get the right access, and budgets and claims stay inside the business. (1) Hover any permission box to see what it allows. Cost User, shown here, covers budgets, subcontracts, claims and invoices. Notice PDFs are named after their subject Before A downloaded or emailed notice PDF was named by its reference only. After Notice PDFs are now named "reference - subject" (for example "CI-001 - Lot 1 Tree Clearing.pdf"), both from Download PDF and when attached to issue, forward and chase emails. Impact Notices are easy to find in a downloads folder or an inbox. Beta tags removed Notices, the Provisional Sum Register and other areas that have been in everyday use no longer carry a Beta tag. Fixes Resubmitting a PO or subcontract no longer leaves an old approval waiting Before Submitting twice, or resubmitting after a change, could leave the earlier approval open, so approvers saw duplicates in Pending my action. After A new submission now closes the earlier approval as "Superseded by a new submission for approval", and moving a PO back to Draft cancels its approval. Stale approvals have been cleared. Budget Adjustment shows $0 net impact for reallocations Before On a new Budget Adjustment, the Net Budget Impact added up reallocation lines, so moving budget between cost codes looked like an increase. After Net Budget Impact now nets increases against decreases, so a pure reallocation shows $0.00. This was a display issue only; approved totals were always correct. BoQ Builder imports land in the estimate's own project Before A KAI import in the BoQ Builder could save to the project selected in the header rather than the estimate's project, which looked like an import that failed and then worked on a second try. After The BoQ Builder always uses the estimate's project, and any import error now stays on screen so you can see what went wrong. Have feedback or an idea? Tell us through the feedback portal in the Deep Space web app.