What Got Shipped Today - 18/9/26 - A drawing registers itself from the RFI it came back on, the Project Inbox reads like a mail client, and the Invoice Register stops blocking good invoices

18 September 2026 Features Register a drawing straight from the notice it arrived on "The consultant answered my RFI and attached the revised drawing. Now I have to download it, find the Document Register, and upload it again, hoping I pick the right revision." Before. A document that came back on an RFI response lived in the correspondence thread and nowhere else. Getting it into the Document Register meant downloading the file, walking to a different module, and re-uploading it by hand. The link between the drawing and the question that produced it was lost the moment you saved it, and nothing on the revision recorded where it came from. After. Every PDF attachment on a notice thread now carries a register button. One click opens the register form, and the document lands in the Document Register with its source stamped on the revision, so the record says which notice it arrived on. The file never leaves storage, so there is no download and no re-upload. Registered documents also appear in the Unsorted folder in Explorer, the same behaviour you already know from Upload Revisions.Impact. The gap between correspondence and document control closes. A drawing that comes back on an RFI is in the register in one action, with provenance attached, which is exactly what an auditor asks for eighteen months later. The Project Inbox now reads like a mail client "Mail Manager gives me three panes and I can work a project's whole mailbox without thinking. Your inbox makes me click into every thread to find out what it is." Before. The Project Inbox listed threads and made you open each one to see anything. Worse, every page load pulled every thread document for the project and then sorted and sliced them after the fact, so a busy project's inbox got slower as it got fuller. After. A three-pane layout: folders and filters on the left, the thread list in the middle, the message itself on the right. Ordering and pagination now happen at the database, so the list returns the page you asked for instead of the whole mailbox. Big project correspondence loads at the same speed as a small one.Impact. Builders measuring Deep Space against a dedicated mail manager get the layout they already know, on a project inbox that is wired into the rest of the job. Correspondence stops being the module people avoid. Tenders keep their original close date and every extension "The client pushed the close date out twice. The register only shows the last one, so I cannot tell anyone how long we have actually been holding this." Before. Extending a tender overwrote the due date in place. The original close date was gone, the extension history was gone, and there was no record of why anything moved. After. The original close date is pinned the first time a due date changes, and every extension is logged with an optional reason. The tender register surfaces the original date alongside the current one and the extension history behind it. Impact. Estimating can see at a glance which tenders have been dragged out and by how much, which is the signal that tells you whether a client is serious or stalling. Tender Types are yours to maintain "We use contract models the dropdown has never heard of, and adding one means raising a ticket with you." Before. The tender type list was fixed in the product. Adding, renaming, or retiring an option needed a developer. After. Tender Types are now a per-workspace registry, maintained from Company Settings. Add the contract models you actually use, rename them to your language, retire the ones you do not, and the list flows through the opportunity and tender screens immediately.Impact. One less thing that needs us. Your tender register speaks your contracting vocabulary on day one instead of on the next release. Improvements Opportunities capture when the tender lands and what you are chasing "Probability of what? And I need to know when the documents are actually expected, not when they are due back." Before. The opportunity form captured the tender due date but nothing about when the documents were expected to arrive, and no place at all for the mark-up you are targeting. The Probability field was ambiguous enough that two estimators read it two ways. After. Two new fields on the create form and in the detail drawer: expected tender arrival date, which is when the documents are expected to land with estimating, and target mark-up percentage. Probability has been relabelled so it says what it means.Impact. The pipeline view starts carrying the numbers a bid or no-bid conversation actually turns on, rather than a date and a guess. The portal stops offering a button that was never yours to press "I opened a drawing in the portal and there is a Push to DS Site button. I am the subcontractor. What is DS Site?" Before. Portal parties (subcontractors, clients, consultants) opening a registered document in the Document Register saw a Push to DS Site action in the detail drawer. Publishing to site is a builder-side decision, so the button was either confusing or, if pressed, doing something on the builder's behalf that they never asked for. After. The action is hidden across the portal Documents surfaces. Publishing stays where it belongs, with the builder. Impact. The portal shows external parties only what is theirs to do, which is the whole premise of giving them a portal instead of a login. Fixes Forwarded mail brings its attachments with it Before. Mail forwarded to a project inbox address arrived in the Project Inbox declaring it had no attachments, while the files themselves sat quietly in Project Documents. The message and its evidence were in the platform but not in the same place. After. Ingested mail now links its uploaded files, so the attachments show on the message where you would expect them. Variations on the head contract schedule carry their real cost Before. On the head contract schedule of values preview, variation lines printed cost equal to sell, so variation margin read as zero on every job. The figure was wrong in a way that looked deliberate, which is the worst kind of wrong. After. Variation lines carry their own cost through to the preview, and variation margin reports the actual number. Raising a purchase order variation no longer demands an identifier or crashes Before. Create Variation Request refused a perfectly complete line because the line identifier was wrongly mandatory, and Modify Order Item crashed to the error page. Separately, editing a line with a blank identifier field could erase a stored one. After. A variation line needs a name and an amount, nothing more. Modify Order Item opens. A blank identifier on edit no longer wipes the real one. Unticked invoice lines stop counting against the purchase order balance Before. The purchase order balance guard counted every line on the draft invoice, including the ones the operator had deliberately unticked. Invoices were blocked for exceeding a balance they were never going to touch. After. The guard reads the selected lines only. Untick a line and it leaves the calculation, as it always should have. Inclusive-of-GST invoices stop being blocked at authorisation Before. The over-commitment guard compared the invoice total against the purchase order without checking whether the document's amounts were inclusive or exclusive of GST. An inclusive-of-GST invoice was measured as if it were exclusive, so it looked ten percent larger than it was and got refused at Send for Authorisation. After. The detected GST basis travels with the draft and the guard reads it before deciding. Valid invoices pass. Genuine over-commitments are still caught. My Approvals reads in plain English Before. The My Approvals widget, inbox, and drawer labelled most records as a raw entity type followed by a document reference, so an approver saw machine text where a human-readable name belonged. Only purchase orders, invoices, subcontracts, and payment claims escaped it. After. Every approval entity type resolves to a readable label. What is waiting on you is legible without opening it. Tell us what to build next Every one of these came from a builder telling us what was in the way. If something on your job is slower than it should be, send it through the feedback portal in the Deep Space web app and it lands straight with the team.