Site File Set-Up for Principal Contractors: Digital Structure, Standards, and Roll-Out Across Sites

TL;DR

• An audit-ready PC site file is about fast, consistent evidence: planned arrangements, live risk control, monitoring, action close-out, and controlled handover.
• Standardise a repeatable top-level folder structure across all projects, with flexible subfolders to suit scope (demo, fit-out, M&E, interfaces).
• Stop “final_v7” confusion with simple naming, clear revisions, and a working vs published (read-only) split for approved documents.
• Use one master action log with IDs and linked close-out evidence, and keep it current via a weekly filing and review rhythm.
• Align your site file with principal contractor duties cdm 2015 by defining minimum evidence standards for inductions, inspections, RAMS, permits, change control, and archiving.

Note to the reader: The information on this page is for general guidance only. For project specific advice, consult a competent professional.

When site records are spread across email chains, WhatsApp photos, and “final_v7” documents, control slips quickly—especially across multiple live projects. A proper principal contractor site file setup service isn’t about creating more paperwork; it’s about making evidence easy to find, consistent to maintain, and ready to hand over when the job demands it.

This article breaks down what an audit-ready digital site file looks like for Principal Contractors (PCs) on non-domestic projects under CDM 2015, and how to roll standards out across sites without drowning the team in admin.

Principal Contractor Advisory Support

Need a Competent Health & Safety Advisor for Your CDM Project?

Practical CDM support for Principal Contractors — advice, documentation, and structured systems to help you run organised, compliant projects.

If you’re managing the Principal Contractor role alongside running the job, we provide the expert guidance and support that keeps your Construction Phase Plan, RAMS, and site records properly organised and ready when clients or auditors ask to see them.

Experienced construction safety advisors supporting SME Principal Contractors across the UK.

What “audit-ready” means for a Principal Contractor site file (CDM 2015)

For a PC, “audit-ready” is less about a perfect folder tree and more about being able to show clear, consistent evidence that:

• arrangements were planned and implemented (not just written down once)
• risks were assessed and controlled in real time
• induction, supervision, inspections, and monitoring were carried out and followed up
• actions were tracked to completion with ownership and dates
• the latest approved information was used on site
• handover and archiving are controlled and retrievable

It also means your team can locate the right evidence quickly: by project, by date, by contractor, and by topic.

CTC supports compliance; legal duty remains with duty holders.

Core components of a PC site file system

A strong system balances consistency (so every project looks familiar) with flexibility (so it matches the job). Most PCs need five building blocks.

1) A standard folder structure that mirrors site reality

Use a repeatable top-level structure across all projects. Keep it aligned to how you manage the job day-to-day, not how someone imagines it should run. Typical “top-level” sections include:

• 00_Project controls (contacts, org charts, key dates, meeting cadence)
• 01_PCI & pre-start (pre-construction information received, key constraints)
• 02_CPP & management arrangements (construction phase plan, logistics, welfare, emergency)
• 03_RAMs & permits (SSOW, permits, lifting plans, temporary works registers where applicable)
• 04_Inductions & competence (induction records, briefings, cards/tickets as required by your process)
• 05_Inspections & monitoring (site inspections, plant checks, scaffold reports, service locates evidence)
• 06_Incidents & close calls (reports, investigations, learning actions)
• 07_Change control (design changes received, site instructions, revised sequences)
• 08_Communications (minutes, coordination notes, interface records)
• 09_Handover & archive (final file index, retention notes, close-out summary)

Keep the top level stable. Subfolders can flex by scope (e.g., demolition, enabling works, fit-out, M&E heavy).

2) Naming and version rules that stop “final_final” chaos

Most site file problems aren’t missing documents—they’re duplicated, mislabelled, and out of date. Agree simple rules that anyone can follow:

• One document = one “home” (no copies in multiple folders unless it’s a controlled “published” copy)
• Use a consistent filename pattern (date + project + doc type + area + revision)
• Separate “working” from “published” (drafts can live in a working area; only approved versions go to the live site file)
• Use clear revision markers (Rev A/B/C or 01/02/03—pick one)
• Lock down editing for “published” documents to avoid silent changes

