Study the SMSTS as a management course, not a law recital. Anchor every topic to a duty-holder decision: who is responsible, what control comes next in the hierarchy, what must be written down, and when work must stop. Practise with short site scenarios, critique your first answer against the hierarchy of control, and keep a self-check rubric so you can see whether your reasoning is specific, sequenced and documented rather than generic.
Studying the SMSTS from the duty holder's position
The SMSTS (Site Management Safety Training Scheme) is a CITB Site Safety Plus course aimed at people who direct construction work, so this guide teaches each topic as a decision a site manager must make and justify.
A site manager rarely needs to quote a regulation number; they need to recognise that a situation falls within their duties and act accordingly. So build your revision around judgement calls: whether a control is adequate, whether a subcontractor's paperwork actually covers the task, and whether work can proceed today. When you meet CDM 2015, permits or toolbox talks, ask what decision the document or process forces you to make.
One short administrative note: practical details such as course formats, assessment arrangements and renewal sit with CITB, and their Site Safety Plus page is the issuer reference for that information. Keep those logistics separate from technical revision, which should stay anchored in what a manager does on a live site.
- Study each topic as a decision the site manager must make.
- Keep administrative details (format, booking, renewal) with the issuer.
- Read every control or document by asking: what action does this compel, and who acts?
CDM 2015 duty holders: who decides what, and why the roles get confused
CDM 2015 defines duty holders by function: the client, principal designer and principal contractor each carry distinct management duties, and a person's duties depend on the role they perform, not their job title.
The confusion arises because one organisation can hold several roles, and because titles on site do not always match CDM functions. A contractor managing the construction phase is the principal contractor for that phase regardless of what their letterhead says. The principal designer plans, manages, monitors and coordinates health and safety in the pre-construction phase; the client ensures suitable arrangements and key information exist. Learn these by function: who plans, who coordinates, who manages the phase in question.
Note the distinction between a designer's duties (eliminating and reducing foreseeable risks through design decisions) and a contractor's duties (managing risks during construction). These duties interact but are not interchangeable, which is why they are easy to conflate when one organisation holds both roles. Drill this by walking a project from design stage to handover and naming who holds which duty at each step, including small projects where some roles collapse together.
- Client: ensures suitable arrangements and key information are in place.
- Principal designer: plans, manages and coordinates pre-construction phase health and safety.
- Principal contractor: plans, manages and monitors the construction phase.
- Roles follow the function performed; organisations can hold more than one.
Risk assessment versus method statement: the pair most often merged
A risk assessment identifies hazards, evaluates who might be harmed and how, and records the controls; a method statement describes how a specific task will be carried out step by step. They inform each other but answer different questions.
The risk assessment answers 'what could go wrong and how will we prevent it' across a scope of work. The method statement answers 'what exactly will we do, in what order, with what equipment and by whom' for a defined task. A risk assessment can exist without a method statement, but a good method statement draws its content from the assessment's controls. Merging the two produces paperwork that is generic, unsequenced and useless to the operative on the day.
The practical test: read the document and ask whether you could hand it to a supervisor to run the job. A risk assessment alone usually cannot, because it lists controls without sequencing the work. A method statement that never mentions a hazard or control is also defective, because the sequence may itself introduce risk. Both documents must also be communicated to the workforce; an unread assessment protects nobody.
| Aspect | Risk assessment | Method statement |
|---|---|---|
| Core question | What could harm people and what controls reduce it? | How is this specific task performed, step by step? |
| Scope | Often covers a work activity or area | Tied to one defined task or operation |
| Typical content | Hazards, persons at risk, risk rating, controls, reviewer | Sequence, plant and materials, competence, permits, emergency arrangements |
| Primary use | Deciding whether the work is safe enough to proceed | Briefing and directing the workforce on the day |
| Failure mode when confused | Generic hazards listed with no task sequence | A procedure with no hazard control rationale |
The hierarchy of control: applying elimination before paperwork
The hierarchy of control ranks measures from most to least effective: eliminate the hazard, reduce it, isolate people from it, control it through safe systems, then rely on personal protective equipment as a last resort.
The order matters because lower-tier controls depend on human behaviour and equipment condition, while elimination removes the exposure entirely. Lower-tier controls feel like the immediate fix because they can be issued on the spot, which is precisely the trap of the concept: the temptation is to reach for the tier you can deliver today. Train yourself to pause at each tier in sequence and record why a tier is not reasonably practicable before descending to the next.
Worked scenario: a roof-level air-handling unit needs filter replacement on a live building. First instinct: issue harnesses and a briefing. Better decision: check whether access at height can be eliminated or reduced, for example by specifying a reach system from below, a designated platform, or relocating filters to a plant room at floor level in future specifications. Why it matters: fall-arrest manages the consequence of a fall; a redesign removes the fall entirely and also removes ongoing rescue, inspection and training burdens. The learning point is showing the sequence, not just the final choice, and when a lower-tier control is genuinely the answer, say why: short duration, hazard not reasonably designable-out in the current installation.
Site controls in practice: inductions, permits and the subcontractor arriving early
Day-to-day controls such as site inductions, permits to work, toolbox talks and monitoring exist to make safe systems real. Knowing what each is for, and what evidence each produces, turns them from paperwork into management tools.
A site induction ensures every person entering site knows the site-specific risks, rules and emergency arrangements. A permit to work authorises defined high-hazard tasks under stated conditions and expires or is rescinded when conditions change. Toolbox talks deliver short, task-focused safety communication; monitoring and inspection verify that controls remain in place. Each produces evidence a manager can point to, but each also imposes a duty to act on what it reveals.
Worked scenario: a groundworks subcontractor arrives at 07:30 with two operatives whose induction is booked for 09:00, and their excavation is scheduled to start immediately. Plausible mistake: letting them begin because 'they are experienced' or the foreman has seen their RAMS before. Better decision: no induction, no entry to the work area; reschedule the task or run the induction now, and check that their method statement matches this site's services, access and permit arrangements rather than being generic. Why it matters: the principal contractor manages the construction phase, so delegating a task does not transfer that responsibility. Record who was inducted, when the permit was issued and what monitoring found.
- Induction: site-specific risks, rules and emergency arrangements for everyone entering.
- Permit to work: formal authorisation for defined high-hazard tasks under stated conditions.
- Toolbox talks: short, task-focused communication; record topics and attendance.
- Monitoring and inspection: verify controls remain effective and act on findings.
A repeatable method for case-style scenarios
Work case scenarios in a fixed order: identify the duty holders, identify the hazards, rank controls through the hierarchy, state who must act and document what, and decide whether work can proceed. Consistency beats brilliance.
The order is the point. Naming duty holders first prevents you assigning duties to the wrong party later. Ranking controls in hierarchy order prevents the automatic reflex of reaching for PPE. Close every scenario with a decision, an action and a document; an answer that stops at the hazard is incomplete. Write answers as short labelled steps rather than flowing prose so the sequence stays visible.
Worked scenario: a site has an unmarked services corridor where an excavator must dig a drainage run. Mistake: writing 'deep excavation, use spades, wear hi-vis'. Better decision: identify the principal contractor's duty to manage the phase; check utility records and permit arrangements; require a services location exercise before breaking ground, a permit to dig specifying exclusion zones and a banksman, and a review of whether the drainage route can be adjusted away from the corridor. Why it matters: the first answer treats a potentially fatal hazard as a routine task with PPE; the second removes uncertainty about services before any exposure occurs, then documents the remaining controls. Exercise with a self-check rubric: take one real or imagined task on a site you know and write a half-page method statement plus a risk assessment, then score four points.
- Step 1: name the duty holders and their phase.
- Step 2: list hazards and who is exposed.
- Step 3: rank controls from elimination downward, with reasons for skipped tiers.
- Step 4: state who acts, what is documented, and when work stops.
- Self-check rubric: (1) duty holder named; (2) hierarchy appears in order with reasons for skipped tiers; (3) a supervisor could run the task from the method statement alone; (4) a stated trigger for stopping work exists.
An adaptable preparation sequence and readiness checks
Prepare in four passes: build the CDM duty-holder map, drill the hierarchy of control, practise document critique on RAMS, then rehearse full case scenarios under time. Close each pass with the readiness checks below.
Pass one: draw the duty-holder map for three project shapes (single contractor, multi-contractor with a principal designer, client-led with several appointments) and state each role's function from memory. Pass two: take ten everyday construction tasks and list a control at every tier of the hierarchy, even where the answer is 'not reasonably practicable, because...'. Pass three: find or write one weak method statement and rewrite it so a supervisor could run the task. Pass four: complete full case scenarios and self-mark against the four-point rubric.
Keep the passes in order: case practice is only useful once the underlying decisions are automatic. Fit it around your working week by tying passes to real site events, such as reviewing a permit or an induction you actually witnessed, which turns daily work into rehearsal. Readiness checks before assessment day: you can distinguish a risk assessment from a method statement in one sentence each; you can assign duties for a given project shape without hesitation; you can rank controls for a work-at-height and an excavation scenario in order with reasons; and your scenario answers always end with a decision, an action and a document. If any check fails, return to the matching pass rather than rereading notes from the start.
- Readiness check 1: one-sentence definitions of risk assessment and method statement.
- Readiness check 2: duty-holder mapping for at least two project shapes.
- Readiness check 3: full hierarchy of control for height and excavation tasks.
- Readiness check 4: every scenario answer ends with decision, action, documentation.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.