Approval workflows now cover HC Variations, SC Variations & HC Progress Claims

User Story As a Commercial Manager, I couldn't stop a variation or claim from going out before it had internal sign-off, so I can now gate every one of them behind an approval step before they leave the business. Before Head Contract Variations, Subcontract Variations, and Head Contract Progress Claims could be issued or served the moment they were drafted. There was no way to enforce that a variation or claim had been reviewed and approved internally before it reached the client or subcontractor. After All three record types now run on the Deep Space web app's approval engine. "Generate & Send Document" on an HC Variation, "Issue" on an SC Variation, and "Serve Payment Claim" on an HC Progress Claim are all blocked until the record has been submitted for and passed internal approval. Each record gets a Submit for Internal Approval button, and routing, thresholds and approvers are configured the same way as existing approval workflows, under Manage, Delegation of Authority. Approvers get an email and in-app notification and land directly on the record when they click through. If no workflow has been configured for a given record type, approval defaults to Project Manager then workspace admin, so nothing gets stuck waiting on setup. Impact Variations and progress claims can no longer leave the business unreviewed. For progress claims specifically, this also protects the SOPA clock, since it only starts once a claim has been signed off internally, not the moment it's drafted. Keep the feedback coming, we're here to listen to you, and thanks for your support. Published 13 July 2026