The NEBOSH IGC's difficulty is not volume of content; it is translation. Unit GIC1 is an open-book, scenario-based exam where every management concept — moral, financial and legal arguments, management systems, human factors, monitoring — must be re-expressed in the language of the scenario, at the depth set by each command word, and defended afterwards in a closing interview. Unit GIC2 then tests a different skill: producing a suitable and sufficient risk assessment of a real workplace. This guide trains both moves separately, works through two decision scenarios, and finishes with a preparation sequence and readiness checks.
Why an open-book exam is not an easy exam: the translation gap
GIC1 is scenario-based and open book, with a closing interview about your submission. The tested skill is applying management concepts to the given scenario in your own words, not locating material to paste in.
Open book changes what is being marked, not what earns credit. Copying a definition from your notes into a scenario question produces a sentence that could belong to any workplace; the question is built around one named organisation with its own people, machines and events. Each point you make should carry a scenario anchor — a role, a plant item, an incident, a stated condition. NEBOSH also describes a closing interview in which you are asked questions about your submission, so every line needs to be yours and explainable on demand.
Train the translation directly. Take each syllabus point and rewrite it as 'in this scenario, that means…'. For example, 'insufficient supervision' becomes 'there is no supervisor on the loading bay between 15:00 and 17:00, when agency staff work alone'. A useful test: if a sentence would survive unchanged if you swapped in a different workplace, it is still generic. Collect several scenario anchors per page of notes and practice attaching them to command words, so recall and application become one motion rather than two.
Command words set the depth of your answer — calibrate to them
NEBOSH's assessment criteria use verbs from identify up to justify. Each word sets how developed an answer must be, and matching depth to the word is a learnable skill rather than a matter of writing more.
The hierarchy runs: identify means name it; outline means give the main features; describe means set out detail of the same thing; explain means give reasons or mechanisms; discuss and justify mean weigh points and argue a case. A one-line answer under 'explain' is underdeveloped; a full paragraph under 'identify' spends time the mark does not need. Before writing, circle the command word and decide the shape of the answer it asks for.
Exercise: take one scenario fact — a worker operating an unguarded bench-mounted grinder for two hours daily — and write three answers: identify the hazard, outline the risks, explain why those risks arise. Expected observations: the identify answer is one line; the outline answer adds features such as flying fragments and entanglement; the explain answer must contain causes — no guarding, prolonged exposure, worn or unsuitable wheels. If your explain answer reads like your outline, the depth dial is broken; rewrite until each sentence answers a 'why' or a 'how'.
| Command word | What it demands | A calibrated answer looks like | Typical mismatch |
|---|---|---|---|
| Identify | Name the item or issue | A short list with little elaboration | Writing full explanations when a list is asked for |
| Outline | Give the main features | A phrase or sentence per point | Single words that name a thing but give no features |
| Describe | Set out what it is or how it works in detail | Consecutive detail about one thing | Scattering points across unrelated topics |
| Explain | Give reasons or mechanisms | 'Because' and 'how' links drawn from the scenario | A list of items with no causal links |
| Discuss / Justify | Weigh points and argue a case for the scenario | A reasoned case supported by scenario evidence | Restating facts without reaching a conclusion |
Moral, financial and legal arguments are three separate lines of reasoning
When asked to justify improvements, build three distinct arguments — moral, financial and legal — each anchored in the scenario. Blending them into one list blurs the reasoning the question asks you to demonstrate.
Keep the strands separate from the start. The moral argument rests on societal expectation and the right to a safe and healthy working environment expressed in the ILO Declaration on Fundamental Principles and Rights at Work. The financial argument distinguishes direct from indirect costs and insured from uninsured costs — the uninsured, indirect costs are usually the larger and less obvious set. The legal argument draws on employers' core duties in ILO Convention C155 Article 16 and Recommendation R164, and on what enforcement agencies can do when duties are not met. Each strand is its own reasoning chain ending in 'therefore this improvement is needed'.
Worked scenario: a distribution centre where a stacker truck has struck a racking leg and pedestrians have reported near-misses. The tempting answer is 'accidents cost money and are bad for morale'. The better decision is three anchored strands: moral — people on foot have reported near-misses, showing a foreseeable threat to those who cannot control the vehicle's movement; financial — racking repair may be insured, but damaged stock, investigation time and operator cover are likely uninsured indirect costs; legal — employers carry core duties under C155 Article 16, and repeated near-misses point to duties not being discharged. This matters because the strands are assessed as separate reasoning, and each needs its own scenario evidence.
ISO 45001 and ILO-OSH 2001: compare the frameworks, do not memorise two lists
The syllabus asks you to identify components of management systems based on ISO 45001 and ILO-OSH 2001 and recognise benefits and limitations of different types. Structured comparison serves you better than rote recall.
Treat the two as comparable frameworks rather than parallel lists: both organise health and safety work into a continuous cycle of planning, implementing, checking and improving, and both put policy, responsibilities and competence at the centre. ISO 45001 is the international standard; ILO-OSH 2001 is the ILO's guidelines framework. The assessed judgement sits in the benefits and limitations question: a structured system clarifies responsibilities and makes monitoring routine, but paperwork alone controls nothing — a system without worker participation or genuine risk assessment produces files rather than safety.
Practise by mapping scenario events onto the cycle. A new machine arrives: that triggers planning (risk assessment before use) and implementation (controls, information, training). Near-miss reports accumulate: that feeds checking and review rather than blame. When a question asks what a good policy contains or where a system type falls short, anchor the answer in that behaviour. Note too that elements 1.1, 1.2, 2 and 3 also appear in the practical assessment, so system language earns its keep twice — in your GIC1 answers and in the justification column of your GIC2 action plan.
Hazard, risk and control: keeping the three columns honest in GIC2
GIC2 asks for a risk assessment of your workplace plus an action plan, using the 5-step approach. Marks ride on separating the hazard (what could cause harm), the risk (likelihood and severity) and the controls that reduce it.
Two habits distort the columns. The first is writing control failures as hazards: 'inadequate training' and 'poor housekeeping' are states of the workplace, not things with potential to cause harm. The second is recommending generic measures — 'more training will be provided' — without first describing the controls that already exist and evaluating them. The syllabus expects that sequence explicitly: describe existing controls, evaluate them, then explain suitable additional measures. An action plan built on an unevaluated baseline looks arbitrary and gives the reader no reason to prioritise one recommendation over another.
Worked scenario: a loading bay where delivery vans reverse while pedestrians cross to the stores door. The tempting submission reads: hazard — lack of supervision; risk — accidents; additional control — refresher training. The better decision keeps the chain intact: hazard — reversing vehicles conflicting with people on foot in a shared space; risk — a pedestrian being struck and crushed; existing controls — hi-vis vests and a corner mirror, evaluated as giving limited visibility at peak times; additional controls — a segregated walkway and a marshal-controlled reversing routine, entered first in the action plan. This matters because each column earns credit on its own terms, and the evaluation step is what makes the extra measures defensible rather than decorative.
Incidents, monitoring, audit and review: which word means what
Elements 3 and 4 distinguish terms that sound interchangeable: incident versus accident, proactive versus reactive monitoring, and audit versus review. Precision here changes how you read any scenario.
NEBOSH adopts ISO 45001's definition of an incident: an event in the workplace that causes, or has the potential to cause, harm, injury, ill-health or damage. A near-miss is therefore an incident, and 'accident' survives mainly inside named models such as Reason's accident causation. Monitoring splits into proactive measures taken before harm occurs — inspections, sampling, safety observations — and reactive measures taken after it: injury and ill-health statistics, and incident investigations. Audits are systematic, largely independent evaluations of the management system; review is the organisation's own periodic judgement of performance and of what must change next.
A sorting drill fixes the boundaries. List ten evidence items — inspection findings, a fork-lift near-miss, lost-time injury counts, an external audit report, safety committee minutes, sickness absence data — and place each as proactive or reactive, then as audit input or review input, then name who should act on it. In scenario questions, follow the scenario's own usage: if the text describes a near-miss with a falling load, treat it as an incident in which harm was potential rather than actual, and reason about both what happened and what could have happened under slightly different conditions.
A preparation sequence and readiness checks for both units
Sequence the two skills separately: management knowledge with scenario writing for GIC1, hazard-spotting with control evaluation for GIC2, then combine them under timed conditions and rehearse explaining your answers.
Work in blocks. Early weeks: elements 1 to 4, using command-word drills and the scenario-rewriting habit from the first section. Middle weeks: hazard elements 5 to 11, learned through repeated walks of your own workplace that produce hazard–risk–control triples. Next: draft a GIC2-style risk assessment and action plan for your workplace, following NEBOSH's dedicated GIC2 guidance document, which your Learning Partner can point you to for format and submission arrangements. Final phase: a timed scenario practice paper, then read your answers aloud as if defending them in the closing interview — anything you cannot explain in your own words needs rewriting, not memorising.
Readiness checks before you book: from one scenario fact, produce answers at identify, outline and explain depth and hear the difference between them; from one incident, build moral, financial and legal strands with scenario evidence in each; from one workplace walk, produce at least five triples whose hazards are objects or activities, not missing controls; and explain every line of a practice submission without consulting your notes. Treat these as learning milestones, not grade predictions. Assessment dates, fees and submission windows are set by NEBOSH and Learning Partners — check nebosh.org.uk for current administrative arrangements.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.