3) Evidence standards: what counts as “good enough” on site

PC evidence is often a mix of documents, photos, checklists, and sign-offs. The trick is making it consistent and searchable.

Practical standards that work across sites:

• Photos: include date, location/area, what it shows, and the related action reference if there is one
• Briefings and toolbox talks: link the briefing record to the risk, RAMS, or change that triggered it
• Inspections: capture the inspection type, area, findings, and close-out evidence (not just the initial report)
• Permits: file by date and activity, and link to supporting controls (isolation, service scan, lift plan)
• Subcontractor submissions: store the “accepted/approved for use” version and a record of review

Decide upfront what must be captured every time (minimum dataset) versus what is “as needed”. That’s how you avoid admin overload.

4) Action tracking that actually closes the loop

A site file becomes audit-ready when actions don’t disappear. Keep one master action log per project, and make everything point back to it:

• Single action ID (used in inspection reports, photos, meeting minutes)
• Owner (named role/person) and due date
• Status (open / in progress / closed)
• Close-out evidence link (photo, re-inspection, sign-off)
• Reasonable categorisation (e.g., housekeeping, access/egress, lifting, services, temporary works)

If you do only one thing to improve control across sites, standardise action tracking and the way evidence attaches to it.

5) Handover and archiving built in from day one

Handover is easier when it’s planned. Build the end state into your structure:

• use a final file index that mirrors the folder structure
• keep a document register for key controlled documents (CPP, emergency arrangements, inspection schedules)
• make sure the final “published” set is complete and duplicates are removed
• archive with clear naming (project, site, dates) so you can retrieve later

Rolling out standards across multiple sites (without slowing the job)

Consistency across projects is what prevents reinvention on every start. The goal is a repeatable system that works for a small job and scales to a major programme.

Start with a “minimum viable” standard

Set a baseline that every project uses:

• the same top-level folder structure
• the same naming and revision approach
• a standard action log format and routine
• defined evidence expectations for inspections, briefings, and close-out

Then allow project-specific add-ons (e.g., interfaces, logistics constraints, high-risk activities) without changing the core.

Set permissions and responsibilities clearly

To maintain PC control without bottlenecks:

• give subcontractors a defined route for submissions (and prevent “shadow folders”)
• make one role accountable for publishing controlled documents
• use read-only areas for live, approved information
• agree who closes actions and who verifies close-out

Build a weekly rhythm so the file stays live

Audit-ready doesn’t happen in a last-minute scramble. A simple cadence keeps it current:

• weekly check that inspections are filed and actions updated
• publish updated RAMS only via the controlled route
• file meeting minutes and link any actions to the master log
• spot-check that “latest version” rules are being followed

A fictional site anecdote: where file structure saved time (and stress)

On a busy refurbishment project, a site manager was covering two sites and relying on photos saved to a phone and a shared folder full of loosely named documents. When a client asked for evidence of close-out on a set of weekly inspection findings, it took hours to match photos to actions—and one key photo couldn’t be tied to a date or location.

On the next project start, the team adopted a simple standard: every inspection action got an ID, every close-out photo included that ID in the filename, and only approved documents were published to the live folder. A month later, the same type of request came in. This time, the site manager pulled the action log, clicked the linked evidence, and closed the query in minutes—without stopping the day’s work.

Free Resource for Principal Contractors

Principal Contractor Toolkit: 37 Essential CDM Templates

A practical set of ready-to-use forms designed to help SME Principal Contractors keep their projects organised and properly documented.

Includes key construction phase records, inspection forms, registers, and supporting templates commonly required on CDM projects — all structured so you know when and how to use them.

Built for real construction projects — not generic paperwork.

What to expect from a principal contractor site file setup service (in practice)

If you’re evaluating a principal contractor site file setup service, it should typically cover:

• site file architecture that fits your projects and CDM 2015 PC evidence needs
• naming and version rules that are simple enough for site use
• standard evidence approach for inspections, monitoring, briefings, and close-out
• action management method that links findings to evidence and completion
• handover/archiving method so you can close a job cleanly
• roll-out approach across multiple sites with minimal disruption

