How to Use This Resource: Principal Contractor Duties Start‑Up Checklist

Purpose and outcome (what “good” looks like)

This checklist is a job start / mobilisation tool to prove you have properly accepted the Principal Contractor (PC) role and set up the minimum basics required under CDM 2015 and the Building Regulations dutyholder rules.

Good completion means:

• ✅ You can show you had the right information before starting (not guessing on asbestos, services, design, sequence).
• ✅ Your Construction Phase Plan (CPP) and first RAMS match the actual first activities on site.
• ✅ Site basics are in place: welfare, boundaries, access, traffic plan, emergency arrangements.
• ✅ Key people are appointed and contactable (Client, PD, PC, supervisor, first aid/fire, temporary works where needed).
• ✅ If the project is notifiable, the F10 is verified and displayed on site.
• ✅ You have a clear “go / no‑go” decision if information or controls are missing.
• ✅ You can file it as evidence of a structured start and ongoing control.

Who uses it (roles and responsibilities)

When to use it (trigger points and timing)

• Main use: at the pre-start / mobilisation meeting before anyone starts work.
• Also use it: when there is a material change (programme change, new high-risk activity, design change, new subcontractor, change of supervisor, new phase such as demolition → build).
• If you take over mid-job: complete it as a “PC handover start-up” and record what you’ve checked and what you still need.

Rule of thumb: if you wouldn’t be comfortable explaining your set-up to an inspector or Building Control, pause and use the checklist to close the gaps.

Before you start (inputs and evidence you’ll need)

Gather these before the meeting so you’re not trying to “wing it” on the day:

• Contract / order confirming you are the PC (or written confirmation by email/letter).
• Notifiability check and (if notifiable) the F10 notification details:
  • Copy of the submitted F10 (or screenshot/PDF) and the notification number/reference.
  • Who submitted it (usually the Client/PD) and confirmation it is current (updated if key details change).
  • Plan for displaying the F10 on site where workers can see it (e.g., site notice board / welfare unit).
• Pre‑Construction Information (PCI): site hazards, existing drawings, restrictions, surveys (including asbestos where relevant), services information.
• Design pack you can build from: drawings/specs and any known temporary works needs.
• Programme and sequence (first week activities especially), working hours, delivery constraints, neighbours/tenants/school hours.
• Subcontractor list (who, when, what they’re doing) and basic competence/insurance checks you will rely on.
• CPP draft (even a simple one) and the first RAMS set for day-one/week-one tasks.
• Site set-up plan: welfare, power/water, lighting, access, fencing/hoarding, storage, traffic management.
• Emergency plan basics: first aid, fire, muster point, nearest A&E, spill response, accident reporting route.
• Building Control route and hold points: who the Building Control body is, what inspections are needed, and what evidence you must keep.

How to complete it (step-by-step in real site terms)

1. Run it as a short mobilisation meeting (20–45 mins)
   • Attendees: PC lead + site supervisor as minimum; invite PD/client if possible; include key trades if starting immediately.
   • Have the CPP, drawings, programme, and site set-up plan on the table (paper or screen).
2. Fill in the job details and confirm PC acceptance
   • Check the contract/order actually covers the PC role. If it doesn’t, mark “No” and stop to clarify.
   • Agree the start date and the initial scope (what is in/out, and what “day one” looks like).
   • Sign the PC acceptance statement once you’re satisfied you can meet the duties (or record what is missing and set a “no start” condition).
3. Work through the checklist top to bottom
   • Tick items only when they are done (not “we’ll sort it”).
   • In “Evidence/notes”, write where the proof is (e.g., “PCI email dd/mm”, “CPP v3 in site file”, “Asbestos survey in H&S folder”, “Photo set in job photos”, “F10 PDF posted on noticeboard”).
   • For anything not done: write an action, an owner, and a date.
4. Make a clear “go / no-go” call on missing information
   • If PCI/surveys/services info are missing, do not “assume”. Record what is missing and escalate to the Client/PD.
   • If the project is notifiable and the F10 hasn’t been confirmed, treat it as a mobilisation gap: chase it and record the action.
   • If the first activities include higher-risk work (height, excavations, lifting, hot works), do not start without the specific controls and permits in place.
