What Got Shipped Today - 7/10/26 - KAI levels your quotes, claims that can't overshoot the contract, and PO balances that hold funds the moment an invoice is submitted
7 October 2026 Features KAI levels the quotes in a trade in seconds User story As an estimator with five subbie quotes on my desk for one trade, I spend hours lining up who has included what, so KAI now reads them side by side and shows me the gaps, the exclusions and the apparent low before I pick up the phone. Before Levelling quotes meant reading every PDF, building your own comparison sheet and hoping you spotted the exclusion buried on page four. Quotes arrived on mixed GST bases, so the cheapest one on paper was not always the cheapest one in fact. After On a tender package, file each quote to its trade and choose KAI scope levelling. KAI builds a scope matrix across the quotes, marking every item as included, excluded, unclear or not mentioned (silent is not the same as excluded). It normalises GST so prices compare like for like, names the apparent low, flags quotes that sit well off the field, lists the gaps per subcontractor, and drafts clarification questions you can copy straight into an email. Levelling stays within one trade and never mixes trades. The result exports to Excel with a Levelled sheet, Clarifications, and Gaps and risks, ready to sit against your own take-offs. Impact A comparison that used to take an afternoon comes back in well under a minute, and the clarifications you send are specific enough to close gaps before award, not after. (1) KAI puts every quote on one ex GST footing and names the apparent low. (2) The scope matrix marks each item as included, excluded, unclear or not mentioned, per subcontractor. Known limitations KAI needs at least two quotes it has read in the same trade. Quotes must be filed to a trade on the Quotes tab before they can be levelled. Improvements Head contract claims warn when a line goes past 100%, and show the true percentage User story As a contract administrator back-entering claims, I need to know the moment a line is claimed or certified past its value, so it can't hide behind a total that still looks right. Before A head contract progress claim let an SOV line be claimed and certified past 100% with no warning. Every SOV screen capped the percentage and progress bar at 100%, so an over-claimed line was invisible until the final claim. After When a line's claimed or certified to date would exceed its value, the line is flagged and submit is held until you either correct it or override with a reason. Every override is recorded. SOV screens now show the true percentage (for example 108%) instead of stopping at 100%. Impact Over-claims are caught on the claim where they happen, with an audit trail, rather than surfacing months later as a gap you have to unpick line by line. PO Balance Remaining holds funds once an invoice is submitted, with the breakdown underneath User story As a site engineer raising an invoice against a PO, I need the balance to reflect what is already in approval, so I don't push a second invoice through against money that is already spoken for. Before PO Balance Remaining only moved for paid invoices, while the PO line check counted invoices still in progress. The same PO could show a full balance on the register while the line check said it was spent. After There is now one rule for what is committed against a PO, used by the register, the PO details and the line check. An invoice reduces Balance Remaining as soon as it is submitted for approval. PO details show the breakdown under Balance Remaining: Pending approval, Approved but not paid, and Paid. Rejected invoices and voided or deleted Xero bills never count. Impact One balance everyone can trust. Two invoices in approval at once can no longer both see the full amount. (1) The PO details panel now breaks Balance Remaining into Pending approval, Approved but not paid, and Paid, so you can see exactly what is committed against the order. Workspace Managers can manage DS Site access, and the User Directory shows everyone's permissions at a glance User story As a workspace manager onboarding a new site team, I need to give people DS Site access myself and see who has what without opening every user. Before Only a company directory admin could open DS Site Permissions for a user. To check anyone's permissions you had to open each user one at a time, and a user without rights could flip workspace permission toggles only to be refused on Save. After Workspace Managers can now add, re-role, invite and remove DS Site members from the User Directory. The list view shows a Workspace Permissions column, with a pill for each permission, and a DS Site column showing each person's role, Invite pending, Deactivated or Not a member. Pills update as soon as you save. Users who are not Workspace Managers see the permission settings read-only, with a note to ask a workspace manager. Impact The person running the workspace can get a site team onto DS Site without waiting on someone else, and a permissions audit is now a single scroll. (1) The new Workspace Permissions column shows a pill for every permission a user holds. (2) The DS Site column shows each person's DS Site role or status. Edit the lines of a Draft PO variation User story As a project engineer who spots a wrong cost on a PO variation before it is approved, I want to fix the number, not delete the draft and start again. Before On a Draft PO variation, only the status could be changed. Fixing a line meant deleting the draft and recreating it, which left gaps in variation numbering and lost any notes or attachments. After While a PO variation is in Draft, you can edit its line items (description, cost code, quantity, rate and amount) and add or remove lines, the same way you can on a subcontract variation. The revised PO total preview updates as you go. Approved variations behave exactly as before. Impact Draft is now where you get the numbers right, on both POs and subcontracts. One place to import and export your financial model User story As a workspace admin updating our cost codes, I want one obvious, safe way to bring changes in and out. Before Admin › Finance › Financial Model offered Import and Export buttons on the Cost Codes and Budget Categories tabs as well as a separate Import / Export tab, so there were three ways to move the same data, each behaving differently. After The per-tab Import and Export buttons are gone. The Import / Export tab is the single entry point: it exports your budget categories, cost codes, cost types and the links between them as one workbook, and imports changes back with a full preview before anything is written. Impact No more guessing which import to use, and no partial imports that leave categories and cost codes out of step. (1) The Import / Export tab is now the one place to move your financial model in and out. (2) The Cost Codes header keeps Manage Lifecycle and New Cost Code, without the old Import and Export buttons. A cleaner standard trade list User story As an estimator scanning trades by discipline, I want one clear name for each trade, not two versions of the same thing and a few typos. Before The standard trade list carried duplicates (Concrete and Concreting, Gas Fitters and Gas Fitting), typos, US terms, and entries that are not trades at all. Trades many builders add for themselves, like Passive Fire and Lifts, were missing. After The standard list has been tidied: typos fixed, duplicates merged, non-trades retired, and commonly added trades such as Passive Fire, Dry Fire, Wet Fire, Lifts, Timber Doors and 1st and 2nd Fix Carpentry added. The standard discipline grouping now recognises the corrected trades. Existing packages keep their trade names. Impact The trade picker reads the way your team lets work, and the same scope is no longer split across two names. Fixes Head contract Balance Remaining is calculated at contract level, so a final claim can't overshoot User story As a commercial manager closing out a job, I need the final claim to land on the revised contract value, not past it. Before Balance Remaining on the Head Contract Register, and the default amount on a new claim, added up each SOV line's balance separately and treated a line claimed past 100% as zero. The excess was never netted off, so a final claim could exceed the revised contract value. After Balance Remaining is now the revised contract value less certified to date, at contract level. A claim that would take gross claimed to date past the revised contract value is flagged, and going ahead needs an override with a recorded reason. Impact Your last claim lands on the contract sum, so you are not explaining an overclaim to your client at close-out. Paid to Date on Progress Claims (to client) matches your Invoices register User story As a finance user, I need the Paid to Date card to agree with what the Invoices register says we have been paid. Before The Paid to Date card on Progress Claims (to client) could show a different figure from Total Paid on Invoices (to Client) for the same project. After Paid to Date now reads ex GST from the same paid invoices as the Invoices (to Client) register, so the two cards agree. Impact One paid figure across the commercial module, so the number you quote is the number that reconciles. (1) Paid to Date on Progress Claims (to client), ex GST. (2) Total Paid on Invoices (to Client) now shows the same figure. Converting an email to a notice fills the right field for every notice type User story As a contract administrator turning a client email into an instruction, I expect the email's text to land in the instruction, not vanish. Before Convert to Notice in the Project Inbox always put the email text into the general body field. For a Client Instruction, CAN, Notice of Delay, EoT or variation, the main text box opened empty. After The email text now lands in the main text field of whichever notice type you choose, with its formatting, and moves with you if you change type. Impact Converting an email is one step again, whatever the notice type. Reopened Notice of Delay and EoT drafts keep the Head Contract's contract standard User story As a contract administrator, I need a notice issued under AS4000 to say AS4000, even if I finish it the next day. Before When a saved NoD or EoT draft was reopened, the form fell back to the project's default contract standard instead of the selected Head Contract's. The clause list switched, the PDF could print the wrong "Issued under" line, and bulk Export to PDF from the register had the same problem. After The selected Head Contract's standard is now used everywhere: the clause list, the draft PDF, the register's bulk export and the issued notice. The project default only applies when there is no Head Contract. Impact Notices cite the contract they are issued under, every time. Client portal Explorer grid view shows every drawing User story As a client representative browsing drawings in the portal, I want the thumbnail grid to show the whole folder. Before In the client portal's Documents › Explorer, grid view showed only one clipped row of thumbnails, with the rest of the panel empty. After The grid now fills the panel and scrolls, showing every document in the folder. Impact Clients can find the drawing they need by sight, without switching views. Have feedback or an idea? Tell us through the feedback portal in the Deep Space web app.
How do you feel about this update?
