What Got Shipped Today - 20/8/26 - Price lists in the BoQ, Provisional Sums draw down in stages, submitted variations can come back

20 August 2026 Twelve changes reached production today. The through-line is commitment: what a price came from, what has actually been drawn down, who signs first, and who is waiting on whom. Features Build a BoQ line straight from a supplier price list As an Estimator, I kept a supplier’s rates in a spreadsheet beside Deep Space and retyped them into every BoQ, so I can now pull the rate from a price list inside the platform and keep the link back to where it came from. Before. Rates lived outside the estimate. Every BoQ line was typed from a PDF, an email or a spreadsheet tab, and once it was in, nothing recorded which supplier quoted it or when. Three months later, nobody could say whether $1,950 for a 50T crane was still the number. After. The Add New Item modal has a new From Price List tab. Pick a workspace price list, search it by code, name, unit or cost rate, and confirm. The cost, sell and margin trio prefills and stays coupled, the item’s default cost code carries the budget category and cost type with it, and lump sum items seed at quantity 1. If you do not have a price list yet you can create one and add its first item without leaving the modal, so an empty workspace goes from zero to a priced BoQ row in a single flow. Every line built this way carries its lineage. The BoQ row shows a teal Price List pill, and opening it tells you the list, the supplier, the item code, the rate at the moment you linked it, and the current list rate. When those two diverge, the platform says the list price has moved rather than letting you find out at buyout. Impact. Rates stop being folklore. An estimate you priced in March can be interrogated in August, line by line, with the source and the drift both on screen. Overriding a rate is still one keystroke, and the override is now visible instead of silent. Known limitations. This is the first phase and carries a beta pill. New price lists take a supplier name as free text for now; picking a supplier from the directory arrives with the purchase order integration. Workspaces with no price lists see one new tab with an empty state and nothing else changes. Draw down a Provisional Sum in stages As a Commercial Manager, a Provisional Sum was either fully approved or not approved at all, so I can now authorise spend against an allowance progressively and see exactly what is left. Before. Activation was all or nothing per Provisional Sum. Remaining was only ever the full allowance or zero, which is not how a PS behaves on a real job. Costs land in pieces, and the register could not represent that. After. A Provisional Sum now carries a drawdown ledger. Add a drawdown, price its lines with margin, approve it, and the register plus the head contract PS tab show Allowance, Drawn and Remaining at every point. Drafts can be edited or deleted freely with no money effect. Drawdowns within the allowance move the claimable figure only, so a claim can never run ahead of what has actually been authorised. Cross the allowance and the platform crystallises the net adjustment through whichever instrument that contract is set to. In Direct mode a single PS adjustment line appears in the schedule of values and is revised in place as later drawdowns land, so you get one adjustment rather than a stack. In Via Variation mode the crossing generates a draft head contract variation carrying that drawdown’s scope, cost, sell and margin, and the variation becomes the instrument of record. The link runs both ways: dispute the generated variation and its drawdown reverts to unapproved. The mode locks on first approval, so it cannot be changed underneath a live allowance. When the work is done, Close the allowance. Any under-run is issued as a credit through the same instrument, and the status goes to Closed. Impact. This is how AS4000 clause 3 and NZS3910 clause 12 actually work. The client pays actuals plus margin, never the estimate, and every movement is a traceable adjustment line rather than an edit to a signed figure. Exactly one record contributes to the contract sum for any drawdown, enforced in the aggregation layer, so a drawdown can never double the contract value. Known limitations. Provisional Sums already activated line by line keep the old behaviour and live out that life. A PS switches to the ledger at its first drawdown, and once it has, per line approval steps aside. Pull a submitted head contract variation back to draft As a Contract Administrator, a variation I submitted to the client was stuck there even when it needed a correction, so I can now revert it to draft, fix it and resubmit without asking anyone to unlock it. Before. A variation had a status chip but no lifecycle behind it. Once it read Submitted there was no legitimate way back, so a typo or a repriced line meant an out of band unlock from us before the record could be corrected. After. Submitted variations get a Revert to Draft action, guarded by a notice that spells out the consequence: reverting removes the variation’s pending schedule of values lines from the head contract and they stop being claimable until it is submitted again. Reverting is blocked outright while a claim or payment schedule references those lines, so the revert can never strand certified money. Draft variations can be deleted from the register, and every variation now carries a Timeline you can open to see each transition on the record. Impact. Correcting a variation is a normal Tuesday action instead of a support ticket. The audit trail holds, because the platform refuses the revert in exactly the cases where an audit trail would be broken by it. Choose who signs a subcontract first As a Commercial Manager, our subcontract execution order was fixed for everyone, so I can now set the signing sequence our business actually uses and have every subcontract follow it. Before. One signing order was hard coded platform wide. Subcontractor first is the ANZ norm and the right default, but a minority of builders genuinely sign first, and that is a legitimate process choice rather than a mistake. It happens where the subcontractor’s or supplier’s own form governs, on structural steel, lifts, major plant hire and tier one supply agreements, or where a builder wants to lock a scarce trade quickly. After. Workspace Settings, Commercial section, now carries a signing sequence setting with two values: subcontractor signs first and head contractor countersigns, or head contractor signs first. Every existing workspace lands on subcontractor first with no action required. Only an admin can change it, and the change is written to the audit log with who, when, and what it moved from and to. The setting is a default. The sequence is pinned onto the subcontract at the moment it is issued for execution, so changing the setting never alters a contract already out for signature. Contracts in flight complete on the order they were issued under. Impact. Signing order becomes company policy rather than whatever the last person chose in the e signature tool. Procore, Autodesk Build, Aconex, Jobpac, Vista and Workbench all push this into the e signature layer, configured per envelope by whoever hits send, which makes it inconsistent between users and unenforceable as policy. A workspace default that pins onto the contract holds. Known limitations. Subcontracts only in this version. Per document type overrides, a per contract override at point of send, and conditions precedent on countersignature are all follow ups. Improvements The Tender Tracker now matches the register As an Estimator, the Tracker was the view I wanted to live in but it was missing the numbers and filters I relied on, so I can now work the whole pipeline from one screen. Before. The Tracker had the board and the list, and the register had the summary tiles, the filters and the readable table. Working a pipeline meant bouncing between the two, and on a long list the column headers scrolled away so you lost track of which figure was which. After. Four things land together. The Tracker hub now carries the register’s summary tiles: live tenders, closing this week, submitted awaiting result, and win rate on a rolling twelve months. The list gets a Type filter and a Closes date range filter. The header freezes so it stays put however far you scroll. And tags render on the list rows, so the shorthand your team uses to sort work is visible without opening anything. Impact. One screen answers what is live, what closes this week, what is still out with a client, and how you are converting. The tile calculations run off one shared implementation, so the Tracker and the register can never quietly disagree about your win rate. Approval steps can draw from a project team or the whole workspace As a Director, our approval routes had to pull approvers from one place for the whole workflow, so I can now mix a project role on one step with a value based delegation on the next. Before. Role scope was set once for an entire approval workflow. The common shape, where step one goes to this project’s site manager and step two follows delegated authority by value, was not buildable. Delegation of authority was also hidden whenever a workflow was scoped to a project, which made a project ladder with a value gate impossible to construct. After. Every fixed role step in a workflow carries its own Roles from selector: workspace role, or this project’s team. Delegation of authority is available on any step regardless of scope. The workflow level setting is now clearly labelled as the default role source, seeding new steps rather than governing all of them, and each step’s own scope overrides it. Existing workflows read their stored scope and keep behaving exactly as they did. Impact. Approval routes can finally describe how a builder actually approves. The person closest to the work signs first, and the money gate above them resolves on value, in one route, without a workaround. Invoice register detail reads clearly and links straight to Xero As a Contract Administrator, the invoice detail panel labelled things in language that did not match what I was looking at, so I can now read it at a glance and jump to the Xero record in one click. Before. The matched detail panel called the invoice a Claim ID, which is a different object in the platform, and the Xero reference was text you had to go and find manually on the other side. After. Labels say what the fields are. The Xero reference is a link that opens the corresponding record in Xero. Impact. Less second guessing on a screen that reconciles money, and one less tab hunt when you need to see the bill itself. One portal invite email per person, per project As a Contract Administrator, inviting a subcontractor to a handful of projects filled their inbox with near identical emails, so I can now invite them once per project and nothing else. Before. Inviting one person to a company plus a number of projects sent one email for the company assignment and then one for every project on top. From the recipient’s side it looked like a system misfiring, on their very first contact with us. After. The company assignment email is suppressed by default. Each person receives one invite per project they have been given access to, and nothing more. Impact. A portal invite now looks deliberate. First impressions on a subcontractor portal matter more than most things we ship, because the alternative to using it is ignoring it. Subcontract variations lose the payment claim tickbox As a Contract Administrator, the new subcontract variation form asked me to declare a variation as a payment claim under the Act, which is not what a variation is, so that question is now gone. Before. The New and Edit Subcontract Variation modal carried a This is a Payment Claim under the Act (SOPA or CCA) checkbox. A variation is a change to scope and price, not a payment claim, so the field invited a wrong answer on a document with statutory consequences. After. The checkbox is gone from both the new and edit flows, and the flag is no longer sent. Impact. One fewer opportunity to mislabel something that matters under security of payment legislation. Fixes Subcontractors can see the bookings waiting on them As a Site Manager, I booked a subcontractor onto a programme task and heard nothing back, because the only way they could respond was a link in an email they had already lost. Before. Booking acceptance shipped with a builder side view and no portal surface at all. The notification email carried a deep link, and that link was the only route in. A subcontractor who opened the portal directly saw no booking, no badge and no alert. Meanwhile the builder side showed pending, accepted and rejected tiles, so the capability appeared to work from one side of the fence only. After. The portal Programme tab now shows a banner above the Gantt listing every booking waiting on that company, with the task name, trade and dates on each row. Respond opens the same accept and reject dialog the email link opens, so there is one implementation and it cannot drift. The banner disappears once nothing is pending. Impact. The loop closes inside the portal. A subcontractor who has lost the email can still respond, and a booked date stops being a guess. Known limitations. The banner lives on the Programme tab. A subcontractor sitting on another tab still gets no alert, which needs a global surface and is being tracked separately. Converting an opportunity to a tender keeps its people As an Estimator, converting an opportunity to a tender asked me for a location the project already had and quietly dropped the team members I had just selected, so both of those are fixed. Before. Three problems, one flow. The convert wizard re asked for a location the project already carried. Team members selected during conversion were silently lost on save, with no error to tell you. And the Add button in a tender’s Team section was permanently disabled, so you could not put them back afterwards either. After. Location is gone from the convert wizard and from the new and edit tender modals, since the project already holds it. The tender level Team concept has been retired in favour of the Estimator and Coordinator carrying ownership, which removes a third parallel people list that had no downstream behaviour attached to it. Adding and removing people on a tender works, and a successful save no longer reports a failure. Impact. A converted tender arrives with the right people and the right location, first time. One people concept instead of three. A voided Xero bill number no longer blocks a re-push As a Contract Administrator, I voided a bill in Xero and then could not push the corrected version back under the same invoice number, so that now works. Before. The preflight check that looks for an existing bill treated voided and deleted documents the same way and filtered both out of the same number lookup. Xero does not, so the number was reported as free when Xero still considered it taken, and the push failed. After. A voided document number is treated as taken rather than free, and the push resolves correctly. Impact. Voiding and re-pushing a corrected bill is a normal correction path again. Something here you would do differently, or something missing you need? Tell us through the feedback portal in the platform. It goes straight to the people who build this.