📁 Documents now live with the commercial records you actually work in

On a live project, documents don’t exist in isolation. They’re created for a reason, at a specific moment, to support a commercial decision. A subcontractor submits a claim and sends through an invoice. You issue a payment schedule and attach supporting notes. A variation is priced, approved, and backed up with correspondence. A client invoice goes out with calculations and justification. Until now, those documents often ended up scattered. Some were attached to the contract. Some lived in a general document register. Others sat in email threads or shared folders. When it came time to review, certify, or explain a position, you had to remember where things were stored and piece the story back together. This update removes that friction. Documents are now attached to the records they relate to We’ve made the Documents panel a standard part of commercial records, not just contracts. When you open a record, the documents that support it are now right there, in context. This applies across both client-side and subcontractor-side workflows. Client-side records Head contracts Progress claims Payment schedules (received) Client invoices Variations Subcontractor-side records Subcontracts Subcontractor progress claims Payment schedules (issued) Approved payables and invoices Variations You no longer have to jump back to a parent contract or search a register to find what supports a specific claim or invoice. What this looks like in real life A subcontractor submits a progress claim. Their invoice and backup are uploaded directly against that claim. When you assess it, everything you need is already there. When you issue the payment schedule, it sits on the same record. If there’s a query later, the documents haven’t moved. At the same time, those documents are automatically synced into Project Documentation, filed under the correct system folders. That means your project document structure stays complete and up to date without anyone having to upload the same file twice. Consistent behaviour, everywhere Across all supported records, you can: Upload documents directly on the record View and download supporting files Behind the scenes, documents are stored in a clear, predictable structure and automatically tagged with the project, record type, and record ID. Documents attached to a child record stay with that record. They don’t automatically appear on the parent contract unless you intentionally link them. That keeps records clean and avoids duplication, while still maintaining a complete project document set. Permissions follow the record, so access stays consistent with how your team already works. Why this matters When you’re certifying claims, answering questions, or preparing for audits, you shouldn’t be reconstructing history. This update means: Supporting documents are where you expect them to be Project documentation stays organised automatically Commercial reviews take less time Audit trails are clearer and easier to defend Fewer documents fall through the cracks It aligns Commercial with how Delivery and HSEQ already work in Deep Space, and reflects how teams actually manage jobs day to day. Less searching. Less rework. More confidence when it counts. As always, feedback is welcome.