What Got Shipped Today - 27/10/26 - Client-ready weekly reports, duplicate invoice protection, drawing revisions in one click, Cost Plus claims and Xero tracking that sets itself up

27 October 2026 Features A weekly progress report you can send straight to your client "As a Contract Administrator, I spend a couple of hours every Friday pulling photos, progress and safety numbers into a client report by hand. I want the platform to build it for me." Before: The Weekly Progress Report was built for a PCG meeting: a programme Gantt plus the commercial registers. It had no photos, no plain-language summary of works, no safety section, and Generate & Publish went straight to a live link with no chance to check it first. After: Choose the client report under Report for and the platform builds a stakeholder report from data already in your project. The cover carries your logo, the project, location, Project Manager, stage and week number. Inside: a Summary of works (completed this week and coming up, by trade), Progress photos picked from the week's site diaries and DS Site captures, a Progress snapshot of milestones, Health & Safety, Information required from the client, and attachments. Commercial sections stay out of the client version. Every report is now generated as a draft first, so you can untick sections, choose the photos and read it through before you publish and share the link or PDF. Impact: The Friday report goes from a couple of hours of copy and paste to a few minutes of review, and it always matches what's recorded in the project. Known limitations: Scheduled generation and an automatic email to a stakeholder distribution list are coming next. (1) Pick who the report is for: the PCG status report or the new client-ready version. (2) Every report starts as a draft you can review before publishing. (1) The client cover: your logo, project details, week number and a contents list, ready to send. (1) The Summary of works lists what was completed this week and what's coming up, trade by trade. (1) Choose exactly which site photos from the report week go into the report. KAI can add an action to your list, with your say-so "As a Site Manager, when I'm talking a problem through with KAI I want it to put the follow-up on my action list, not just tell me to do it." Before: KAI and connected assistants could read your Delivery actions but couldn't create one. You still had to open Action Items and type it in yourself. After: Ask KAI (or an assistant connected to Deep Space) to create a Delivery action and it shows you a preview first: title, description, due date, priority, category and location. Nothing is saved until you confirm. The action is created by you, assigned to you, labelled with the assistant that made it, and appears in the Action Items register and on your Home My Actions card. For outside assistants this needs a separate opt-in on the connection page, and you need Manager or Collaborator access on the project. Impact: The thing you just decided to do lands on your list in the same conversation, so it doesn't get lost between the chat and the register. Known limitations: Actions can only be assigned to yourself for now. Editing, completing and assigning to others are not included. New projects set themselves up in Xero "As an Accounts lead, I don't want to create a tracking option in Xero and then map it in Deep Space every time we win a job, and I don't want costs landing in Xero without a project tag because someone forgot." Before: Every new project meant two manual steps: create its tracking option in Xero, then add the mapping row in Finance Integrations. Miss either one and the project's transactions went to Xero untagged. After: Turn on Auto-create Project Tracking in Xero in Finance Integrations (Xero tab, just above Project Mapping) and pick the Xero tracking category that holds your projects. From then on, when a project reaches Delivery or DLP, Deep Space creates its tracking option in Xero, named after the project, and adds the mapping row for you. Projects created directly are set up the moment they're created. If an option with the same name already exists, Deep Space links to it instead of making a duplicate. Projects already running get a Review and create button so you can catch them all up in one go. If Xero refuses, the project still moves to Delivery and the failure appears under Project Mapping with the reason and a Retry button. Impact: Every project is tagged in Xero from day one, with no double handling and nothing that fails silently. How to use it: The switch is off by default. If your Xero connection was set up before 23 October, disconnect and reconnect it once so Xero grants permission to create tracking options. Reconnecting the same Xero organisation keeps all your existing mappings and settings. Known limitations: Renaming or archiving a project doesn't yet rename or archive its option in Xero. (1) Switch auto-create on and choose the Xero tracking category for your projects. (2) New projects appear here as mapping rows automatically. Duplicate invoices are caught before they're paid "As an Accounts lead, I need the platform to stop a resent invoice before it gets paid a second time, not after Xero shows it twice." Before: A supplier could resend the same invoice, a copy could be linked to a different purchase order, and it could travel all the way through approval to Xero with no warning. After: Every invoice is checked for duplicates. An identical file is caught on upload, even if it's been renamed. After KAI reads it, the same supplier, invoice number and amount is flagged, and so is the same supplier and amount within 7 days. The same number with a different amount is flagged as Revised or resent? Only the copy is flagged, never the original. A banner on the invoice names the original and gives you Open existing, Mark as duplicate or Not a duplicate (with a reason, logged on the Timeline). Until it's resolved, Send for Authorisation, Push to Payment Schedule, Authorise Payment and Push to Xero are all blocked with a message naming the original. KAI no longer auto-links a copy, and a new Possible duplicate badge and filter sit on the Invoice Register. Impact: The double-payment loop is closed. The same bill can't be paid twice by accident, and your team sees why in plain words. Every drawing revision, one click away "As a Site Manager, I need to see what changed between the last two revisions without hunting through folders." Before: Opening an older revision or comparing two took six or more clicks, superseded revisions were hard to open, and the register labelled versions as v1 and v2 instead of their Rev. After: Every row on the Document Register now shows a Rev pill (for example "Rev E of 2"). Click it to see every registered revision, newest first, with View on each and vs current to compare. A Compare A to E quick action sits on each row and opens straight to previous vs current. The document drawer now leads with its revisions. In the drawing viewer, a new revision dropdown in the header lets you switch to any registered revision in place, at the same zoom and position, with each one tagged Current or Superseded. Compare now opens straight on the revision pair, labelled by Rev (for example Rev A vs Rev E) with Current and Superseded tags, and you can swap sides or pick any other registered revision from either side. Impact: Checking what changed between revisions takes one or two clicks, from the register or from the drawing itself. (1) The Rev pill on each register row lists every registered revision. (2) Compare any older revision against the current one in a click. (1) The previous revision, tagged Superseded. (2) The current revision. Compare opens on this pair with one click, labelled by Rev. Section only Schedule of Values for your client "As a Commercial Manager, I want my client to see one line per estimate section, not 465 items, while I still track cost by cost code." Before: Build SOV could group by category or show every item, so a detailed estimate meant a long client Schedule of Values. After: A new Section only option on the Build SOV group-by bar gives one client line per estimate section, with cost and sell rolled up and an optional section-level sell override (spread across the items pro rata to cost, to the cent). Underneath, every item keeps its own cost code, so the Budget Register, cost progress, Margin Analysis and variations still report by cost code. Claims are entered at section level and flow down to the items. The SoV preview and claim PDF show one row per section. Provisional sums and contingencies stay as their own lines. Impact: Your client sees a clean, short schedule, and you keep full cost code detail behind it. Known limitations: The Xero invoice still lists item lines. That's coming next. Cost Plus claims prefill from cost, and dayworks run as a running total "As a CA on a cost plus job, I want the claim to bill the approved cost since the last claim plus our fee, without me building it in a spreadsheet." Before: Cost Plus head contracts (shipped yesterday) had no claim mode of their own, so the CA still had to work out the period's reimbursable cost and fee by hand. Dayworks meant raising top-up variations every time the cost grew. After: On a Cost Plus head contract, the progress claim opens in a new Cost Plus prefill mode. Each Schedule of Values line bills the approved cost on its cost codes up to the claim's cut-off (certified subcontract claims, approved supplier invoices, accepted credit notes, manual entries and cost transfers) that no earlier claim has billed. The Fee line is that reimbursable cost times your Fee %. Non-reimbursable codes are listed and excluded, cost on unlinked codes is flagged, and a record entered late is picked up by the next claim and marked "Late", never billed twice. A line over its estimate is flagged, not blocked. A Records column shows every cost record behind each line, and Recalculate from cost refreshes the claim. Separately, a new Cost plus / dayworks head contract variation type takes a not-to-exceed cost and a Fee %. Once approved, Draw down from cost pulls the new cost on its code at cost plus fee, and the variation shows its running total: allowance, drawn, and left or over. Impact: Cost plus and dayworks claims are built from the cost already in the platform, with the fee worked out and every dollar traceable to its record. Known limitations: The open-book cost schedule on the claim PDF and client portal is coming next. Improvements Weekly reports only show this week "As a Project Manager, I don't want draft RFIs or variations from February turning up in this week's report to the client." Before: RFI Status listed every RFI, including drafts and superseded ones. Variations and progress claims listed everything since project start. Empty sections still printed, and the lookahead Gantt used less than half the page width. After: Reports cover the 7 days ending on the report date. RFIs show open ones plus any closed that week, never drafts or superseded. A new Variations and progress claims setting lets you show This week's movements only or This week's movements, plus all open. Sections with nothing to report are left out, and the Gantt fills the page. Impact: What the client reads is this week's story, with nothing internal slipping through. (1) Set the period for variations and progress claims. The report covers the 7 days ending on the report date. Column and filter panel on the Document Register "As a Document Controller with hundreds of drawings, I want to filter and sort the register the same way I do on every other register." Before: The Document Register had its own toolbar filters, but no per-column filters, no header sort and no way to choose columns, unlike the Invoice Register, Budget Register and Project Documents Explorer. After: A Columns & Filters panel now sits on the Document Register. Filter by any column, sort from the column headers, show, hide and reorder columns, and see your active filters as chips with Clear all and a filtered count. Your existing toolbar filters, including the revision date range, still work and combine with the panel. Impact: Finding the right drawing in a long register takes a few clicks, and the register works like the rest of the platform. Subcontractor payment schedules carry a Payment Due Date to Xero "As an Accounts lead, I want the Xero bill to fall due when we actually pay the subbie, not on the statutory schedule deadline." Before: A subcontractor payment schedule had one due date, the statutory schedule deadline, and that's what Xero used as the bill due date. After: Every subcontractor payment schedule now has two dates: Schedule Due (Statutory), worked out from the claim date and the response period in business days for the subcontract's state, and Payment Due Date, from the subcontract's payment terms. Both can be edited until the schedule goes for approval. The Xero bill now uses the Payment Due Date. A new Payment Schedule Response Period field on the subcontract (shown when SOPA or CCA applies) defaults to the state's period if left blank. The Payment Schedules (Issued) register gains a Payment Due column, and the payment schedule and RCTI documents print the payment date. Impact: Your Xero aged payables match when the money actually goes out, while the statutory deadline stays tracked in Deep Space. Change security and retention on an executed head contract "As a Contract Administrator, the client agreed to change retention after we signed, and I need the platform to reflect that without breaking past claims." Before: Security and retention were locked once a head contract left Draft, so a change agreed after execution couldn't be recorded. After: Workspace administrators get a new Amend action on the Security & BGs tab of an executed head contract. A reason is required. Claims already submitted or certified keep the settings they were made under. Draft and new claims use the new settings, and retention caps count what was already held. Every amendment is listed under Amendment history with the date, who, old and new values and the reason. Impact: Contract changes are recorded properly, and no claim already in progress is re-priced behind your back. Linking a programme task in a subcontract SoV updates the programme "As a Project Manager, when I link a programme task to a subcontract line, I want the programme to know who's doing it and the cost code." Before: Linking a task in a subcontract Schedule of Values did nothing on the programme. Planners typed cost codes and subcontractors in by hand. After: When a subcontract SoV line is linked to a programme task, the cost code is written to the task straight away, and the subcontractor once the subcontract is approved. A link icon shows on the programme, and the hover names the subcontract and SoV line. A planner's own value is never overwritten. If a task's code is more specific than the line's, it's treated as a match, and if the line covers several codes, the task asks the planner to pick one. Saving the SoV tells you if anything on the programme needs a decision. The subcontractor is set as a pending booking, with no notification sent at that point. Impact: The programme and the commercial side agree on who's doing what, without typing it twice. Induction approvals name the company "As an approver, I can't approve an induction when all I see is a submission number." Before: Company General Induction approvals showed as "Company General Induction 5131", with no company or requester, so approvers had to click in to find out who it was. After: Induction approvals now show the company name in My Approvals, the Home widget and the approval email subject, plus the person who sent the induction invite. Inductions submitted without an invite read "Auto-requested from DS Site". Existing approvals have been updated too. Impact: Approvers can see who they're approving at a glance. DS Site forms explain why a submission was blocked "As a subcontractor on site, when the form won't submit, I need to know what's missing." Before: When a form rule blocked a submission (for example, needing an induction for the same site first), DS Site and the Deep Space web app only said "Some fields are incomplete or incorrect", with nothing listed. After: The message now spells out the rule: which form or category is needed, for which site or value, and over what period. If the field it depends on is blank, it asks you to fill it in. The same wording appears on the Deep Space web app and DS Site, with no DS Site update needed. Impact: Workers fix the problem on the spot instead of calling the office. Known limitations: The rule is checked when you press Submit, not as you fill in the form. Portal folders show what's inside "As a subcontractor in the portal, when I open a folder I expect to see its subfolders, not a blank page." Before: In the portal's Documents explorer, opening a folder that only held subfolders showed an empty page, and long folder names were cut off in a narrow folder tree. After: Opening a folder now lists its subfolders and files in the document area, and you can open subfolders from there. A truly empty folder says so. The folder tree is wider, so full names are readable. Impact: Portal users find documents without guessing which folder to click. Fixes Weekly report project list only shows projects you can open Before: The Project dropdown on the Weekly Progress Report listed every project in the workspace. Choosing one you weren't a member of failed with a generic "Failed to generate report". After: The list now matches your project access, the same as the project switcher in the header. Impact: No more dead ends when generating a report. Publishing a draft programme keeps the progress you entered Before: Progress entered in a draft programme could be lost when the draft was published, inline progress edits could fail, and saving a task in the drawer could rewrite dates nobody touched. After: Publishing now applies only what you changed in the draft. Progress changes are listed in the publish review alongside date changes. If someone changed the same task on the Live programme in the meantime, it's shown as a conflict for you to confirm. Inline progress edits save, and a progress-only save no longer moves the schedule. Impact: What you publish is exactly what you changed, and nothing on Live is overwritten by accident. (1) The publish review lists only the edits made in the draft, including progress. Project Inbox replies stay in their own thread Before: If you worked across several projects, a reply picked up by one project's mailbox sync could be saved against that project, and disappear from the thread it belonged to. After: A reply now always joins the project of the thread it belongs to, whichever project's sync picks it up, and it's stored only once. Replies that were already saved against the wrong project have been moved back. Impact: Every conversation shows up complete, in the right project. Have feedback or ideas? Tell us through the feedback portal in the platform. We read every message.