5. Lock down the first week plan
   • Confirm the first RAMS cover the real sequence and site conditions.
   • Confirm who is supervising each activity and how you’ll coordinate trades (interfaces, shared access, deliveries).
6. Confirm site arrangements are physically in place
   • F10 displayed (if notifiable): check a printed copy is on the site notice board/welfare and it matches the current project details.
   • Welfare available from day one (not arriving “next week”).
   • Boundaries, signage, pedestrian/vehicle routes and storage areas marked out.
   • Emergency arrangements posted/briefed (muster point, extinguishers, first aid).
7. Brief the team
   • Prepare the induction and the first-day briefing points (site rules, PPE, traffic, emergency, “stop the job”).
   • Confirm competence checks for anyone starting (tickets/cards/experience/supervision level).
8. Finish with actions and sign-off
   • List open actions clearly. If an action is a “must-have before start”, mark it as such and delay start if needed.
   • Get the PC and site supervisor signatures. PD/client signatures are helpful if they attend, but don’t rely on that to run your site safely.

Review and approval (what to check and when to escalate)

Minimum review: PC lead reviews and signs. Site supervisor signs to confirm the arrangements match site reality.

Escalate (and consider “no start”) if any of these apply:

• ⚠️ No PCI, no key surveys, unclear asbestos position, or unclear services.
• ⚠️ The project appears notifiable but the F10 status is unknown, or you can’t get the F10 details for the site notice board.
• ⚠️ Design information is incomplete for the planned work, or design responsibility is unclear.
• ⚠️ CPP/RAMS are generic and don’t match the sequence, access, or constraints.
• ⚠️ Welfare, boundaries, or traffic management cannot be put in place for day one.
• ⚠️ High-risk work is planned but controls/permits/competence are not ready (e.g., scaffold not inspected, no lifting plan, no excavation support plan).
• ⚠️ Building Control route/hold points are unknown and you’re about to cover up work that needs inspection (drainage, fire stopping, structure, insulation, DPM).

Recordkeeping (where to store it, version control, retention)

• Store with the job pack (site file and/or digital project folder) under a clear folder such as: 01 Mobilisation / Pre-start.
• Link evidence: keep photos, CPP/RAMS versions, F10 copy (if applicable), induction records, permits and inspection records in the same job pack. The checklist should point to them.
• Version control: if you update the checklist after changes, mark it as Rev 1, Rev 2 (or “updated dd/mm”) and keep the older copy (don’t delete it).
• Retention: keep for at least the life of the job plus your normal H&S/quality record retention period. If in doubt, keep it with the H&S file and handover information so it’s available for audits, claims, and investigations.

How often to review or update

• At mobilisation: complete once, properly, before start.
• Re-check after: major design change, programme change, new phase, new subcontractor, significant incident/near miss, change of supervisor, or new high-risk activity.
• Also re-check (if notifiable): when key project details change (dates, dutyholders, programme) so you can confirm the F10 is still accurate and the copy on the notice board is current.
• During the job: use your normal monitoring (inspections, toolbox talks, supervisor checks) and update the CPP/RAMS as needed—then note in the checklist evidence where the updated documents are filed.

Common mistakes (and how to avoid them)

Worked example (quick scenario)

Job: Small shop fit-out with minor structural alterations and new services. Start planned Monday.

• Friday pre-start: You complete the checklist with the supervisor. You confirm the job is notifiable and get the F10 PDF from the PD/Client. You note: “F10 posted on welfare noticeboard”.
• Gap found: PCI is missing up-to-date services info for the rear yard excavation for a new drain run.
• Decision: You record “No—enough info to plan?” and set an action: Client to provide services drawings and confirm scan by Sunday 12:00. You mark: “No excavation until confirmed.”
• What you can start: You tick welfare/security/induction/traffic set-up, and RAMS for non-intrusive strip-out, protection, and setting up work areas.
• Building Regs control: You confirm Building Control route and agree hold points for structure and fire stopping. You add a simple photo plan for hidden works.
• Monday: You start permitted tasks, brief the team, and monitor. Excavation only starts once the missing info is received and the RAMS are updated and briefed.