Quick reference: a practical standard you can adopt across sites

Area	Standard to set	Why it helps the PC
Folders	Fixed top-level structure used on every project	Faster onboarding; easier auditing and handover
Filenames	Date + doc type + area + revision	Searchable, reduces duplicates and confusion
Revisions	Working vs published; published is read-only	Prevents outdated information being used on site
Evidence	Minimum dataset for inspections/photos/briefings	Consistent proof of monitoring and follow-up
Actions	One master log with IDs and linked close-out	Shows control and completion without admin overload
Handover	Final index + tidy archive naming	Clean close-out; easier retrieval later

FAQs

What’s the difference between a site file and a “project file” for a Principal Contractor?
A PC site file is the live, working record of how the construction phase is being planned, managed, monitored, and controlled on site. It focuses on day-to-day delivery evidence: inductions, inspections, briefings, RAMS in use, permits, action close-out, and change control. A wider project file may include commercial correspondence, design development history, and broader programme documentation. In practice, many organisations hold both, but the PC site file needs to be immediately usable on site and consistently maintained.

 

How detailed should the folder structure be?
Detailed enough to find things quickly, but not so detailed that the team files documents in the wrong place. A stable set of top-level folders across all projects, with a small number of sensible subfolders, usually works best. If people need a “map” to file a document, the structure is too complex.

 

What evidence matters most for demonstrating PC control under CDM 2015?
Evidence that shows the arrangements are working in practice: a clear construction phase plan and site arrangements, proof that inductions and briefings happened, inspection and monitoring records, action tracking to close-out, and proof that the latest information and RAMS were used. It’s the combination of planned arrangements plus consistent follow-through that demonstrates control.

 

How do you avoid admin overload when standardising across multiple sites?
Set a minimum standard (folders, naming, action tracking, and core evidence) and make everything else optional based on risk and scope. Build the routine into weekly site rhythm so filing and close-out happen little and often. Use one action log and link evidence to it, rather than creating separate trackers for each inspection type.

 

Who should be responsible for keeping the live site file up to date?
The PC should assign clear responsibility for publishing controlled documents and maintaining the live record, with support from the site team. The key is role clarity: who uploads, who approves/publishes, and who verifies close-out. Without that, documents drift into personal inboxes and “side folders”.

 

Can we run paper and digital records together?
Yes, but decide which is the “source of truth”. Mixed systems fail when the same record exists in two places and neither is complete. If paper is used for immediate site capture, set a routine to upload and file it digitally so your evidence remains searchable and consistent across sites.

Summary

An effective PC site file system under CDM 2015 is built around a repeatable digital structure, simple naming/version rules, consistent evidence standards, and action tracking that closes the loop. When those basics are standardised across sites, Principal Contractors keep control without turning record-keeping into a full-time job.

How we can help. If you want a consistent, audit-ready digital site file standard rolled out across your non-domestic projects—covering structure, naming/version control, evidence expectations, action tracking, and handover—CTC can set it up and embed it with your teams while keeping duty holder responsibilities clear.

Disclaimer

This resource is provided for general guidance only. Always consult a competent professional for project specific advice. No warranty or guarantee is given or implied regarding completeness, accuracy, or compliance.

Principal Contractor Support

Running a CDM Project as Principal Contractor?

Get the structure, advice, and documentation support you need to manage the role properly.

When you take on the Principal Contractor role, the responsibility for the Construction Phase Plan, site safety records, RAMS, and CDM compliance usually lands on the desk of a busy director or site manager.

CTC South West provides practical advisory support and structured systems that help you keep your documentation organised, your responsibilities clear, and your projects ready for client checks or audits.

Expert CDM support, site-ready documentation, and organised compliance records — all built around how construction projects actually run.

• Construction Phase Plans structured and ready for client review
• RAMS and project documentation tailored to your actual work
• Ongoing competent person support for Principal Contractors

Practical advice from experienced construction safety advisors — supporting SME Principal Contractors across the UK.