BuildQS Legal Suite: insurance and project documents
Keep insurance certificates, signed project contracts and company records together in BuildQS Legal Suite, and understand what Document check means before an application.
Luke Sanders
IT Developer
Table of contents
Before preparing an application for payment, it helps to know which signed contract is recorded against the project and whether the business's insurance certificates need attention. Those records sit alongside the valuation, but they answer different questions.
BuildQS Legal Suite brings insurance certificates, signed project contracts and optional company documents into one area. Where the feature is enabled for your business, you can record the relevant files and use a project-level Document check to check required recorded evidence before submitting an application for payment, shown as an AfP in the interface.
The important word is recorded. An uploaded certificate isn't verification of insurance cover, and an uploaded contract isn't confirmation of valid signing or legal effect. This guide explains what the workflow does, how its statuses work and the current limits, including client sharing.
Construction document management in Legal Suite
Legal Suite separates business-wide records from project-specific documents. Insurance certificates sit at business level; signed contracts belong to individual projects. Optional company records have their own section and aren't part of the required-document submission check.
Business insurance certificates
The Insurance section has records for:
- Public Liability (PL).
- Professional Indemnity (PI).
- Employers' Liability (EL).
Upload the relevant certificate and enter its recorded expiry date. The business-level certificate record is used when evaluating the document check for its projects, rather than requiring another copy for each one.
That doesn't establish whether a particular policy covers a particular job. You still need to check the policy terms, scope and limits with the appropriate adviser or insurer.
The section distinguishes an in-date recorded certificate, an approaching expiry, an expired certificate and a missing upload. “Not uploaded” describes the evidence in BuildQS; it doesn't, by itself, establish that the business has no insurance.
Not-applicable declarations
If the business considers a policy type not applicable, an owner can record a reason through the N/A controls. The record is labelled as a business declaration.
Use that distinction carefully. The declaration isn't a verified exemption or insurance advice. Don't use an N/A setting simply to turn a warning green without checking the business's circumstances.
Optional company documents
The Company documents section holds named records such as VAT or CIS documents, company policies and other supporting files. Give each document a name that makes its purpose clear to an authorised reader.
These records are optional. A missing optional company document doesn't block an AfP through Document check, and these documents aren't included in the client share settings described below.
Keep signed contracts against the right project
A signed project contract belongs to its project, not to the business-wide insurance list. In Legal Suite, the project record shows whether a signed contract has been uploaded and lets an authorised reader download the current file.
Check the project before selecting the document. Similar project names or a contract covering another package aren't a reason to use the same file without reviewing what it actually relates to.
The current signed-contract upload workflow does not ask for an expiry date. Insurance expiry tracking and the presence of a signed project contract are separate checks. That is a software distinction, not a statement that contractual periods or obligations never end.
If you upload a replacement signed contract, BuildQS asks you to confirm the replacement. The previous version is retained while the new upload becomes the current record. Make sure the replacement is the document you intend the team to use; a revised file name alone doesn't explain a contractual change.
Retention of previous versions also shouldn't be confused with an unlimited backup or recovery guarantee. The practical point here is narrower: replacing the current record doesn't overwrite its previous version through that operation.
For the wider valuation structure that sits alongside these documents, see the Master Valuation Schedule guide.
Understand Document check before submitting an AfP
Document check is a setting on the project. When it is on, BuildQS evaluates the recorded signed contract and required business insurance evidence when you submit an application. This is a document-policy check within BuildQS, not a judgement on the legal validity of your application.
The main statuses mean:
- AfP blocked: a required upload is missing or a required insurance certificate's recorded expiry has passed. Update or review the identified record before trying again.
- Needs attention: a required insurance certificate expires within 14 calendar days, including today and day 14. That expiry alone doesn't block submission, provided there isn't another missing or expired required record.
- AfP allowed: this document check permits submission. Other application requirements still apply.
An approaching expiry and an expired certificate are therefore different cases. You can prepare for a renewal while a certificate is within its recorded dates; once its recorded expiry has passed, an enabled check treats it as a blocker.
The expiry date itself is included in the attention window. Status is evaluated using the relevant London calendar date, so check the date shown with the result rather than assuming a previously viewed status is still current.
If Document check is off, the interface identifies that separately. It doesn't mean the files are complete, the business's insurance is adequate or contractual requirements have been waived. Don't read the absence of a software block as professional approval.
You may also see Document status unavailable or a checking message. Those aren't an all-clear. Refresh or retry as indicated; the server rechecks enabled document requirements at submission rather than relying on a previously displayed green badge.
The document result is only one part of preparing an application. Our construction payment application checklist covers the valuation breakdown, previous certified amounts and supporting information to consider alongside it.
A worked example: approaching expiry or a missing contract?
Take a fictional Office refurbishment project, checked on 18 November 2026, with Document check on. Assume its signed contract and all other required insurance records are present and within their recorded dates.
Its Public Liability certificate has a recorded expiry of 25 November 2026, seven days away. The project shows Needs attention. That approaching expiry alone doesn't block an AfP through this check. The owner should review the certificate and arrange the renewal record when available.
Now change just one fact: the recorded expiry is 17 November 2026. It has passed by the example's check date. The project is AfP blocked, and the owner needs to review or update the required evidence before submission can pass the enabled document check.
There is a third case worth recognising. Keep the expiry at 25 November, but remove the signed contract upload from the example. The result is still AfP blocked, because a missing required contract takes precedence over the nonblocking insurance warning.
For the edge of the attention window, an expiry of 2 December 2026 is 14 days after the example's check date and still needs attention. An expiry of 3 December is 15 days away and doesn't trigger that approaching-expiry warning, assuming every other required record meets the checks.
None of these results certifies the underlying insurance or contract. They explain how the recorded facts affect the project's document-policy result. They also don't calculate the amount of an application or tell you when the payer will certify or pay it.
Upload and maintain the records
The business owner manages Legal Suite uploads, replacements, declarations and settings. Other authorised team members can view or download records available to them, subject to business and project access. Don't assume an ordinary admin role gives permission to change the vault.
For a normal upload:
- Open Legal Suite for the relevant business and select Upload document.
- Choose Insurance certificate, Signed project contract or Company document.
- For insurance, select PL, PI or EL and enter the recorded expiry. For a signed contract, choose the correct eligible project. For a company document, enter a clear name.
- Select the file, review the details and upload it.
- Check the accepted upload and refreshed record rather than assuming a file selection means the upload succeeded.
The main signed-contract picker lists projects with Document check on. If the project isn't offered there, review its document setting and your access before uploading a contract somewhere else.
The upload dialog accepts PDF, JPEG, PNG, Word and Excel files, with a maximum of 15 MiB per file. Files must pass the workflow's admission checks. Acceptance is not verification of the document's contents, signature or legal effect.
Use Replace or Upload renewal on the existing insurance record when a newer certificate is available, then check its recorded date. For a contract replacement, read the confirmation before proceeding. The page centres on current records; don't confuse a retained earlier version with the current document your team is looking at.
Optional company documents can also be replaced. Removing one from the active Company documents list retains its file and history records through that operation; it isn't a promise of permanent deletion from all storage.
What Share with clients currently does
The Share with clients section currently saves separate settings for insurance and signed contracts. These settings are off by default, and the client list is based on clients associated with scoped BuildQS projects.
Client access is not connected in this workflow. Turning a setting on does not give the client access to the file, send an email, attach a document to an AfP or record receipt or acknowledgement. The interface confirms that it has saved the share settings, not that it has delivered documents.
If a client needs a certificate or signed contract, follow your agreed delivery process. Don't treat the saved switch as evidence that they received or accepted anything. Optional company documents are outside these share settings.
That boundary matters when documents relate to a change in scope or a contractual requirement. Our guide to variations in UK construction contracts provides broader context; a document stored in Legal Suite doesn't establish that a variation has been instructed or agreed.
Frequently asked questions
Does Legal Suite verify that insurance cover is valid?
No. It records uploaded certificates, dates and business declarations. A status based on those records isn't confirmation of cover, policy scope or an exemption. Check the actual policy and obtain appropriate insurance advice where needed.
Will an insurance expiry warning block every application?
No. The project-level Document check must be on for its required-document rules to block submission. An approaching expiry within 14 days is nonblocking by itself; missing required records or a passed recorded insurance expiry can block it. Other application checks remain separate.
Do signed contracts need an expiry date in Legal Suite?
No. The current workflow records the signed contract against the project without asking for an expiry date. Insurance certificates have recorded expiry dates. This difference doesn't determine the duration or legal effect of the contract itself.
Does switching Share with clients on send my documents?
No. It saves the relevant share setting only. Client access and document delivery aren't connected in the current workflow, so it doesn't establish sending, receipt, acknowledgement or attachment to an application.
Discuss the document workflow for your projects
Review the plans for your team, or use the demo link below to discuss Legal Suite availability and how its document checks fit your workflow.
See pricingBook a DemoPrefer to walk through your workflow live first? Book a Demo
Sources
- BuildQS Legal Suite document, permission and project-readiness implementation, reviewed on 17 November 2026. This guide describes the workflow where enabled; release and account availability should be confirmed.
- Construction payment application checklist, for the application-preparation context.
- Master Valuation Schedule guide, for the project valuation structure.
The Office refurbishment example is fictional. The article explains product behaviour and recorded-document checks, not legal or insurance advice, contract validity, policy coverage or statutory entitlement.