What Got Shipped Today - 23/7/26

23 July 2026 A big day across the platform. The document explorer picks up two file-management moves you have been missing, Submittals grow up into a proper action-and-signature workflow, accepted payment schedules now flow to Xero on their own, tender invites get smarter about who they come from, and every workspace can now shape its own trades list. Features Submittals now show whose court the ball is in, with a signature gate to close As a Contracts Administrator handling external submittals (shop drawings, samples, certifications), I could never tell at a glance who owned the next action or whether something still needed signing, so I chased status by email. Now the register tells me, and nothing closes until it is signed. Before. Submittals had no owner field, no working status, and no way to force a sign-off. You tracked whose turn it was in your head or in your inbox, and a document could be marked done whether or not it had actually been signed. After. Every submittal now carries an Action Required By field (person or company), a status of Open, Closed or Archived you can filter on in the register, and a signature workflow. A submittal flagged as needing signature cannot move to Closed until it is signed, through the no-login portal for external parties.Impact. You can open the Submittals register and immediately see what is outstanding and who is holding it up. Sign-off is enforced, not assumed, so a closed submittal genuinely means closed. This is the largest of the three gaps builders benchmarking us against Procore kept pointing at, and it is now handled natively in the Deep Space web app. Copy files and folders in the document explorer, the way your desktop does As anyone managing project or company documents, I could move files but never copy them, so duplicating a folder structure into another location meant re-uploading everything by hand. Now I select, copy, and pick a destination. Before. The document explorer only offered Move. There was no way to duplicate a file or a whole folder tree to another location, so reusing a structure meant rebuilding it from scratch. After. Select files and folders, hit Copy, and choose where they land. Fully selected folders copy recursively with their structure intact. Same-name files auto-suffix "(copy)", "(copy 2)" and so on, exactly like an operating system. The copy runs as a background job with a live progress chip, so large copies do not tie up your screen. The confirm step before a copy runs, showing how many files and how much data will be copied, and a note that it runs in the background. After the copy, the duplicated file appears with a "(copy)" suffix and the background jobs chip shows the copy has completed. Impact. Setting up a new project's document tree from an existing one is now minutes, not an afternoon of re-uploading. Because copies start a fresh version history and never share the original's storage, duplicating a file can never accidentally corrupt or delete the source. Build your own trades list, and add a trade without leaving the tender package As an estimator or CA setting up a tender package, I was stuck picking from a fixed, platform-wide trades dropdown that never matched how our business names things. Now the list is ours to shape, and I can add a missing trade inline. Before. Trades came from a single global list shared by every workspace. If the trade you needed was not there, you could not add it, and one customer's additions would have leaked to everyone. After. Each workspace now has its own customisable Trades list, managed under Company Settings (add, rename, archive, restore). In the tender package trade dropdown, a "+ Add new trade" option lets you create a trade inline and select it on the spot. Your existing packages keep resolving their trades with no migration, and DS Site draws from the same registry.Impact. Your trades finally read the way your team talks, per workspace, with no cross-contamination between builders. No more stopping mid-package because a trade is missing, and no more forcing a job into the closest wrong label. Accepted payment schedules push to Xero on their own As a commercial manager, once I accepted a subcontractor payment schedule I still had to push it into Xero by hand, and had no clear read on where each one sat. Now it goes across on its own and I can see the status. Before. Accepting a payment schedule did not move anything into Xero. Someone had to push it manually, and the Invoice Register gave no signal of whether an item had gone across. After. When a payment schedule is accepted, it pushes to Xero automatically. The Invoice Register carries a new status so you can see exactly where each item sits, and a status update confirms once the push to Xero has completed. Impact. One less manual step in the money chain, and a clear line of sight from invoice to accepted schedule to Xero without leaving the platform. Improvements Choose who tender invites come from at publish As a CA publishing a tender, my invites always went out from the system notifications address, which subbies did not recognise and which sometimes tripped their spam filters. Now I can send from my own connected mailbox when I want the recognition. Before. Invites could only be sent from the central system notifications address. It kept responses centralised, but a sender subbies did not recognise hurt open and response rates, and the notifications address was occasionally caught by safe-sender filters. After. At the Review and Publish step you now pick the sender: the system notifications address (default, responses stay centralised) or your primary connected mailbox (the invite arrives from your own address). Either way, replies route back to the builder's company email rather than stranding a bid in a personal inbox, and your choice is remembered for next time.Impact. Response rate is the whole game in tendering. When a recognisable sender lifts engagement, you can choose it, without losing centralised bid capture or leaving replies to get lost. Your company logo on printouts, and export to PDF in one click As anyone sending a tender out of the business, I wanted our own branding on it and a fast way to get a clean copy, so subbies can now print straight from the view with our logo on it. Before. The view had no company branding on its printed output and no direct way to export it. After. Your company logo now appears on the output, and a new Print / PDF button exports a clean, branded copy in one click.Impact. Documents you send out look like yours, and getting a PDF is one click instead of a workaround. Fixes Moving a file onto a same-named file now asks, instead of silently duplicating As anyone tidying documents, moving a file into a folder that already held one with the same name used to leave me with two identical names and no warning. Now I get a choice. Before. A file move into a folder containing a same-named file succeeded silently, leaving two files with identical names and no prompt. It was the only place in the system with no collision handling, and the duplicates were confusing. After. When a move hits a name clash, you now get an operating-system-style prompt per file: Replace (the moved file's latest version is appended as a new version of the existing file), Keep both, or Skip. Nothing is ever deleted from storage; superseded series are soft-archived. Impact. Moving files behaves like every other file system you use, and it now matches how uploads and copies already handle name clashes. No more silent duplicates to hunt down later. Unapproved variations no longer flow into the claim or payment schedule Before. The schedule of values could pick up variations that had not been approved yet, muddying what was actually claimable on a subcontractor claim. After. A new guard keeps unapproved variations out of the schedule of values until they are approved, so the claim and payment schedule reflect only approved values. Impact. Claims and payment schedules stay accurate, and you are not manually stripping out variations that should not be there yet. Invoice edits stay in sync with the linked claim and payment schedule As anyone editing invoice data after it is captured, my edits used to leave the linked claim and payment schedule out of step, so I had to reconcile all three by hand. Before. Editing extracted invoice data after creation did not always propagate to the linked subcontractor claim and payment schedule, so the three could drift apart. After. Edits to invoice data now propagate to the linked claim and payment schedule, keeping one consistent set of figures across all three, and downstream Xero sync uses the latest unified data. Impact. No more manual reconciliation between invoice, claim, and payment schedule after an edit. Have something you would like to see, or something that is not working the way it should? Tell us through the feedback portal inside the platform. Keep the feedback coming, we're here to listen to you, and thanks for your support.