What Got Shipped Today - 22/7/26

22 July 2026 Features Certify and dispute payment schedules line by line User story As a contract administrator, I used to accept or reject a subcontractor's payment schedule as one whole record, so I can now agree, dispute, or partially certify each line, with a defensible reason attached to every rejection. Before A payment schedule could only be accepted in full. If a single line was wrong, you either passed the whole thing or held up payment on everything while it got sorted out. After Every line in the Schedule of Values now carries Approve, Partial, and Reject. Partial certification locks the line at the certified amount and flows straight through to the claim and the subcontract. Rejections require a reason, chosen from a clause-based list tied to the subcontract type (AS 4901 and similar) or written in manually. Touch any line and the schedule moves to Partially Finished. You can still accept the untouched remainder in one action, with a warning before you commit. Impact The payment schedule becomes the place certification decisions actually happen, line by line, and every dispute carries a written, contract-referenced reason. That is exactly the record you want if a certified amount is ever challenged. The Schedule of Values with per-line Approve, Partial and Reject actions, and a Partially Certified status once some lines are actioned. Rejecting a line asks for a situation and a clause-based reason (AS 4901 shown), so every dispute leaves a defensible record. --- See and open any prior revision from the Document Register User story As a PM, CA or site manager, I could already see version history in Explorer for working files, but the controlled Document Register had no equivalent, so I can now pull up the full revision history of a registered drawing and open any prior issue in a click. Before Version history already existed in Explorer for working files. The Document Register, the controlled environment, had no equivalent. It only showed the current revision, so checking a previous issue meant hunting down the old file or dropping into compare mode. After That same history now extends to the register. Each register row opens a Revision History view listing every revision, with revision, date, who uploaded it, when, and a clear Current or Superseded flag. Click any revision to open the file. Compare is launchable straight from the list, labelled Compare Revisions in the register (Explorer keeps Version History and Compare Versions for working files), and KAI can summarise what changed between any two revisions. Impact The controlled register now has the revision visibility Explorer already had, so anyone on site can check what changed from the last issue without leaving the register or guessing which file was current. The new Revision History panel on a registered drawing, showing current and superseded revisions with a Compare Revisions button. Compare Revisions lets you pick any two revisions and run a KAI text diff or a visual overlay. --- One log for every notification the platform sends User story As an admin, I could not see what emails and notifications Deep Space had actually sent on a project, so I can now open one log and see every notification, filtered by type. Before Notifications went out (RFIs, notices, subcontractor emails) with no single place to confirm what had been sent, to whom, or when. If a client asked whether something had gone out, there was no easy answer.After A workspace-wide notification log shows every email and in-app notification, filterable by project and by type, including notice emails. Known limitations In beta while testing continues across the many places notifications fire. The project filter applies to notifications sent from now on; older records were not tagged with a project and cannot be filtered by project retrospectively. Impact Full visibility over what the platform is sending, so the commercial team can confirm a notice landed and answer client queries from the record rather than from memory. Improvements Invoice Register edits now carry into the claim and payment schedule User story As a commercial user matching invoices to subcontracts, my edits and attachments used to stop at the Invoice Register, so I can now edit the register once and have those changes carry into the generated claim and payment schedule. Before After matching an invoice to a subcontract, saving changes was clunky, and documents did not carry across to the generated records. After Saving changes after a match is smoother, and edits to fields and line items in the register now reflect on the generated claim and payment schedule. Documents are attached to the claim and payment schedule when they are generated. Where no Schedule of Values is matched, the flow safely falls back to the existing workflow. Impact One edit in the register instead of three, and the paperwork travels with it. Upload dropzone now tells you folders can be dragged in User story As someone uploading to the CDE, I assumed the dropzone took individual files only, so I can now see that whole folders can be dragged straight in. Before The dropzone hint listed PDFs, images and Office files, so users assumed a folder had to go through the separate upload-a-whole-folder link. Dragging a folder already worked. Nothing said so. After The hint now names folders alongside PDFs, images and Office files. Drag a folder onto the dropzone and it uploads, subfolders and all. Impact A capability that already existed is now discoverable, which means fewer file-by-file uploads. Spotted something, or want to help shape what we build next? Send it through the feedback portal inside the Deep Space web app. We read every note.