What Got Shipped Today - 15/9/26 - An opportunity lands in one action, a progress claim shows its whole schedule, and a subbie's own claim number follows the money

15 September 2026 Features Capture a whole opportunity in one action User Story As a business development manager, I had to save a thin opportunity record and then walk through Details, Overview and Commercials to finish what I already knew at the start, so I can now enter the entire opportunity from the Add Opportunity form and be done. Before The create form took a subset of the opportunity record. Everything else meant a second pass through three other screens, on every single opportunity. After Add Opportunity captures every field on the record, with validation and required-field logic on the one form. No forced second pass. Impact For the person whose first touch on every job is this form, the job is now one action instead of four screens. Opportunities land in the tracker complete, which means the pipeline reads true from the moment it is created rather than after someone circles back. Edit a progress claim against the full schedule of values User Story As a contract administrator, reopening a draft claim only let me add schedule of values items one at a time from a dropdown, so I can now see and edit the entire schedule of values in the claim. Before The edit flow showed a dropdown, not a schedule. Adding a line meant finding it in a list, and section headings could not be brought in at all. On a long estimate, which is most of them, that is an exercise in patience. After Reopening a draft claim shows the complete schedule of values, including group and section headings, ready to edit as a table. Impact Claims are submitted by section heading because estimates run long. Editing the whole table in place is how that actually gets done, instead of reconstructing it one dropdown selection at a time. Carry the subcontractor's own claim number through the pipeline User Story As a contract administrator issuing a payment schedule, the only reference on the record was our system-generated claim number, which is not the number the subcontractor claimed under, so I can now record their claim reference and have it follow the claim everywhere. Before The system-generated subcontract claim number could not be edited, and there was nowhere to record the number the subcontractor put on their claim. Security of payment legislation expects the respondent to identify the payment claim being responded to. After An editable subcontractor claim reference sits on the claim. It shows in the claims register, and it is available as a tag in payment schedule templates and the payment schedule email template. Impact The payment schedule now names the claim the subcontractor recognises, so reconciliation on both sides stops being a matching exercise. Historical claims can be backfilled with the real reference. Improvements Provisional Sum allowance and drawdown forms, redesigned User Story As a commercial manager raising a provisional sum, I was typing the same description into three fields and reading a nine-column line table that ran off the side of my laptop, so I can now work through one designed form that fits the screen. Before The New Allowance, Edit Allowance and New Drawdown forms each carried their own hand-copied version of the same layout, which meant they drifted apart. Lines sat in a nine-column table that clipped at laptop width and inside the detail drawer. Title, description and the first line's description all asked for the same text. The primary action on an allowance read "Attach", which is not what raising an allowance does. After One shared form drives the register modal, the drawer edit and the Head Contract tab, so all three produce identical records. Lines are stacked rows rather than a wide table, with description and cost code on the first row and quantity, rate, cost, sell and margin on the second. The line description is optional and defaults to the title on a single-line allowance. The primary action reads Approve, and the drawdown modal states which allowance it draws against and how much is left. Impact This surface works at 1280px and at 1024px without anything running off the edge, and inside the 560px drawer. The wording now matches what the action does to the contract sum, which is the difference between a form you second-guess and one you trust. The redesigned New Provisional Sum form. One title, an optional line description, the cost code picked from the workspace cost structure, and cost, sell and margin on a single line that fits the screen. Edit a draft drawdown before it is approved User Story As a commercial manager, a drawdown I had created could only be approved, declined or deleted, so I can now correct one while it is still a draft. Before A drawdown card in the Provisional Sum drawer offered Approve, Decline and Delete, and nothing else. A typo in the title, a wrong line, or a changed quantity meant deleting the drawdown and building it again. After Draft drawdowns carry an Edit action that reopens the New Drawdown form in edit mode, with the title, description and lines all editable. Impact Getting a drawdown slightly wrong is no longer a delete-and-redo. The drawdown keeps its place in the ledger while you fix it. Cost codes on Provisional Sum lines now come from a picker User Story As a commercial manager, every cost code field on a provisional sum was a free-text box, so I can now pick a real code from the workspace cost structure and know it will land in the Budget Register. Before Scope and drawdown lines took a typed cost code with no dropdown, no search and nothing checked against the workspace cost structure. A code that did not match, or an empty one, disappeared silently from the Budget Register and showed as raw text on the Head Contract schedule of values. After The cost code is set once on the allowance, from a picker. Drawdowns inherit it. Attaching an allowance and approving a drawdown both require a code that resolves. Impact A provisional sum that looks right on screen now reconciles against the Budget Register, because the code on the line is a code the platform recognises. The silent-vanishing class of problem is closed at the point of entry rather than found weeks later. Bulk metadata review opens on the drawing's title block User Story As a document controller reviewing an imported drawing set, the preview showed me the whole sheet when everything I was checking lives in one corner of it, so I can now land straight on the title block. Before Bulk Metadata review in Project Documents opened on the full drawing. Drawing number, title, revision and discipline all sit in the title block, so every sheet started with a zoom and a pan. After The preview opens zoomed to the title block region. Impact On a set of two hundred drawings that is two hundred zoom-and-pan actions removed. Reviewers read the fields they are checking without hunting for them first. Schedule of Values setup resumes where you left off User Story As a contract administrator part-way through building a schedule of values on a draft head contract, reopening the setup dropped me back at step one, so I can now return to the step I was actually on. Before If a head contract was still in Draft and the schedule of values was partly built, Open SOV Setup restarted at Step 1: Source. The work was saved, but nothing on screen said so, which is its own kind of lost. After Reopening SOV Setup returns to the step in progress with the work intact and visible. Impact A schedule of values on a real contract is not a one-sitting job. Being able to leave it and come back without wondering whether it saved is the whole point of a draft state. Fixes Estimate section headings survive the import into a Head Contract schedule of values Before Importing an estimate into a head contract schedule of values showed the section headings in the import preview, then dropped them on the next step. The schedule came through as a flat list of lines, so claims could not roll up by section. After Section headings are retained through the import and through the wizard's Review step, so the schedule of values arrives structured the way the estimate was. Impact Progress claims are made by section on long estimates. Losing the structure at import meant rebuilding it by hand or claiming line by line. The imported schedule now matches the estimate it came from. Tender portal accepts bids until 5:00 PM on the closing day Before An invitation to tender told subcontractors the tender closed at 5:00 PM on the closing date. The portal enforced the deadline as midnight UTC, so on the closing day itself subcontractors were met with "Submission deadline has passed" and could not submit. After The deadline is enforced at 5:00 PM Sydney time on the closing date, matching what the invitation to tender promises. If a subcontractor does arrive after close, the message now tells them the builder can submit a bid on their behalf rather than leaving them at a dead end. Impact Bids that were being locked out on the day they were due now land. The date shown to a subcontractor and the date the platform enforces are the same date. Spotted something, or want to tell us what to build next? Use the feedback portal inside the Deep Space web app. Every item on this list started there or in a conversation with a builder.