What Got Shipped Today - 22/9/26 - P&G priced as a percentage, bulk archive, and a claim that spots the variations you never passed on

22 September 2026 Features Price P&G as a percentage of the works, and let the project remember the number User Story As a quantity surveyor, I priced every head contract variation the standard ANZ way (works at cost, then Preliminaries and General as a percentage of the works subtotal, then margin on the total), but the platform only took P&G as a lump sum, so I worked the dollars out on a calculator and keyed them in by hand on every single variation. Before Cost Rate was the only way to value a scope line. A QS pricing P&G at 12% of the works subtotal had to compute it externally and enter it as a fixed figure, on every variation, with no record anywhere of what percentage it came from. After Add Scope Item now carries a Line Type control: Fixed (unchanged, and still the default) or Percentage of works subtotal. Choose percentage and the Quantity, Unit of Measure and Cost Rate fields give way to a Percentage field, pre-filled from a project-level default and editable on that line. A read-only Basis shows the subtotal it is calculating off and how many lines make it up. The line carries a cost code like any other, so it flows into the Budget Register, the contract sum, progress claims, and the Variation Items table on the generated variation document. Impact The cascade printed on your variation order document is now the cascade the platform runs. Set the percentage once on the project and every variation after it prices itself. The calculator comes out of the loop, and so does the transcription error that comes with it. Add Scope Item in percentage mode. The Basis shows the works subtotal it is calculating off and how many lines make it up, and the cost amount is derived rather than keyed. Known limitations Percentage lines do not stack in this first cut: a second on-cost calculated off a P&G-inclusive subtotal is not yet supported, and percentage lines always calculate off the fixed lines, never off each other. This applies to head contract variations only for now. Margin defaults that live on the project and on the cost code User Story As a commercial manager, margin is not flat across my job (PC items run around 10%, builder-priced trades 15 to 20%, preliminaries around 5%), but there was no default anywhere, so every variation line got keyed by hand and every one of them was a chance to get it wrong. Before Markup and margin were blank on every new line. The right number lived in someone's head or in a spreadsheet beside the screen. After Set a default markup percentage at project level, and override it per cost code. New variation lines pick the number up automatically, and it stays editable on the line. The Default markup % field is now on both the create and the edit dialog for a cost code, so you can set it inline on the row or through the pencil, whichever you reach for. Impact Pricing a variation becomes a matter of describing the work, not remembering the rate. The percentage you agreed at contract award is the percentage that turns up on the line, on every job, for every person on your team. Setting a default markup across a whole budget category, with a live count of how many cost codes it will actually apply to. The head contract claim now tells you which approved subbie variations you never passed on User Story As a contract administrator, an approved subcontract variation flowed into the subbie's claim and got paid while the matching head contract variation sat unapproved or missing from my claim, and nothing anywhere told me. The cost had left the business and the revenue was never billed. Before Silence. The gap compounded quietly across a claim cycle and surfaced at final account, long past the point where it could still be recovered. After When you prepare a head contract progress claim, the platform now surfaces every approved subcontract variation whose linked head contract variation is either unapproved or absent from the claim in front of you. Each one lists the SVO reference and subcontractor, the cost value approved, the reason it is being flagged, and links straight through to both records. Impact Nobody notices money they simply did not claim. This puts the gap on the screen at the exact moment the decision is being made, while the claim is still open and the correction still costs nothing. It is informational, not blocking: the CA makes the call, the platform just refuses to let the question go unasked. The exception strip on a new head contract progress claim, listing every approved subcontract variation the claim does not cover, why, and the head contract variations each one is linked to. Archive a batch of files in one action User Story As a document controller, a bad batch upload or a run of superseded drawings meant opening each file's drawer and archiving it one at a time. Clearing 74 files off a project was not realistic work. Before Single-file archive from the detail drawer, and nothing else. Both the Explorer and the Document Register had multi-select, and neither could do anything destructive with it. After Archive is now in the Explorer selection toolbar alongside Compare, Move, Copy and the rest, and in the Document Register bulk actions menu. Select, confirm, done. The confirmation lists the files, and in the Explorer it calls out separately when the batch contains documents that are on the Document Register, naming how many, because archiving removes them from the Register as well. Impact Clean-up stops being a reason to put clean-up off. The whole batch goes through one server-side operation rather than one call per file, so a set of 74 completes in a single pass instead of timing out. Bulk archive from the Explorer, warning that two of the selected files are on the Document Register and will leave it as well. Known limitations The Explorer action is file-only and is disabled when your selection includes folders. Folder deletion keeps its existing flow. There is still no permanent delete anywhere in the platform: archive hides the document from every active listing and retains the record. An attachment can become the next revision of a drawing you already hold User Story As a document controller, a marked-up Rev D came back on an RFI reply or landed in the Project Inbox, and registering it minted a brand new document series, so the register grew a second copy of a drawing it already had. Before The register button on an attachment chip opened a bespoke form that could do exactly one thing: create a new document. A revision answering an RFI about a drawing already on the register had nowhere correct to go. Email attachments that never became notices were a dead end entirely. After Attachments now register through the same Upload Revisions flow the Document Register uses. Register a brand new first revision, or pick the existing revision it replaces, straight from the thread the file arrived on, with the source recorded. This works on notice replies and on Project Inbox emails alike. Impact The document control path is one path now, wherever the file came in. Drawing history stays on one series instead of forking into duplicates that somebody has to reconcile later. As part of the same tidy-up, the attachment chip no longer offers two buttons that do the same job: Save to Explorer has gone, because Register reaches the same destination and does more. Upload revisions opened straight from a Project Inbox email. Drop the attachment onto the drawing it revises, or register it as a new one. Open Commitment on the Budget Register User Story As a project manager, I wanted to know how much of what I have already committed is still to be invoiced against, and the twenty columns on the Budget Register had no answer. Pending Commitment sounded like it should be it, and means something else entirely. Before Pending Commitment covers draft POs and draft subcontracts: commitment that is not approved and may never be real. That is a backward-looking question. Nothing on the register answered the forward one, which is contracted exposure. After A new Open Commitment column, available in the chooser on every workspace: approved commitment not yet invoiced. It is calculated as committed value less the actuals booked against those commitments, attributed per commitment rather than per cost code, so a cost code that also carries direct costs or bank transactions does not render negative. Column tooltips are now populated in plain language across Pending Commitment, Open Commitment, Remaining, Variance, Committed and Actuals to Date, and the Show info panel lays out the commitment lifecycle in order: Pending Commitment (drafts), then Committed (approved), then Open Commitment (approved, not yet invoiced), then Actuals to Date (invoiced). Impact Forward exposure is now a number on the screen rather than a calculation somebody does in their head with the wrong inputs. And the register explains itself: the difference between budget not yet committed and committed spend not yet invoiced is written down where the person reading the column can find it. Improvements A subcontract variation now shows where it went Before Open a subbie variation and you could see its subcontract, its claim and its payment schedule, and nothing at all about whether it was ever passed through to the client. The link existed, it just only pointed one way. After The subcontract variation drawer carries a Linked head contract variations panel: each head contract variation the SVO fed, with its status and the sell value attributable to this variation, and the individual scope lines listed underneath. One SVO feeding several lines groups into one row. One SVO feeding two different head contract variations lists both. If it was never passed through, the panel says so rather than hiding, because the absence is the information. In the other direction, the Imported from subcontract variation reference on Scope Item Detail is now clickable and opens the source record over your current context. Impact The question a CA actually asks, "did this ever reach the client, and on which variation", is now answerable from the record they are already looking at, in either direction. Your programme keeps its WBS codes and its percent complete Before An MS Project import landed task names and dates and dropped almost everything else. The WBS numbering your programme is organised around existed in the file and was rendered in no view in the platform, so anyone looking for their own WBS after import could not find it. After The importer now carries WBS codes and % Work Complete through, and the WBS code shows on the programme grid and on the lookahead export. Impact An imported programme reads like the programme you imported. Your own numbering survives the trip, which matters most for the people on site reading a lookahead rather than the scheduler who built it. The Project Inbox gets its Notice column, notice filter and Participants column back Before The Project Inbox rebuild traded away three things people used daily: the Notice column, the filter for messages linked to a notice, and the Participants column. After All three are back, with the notice link denormalised onto the search projection so filtering on it is fast rather than merely possible. The Project Inbox stops fighting your project selector Before The Refine rail rebuilt the whole query string from filter state every time you touched it, which dropped any parameter it did not own. The project selector put your project back, the rail stripped it out again. After The rail now edits the parameters it owns and leaves the rest alone. Your selected project stays selected. Submittals now live in one place Before Two Submittals entries in the menu: the new module under Documentation, and the legacy Coordination Submittals page it replaced. After The legacy menu entry is hidden. Submittals is under Documentation, and there is one of it. Fixes RFI and notice PDF downloads stop expiring Before The Download PDF control held a pre-signed link generated when the drawer opened and kept it for the drawer's whole life. Fifteen minutes later that link returned a 403, which read to customers as "the RFI PDF expires too quickly". After The link is minted when you click it, and notice PDF links now live 24 hours rather than 15 minutes. Attach PDF can file the document you actually chose Before On a payment schedule, Attach PDF could only ever file the payment schedule itself. On a contract billed by RCTI, that meant the RCTI never reached the record or Xero, no matter which document you picked. The covering email had the same problem: whichever document you sent, the email that went with it was the payment schedule's. After Attach runs from the template card for the document you chose, files into Unsorted, and records the CDE series it created against that document. The covering email follows the document being sent. The notice composer stops writing drafts you did not ask for Before Auto-save patched the entire notice form on a 1.5 second debounce with no dirty check, so opening a draft and closing it again rewrote it. Two separate reported defects came out of that behaviour. After The composer writes a draft when you ask it to, and only then. Spotted something, or want to tell us what should come next? The feedback portal is in the Deep Space web app, and everything raised there lands in front of the product team.