What Survives the Project

A construction project ends and its records are needed for years afterwards, by which time nothing that produced them still exists.

For teams turning what survives the project into a repeatable record, employee attendance tracking provides a useful operational reference for time, attendance and reporting workflows. It should be assessed alongside ICO employment guidance so the software choice remains grounded in site practice and applicable guidance.

What the questions are

A defect claim, which can arrive many years after completion depending on the jurisdiction and the contract.

A payment dispute, which arrives sooner and is argued from contemporaneous records.

An accident investigation, which can follow an injury that developed slowly.

A regulatory audit of certified payroll or right-to-work compliance.

And an occupational health claim decades later, where the question is who was present in a particular area at a particular time.

What to keep

The register: who was on site, when, engaged by whom.

Induction records with content versions.

Competence evidence as it stood, not as it stands now.

Permits, issued and closed.

The site diary and the photographic record.

Statutory returns where they apply.

And the risk assessments and method statements in force at each period.

Format matters more than people expect

Records locked in a proprietary system are records you will not have.

Export to something readable without the original software: structured data plus a readable rendering.

Because in year seven the supplier may not exist, the licence will have lapsed, and nobody will remember the login.

A folder of PDFs and a CSV is a worse system and a better archive, and the archive is what the questions arrive at.

Who holds it

Named, at company level rather than project level, because the project team disperses.

With a stated retention period per category, derived from the contract, the limitation periods and any statutory rule — whichever is longest.

And a review date, so the archive is not kept forever by default, which creates its own obligations around personal data.

The handover task

Executed at completion, as a deliverable with a date and an owner.

Because at handover everybody is finishing and the records are the last thing anybody thinks about, which is how a project's entire register is lost with a decommissioned server.

Put it in the project close-out plan alongside the building manual and the as-builts, where it will actually happen.

The personal data tension

Long retention of a register containing identity documents and biometric data is hard to justify.

Which resolves by category: presence and engagement data kept long, identity documents and biometrics deleted on the local rule, emergency contacts deleted at project end.

So the archive is not the live system frozen, but a deliberately reduced version of it, and deciding what that contains is a task for the start of the project rather than the end.

Testing it

A year after completion, try to answer a question from the archive.

Who was on site on this date, engaged by whom, with what competence evidence.

If it takes an afternoon, the archive works. If nobody can open the file, it does not, and there is still time to do something about it.

The measure

Archive completed at handover, as a close-out item, yes or no.

Retention periods set per category rather than as one figure.

And a retrieval test passed, which is the only evidence that any of it was done properly.

What to agree with the client

Which records they want at handover and in what format.

Whether their retention replaces yours or sits alongside it, which is usually alongside — their copy does not discharge your obligations.

And who holds the statutory returns, which on publicly funded work may have their own prescribed custodian.

Agreed at contract stage, because at handover it becomes a negotiation with somebody who has already paid.

The smallest workable version

A folder per project: the register as a spreadsheet, induction and competence evidence as PDFs, the diary, the photographs, the permits.

On company storage, not a site server or a personal device.

With a retention date and an owner named in the close-out document.

Half a day at completion, and it is the difference between answering a question in year five and explaining why you cannot.