What Got Shipped Today - 28/9/26 - Departures raise their own purchase orders, revisions find their drawings, and clients choose their own categories

Published: 28 September 2026 Monday, and the crew came back from the weekend with the thrusters already warm. Here is what landed across the platform today. Features Build a departure's estimate line by line, then raise it straight to a purchase order "When a site change turns up, I want to cost it the way I would cost a PO, line by line against the right cost codes, and then raise the order without keying it all again." Before: A departure held one estimated cost figure against one cost code. The real build-up lived in a spreadsheet, and when the departure was converted it could only become a head contract or subcontract variation, landing as a single line. After: The departure drawer now has line items (description, cost code, qty, unit, rate, amount). New lines start on the departure's header cost code and can be moved to any other, and the estimated cost adds itself up from the lines. In the Convert dialog, Purchase Order (PO) now sits alongside HVO and SVO: pick the supplier and a Draft PO is created in the PO Register with the line items, attachments and linked documents copied across. The departure keeps its link to the PO, and a head contract variation can still be raised from it afterwards, so you can pay the supplier and recover from the client off the same record. Impact: The estimate lives in the register instead of beside it, and the cost you worked out on day one is the cost that reaches the order. Screenshot: the Convert departure dialog with the new third option. 1. Purchase Order (PO), which creates a Draft PO against a supplier with the departure's line items. Upload revisions now puts each new revision on its drawing for you "When a consultant reissues twenty sheets, I want the platform to know which drawing each file belongs to, not make me drag every one of them by hand." Before: Every file dropped into Upload revisions landed in To sort, even when its file name started with the exact doc number of a drawing already in the register. A 20 sheet reissue meant 20 manual drags. After: When a file's doc number matches exactly one registered drawing, it is placed on that drawing as soon as you drop it, and the revision badge flips (for example Rev 1 to Rev 2). The doc number and revision are read from the file name and from the text printed on the drawing itself, and each card says why it was matched. Unlink sends it back. Anything uncertain stays in To sort with a short reason: an older revision than the register, two files for the same drawing in one drop (only the newest is placed), or a file name that disagrees with the title block. Nothing uploads until you click Upload. Impact: A full consultant reissue goes from a morning of dragging to a quick check and one click. Screenshot: a revision matched on drop. 1. The file lands on its registered drawing, Rev 1 moves to Rev 2, and the card reads "Matched by doc number in the file name". Known limitations: Scanned sheets with no readable text match on the file name only, and files with no recognisable doc number stay in To sort. Improvements Set your own categories for Client Instructions, Notices to Superintendent and RFIs "Our instructions have their own categories on every job. I don't want to file them under A, B, C and D." Before: The Client Instruction composer offered the default A, B, C, D categories, and only Submittals could have their dropdown lists changed. After: A Customise list link now sits beside the dropdown in the composer for Client Instructions, Notices to Superintendent and RFIs. Workspace admins set the workspace list. Clients issuing instructions from the client portal can keep their own list for their organisation, without asking the builder, and it never changes the builder's list. Notices already issued keep the category they were issued with. Impact: Every instruction is filed under a category that means something to the people reading it, which is what makes the register searchable and countable later. Screenshot: the Category field in a new Client Instruction. 1. Customise list, where you replace the default categories with your own. Known limitations: In the client portal, the link appears for client users whose role has Manage Team switched on. Site Instructions, Notices of Delay and Extensions of Time keep their contract-defined lists. Share project folders with clients and consultants, not just subcontractors "My client needs the construction drawings in their portal. I shouldn't have to email them a link." Before: The folder sharing control in Project Documents only listed subcontractors, so a client could open their portal and find no accessible folders, with every row in the Document Register locked. After: One Share with company control in the folder drawer now lists subcontractors, clients and consultants from your directory. Share a drawings folder with your client and those folders, their subfolders and the matching Document Register rows open up in their portal. If a client's account is not linked to a company, the portal now says so plainly instead of showing an empty page. Impact: Clients see the documents you meant them to see, and you manage it yourself from the folder, no support request needed. Fixes The approval route opens on the record you are looking at Opening the approval route from a record (for example in the Invoice Register) could briefly show the approval of the record you viewed before it. It now always shows the current record's route. Choosing Total Amount on a PO line keeps the value Editing a purchase order line and switching it to Total Amount cleared the figure back to $0. The value now carries across as expected. Removing a PO line explains why it can't be removed When a purchase order line could not be deleted (for example because invoice lines are already matched to it), the message showed an internal ID. It now names the line and gives the reason. Head contract progress claims say "Payment due date", and paid schedules stop showing Overdue The claim date was labelled as the date a response was expected from the client, but it is calculated from the head contract payment terms and used as the payment due date. The New and Edit Progress Claim and Payment Schedule forms, the claim detail and the register now all call it Payment due date. Accepted payment schedules no longer show a red Overdue badge. DS Site forms with section rules or grid fields now work in the Deep Space web app Forms built in DS Site with section rules opened empty when created from the Deep Space web app, and grid fields showed as a stack of text boxes. Both now render the way they do on DS Site. Got feedback on any of today's updates? Tell us through the feedback portal in the platform. Every note goes straight to the crew building the next release.