What Got Shipped Today - 10/9/26 - Bids line up side by side, your whole financial model exports and comes back, and subbie retention finally gets released

10 September 2026 Features Compare every bid side by side, not one card at a time "I've got three roofing bids in front of me. I want to see how each one priced the same line, on one screen, not by opening three cards in turn." Before. Compare Bids rendered one collapsible card per subcontractor, stacked vertically. To see how two subbies had priced the same line you expanded one card, read the number, collapsed it, expanded the next, and held the difference in your head. Every builder running a competitive tender levelled their bids in Excel instead, because Excel would at least put the columns next to each other. After. A true matrix. Line items run down the rows, subcontractors across the columns, and both the header row and the first column stay stuck in place so you never lose track of which line or whose price you are reading. A roll-up block sits under each column, and a per-column drawer opens the full detail behind any bid. On a narrow screen the columns fold into vendor tabs, so nothing disappears off the side of the page.Impact. Levelling a tender becomes a read rather than a reconstruction. The comparison you were rebuilding by hand in a spreadsheet is now the default view of the screen where you award the work, with the numbers coming straight from the bids themselves. Known limitations. A bid that carries no priced schedule shows its headline price rather than an itemised build-up. Export your whole financial model, edit it, bring it back "I want to restructure our budget categories, cost codes and cost types in a spreadsheet, then load the lot back in without creating a single duplicate." Before. Budget Categories, Cost Codes and Cost Types each exported on their own. Restructuring your financial model meant three exports, three sets of edits and three imports, with nothing guaranteeing the three pieces still lined up when they landed. Re-importing a file you had already imported created duplicates rather than recognising what was already there. After. A new Import / Export tab on Company Settings, Cost Codes. Export Financial Model downloads the complete live model as a four-sheet Excel workbook, every budget category, cost code and cost type, including archived and locked records, with their hierarchy and their links to each other. Import Financial Model reads that same workbook back idempotently: unchanged rows are skipped, edits update in place, new rows are created, and a full validated change plan is shown before anything is written. Nothing is ever deleted. Removing a row from the file leaves the record untouched, and status drives archive, restore, lock and unlock instead. The new Import / Export tab on Company Settings, Cost Codes. One button lifts the whole financial model out as an Excel workbook, the other reads your edited version back in without duplicating anything. Impact. The financial model stops being three registers you maintain separately and becomes one artefact you can lift out, work on in the format your commercial team already lives in, and put back. Setting up a new workspace, or reshaping an existing one after a year of learning, drops from a careful multi-step exercise to a round trip. The submittal loop closes properly: resubmit, void, response due dates "The consultant rejected two of the eight drawings. I want those two back out for review without rebuilding the pack, and I want the email to say when I need an answer." Before. Once a pack went out, it went out. Rejected items had no route back other than assembling a fresh pack by hand. A pack sent to the wrong person could not be pulled. Reviewers received the equivalent of "please take a look" with no date attached. And a pack chased four times read as five separate deliveries in the register. After. Resubmit on a closed pack creates a new pack carrying only the rejected items, numbered in sequence and linked in both directions to the pack it came from. Void is available while a pack is issued and no response has landed: it requires a reason, invalidates the reviewer's access immediately, and writes nothing to the register, while the transmittal itself survives, annotated to say its submittal was voided. The composer now takes a response due date that appears in the reviewer's email and drives days-outstanding and overdue sorting on the submittal list. And multiple deliveries from one submittal collapse into a single register entry with a count, expandable in the drawer to show each delivery with its time and recipients. Impact. The approval loop now behaves like the email chain it replaces, minus the guesswork about who has what and since when. Delivery records stay tamper-proof: there is no path, in the interface or behind it, to erase the fact that something was sent. Known limitations. Nothing chases automatically. The response due date is a date the reviewer can see, not a reminder that fires. Release held retention back to a subcontractor "The subbie hit practical completion three months ago. I could see exactly what we were holding. There was no way to pay it back." Before. Subcontractor Retentions showed what was held against each subcontract, and stopped there. When a subbie reached practical completion or came out of their defects liability period, releasing their money meant leaving Deep Space and doing it somewhere else. After. A release action on the subcontract record. Enter an amount, capped at the balance actually held, and Deep Space generates a payment schedule for it, so the release travels the same approval and payment path as every other payment you make. The held balance reduces and the release appears on the subcontract claim history.Impact. The head contract side of retention release landed last week. With the subcontractor side in place, both ends of the retention cycle now open and close inside the platform, against the same balances the platform was already tracking. Known limitations. Amounts are entered manually. Xero bill posting and automatic release triggered by a defects liability date are not in this release. Split a bound drawing set into sheets while uploading revisions "The consultant issues one bound 45-page PDF. Our register holds 45 individual drawings. I do not want to abandon the revision flow to deal with that." Before. In the Upload revisions modal on the Document Register, a dropped file could only be dragged onto a single registered drawing, marked as a new document, or skipped. A bound multi-sheet set had no split option, so either the whole set was forced onto one drawing, or the user backed out, split it at initial upload instead and re-registered the sheets, which severed revision history against the register entries that already existed. After. Drop the bound set into New files and split it where it sits. KAI breaks it into single sheets and each sheet comes back as its own card in the sort panel, ready to be dragged onto, or matched to, its registered drawing as the next revision.Impact. Consultants can keep issuing documentation the way they always have. A bound set stops being a decision between doing it wrong and doing it twice, and revision history stays continuous through every release. Improvements The payment schedule breakdown separates original contract from approved variations "The certified amount in the header did not match the breakdown table underneath it. I had to work out which number my client should believe." Before. The schedule of values on the payment schedule ran original contract lines and approved variations together in one block. The breakdown total could therefore sit below the document's own certified amount, with nothing on the page explaining the gap, and the client reading it had no way to reconcile the two figures. After. Two clearly separated sections, original contract and approved variations, so every dollar of the certified amount can be traced to where it came from. Impact. A document that goes to your client now reconciles on its own face. Nobody has to take a phone call to explain a difference that should never have needed explaining. Find the right Xero bill in the relink picker "It says there are more than twenty invoices, but only the first best matches are being shown." Before. Linking a supplier invoice to an existing Xero bill offered only the first twenty-five best-match candidates, with no way to search them. If the bill you needed sat outside that twenty-five, you could not reach it at all. After. The candidate list is searchable and paged, the Xero reference shows against each row, and the twenty-five-row cap is gone. Impact. Reconciling against Xero stops depending on whether the bill you want happened to rank in the top twenty-five. You search for it, and you link it. Recover a specific day of site photos yourself "Photos from Tuesday's site walk never made it across. I want to re-check that day myself, not raise a ticket about it." Before. Yesterday's release made Deep Space re-read a DS Site submission after a delay, so photos that finish uploading late are no longer lost going forward. Days that had already passed through still needed someone on our side to go and fetch them. After. A workspace manager picks a date and re-checks it. Anything DS Site is holding for that day that never landed is recovered into the project. Impact. Recovering a day of site records moves from a support request to a control you hold. Site photo history stops having gaps you cannot close yourself. Fixes Ask KAI opens on a document however you got there "I opened the file with the preview icon, clicked the brain, and got 'Missing document context'. Opening the same file from the row worked fine." Before. Opening the file viewer through the preview icon and then opening the Ask KAI panel rendered "Missing document context, cannot start the chat", and no request was made at all. Opening the same file with the brain icon directly from the document row worked. Same file, same panel, different answer depending on which icon you happened to click. After. The viewer carries the document's identity through either entry point, so Ask KAI opens and is usable no matter how the file was opened. Impact. KAI is only useful if it is available at the moment you have a question. One of the two ways into a document no longer quietly closes that door. Manually linked subcontracts now offer the right schedule of values lines "I matched the invoice to the subcontract by hand, and then the schedule of values list came back empty." Before. On the Invoice Inbox, an invoice that had been manually linked to a subcontract could not have its schedule of values line items picked, because the register was resolving the subcontract by the wrong identifier. After. Manually linked subcontracts resolve correctly, so the schedule of values lines load and can be selected as normal. Impact. The manual link is the escape hatch for every invoice automatic matching cannot place. It now leads somewhere. Spotted something that should work differently, or want to see something next? Tell us through the feedback portal in the Deep Space web app. Most of what is above started as a builder telling us it was wrong.