Another Big Day of Shipping - 3/8/26

Published 3 August 2026 A big day on several fronts. Commitments now start where the money is planned, the construction programme became something you can actually build in, the margin picture landed on one screen, and compliance documents chase themselves. Features Raise a Purchase Order or Subcontract straight from the Budget Register "I am already looking at the unbought scope. Why am I retyping it into a PO?" Before. Committing budget meant leaving the Budget Register, opening Purchase Orders or the Subcontract Register, then re-selecting cost codes and re-keying scope and values that were already sitting on screen. Every hop was a chance to mistype a cost code or drop a line. After. Select the budget lines you are buying, hit Create PO/Subcontract, and choose which one you are raising. The order opens prefilled: cost code, cost type, description and budget value per line, with the project already attached. Pick the supplier or subcontractor, trim the value if you are buying part of the scope, and save through the normal approval path. Multi-select works across cost codes. The new Create PO/Subcontract action on the Budget Register. Tick the budget lines you are buying, then choose whether this becomes a purchase order or a subcontract. The purchase order opens with the budget lines already loaded. Pick a cost code from the register and the line arrives prefilled with its description, budget value and cost type, so nothing is retyped.Impact. The Set Up and Move the Money halves of the wheel now touch. Buyout starts from the budget instead of alongside it, so the committed figure lands back against the exact lines you bought, and partial buyouts leave the remainder visible as unbought scope. Known limitations. Budget categories cannot be selected on their own, only cost code lines with a value. Where selected lines already carry commitments you will get a warning showing remaining budget, not a block. Build your construction programme inline, in the grid "It took me twenty minutes to add a handful of tasks. I would have done the whole programme in that time in MS Project." Before. The programme grid and Gantt were effectively read only. Changing anything meant opening the task detail panel, editing, saving, closing. Adding anything meant the full Add Task modal. Building a programme in the platform was slower than building it somewhere else and importing it. After. Add a row directly below any task and it chains itself: start date picks up from the row above, duration defaults to one working day, both editable. Double-click any cell to edit task name, duration, start and finish dates, or predecessor, in place. Edits commit on Enter or when you click away, with no save button to hunt for. Predecessors can be typed by row number, the way schedulers already work.--- Impact. The programme stops being a read-only picture of a plan built elsewhere and becomes the place you build the plan. For a PM living in the programme daily, this is the difference between the platform holding your schedule and the platform running it. Financial Summary tab: the WIP line for one job, opened up "The portfolio report tells me this job is forty five thousand down. It does not tell me why, or what changed since last month." Before. You already had both ends of this. The Commercial Dashboard gives you the live operational picture of a job. The WIP report, which landed last week, gives the board one line per job across the portfolio with earned margin, over and under claim, and cash. What was missing was the middle. When a job's WIP line looked wrong, working out why meant leaving the row and rebuilding that project by hand across the Head Contract register, the Budget Register, the approved forecast snapshot and the claims. Same numbers, four screens, and a spreadsheet to hold them together. After. The Financial Summary is that WIP line opened up into a full statement for a single project. Same definitions, same control basis, and the same figures that roll into the portfolio report, so the two always agree. Four blocks: Revenue from the Head Contract register, Cost from the Budget Register against the approved forecast, Margin derived from both including the risk and opportunity overlay, and Cash covering billing less cost, work in progress and retention in both directions. The header states the forecast basis, what you are comparing to, and who locked the snapshot. Every value is derived. Nothing on this page is typed. Revenue and Cost on one screen: contract value through to anticipated final value on the left, revised budget through to forecast final cost on the right, with the forecast basis and the locked snapshot named at the top. Then the part neither the dashboard nor the portfolio report could do: explain the movement. The margin bridge opens at the last approved margin, walks through everything that took it to today, and closes at the current position. Approved head contract variations, forecast to complete changes per cost code, contingency and trade reserve released or drawn on, and the risk and opportunity net. Each bar names the cost code and the forecast reference behind it, and clicks through to the build-up notes in the approved snapshot or into the risk register. The margin bridge. Opening margin, then a bar per cost code movement, then the risk and opportunity position, closing at margin including risk. Each bar carries the cost code and the forecast reference behind the movement. And because the fastest way to lose faith in a number is not knowing where it came from, Show data sources colour codes every field by origin and prints its derivation underneath. It runs off the same source dictionary as the Commercial Dashboard and the WIP report column tooltips, so a term means the same thing everywhere you meet it. Show data sources switched on. Each figure names where it came from, so Forecast to Complete reads as the approved snapshot total and Cost to complete reads as forecast final cost less actuals. No more guessing which number a number is made of. Impact. The portfolio report tells a director which jobs need attention. This tells them why, on the job, in the same numbers finance will report and reconciling to the same WIP row. Margin sits at the centre of the Builder's Wheel, and this is the first screen that shows it moving rather than just standing still. When the question is why margin dropped forty five thousand, the answer is on the page with a drill-in, not in someone's head. Document expiry reminders that chase themselves, plus a live Expiring Documents register "I find out an insurance has lapsed when someone is already on site." Before. Keeping subcontractor insurances, licences and inductions current was a job that only got noticed when it went wrong. Reminders were scheduled far in advance at the moment a document was captured, so a vendor who had already renewed kept getting chased, duplicates went out, and the form link in an old email could be stale by the time anyone clicked it. There was no single place to see what was about to lapse. After. Three things changed. Reminder emails now go to the vendor's primary contact 1 month, 1 week and 1 day before a document expires, each carrying an Update Document Now button that opens your workspace's document request form directly, with no Deep Space login required. The vendor uploads the renewed certificate in under a minute and it files itself against their company as a new version of the same document. Reminders are computed fresh each morning from your live document register rather than scheduled ahead. A vendor who has already renewed stops being chased immediately, duplicates are gone, and the link in every email is always the current one. A new Expiring Documents tab in the Company Directory lists every subcontractor compliance document in the workspace with its expiry date and urgency, colour coded from expired through expiring within a month, filterable by company, category and expiry window. Each row shows its reminder status, and documents with no reminders scheduled are flagged so nothing slips through quietly. Notification Log now has an Email tab recording every reminder sent, with recipient, document, time and delivery status, so "did they ever get reminded?" is one search away. Company Settings, Induction Settings. Choose which document request form the reminder button opens, and switch on dynamic daily reminders so they are recomputed each morning from your live register instead of pre-scheduled. Impact. Compliance stops depending on someone remembering to check a folder. The platform watches the expiry dates, chases the vendor with a link they can act on without an account, and files the renewal in the right place on its own. Rolling out now. Dynamic reminders are switched on per workspace under Company Settings, Induction Settings. Your workspace admin can enable them, or reach out and we will walk you through it. Improvements Claim SOV Items now shows the whole contract, not just what was claimed Before. The SOV Items tab on a subcontract claim listed only the lines being claimed this period, and certified and programme percentages rendered as dashes. On a claim touching five of eight lines plus two variations, you could not see the cumulative position without opening the subcontract in a second tab. After. Every schedule of values line and every variation shows, claimed this period or not, with contract value, claimed to date, certified to date, remaining and programme percentage, each as a dollar figure and a percentage. Totals reconcile to the claim header and to the claim PDF.Impact. Assessing a claim no longer means reconstructing the contract position from two screens. What you certify, you can see in full. Practical Completion is now a date you can set, and the WIP report uses it Before. The Pract Comp column in the Project Financial Summary (WIP) report showed a dash for every project, and there was no field in the platform to set the date even if you wanted to. After. Practical Completion sits in Project Settings under Dates and Milestones, alongside planned completion and forecast finish. The WIP report resolves the date in order of truth: anticipated practical completion from the programme rollup where extensions of time are in play, then the Practical Completion milestone, then the planned completion date. The date carries into the report CSV and the board pack PDF. The new Practical Completion Date field in Project Settings, Dates and Milestones. The helper text tells you exactly when it is used: it drives the WIP report's Pract Comp column where a project has no programme rollup, and approved extensions of time take precedence. Impact. Approved extensions of time now move the completion date the board sees, instead of the board seeing a blank column. The risk and opportunity register now reaches margin Before. The register said its net position flowed into the forecast, and the WIP report's risk and opportunity adjustment showed zero on every project. Two statements, both wrong in different directions, and a risk register that never touched a margin figure. After. Risk and opportunity adjustment is the project's live net most likely position (risks less opportunities, closed entries excluded), sign flipped so net risk reduces margin. Margin including risk and opportunity follows, along with the downstream margin percentage and margin realised. The register copy now says where the number actually goes. The WIP report with R&O Adjust carrying real numbers, feeding Margin incl R&O and Margin % beside it. The column tooltip states the rule: net risk reduces margin, net opportunity increases it. Pract Comp is populated in the same view. Impact. Carrying risk in a register nobody reconciles to margin is just paperwork. Now the register moves the number that matters. Push an accepted payment schedule to Xero when you are ready Accepted payment schedules that are not yet in Xero carry a Push to Xero button on the record, with the sync state shown next to it. Accepting without pushing is now a decision you can reverse in one click.Impact. No more silent gaps between an accepted schedule in the platform and a payable in the ledger. Faster Head Contract and Subcontract screens Head Contract and Subcontract records with long schedules of values and busy claim histories were starting to slow down to open. Backend work on both record types has cut load times, so there is less waiting on the screens commercial teams open dozens of times a day. Fixes Percentage entry on subcontract claims now works off contract value Typing a percentage on a claim line was calculating against the remaining balance, not the contract value. On a line with a quarter already certified, typing 50 produced half of what was left rather than half of the contract, so claims came out low and nothing on screen explained why. Percentages now resolve against the line contract value and net off prior certified amounts, and the field label reads Claim Amount, dollars or percent of contract, so the basis is on screen.Claim Amount = 76,304.9 50% = 38,152.45* 38,152.45 - 190.076.23 = 19.076.22 this time Subcontract progress claim PDF summary columns The claim summary table on the subcontract progress claim PDF had its columns mis-bound. The contract schedule never reached the renderer, so When Complete and Previously Approved sat at zero on every row, which made Remaining render as a negative number on a statutory payment document, and retention withheld came through as nil. Before. Every row shows the contract as zero, so Remaining reads minus $119,032.50 on the original contract line and retention withheld comes out at nil. After. The contract schedule and the prior certified position both carry through, so Remaining is the genuine unclaimed balance, retention is calculated, and the claim now names the previous claim, its date and what was certified. Certification emails now carry the claim PDF Claims submitted for certification were dispatching with no PDF attached, so the recipient had nothing to assess and the approval loop stalled. The claim PDF is now attached to the email as a file, not a link, along with the claim's own attachments. The payment schedule dispatch uses the same path. No more raw merge variables in claim and payment schedule emails Claim and payment schedule emails were going out to subcontractors with unresolved template variables sitting in the subject line. Those templates now resolve correctly, and an unresolvable variable blocks the send and logs it rather than dispatching raw text to your subcontractors. Register-pushed subcontract claims land in Draft When accounts pushed an invoice through the Invoice Register, the subcontract claim was created already Submitted, so the delivery team never got to assess it before it left the gate. Register-push now creates the claim in Draft. Submitting is a deliberate act by whoever is assessing. Programme durations count working days Task durations were counting calendar days, so a task spanning a weekend read two days longer than the work in it. Durations are now working days against the project calendar, public holidays included, and the field says so. Dependencies now drive successor dates Linking two tasks did not move the dependent task's dates, and where a cascade did fire, the successor started on the same day the predecessor finished. Finish-to-start now means the successor starts on the next working day, and changing a predecessor cascades through the chain. Duration field no longer resets while you type The duration input was snapping back and overwriting values mid-keystroke, so entering a two-digit duration was a fight. Number fields now hold what you type and commit when you are done. Head contract variation quantity rounding Quantities on head contract variations were rounding in a way that shifted the variation total. Corrected. Got something you want to see in the Deep Space web app? Tell us through the feedback portal in the platform. Every entry above started as someone on a site or in a commercial office telling us what was getting in the way.