Principal Contractor Site File Contents: How to Structure an Audit-Ready Evidence Trail

TL;DR

• Use a consistent 01–09 folder structure so teams can find CPP, RAMS, permits, inspections, incidents and handover evidence fast.
• Keep “current/approved” documents separate from a read-only archive; avoid duplicate “latest” versions across paper and shared drives.
• Make principal contractor duties cdm 2015 easy to evidence with clear sign-offs (who/when/what) for CPP, RAMS, permits and briefings.
• Apply simple naming/version rules (date + v#) and maintain a short register to prove traceability and control.
• Stay audit-ready with a one-page site index and a weekly upload rhythm for inductions, inspections, permits and RAMS changes.

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

A well-structured site file makes it easier to manage a project day-to-day and to evidence what you planned, briefed, checked, and controlled. Under CDM 2015 (non-domestic projects), Principal Contractors are expected to be able to show a clear evidence trail for how site is being managed safely and effectively. The goal isn’t to build a huge archive; it’s to keep the right records, in the right place, in a consistent format that stands up to client and auditor requests.

Fictional but familiar example: a site manager takes over a live job with multiple subcontractors already on site. The “site file” is three lever-arch files plus a shared drive with folders named “new”, “latest”, and “old old”. When the client asks for the last six weeks of inspection evidence and the RAMS briefings for two trades, it takes half a day to piece together what happened. Nothing was necessarily missing on site — it just wasn’t structured. This guide helps you avoid that situation.

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.

Scope and CDM 2015 context (Principal Contractor, non-domestic)

This article focuses on Principal Contractor duties under CDM 2015 for non-domestic projects and the practical records that typically demonstrate those duties in action. It does not cover domestic client arrangements, HRBs, or Building Safety Act gateway processes.

CTC supports compliance; legal duty remains with duty holders.

What “site file contents” should achieve for a Principal Contractor

• Control: the current plan, current RAMS, current permits, current drawings — no ambiguity.
• Traceability: who approved what, who briefed what, and when (sign-offs and version history).
• Consistency across sites: the same structure so teams can move between projects without relearning.
• Audit readiness: you can answer typical client/auditor questions quickly, using named, dated evidence.

Recommended site file structure (practical, audit-ready)

Below is a workable baseline for site file contents for a Principal Contractor. You can run this as physical folders, digital folders, or both — but keep one “source of truth” to prevent duplication.

01. Project administration (PC-controlled)

• Project directory (key contacts, site address, access arrangements, emergency address/postcode)
• Communication plan (site notice boards, briefings, escalation route)
• Meeting minutes (site coordination, progress, H&S meetings) and action tracker
• Correspondence register for H&S-critical items (RFI responses affecting safe methods, agreed changes)

02. Construction Phase Plan (CPP) and arrangements

• Current Construction Phase Plan (controlled version)
• Site rules / induction standard
• Traffic management arrangements
• Welfare arrangements and inspection evidence
• Emergency arrangements (fire, first aid, spill response) including drill records where used

03. Risk management and RAMS control

• Risk register / significant risk summary used on site (as applicable)
• Approved RAMS (trade package folders)
• RAMS review log (what changed, when, who approved)
• Briefing records / task briefings / toolbox talks linked to specific RAMS and dates

04. Competence and onboarding (site-facing evidence)

• Induction records (daily induction log and signatures)
• Training/competence evidence relevant to site activities (e.g., plant tickets) where your PC arrangements require it on site
• Subcontractor start-work checks / onboarding checklist
• Visitor log and controls (where used)

05. Permits and high-risk controls (where applicable)

• Permit to work system (live permits and closed permits filed by date)
• Hot works controls and fire watch records
• Confined space controls (if applicable)
• Temporary works control evidence (appointments, registers, inspections) where within PC arrangements
• Lifting operations (lift plans, briefing records, thorough examination evidence as required by your arrangements)
• Excavations permits/inspections and service locating records

06. Inspections, checks, and monitoring

• Planned inspection schedule (what, who, how often)
• Site inspection reports (weekly/daily as used), close-out evidence
• Plant and equipment checks (pre-use, weekly where required)
• Scaffold/edge protection inspections where applicable
• Fire equipment checks (where used)

07. Incidents, close calls, and corrective actions

• Accident/incident/near miss reports
• Investigation notes and evidence (photos, statements if used)
• Corrective action log and verification of completion
• Any notifications required by your internal process

08. Change control and design/temporary changes (PC evidence trail)

As Principal Contractor, you’re often coordinating changes that affect how work is done on site. Keep practical evidence of:

• Change requests affecting sequencing/method/temporary arrangements
• Updated RAMS and re-briefings resulting from changes
• Drawing/REV registers used on site (current issue only)

09. Handover and demobilisation (PC side)

• Snag / outstanding actions list (where within PC scope)
• Removal of temporary works and last inspections
• Final welfare removal checks
• Site closure checklist

Naming conventions, version control, and sign-offs (make evidence easy to follow)

Most “missing evidence” in audits is actually evidence that exists but can’t be traced — because files are unnamed, undated, or stored in multiple places.

Simple file naming that works on site

Use a consistent pattern so anyone can find the latest document quickly:

• [ProjectCode]_[Trade/Topic]_[DocumentType]_[Location/Area]_[YYYY-MM-DD]_vX
• Example: SWL01_Electrical_RAMS_AreaB_2026-02-14_v3

Avoid “FINAL”, “FINAL2”, “LATEST” in filenames. The version number and date should tell the story.

Version control rules (practical minimum)

• One controlled folder for “Current/Approved” documents used on site.
• One archive folder for superseded versions (read-only if possible).
• A short document register listing: document name, version, date approved, approver, status.
• Withdraw superseded paper copies from notice boards and folders when updates are issued.

Sign-offs that stand up to scrutiny

For core controls (CPP, RAMS, permits, briefings), sign-off should show:

• Who approved/briefed (name and role)
• When (date/time where useful)
• What (document title/version or permit number)
• Who received the briefing (signatures or equivalent record)

If you use digital signatures, keep the exportable audit trail (not just a screenshot).

What to keep on site vs centrally (avoid duplication without losing control)

As a rule: keep on site what you need to run the work safely and what you may need to evidence quickly during a visit. Keep centrally what is high-volume, corporate, or better managed in a controlled system — but ensure it can be produced quickly.

Record type	Best kept on site	Best kept centrally	Practical note for PCs
Current CPP and site rules	Yes	Copy	Site team must be able to show the current version immediately.
Approved RAMS (current)	Yes	Copy + archive	Keep only current on site; archive centrally (or in read-only archive folder).
Superseded RAMS/CPP versions	No	Yes	Archive to avoid “two versions in the cabin”.
Inductions and daily briefings	Yes (active period)	Yes	Scan/upload weekly to maintain continuity and reduce loss risk.
Inspection reports and close-outs	Yes (current month)	Yes	Keep a clear index so a spot-check can be answered quickly.
Plant registers / thorough examination certificates	Relevant items only	Yes	Have a site list with certificate references; store full packs centrally.
Permits to work	Yes	Yes	Live permits accessible on site; closed permits filed by date then stored centrally.
Incident investigations	Summary and actions	Yes	Keep actions visible on site; store full investigation pack centrally.

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.

Typical client and auditor requests (and where your evidence usually lives)

These are common asks on non-domestic projects when someone is checking PC arrangements. Build your site file contents so you can answer these without a scramble.

• Construction Phase Plan: current version, evidence it’s implemented (site rules, welfare, traffic management).
• RAMS control: approved RAMS for a live activity, evidence of briefing, evidence of review after change.
• Inductions: induction records for a sample of operatives on site that day.
• Monitoring: last 4–6 weeks of site inspections and close-out evidence.
• Permits: hot works/excavation/lifting evidence for a sample activity, including close-out.
• Competence checks: proof that those doing specific higher-risk tasks were checked against your process.
• Incidents and learning: near miss/incident records and evidence that actions were completed and communicated.
• Document control: how you prevent outdated documents being used (register, versioning, withdrawal of superseded copies).

Avoiding duplication and missing evidence across multiple sites

Multi-site programmes fail on consistency, not intention. The following controls keep evidence complete without creating extra admin.

Use a “one-page index” per site

Create a simple index (digital or paper) that lists the live contents of the site file by section, plus where the central archive sits. Keep it updated weekly.

Set a weekly “upload rhythm”

• End of week: upload inductions, briefings, inspections, permits, and any changed RAMS.
• Lock the week’s folder (read-only) once uploaded to prevent silent edits.

Keep a single RAMS register per project

A RAMS register reduces duplication by making it obvious what is approved and current. Minimum fields:

• Trade/package
• RAMS title
• Version/date
• Approval date/approver
• Briefing date(s)
• Status (Current/Superseded)

Standardise section numbers across all projects

If every job uses the same section numbering (01–09 as above), you can ask for “Section 06 inspections for the last month” and get the same thing back from every site.

Quick checklist: site file contents for a Principal Contractor (minimum workable set)

• Current CPP (controlled) and site rules
• Emergency arrangements and welfare evidence
• Approved RAMS + RAMS register + briefing records
• Induction records and visitor controls
• Permits to work (live + closed filed)
• Inspection regime evidence + close-out actions
• Incident/near miss log + corrective actions
• Current drawing/REV register used on site
• Document control: versioning, archive, withdrawal of superseded copies

FAQs

What are the most important site file contents for a Principal Contractor under CDM 2015?
The most important items are the current Construction Phase Plan, controlled/approved RAMS for the work being carried out, evidence of briefings/induction, permits for higher-risk activities (where used), inspection and monitoring records with close-out actions, and an incident/near miss log with evidence of learning and completion of corrective actions.

 

How do I show that RAMS are “current” and not duplicated across folders?
Use one “Current/Approved” folder and one “Archive/Superseded” folder, backed by a RAMS register that lists the approved version and date. Withdraw or clearly mark superseded paper copies. If a change is made, update the register, reissue the document with a new version/date, and record the re-briefing.

 

Should the site file be paper, digital, or both?
Any approach can work if you keep one source of truth. Many projects run a hybrid: essential live controls on site (CPP, current RAMS, permits, emergency info) with a central digital archive for everything else and for resilience. The key is to avoid parallel “latest versions” in multiple places.

 

What inspection records do clients and auditors typically ask for?
Common requests include the last 4–6 weeks of site inspections (weekly or daily, depending on your system), evidence that issues were closed out, and specific inspection regimes relevant to the work (e.g., excavations, work at height controls, plant checks, fire points). They often sample a few findings and ask to see the fix and the verification.

 

How long should a Principal Contractor keep site file records?
Retention is usually set by your company policy, contract requirements, and the nature of the record. Practically, ensure your records are stored centrally at project close in a controlled archive so they remain retrievable if requested later. What matters day-to-day is that records are complete, legible, and traceable while the project is live and during close-out.

 

What’s the easiest way to stay audit-ready across multiple sites?
Standardise the same folder/section structure on every project, apply a simple naming/version control rule, keep a one-page index per site, and set a weekly upload rhythm to a central controlled location. That combination prevents missing weeks, reduces duplication, and makes sampling checks straightforward.

Summary (and how we can help)

Strong site file contents for a Principal Contractor come down to clarity: a consistent structure, controlled “current” documents, a clean archive, and sign-offs that show who did what and when. If you can quickly produce the CPP, current RAMS with briefing evidence, permits, inspections with close-outs, and incident learning, you’re building the kind of audit-ready evidence trail clients and auditors typically expect on non-domestic projects under CDM 2015.

How we can help: If you want to standardise your PC site file structure and document control across multiple sites, CTC can support you to implement consistent, practical compliance records (while legal duty remains with duty holders).

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.