What contractor bankruptcy teaches you about your document strategy
When a contractor enters administration mid-build, the documents they were holding may never be recoverable. What that exposes about most document strategies.
The test of a document strategy is not what happens when the contractor finishes the job. It is what happens when they do not. A developer whose main contractor entered administration mid-build put it plainly: the documents that were never produced will never be recoverable. Not delayed. Not retrievable through legal correspondence. Gone.
What administration actually does to the record
When a contractor enters administration, contractual obligations are suspended immediately. The administrator's role is to realise value for creditors: to assess what assets exist, what work can continue under new arrangements, and what must stop. Chasing outstanding operation and maintenance manuals, certifying warranties for incomplete packages, signing off inspections on built-in elements, and assembling handover documentation are not part of that mandate. Administrators have no duty to the employer that appointed the contractor. Their duty runs to creditors.
For the developer, this creates a gap in the record that is qualitatively different from a late document submission. A late submission can be chased. A gap created by administration is structural.
ISG's collapse in September 2024 made this concrete at scale. The company carried a significant live project pipeline when the administrator was appointed. For each affected site, the same practical question arose: which documents had been formally transferred to the client before the date of appointment, and which remained in transit? Those in transit, including O&M manuals, commissioning records, pressure test results, and subcontractor warranties, did not automatically transfer. Recovering them required direct approaches to individual subcontractors and suppliers, without the contractor as intermediary, with no contractual leverage, and with no guarantee of response.
Supplier warranties expose the specific mechanism at work. Where a manufacturer's warranty was issued to the contractor as the purchasing entity, the developer has no direct relationship with that supplier. The warranty exists in the name of a company no longer operating, managed by an insolvency practitioner whose mandate runs to creditors, not to the developer. Whether the warranty transfers, and under what conditions, is a legal question with no certain answer. In practice, many do not transfer cleanly, and some require the developer to re-procure equivalent coverage at their own cost.
Test results present the same problem in a different form. Pressure tests, air tightness results, fire-stopping inspections witnessed by the contractor's quality team: these may exist in the contractor's systems. They may also not have been formally recorded at all. Where an inspection record sits on a site manager's device or in a platform the developer cannot access, it is functionally lost the day that person's employment ends.
The compliance dimension has changed
For most of the last decade, a gap in completion documentation was an operational problem. It meant defects could not be properly attributed, warranties could not be claimed, and buyers received an incomplete homeowner manual. Costly, and potentially damaging in disputes, but not in itself a regulatory failure.
The Building Safety Act 2022 changed that position for higher-risk buildings. The golden thread obligation requires a complete, accurate, and up-to-date record of the building to be maintained and passed on at each stage of the asset's life. Where a contractor's insolvency creates a gap in that record, the obligation does not pause. The principal designer, principal contractor, and building owner all carry continuing responsibility for the completeness of the information passed to the next dutyholder. An absent document is a gap in the golden thread, not an external event that provides relief from it.
For buildings outside higher-risk scope, the direct regulatory exposure is lower. The commercial and transactional exposure is not. Institutional investors, housing associations, and mortgage lenders are increasingly forensic about completion documentation at the point of acquisition or disposal. Residual defect risk attached to absent documentation is a factor in sales negotiations that it was not ten years ago. Portfolio managers at registered providers are being asked by their boards to evidence the completeness of their handover records in ways that make gaps visible at fund level, not just at site level.
The structural weakness most organisations have not addressed
Most developers do not have a document strategy in the sense the term implies. They have a document expectation: a list of what the contractor should deliver at practical completion, a process for chasing it when late, and a filing location for when it arrives.
That expectation works when the contractor fulfils it. It fails when the contractor cannot, because the collection process runs entirely through the contractor as intermediary. The developer never holds the document until the contractor passes it across. Suppliers deal with the contractor, not the employer. Warranties are issued in the contractor's name. Test records sit in systems the developer cannot access.
Once the contractor is gone, the developer has no direct route to the documents in that pipeline. A manufacturer who supplied fire-rated boards or mechanical plant to the contractor has no contractual relationship with the developer, no obligation to respond to requests made outside the original supply chain, and no commercial incentive to invest time in recovery without one.
The corrective is not to build a better post-PC chase process. It is to change the relationship with documents during the build itself: to collect documents directly from source, progressively through construction, rather than accepting a bundle from the contractor at the end. Warranties requested from manufacturers at the point of installation. Inspection records captured in a system the developer controls, not the contractor's platform. Test certificates uploaded to the project record as they are produced, not assembled into a handover pack weeks after practical completion.
Structured document collection, running against a defined requirement set for each package with automated follow-up for missing items, makes this operationally viable at scale. Classification matters at this stage as much as collection. Documents gathered into an unstructured shared location are theoretically present and practically inaccessible. Auto-classification that maps each document to the correct plot, the correct compliance category, and the correct validation checklist means that when the record needs to be interrogated, whether for a sale, a Building Safety Regulator audit, or an Ombudsman referral, the relevant documents surface without a manual search through folder structures built by whoever was managing the project at the time.
A document strategy that relies on the contractor to assemble the record at the end of the job is a strategy that fails the moment the contractor does.
What that means for documents before exchange
The exposure does not begin at practical completion. For developers acquiring sites, entering joint ventures, or drawing on construction finance, significant documentation is produced before a single unit is built.
Planning consents, structural surveys, environmental assessments, and utility agreements are frequently held by advisers, architects, or previous owners, not by the developer. Where an acquisition involves a distressed seller or a counterparty with uncertain financial continuity, the due diligence record needs to exist in a structure the developer controls, not only in a data room maintained by the other side. A document that exists only in the vendor's system, accessible only while the deal is active, is not a document the developer actually holds.
The same logic applies to construction finance documentation. Lenders' technical advisers produce surveys, draw-down certificates, and stage completion reports that form part of the permanent asset record. Where those documents sit only in the lender's systems, the developer's record of their own asset depends on a third party's access controls remaining unchanged indefinitely. That is a continuity risk with no contractual backstop.
A governed pre-completion environment, where both parties can contribute, access, and retrieve the relevant documents during the transaction, means the record moves into the developer's permanent project file before the deal closes, independently of what happens to any other party's systems afterward. The record does not begin at practical completion. For organisations that govern their documents from the point of acquisition, it begins the day the project does.
What this means in practice
The organisations best placed when a contractor fails are not the ones with the most aggressive legal remedies available after the event. They are the ones whose document record was built independently of the contractor holding it. Getting there requires treating document collection as a structural activity running in parallel with construction, not a deliverable expected at the end of it. Guided Home's Document Assurance layer, encompassing collection from source, auto-classification, and validation against compliance checklists, builds that record from the first day of a project in a system the developer controls, so continuity does not depend on the contractor's.