# Model Role SOP / Operating Playbook for an Occupational Health and Safety Coordinator

A reusable occupational health and safety coordination playbook from report intake through communication, incident learning, action follow-up, effectiveness review and operating cadence.

**Learn the occupational safety coordination workflow:** [Open the course and enrol](https://mtfinstitute.com/programs/occupational-health-safety-coordination/#enroll)

**Resource type:** role sop operating playbook  
**Evidence geography:** United States  
**Evidence scope:** A structured purposive study of 100 current United States occupational health and safety coordination vacancies observed on 30 September 2026, plus a separate 22-source review of current changes in safety-coordination work.  
**Accepted source SHA-256:** `be092dedb5e67cc4c5ed5f25d4509a4e0a1e56a3a08f8f57fe4953d51d3748e0`

## Model Role SOP — Occupational Health and Safety Coordinator Operating Playbook

## How to use this model

This playbook is an evidence-derived operating model for local adaptation. It is not universal employer policy, legal advice, an executable high-hazard procedure, or professional authorization. It does not grant stop-work, permit, engineering, industrial-hygiene, medical, regulatory, disciplinary, competent-person, qualified-person, or emergency-command authority.

The model describes how an Occupational Health and Safety Coordinator can receive information, preserve facts, coordinate people, route decisions, maintain records, track actions, and make unresolved risk visible. It must be adapted before use. The accountable employer remains responsible for defining authority, approved processes, required training, records, systems, and escalation routes.

Fields marked with the following labels are controlled locally and must be completed or confirmed by an authorized person:

- **[LOCAL — EMPLOYER POLICY]**: controlled by the employer's approved policy, procedure, delegation, or collective-bargaining arrangement.
- **[LOCAL — APPROVED SYSTEM]**: controlled by the employer's approved form, log, platform, record location, access rule, or non-digital fallback.
- **[LOCAL — JURISDICTION]**: controlled by applicable federal, OSHA-approved State Plan, state, local, sector, or other jurisdictional requirements.
- **[LOCAL — QUALIFIED SPECIALIST]**: controlled by a person with the required legal, technical, engineering, industrial-hygiene, medical, mental-health, privacy, or other professional competence.
- **[LOCAL — SITE AND WORK]**: controlled by the actual workplace, task, people, contractors, hazards, equipment, language needs, accessibility needs, and current conditions.

No local label may be completed by guesswork. If an applicable field is unresolved, the coordinator records the gap, uses the approved protected route, and escalates it to the accountable owner.

## Purpose and scope

### Purpose

The purpose of this model is to make everyday safety-coordination work observable, reviewable, and easier to hand over. It connects five recurring work-product families:

- hazard, concern, close-call, and worker-report intake;
- observations, inspections, audits, and assessments;
- toolbox talks and short supervisor safety briefings;
- incident and near-miss intake and learning support;
- corrective-action tracking, closure evidence, and effectiveness review.

The model also connects those products to supervisor routines, records, metrics, worker feedback, contractor handoffs, specialist review, and accountable leadership decisions.

### Intended user

The intended user is an aspiring or early-career Occupational Health and Safety Coordinator, or an operational professional performing equivalent coordination work, under defined employer, site, and jurisdictional authority. The model assumes access to an accountable supervisor or safety leader and to named specialists when a decision falls outside coordinator authority.

### Included coordination work

The coordinator may act within **[LOCAL — EMPLOYER POLICY: delegated coordinator authority]** to:

- receive, acknowledge, document, triage, and route information;
- identify and record an observed condition without claiming a technical determination;
- coordinate a briefing using validated site information;
- recommend an action and track the accountable owner;
- verify that agreed completion or effectiveness evidence exists;
- prepare bounded logs, dashboards, summaries, and handoffs;
- activate an employer-defined urgent or emergency route;
- communicate lawful status or outcome feedback to the person who raised a concern.

### Excluded practice

This playbook does not provide instructions for operating equipment; lockout or tagout; confined-space entry; fall protection; respiratory protection; electrical work; hazardous-material handling; exposure monitoring; medical care; mental-health care; or emergency command. It does not design controls or replace employer-provided, role-specific, or site-specific training.

The coordinator does not independently decide:

- what technical control is adequate;
- whether an exposure is acceptable;
- whether a person is medically fit or may return to work;
- whether an event is legally recordable or reportable;
- whether discipline, legal action, or regulatory notification is required;
- who has competent-person or qualified-person status;
- whether a safety-critical suggestion from software or AI is correct.

Those matters go to **[LOCAL — QUALIFIED SPECIALIST: named decision owner]**, **[LOCAL — EMPLOYER POLICY: accountable role]**, and **[LOCAL — JURISDICTION: applicable requirement]**.

## Operating principles

- **Life safety comes first.** When immediate danger, injury, illness, fire, release, or an urgent health concern exists, use **[LOCAL — EMPLOYER POLICY: emergency route]** and contact **[LOCAL — SITE AND WORK: authorized responder]**. Coordination records follow after the immediate response permits.
- **Facts are separated from interpretations.** Record what was seen, heard, reported, or produced by an approved system. Mark uncertainty and conflicting accounts. Do not invent causation.
- **The reporter is treated with respect.** Welcome reports, listen without blame, protect confidentiality, explain the route, and avoid any practice that discourages reporting.
- **Authority is explicit.** Each decision has a named owner. The coordinator makes only decisions within **[LOCAL — EMPLOYER POLICY: written delegation]**.
- **A handoff is confirmed, not assumed.** Record who accepted the item, what they accepted, the next action, the due point, and how status will return.
- **Closed is not the same as effective.** Administrative completion is recorded separately from evidence that the intended control is present and working.
- **Activity is not outcome.** Counts of reports, talks, or inspections do not by themselves prove that risk increased or decreased.
- **Tools assist; people remain accountable.** Forms, mobile systems, dashboards, analytics, and AI do not inherit authority from their users.
- **Local rules control.** Federal context does not replace the applicable State Plan, state or local rule, employer process, collective-bargaining term, site requirement, or specialist judgment.

## Roles and interfaces

### Occupational Health and Safety Coordinator

The coordinator owns the quality of intake, documentation, routing, follow-up, and visibility within delegated authority. Typical outputs include an observation record, incident or near-miss file, corrective-action status record, briefing record, and bounded status summary.

The coordinator does not become the accountable control owner merely by recording or following an item. Ownership must be assigned under **[LOCAL — EMPLOYER POLICY: action-ownership rule]**.

### Supervisor or operational leader

The supervisor or operational leader confirms current work conditions, operational ownership, worker availability, and actions within their authority. The role validates task-specific facts used in a briefing and addresses assigned actions under **[LOCAL — EMPLOYER POLICY: supervisor responsibilities]**.

### Worker or reporter

The worker or reporter supplies information voluntarily through **[LOCAL — APPROVED SYSTEM: named, anonymous, accessible, and alternative reporting routes]**. The person may ask questions, correct the record, identify confidentiality needs, and receive lawful follow-up. Reporting does not transfer the employer's duty to assess and act.

### Accountable safety or employer leader

This role sets local policy, delegates authority, resolves priorities, assigns resources, accepts residual risk where legally permitted, and decides issues reserved to employer leadership. Identify the role as **[LOCAL — EMPLOYER POLICY: accountable safety or employer leader]**.

### Qualified specialists

Specialists handle decisions requiring credentials, legal authority, technical competence, or protected professional judgment. Locally name at least:

- **[LOCAL — QUALIFIED SPECIALIST: engineering or technical control contact]**;
- **[LOCAL — QUALIFIED SPECIALIST: industrial-hygiene or exposure contact]**;
- **[LOCAL — QUALIFIED SPECIALIST: occupational health or medical contact]**;
- **[LOCAL — QUALIFIED SPECIALIST: legal, regulatory, or recordability contact]**;
- **[LOCAL — QUALIFIED SPECIALIST: privacy, HR, employee-relations, or retaliation contact]**;
- **[LOCAL — QUALIFIED SPECIALIST: emergency-preparedness contact]**.

### Contractors, host employers, and partners

Cross-organizational work requires explicit control and information boundaries. Record **[LOCAL — EMPLOYER POLICY: controlling employer or authority]**, **[LOCAL — SITE AND WORK: points of contact]**, **[LOCAL — APPROVED SYSTEM: record owner]**, and **[LOCAL — EMPLOYER POLICY: action owner and verification owner]** before treating a handoff as complete.

## Required inputs and readiness

Before applying this model, confirm that the following local inputs are available:

- **[LOCAL — EMPLOYER POLICY: coordinator delegation and limits]**;
- **[LOCAL — EMPLOYER POLICY: emergency and urgent-action route]**;
- **[LOCAL — JURISDICTION: applicable federal or State Plan and local context]**;
- **[LOCAL — SITE AND WORK: current work, interfaces, hazards, language, literacy, and accessibility needs]**;
- **[LOCAL — APPROVED SYSTEM: reporting channels and non-digital fallback]**;
- **[LOCAL — APPROVED SYSTEM: observation, incident, action, meeting, and metric records]**;
- **[LOCAL — EMPLOYER POLICY: confidentiality, retention, worker-feedback, and anti-retaliation controls]**;
- **[LOCAL — QUALIFIED SPECIALIST: escalation directory and availability]**;
- **[LOCAL — EMPLOYER POLICY: action priority and due-point method]**;
- **[LOCAL — EMPLOYER POLICY: effectiveness-review rule]**;
- **[LOCAL — SITE AND WORK: contractor and partner arrangements]**;
- **[LOCAL — EMPLOYER POLICY: approved AI and data-use rules]**.

If any input needed for a safety-relevant decision is unavailable, do not fill the gap with a generic assumption. Record the missing input, apply the approved interim route if one exists, and escalate.

## Trigger-to-close workflow

Use this sequence for a report, observation, changed condition, near miss, incident follow-up, overdue action, contractor concern, or safety-relevant digital alert. The sequence organizes coordination; it does not replace the employer's urgent or emergency response.

1. **Recognize the trigger.** Capture how the item entered the workflow, who or what raised it, when it was raised, and whether immediate response is already active. Use **[LOCAL — APPROVED SYSTEM: intake channel and time standard]**.
2. **Protect people and activate the local route.** If the item may involve immediate danger or an urgent health event, use **[LOCAL — EMPLOYER POLICY: emergency or urgent-action route]** and contact **[LOCAL — SITE AND WORK: authorized responder]**. Do not delay that route to complete the form.
3. **Acknowledge and preserve.** Acknowledge the reporter when possible. Record observable facts, the reporter's wording where appropriate, time, source, uncertainty, and evidence provenance. Apply **[LOCAL — EMPLOYER POLICY: confidentiality and evidence-preservation rule]**.
4. **Triage without exceeding authority.** Classify the item only to the degree allowed by **[LOCAL — EMPLOYER POLICY: triage categories and coordinator delegation]**. Mark any technical, legal, medical, recordability, privacy, or authority question for specialist review.
5. **Assign the accountable route.** Identify the supervisor, control owner, specialist, employer leader, contractor contact, or protected channel responsible for the next decision. Confirm acceptance under **[LOCAL — APPROVED SYSTEM: handoff method]**.
6. **Define the expected output.** State what record, decision, action, briefing, review, or verification is expected; who owns it; the local due point; and what evidence will show completion. Use **[LOCAL — EMPLOYER POLICY: priority and due-point rule]**.
7. **Coordinate action and communication.** Provide the validated information needed by the owner, support worker or supervisor communication, and keep sensitive information limited to those with a lawful need.
8. **Track progress and exceptions.** Maintain status, dates, owner, dependencies, aging, worker feedback, and escalation. Use **[LOCAL — APPROVED SYSTEM: action register or fallback]**.
9. **Verify completion and, where required, effectiveness.** Check the agreed evidence. When effectiveness requires specialist judgment, field measurement, or accountable acceptance, route it to **[LOCAL — QUALIFIED SPECIALIST: effectiveness verifier]**. Record completion and effectiveness as separate fields.
10. **Close the loop.** Provide lawful status or outcome feedback to the reporter and affected people, document unresolved limits, and retain the record under **[LOCAL — EMPLOYER POLICY: closure and retention rule]**. Reopen or escalate if the issue recurs or the evidence is insufficient.

## Hazard-report intake and routing

### Intake standard

The intake route should welcome hazards, injuries, illnesses, concerns, and close calls without treating low reporting volume as success. The coordinator should:

- accept reports through **[LOCAL — APPROVED SYSTEM: named, anonymous, verbal, accessible, and non-digital channels]**;
- acknowledge the report within **[LOCAL — EMPLOYER POLICY: acknowledgement expectation]**;
- ask only for information needed to understand and route the concern;
- record the reporter's preferred safe contact method under **[LOCAL — EMPLOYER POLICY: confidentiality rule]**;
- avoid promises about legal, disciplinary, medical, or regulatory outcomes;
- record any concern about retaliation and route it through **[LOCAL — EMPLOYER POLICY: protected retaliation channel]**;
- explain the next handoff and how lawful feedback will be provided.

### Minimum intake fields

- Intake identifier: **[LOCAL — APPROVED SYSTEM]**
- Date, time, and channel: **[LOCAL — APPROVED SYSTEM]**
- Reporter identity or anonymous status: **[LOCAL — EMPLOYER POLICY]**
- Safe contact preference: **[LOCAL — EMPLOYER POLICY]**
- Location or work area at the minimum necessary precision: **[LOCAL — SITE AND WORK]**
- Condition, event, or concern in factual terms: **[LOCAL — SITE AND WORK]**
- Immediate response already taken: **[LOCAL — EMPLOYER POLICY]**
- Urgency category: **[LOCAL — EMPLOYER POLICY]**
- Confidentiality or retaliation concern: **[LOCAL — EMPLOYER POLICY]**
- Accountable next owner: **[LOCAL — EMPLOYER POLICY]**
- Specialist route, if any: **[LOCAL — QUALIFIED SPECIALIST]**
- Feedback point and record location: **[LOCAL — APPROVED SYSTEM]**

## Observation and inspection routing

An observation or inspection record describes what was observed and how it was routed. It does not by itself establish legal compliance or technical adequacy.

### Coordinator practice

- Confirm the purpose, scope, authorized area, participants, and form under **[LOCAL — EMPLOYER POLICY: inspection or observation plan]**.
- Use **[LOCAL — SITE AND WORK: current task and condition information]** rather than a generic checklist alone.
- Record observable conditions, relevant context, and evidence limits. Distinguish direct observation from a statement made by another person.
- If an urgent condition may exist, use **[LOCAL — EMPLOYER POLICY: urgent-action route]** rather than improvising authority.
- Route technical interpretations to **[LOCAL — QUALIFIED SPECIALIST: technical reviewer]**.
- Assign action ownership through **[LOCAL — EMPLOYER POLICY: assignment method]**, not merely to the person entering data.
- Return status to affected workers under **[LOCAL — EMPLOYER POLICY: feedback and confidentiality rule]**.

### Observation record fields

- Observation identifier and date: **[LOCAL — APPROVED SYSTEM]**
- Scope, area, and authorized participants: **[LOCAL — SITE AND WORK]**
- Work as observed: **[LOCAL — SITE AND WORK]**
- Observed condition and evidence provenance: **[LOCAL — SITE AND WORK]**
- Uncertainty or unavailable information: **[LOCAL — SITE AND WORK]**
- Immediate local route used, if any: **[LOCAL — EMPLOYER POLICY]**
- Accountable owner and accepted handoff: **[LOCAL — EMPLOYER POLICY]**
- Specialist question and reviewer: **[LOCAL — QUALIFIED SPECIALIST]**
- Action, due point, and expected evidence: **[LOCAL — EMPLOYER POLICY]**
- Completion and effectiveness status: **[LOCAL — APPROVED SYSTEM]**

## Toolbox-talk preparation and facilitation

A toolbox talk or short supervisor briefing is a coordination aid. It must use validated local information and cannot replace required training, demonstration, qualification, or a high-hazard procedure.

### Preparation

- Define the actual task, audience, work change, and communication purpose using **[LOCAL — SITE AND WORK: current work facts]**.
- Obtain validated hazards, controls, personal protective equipment information, emergency information, and required demonstration from **[LOCAL — EMPLOYER POLICY: accountable site owner]** and **[LOCAL — QUALIFIED SPECIALIST: reviewer, when required]**.
- Confirm language, literacy, disability-access, and participation needs under **[LOCAL — EMPLOYER POLICY: accessibility process]**.
- Prepare task-specific questions that invite workers to identify changed conditions, unclear interfaces, and missing resources.
- Identify what must be deferred to required training or a specialist.
- Use **[LOCAL — APPROVED SYSTEM: briefing form and record location]**.

### Facilitation

- State the task and purpose plainly.
- Ask workers to describe what has changed and what could interfere with the validated controls.
- Invite questions, corrections, and dissent without blame.
- Confirm observable readiness through **[LOCAL — EMPLOYER POLICY: approved readiness method]**; do not infer readiness from attendance alone.
- Pause and route unresolved safety-relevant questions to **[LOCAL — EMPLOYER POLICY: accountable supervisor]** or **[LOCAL — QUALIFIED SPECIALIST: named contact]**.
- Record the validated information discussed, questions raised, unresolved items, owner, and follow-up point.

### Briefing record fields

- Task, audience, area, and date: **[LOCAL — SITE AND WORK]**
- Accountable content validator: **[LOCAL — EMPLOYER POLICY]**
- Specialist validation, where required: **[LOCAL — QUALIFIED SPECIALIST]**
- Language and accessibility arrangements: **[LOCAL — EMPLOYER POLICY]**
- Validated controls referenced: **[LOCAL — EMPLOYER POLICY]**
- Questions and changed conditions raised: **[LOCAL — SITE AND WORK]**
- Observed readiness method and result: **[LOCAL — EMPLOYER POLICY]**
- Unresolved issue, owner, route, and due point: **[LOCAL — APPROVED SYSTEM]**

## Incident and near-miss intake and learning

### Boundary

This section begins after immediate response allows coordination work. It supports fact preservation, privacy, handoffs, and systems-oriented learning. It does not determine medical diagnosis, fault, discipline, legal recordability, regulatory notification, workers' compensation, or return to work.

### Intake and evidence practice

- Open the approved record in **[LOCAL — APPROVED SYSTEM: incident or near-miss system]**.
- Record what is known, what is reported, what is uncertain, and who supplied each item.
- Preserve evidence only as authorized by **[LOCAL — EMPLOYER POLICY: evidence and access rule]**.
- Minimize personal, medical, witness, security, location, trade-secret, and employee-relations data.
- Record the immediate-response owner and status without evaluating clinical or emergency decisions.
- Route recordability, notification, legal, medical, and disciplinary questions to **[LOCAL — QUALIFIED SPECIALIST: applicable decision owner]**.

### Learning questions

Use questions that help the accountable review team understand work as performed:

- What task and conditions existed at the time?
- What information, equipment state, supervision, interfaces, or resources shaped the work?
- Which barriers were expected, observed, unavailable, bypassed, or difficult to use?
- What changed from the expected plan?
- What uncertainty remains, and who can resolve it?
- What immediate response was taken, and what longer-term action needs separate ownership?
- What evidence would show that an agreed action is working?

These questions support learning; they do not establish cause by themselves. Causal, technical, legal, and professional conclusions belong to **[LOCAL — QUALIFIED SPECIALIST: review lead]** or **[LOCAL — EMPLOYER POLICY: accountable investigation owner]**.

### Incident or near-miss file fields

- File identifier and event type: **[LOCAL — APPROVED SYSTEM]**
- Minimum necessary time and location: **[LOCAL — EMPLOYER POLICY]**
- Immediate-response status and owner: **[LOCAL — EMPLOYER POLICY]**
- Facts, sources, uncertainty, and evidence provenance: **[LOCAL — SITE AND WORK]**
- Privacy classification and access group: **[LOCAL — EMPLOYER POLICY]**
- Specialist decisions required: **[LOCAL — QUALIFIED SPECIALIST]**
- Handoffs and acceptance: **[LOCAL — APPROVED SYSTEM]**
- Learning questions and bounded findings: **[LOCAL — EMPLOYER POLICY]**
- Actions, owners, due points, and evidence: **[LOCAL — APPROVED SYSTEM]**
- Feedback and closure status: **[LOCAL — EMPLOYER POLICY]**

## Corrective-action tracking and effectiveness

### Status model

Use status names defined in **[LOCAL — APPROVED SYSTEM: corrective-action workflow]**. At minimum, preserve the difference between:

- proposed or awaiting accountable decision;
- assigned and accepted by an owner;
- in progress;
- completion evidence submitted;
- completion verified;
- effectiveness review due;
- effective, ineffective, or inconclusive under the local review rule;
- escalated, reopened, or closed with a recorded authorized decision.

### Tracking fields

- Source record and issue statement: **[LOCAL — APPROVED SYSTEM]**
- Risk or priority category: **[LOCAL — EMPLOYER POLICY]**
- Accountable action owner: **[LOCAL — EMPLOYER POLICY]**
- Action description approved by the owner: **[LOCAL — EMPLOYER POLICY]**
- Due point and aging rule: **[LOCAL — EMPLOYER POLICY]**
- Completion criterion and required evidence: **[LOCAL — EMPLOYER POLICY]**
- Completion verifier: **[LOCAL — EMPLOYER POLICY]**
- Effectiveness question and review timing: **[LOCAL — EMPLOYER POLICY]**
- Specialist verification, when required: **[LOCAL — QUALIFIED SPECIALIST]**
- Worker or user feedback method: **[LOCAL — EMPLOYER POLICY]**
- Final status, limitation, and escalation: **[LOCAL — APPROVED SYSTEM]**

### Effectiveness discipline

Do not treat a purchase, work order, document update, photograph, or owner statement as automatic proof of risk reduction. Apply **[LOCAL — EMPLOYER POLICY: effectiveness criteria]**. Depending on the locally approved method, evidence may include confirmation that the intended condition exists, feedback from people who use the control, a repeat observation, or a specialist's measurement or judgment. The coordinator records the evidence and route; the coordinator does not perform measurements or specialist evaluations outside delegated competence.

Overdue, disputed, recurring, ineffective, or inconclusive actions are escalated under **[LOCAL — EMPLOYER POLICY: aging and escalation rule]**.

## Supervisor coordination routines

### Daily or shift routine

- Review new reports, observations, changed work, and unresolved urgent items.
- Confirm **[LOCAL — SITE AND WORK: planned work and interfaces]** with **[LOCAL — EMPLOYER POLICY: accountable supervisor]**.
- Identify briefings that need locally validated content.
- Confirm ownership and status for actions due during the period.
- Check that worker feedback and protected routes remain usable.
- Update **[LOCAL — APPROVED SYSTEM: action and record status]**.

### Weekly routine

- Review open and overdue actions with owners.
- Review repeated reports, observations, and near-miss themes without claiming causation from counts alone.
- Confirm that accepted handoffs have a next action and return path.
- Check whether completion evidence and effectiveness reviews are being confused.
- Review worker feedback, confidentiality concerns, and retaliation signals through **[LOCAL — EMPLOYER POLICY: protected review route]**.
- Agree the next week's coordination priorities under **[LOCAL — EMPLOYER POLICY: priority-setting process]**.

### Monthly routine

- Review action aging, effectiveness status, recurring weak signals, and unresolved escalation.
- Compare activity measures with bounded outcome evidence and state limitations.
- Review whether reporting channels, briefing access, specialist routing, and contractor handoffs are working.
- Refresh communication and coordination priorities.
- Present a bounded summary to **[LOCAL — EMPLOYER POLICY: accountable leadership forum]**.

### Lifecycle or change routine

During design, procurement, mobilization, contractor onboarding, or planned change, participate only when invited and authorized. Clarify:

- **[LOCAL — EMPLOYER POLICY: decision owner]**;
- **[LOCAL — SITE AND WORK: affected work and interfaces]**;
- **[LOCAL — QUALIFIED SPECIALIST: required reviewer]**;
- **[LOCAL — APPROVED SYSTEM: record owner]**;
- **[LOCAL — EMPLOYER POLICY: action and control-verification owners]**;
- **[LOCAL — EMPLOYER POLICY: handoff and feedback points]**.

### Event-driven routine

Use the trigger-to-close workflow for reports, changed conditions, observations, incidents, near misses, urgent health concerns, system alerts, contractor issues, and failed or overdue actions. Immediate response always follows **[LOCAL — EMPLOYER POLICY: emergency and urgent-action route]** before ordinary coordination.

## Decisions, handoffs, and escalation

### Decisions the coordinator may support

Within **[LOCAL — EMPLOYER POLICY: written delegation]**, the coordinator may decide how to document an intake, which approved route applies, which information is missing, whether a handoff has been accepted, whether required evidence is present, and whether an item needs escalation. The coordinator may recommend priority or action but records the accountable owner's decision.

### Decisions reserved to others

Route the following without delay:

- immediate danger or urgent health event to **[LOCAL — EMPLOYER POLICY: emergency route]** and **[LOCAL — SITE AND WORK: authorized responder]**;
- engineering, technical-control, exposure, or industrial-hygiene questions to **[LOCAL — QUALIFIED SPECIALIST: technical owner]**;
- legal, regulatory, recordability, notification, workers' compensation, discipline, or return-to-work questions to **[LOCAL — QUALIFIED SPECIALIST: applicable owner]**;
- retaliation, confidentiality breach, sensitive allegation, or worker-rights concern to **[LOCAL — EMPLOYER POLICY: protected route]**;
- contractor or host-employer ownership ambiguity to **[LOCAL — EMPLOYER POLICY: controlling-authority resolver]**;
- a safety-critical AI or digital suggestion to **[LOCAL — EMPLOYER POLICY: accountable human reviewer]**.

### Handoff quality check

A handoff is complete only when the record shows:

- the item and relevant evidence transferred;
- the information intentionally withheld for privacy and why;
- the receiving person and role;
- the date and method of acceptance;
- the decision or action expected;
- the local due point;
- the return path for status and questions;
- any unresolved authority or jurisdiction issue.

## Records and evidence

### Record families

Maintain only the record families approved locally:

- **[LOCAL — APPROVED SYSTEM: report and concern intake]**;
- **[LOCAL — APPROVED SYSTEM: observation and inspection record]**;
- **[LOCAL — APPROVED SYSTEM: briefing or meeting record]**;
- **[LOCAL — APPROVED SYSTEM: incident or near-miss file]**;
- **[LOCAL — APPROVED SYSTEM: corrective-action register]**;
- **[LOCAL — APPROVED SYSTEM: status summary or dashboard]**;
- **[LOCAL — APPROVED SYSTEM: AI-assistance review record]**.

Apply **[LOCAL — EMPLOYER POLICY: record owner, retention, access, correction, legal hold, and disposal rules]** and **[LOCAL — JURISDICTION: applicable record requirements]**.

### Leading evidence

Leading evidence can show whether coordination controls are functioning before an adverse outcome. Locally selected measures may include:

- time from report to acknowledgement under **[LOCAL — EMPLOYER POLICY: time definition]**;
- proportion of items with a confirmed owner and return path;
- open and overdue actions by locally approved priority;
- actions with completion evidence separated from actions with effectiveness evidence;
- repeat observations or reports awaiting accountable review;
- worker questions, corrections, and feedback addressed;
- briefings with validated content and observed readiness evidence;
- accepted contractor handoffs with named record and action owners;
- AI-assisted drafts with a recorded accountable human review.

These measures do not prove injury reduction or legal compliance. Targets and thresholds are **[LOCAL — EMPLOYER POLICY]** fields.

### Lagging evidence

Lagging evidence may include locally defined incidents, injuries, illnesses, near misses, lost time, damage, releases, or other outcomes. Definitions, classification, recordability, reporting, and denominators are controlled by **[LOCAL — JURISDICTION]**, **[LOCAL — EMPLOYER POLICY]**, and **[LOCAL — QUALIFIED SPECIALIST]**.

Do not compare unlike definitions, infer individual performance from small counts, reward non-reporting, or claim causation without an appropriate study and accountable review.

### Bounded interpretation

Every status summary should state:

- the period and population: **[LOCAL — EMPLOYER POLICY]**;
- the definitions and exclusions: **[LOCAL — EMPLOYER POLICY]**;
- the data source and known quality limits: **[LOCAL — APPROVED SYSTEM]**;
- unresolved missing data: **[LOCAL — APPROVED SYSTEM]**;
- the distinction between activity, completion, effectiveness, and outcome;
- the decisions requested from **[LOCAL — EMPLOYER POLICY: accountable audience]**.

## Exception handling

### Approved system unavailable

Use **[LOCAL — APPROVED SYSTEM: non-digital or alternate fallback]**. Preserve the minimum necessary information, maintain access controls, record when the primary system became available, and transfer the record under **[LOCAL — EMPLOYER POLICY: reconciliation rule]**. Do not create uncontrolled duplicate records.

### Anonymous report with limited detail

Preserve the report, document the limits, use only approved contact or follow-up options, and route the concern based on available facts. Do not reject it solely because the reporter is anonymous.

### Conflicting accounts or missing facts

Record each source and uncertainty separately. Do not force consensus or select a preferred account without evidence. Route fact-finding to **[LOCAL — EMPLOYER POLICY: accountable review owner]**.

### Reporter fears retaliation

Limit access, avoid unnecessary identification, explain what cannot be kept confidential, and use **[LOCAL — EMPLOYER POLICY: protected retaliation route]**. The coordinator does not promise a legal or employment outcome.

### Contractor or cross-organizational ambiguity

Pause ordinary handoff closure until **[LOCAL — EMPLOYER POLICY: controlling authority]**, **[LOCAL — APPROVED SYSTEM: record owner]**, and **[LOCAL — EMPLOYER POLICY: action owner]** are identified. Immediate response still follows the locally approved route.

### Owner declines, disputes, or misses an action

Record the response factually, keep the original concern and evidence intact, and escalate through **[LOCAL — EMPLOYER POLICY: action dispute and aging route]**. Do not silently reassign accountability.

### Completion evidence is weak or effectiveness is unclear

Keep completion and effectiveness statuses separate. Request the agreed evidence or route the item to **[LOCAL — QUALIFIED SPECIALIST: verifier]**. Reopen or escalate under **[LOCAL — EMPLOYER POLICY: review rule]**.

### Repeated issue after closure

Link the new observation to the earlier record under **[LOCAL — APPROVED SYSTEM: recurrence method]**, preserve the new facts, and route an effectiveness review. Do not erase or overwrite the earlier closure decision.

### Digital alert or AI output appears wrong

Stop using the output for the decision, preserve an authorized record of the issue, verify against authoritative local sources, use the non-digital fallback, and route the final decision to **[LOCAL — EMPLOYER POLICY: accountable human reviewer]**.

## Privacy, confidentiality, and worker rights

Use the minimum information necessary for the safety purpose. Apply **[LOCAL — EMPLOYER POLICY: privacy classification, access, sharing, retention, and correction rules]** and **[LOCAL — JURISDICTION: applicable privacy and worker-rights requirements]**.

Do not place names, medical details, injury records, witness statements, precise sensitive locations, security information, photographs, trade secrets, or employee-relations information in a broadly accessible log or unapproved tool. Separate operational status from restricted details where **[LOCAL — APPROVED SYSTEM: access model]** allows.

Share information only with people who have a lawful need. Before a contractor or partner handoff, confirm **[LOCAL — EMPLOYER POLICY: permitted disclosure]**, record what was shared, and omit unrelated personal information.

Maintain a reporting climate that supports access, acknowledgement, routing, follow-up, and freedom from retaliation. Low report volume is not proof of a safe workplace.

## Bounded AI assistance

### Permitted assistance

Subject to **[LOCAL — EMPLOYER POLICY: approved AI uses]**, AI may help organize fictional, synthetic, sanitized, or explicitly authorized information; draft a plain-language summary; suggest questions; group non-sensitive themes; or check the clarity of a communication.

### Prohibited delegation

AI may not decide hazards, controls, fault, treatment, recordability, regulatory reporting, work release, discipline, legal compliance, specialist sufficiency, or emergency action. It may not replace site observation, worker participation, authoritative sources, or accountable review.

### Data controls

Do not enter names, medical details, injury records, witness statements, precise locations, security information, photographs, trade secrets, or employee-relations data into an unapproved AI service. Use **[LOCAL — EMPLOYER POLICY: permitted data classes]** and **[LOCAL — APPROVED SYSTEM: approved AI environment]**.

### Human-review record

For each retained AI-assisted output, record:

- use case: **[LOCAL — EMPLOYER POLICY]**
- permitted data basis: **[LOCAL — EMPLOYER POLICY]**
- source facts checked: **[LOCAL — SITE AND WORK]**
- authoritative sources checked: **[LOCAL — JURISDICTION]** and **[LOCAL — EMPLOYER POLICY]**
- omissions, bias, or uncertainty found: **[LOCAL — EMPLOYER POLICY]**
- accountable reviewer and changes made: **[LOCAL — EMPLOYER POLICY]**
- final human decision owner: **[LOCAL — EMPLOYER POLICY]**
- record location and access: **[LOCAL — APPROVED SYSTEM]**

## Blank SOP model for local adaptation

### Document control

- Local title: **[LOCAL — EMPLOYER POLICY]**
- Document owner: **[LOCAL — EMPLOYER POLICY]**
- Approving role: **[LOCAL — EMPLOYER POLICY]**
- Effective date and review point: **[LOCAL — EMPLOYER POLICY]**
- Applicable sites and populations: **[LOCAL — SITE AND WORK]**
- Applicable jurisdiction and State Plan status: **[LOCAL — JURISDICTION]**
- Approved record location: **[LOCAL — APPROVED SYSTEM]**

### Purpose and limits

- Local purpose: **[LOCAL — EMPLOYER POLICY]**
- Coordinator delegation: **[LOCAL — EMPLOYER POLICY]**
- Decisions reserved to accountable leaders: **[LOCAL — EMPLOYER POLICY]**
- Specialist decisions: **[LOCAL — QUALIFIED SPECIALIST]**
- Work, sites, and contractor interfaces covered: **[LOCAL — SITE AND WORK]**
- Explicit excluded practices: **[LOCAL — EMPLOYER POLICY]**

### Local roles

- Coordinator role holder: **[LOCAL — EMPLOYER POLICY]**
- Accountable supervisor: **[LOCAL — EMPLOYER POLICY]**
- Safety or employer leader: **[LOCAL — EMPLOYER POLICY]**
- Worker or committee contact: **[LOCAL — EMPLOYER POLICY]**
- Contractor or partner contacts: **[LOCAL — SITE AND WORK]**
- Technical specialists: **[LOCAL — QUALIFIED SPECIALIST]**
- Legal, privacy, HR, or medical contacts: **[LOCAL — QUALIFIED SPECIALIST]**
- Authorized emergency contact: **[LOCAL — SITE AND WORK]**

### Local channels and records

- Reporting channels, including accessible and anonymous options: **[LOCAL — APPROVED SYSTEM]**
- Urgent and emergency route: **[LOCAL — EMPLOYER POLICY]**
- Observation and inspection form: **[LOCAL — APPROVED SYSTEM]**
- Briefing record: **[LOCAL — APPROVED SYSTEM]**
- Incident and near-miss file: **[LOCAL — APPROVED SYSTEM]**
- Corrective-action register: **[LOCAL — APPROVED SYSTEM]**
- Status and metrics summary: **[LOCAL — APPROVED SYSTEM]**
- Non-digital fallback and reconciliation method: **[LOCAL — APPROVED SYSTEM]**

### Local workflow

1. Trigger and intake rule: **[LOCAL — EMPLOYER POLICY]**
2. Immediate-response route: **[LOCAL — EMPLOYER POLICY]**
3. Acknowledgement and confidentiality rule: **[LOCAL — EMPLOYER POLICY]**
4. Triage categories and coordinator limit: **[LOCAL — EMPLOYER POLICY]**
5. Handoff and acceptance method: **[LOCAL — APPROVED SYSTEM]**
6. Action ownership, priority, and due-point method: **[LOCAL — EMPLOYER POLICY]**
7. Tracking and worker-feedback method: **[LOCAL — EMPLOYER POLICY]**
8. Completion evidence and effectiveness rule: **[LOCAL — EMPLOYER POLICY]**
9. Escalation and reopening rule: **[LOCAL — EMPLOYER POLICY]**
10. Closure, retention, and lawful feedback rule: **[LOCAL — EMPLOYER POLICY]**

### Local cadence

- Daily or shift review: **[LOCAL — EMPLOYER POLICY]**
- Weekly owner and action review: **[LOCAL — EMPLOYER POLICY]**
- Monthly trend and effectiveness review: **[LOCAL — EMPLOYER POLICY]**
- Lifecycle or change participation: **[LOCAL — EMPLOYER POLICY]**
- Event-driven contact and availability: **[LOCAL — EMPLOYER POLICY]**

### Local escalation map

- Immediate danger or urgent health event: **[LOCAL — EMPLOYER POLICY]**
- Technical, engineering, or exposure question: **[LOCAL — QUALIFIED SPECIALIST]**
- Medical or return-to-work question: **[LOCAL — QUALIFIED SPECIALIST]**
- Legal, recordability, or regulatory question: **[LOCAL — QUALIFIED SPECIALIST]**
- Privacy, retaliation, or employee-relations concern: **[LOCAL — EMPLOYER POLICY]**
- Contractor ownership conflict: **[LOCAL — EMPLOYER POLICY]**
- AI or digital-tool concern: **[LOCAL — EMPLOYER POLICY]**

### Local measurement and review

- Leading evidence and definitions: **[LOCAL — EMPLOYER POLICY]**
- Lagging evidence and definitions: **[LOCAL — JURISDICTION]** and **[LOCAL — EMPLOYER POLICY]**
- Data sources and quality checks: **[LOCAL — APPROVED SYSTEM]**
- Targets, thresholds, and limitations: **[LOCAL — EMPLOYER POLICY]**
- Leadership review forum: **[LOCAL — EMPLOYER POLICY]**
- Worker feedback route: **[LOCAL — EMPLOYER POLICY]**

### Local privacy and AI controls

- Data classification and minimum-necessary rule: **[LOCAL — EMPLOYER POLICY]**
- Access, sharing, retention, and deletion: **[LOCAL — EMPLOYER POLICY]**
- Approved AI uses and environment: **[LOCAL — APPROVED SYSTEM]**
- Prohibited data classes: **[LOCAL — EMPLOYER POLICY]**
- Human-review role and evidence: **[LOCAL — EMPLOYER POLICY]**
- Non-digital fallback: **[LOCAL — APPROVED SYSTEM]**

### Local approval check

- Employer-policy owner confirms authority and workflow: **[LOCAL — EMPLOYER POLICY]**
- Applicable jurisdiction is checked: **[LOCAL — JURISDICTION]**
- Specialist routes are verified: **[LOCAL — QUALIFIED SPECIALIST]**
- Systems and fallbacks are tested: **[LOCAL — APPROVED SYSTEM]**
- Site, worker, contractor, language, and accessibility needs are checked: **[LOCAL — SITE AND WORK]**
- Review date and change owner are assigned: **[LOCAL — EMPLOYER POLICY]**

## Worked fictional example

### Fictional setting and local adaptation

North River Components is a fictional U.S. employer with a small assembly and packaging site. The site has pedestrian aisles, carts, stored packaging materials, and contractor delivery activity. This example uses invented people, records, and events. It does not describe equipment operation or a high-hazard task.

For the example, the local fields have been completed as follows:

- **[LOCAL — EMPLOYER POLICY]**: The shift supervisor owns ordinary area actions. The safety manager owns escalation, action priority, effectiveness acceptance, and protected reporting. The site emergency plan controls urgent response.
- **[LOCAL — APPROVED SYSTEM]**: A fictional internal Safety Action Log records concerns, observations, handoffs, actions, and feedback. A controlled paper form is the fallback.
- **[LOCAL — JURISDICTION]**: The employer records that the applicable federal or State Plan, state, and local requirements must be checked by its safety manager and legal adviser; this example makes no compliance determination.
- **[LOCAL — QUALIFIED SPECIALIST]**: The safety manager identifies an ergonomics consultant, occupational health service, legal adviser, and emergency coordinator as specialist routes.
- **[LOCAL — SITE AND WORK]**: The day-shift assembly and packaging area, pedestrian aisles, delivery interface, English and Spanish communication needs, and one temporary worker with a stated reading-access need are included.

### Trigger

A packaging worker uses the named reporting channel to say that empty cartons are repeatedly staged partly inside a marked pedestrian aisle during the afternoon delivery window. The worker describes stepping around a cart and almost contacting another person coming from the opposite direction. No injury occurred. The worker asks that their name not be shared with the delivery contractor.

### Coordinated response

1. **Receive and acknowledge.** Coordinator Maya records the worker's wording, time, area, near-miss description, safe contact preference, and confidentiality request in the Safety Action Log. She acknowledges the report and explains that the operational concern will be shared without the worker's name unless an authorized review requires otherwise.
2. **Check the immediate route.** Maya asks the shift supervisor to review the current aisle condition under the site's ordinary urgent-condition process. The supervisor confirms that the site emergency route is not active and manages the immediate area under local policy. Maya does not invent or direct a traffic-control procedure.
3. **Preserve facts.** Maya separates the worker's account from her later observation. Her record says that cartons were reported in the aisle during the delivery window and that, during an authorized observation later that shift, she saw two stacks extending past the locally marked storage boundary. She records the time and avoids naming the reporter.
4. **Triage and hand off.** Under the fictional local policy, the shift supervisor owns the immediate area action and the operations manager owns the delivery-layout review. Both accept their items in the log. A contractor contact receives only the minimum operational information needed to review delivery staging.
5. **Define outputs.** The expected outputs are an observation record, a supervisor-confirmed staging correction, a review of delivery timing and space, a short validated briefing, and an effectiveness check during two later delivery windows. The safety manager approves the review plan.
6. **Prepare the briefing.** Maya drafts a short English and Spanish briefing using the site manager's validated facts. It explains the locally approved storage boundary, invites workers and contractors to identify blocked sightlines or insufficient space, and names the supervisor route for unresolved conditions. The supervisor validates the content. Maya records questions and observed understanding; she does not treat signatures as proof of readiness.
7. **Track action.** The operations manager assigns a defined storage location and revises the delivery-window coordination plan under local authority. Maya records the owner, due point, completion evidence, and later effectiveness review as separate fields.
8. **Check effectiveness.** During two authorized observations, the supervisor confirms that materials remain within the locally approved area and asks workers whether the revised arrangement creates another access issue. Maya records that no obstruction was observed during those limited checks and that workers raised no new concern. She states that two observations are bounded evidence, not proof that the condition can never recur.
9. **Close the feedback loop.** Maya tells the reporter, through the safe contact route, that the concern was reviewed, the area and delivery coordination were changed, and follow-up observations were completed. She does not disclose contractor personnel information.
10. **Review the pattern.** At the weekly supervisor review, Maya links this event to one earlier observation about delivery congestion. The team keeps the issue visible for the next monthly review rather than claiming a trend from two items.

### Fictional records produced

#### Hazard and near-miss intake

- Identifier: NRC-EXAMPLE-001
- Channel: named internal report with confidential handling
- Factual concern: packaging materials reported partly inside a pedestrian aisle during a recurring delivery window
- Reported outcome: close call; no injury reported
- Confidentiality: reporter name restricted to the safety manager and coordinator
- Handoff: shift supervisor accepted immediate area review; operations manager accepted delivery-layout review
- Feedback point: after completion evidence and two bounded follow-up observations

#### Observation record

- Scope: authorized packaging-area observation during the afternoon delivery window
- Direct observation: two carton stacks extended past the locally marked storage boundary
- Limit: one observation period; no conclusion about all shifts or delivery events
- Immediate route: shift supervisor handled the current condition under local policy
- Next owner: operations manager
- Specialist question: none identified for this limited example; any technical design question would go to the named specialist

#### Briefing record

- Audience: packaging workers, shift supervisor, and delivery contact
- Validated by: operations manager and safety manager
- Access: English and Spanish discussion with a read-aloud option
- Discussion: current delivery interface, locally approved staging boundary, changed-condition reporting route, questions, and feedback
- Readiness evidence: participants described where to raise an unresolved condition; one question about delivery timing went to the operations manager

#### Corrective-action and effectiveness record

- Owner: operations manager
- Completion evidence: approved storage location identified and delivery coordination updated
- Completion verifier: shift supervisor
- Effectiveness question: during the next two observed delivery windows, are materials kept within the locally approved area, and do affected workers identify a new access problem?
- Effectiveness evidence: two limited observations plus worker feedback
- Result: effective for the observed periods, with recurrence monitoring retained
- Limitation: no claim about other shifts, sites, or future conditions

### Fictional monthly summary entry

The summary describes one close-call report, one linked earlier observation, confirmed ownership, completed action, two bounded effectiveness observations, and returned worker feedback. It does not treat the absence of injury as proof that risk was controlled, does not calculate a rate from this isolated example, and does not identify the reporter.

### Fictional AI boundary

Maya considers using the employer-approved AI environment to improve the plain-language wording of the bilingual briefing outline. Before doing so, she removes names, dates, the precise site location, and contractor details; uses only a synthetic description; and records the use case. A bilingual human reviewer checks the translated wording, and the operations manager validates the site facts and final message. AI does not classify the hazard, select the control, approve the arrangement, or close the action.

### Why the example remains bounded

The example demonstrates intake, fact separation, privacy, handoff, validated communication, action tracking, effectiveness evidence, worker feedback, and human review. It does not tell a learner how to operate equipment, control energy, enter a confined space, select fall protection, measure exposure, provide medical care, or command an emergency. All authority, system, jurisdiction, specialist, and site fields remain explicitly local.

## Final adaptation and use check

Before adopting a local version, confirm that:

- every local-control field has an authorized owner and current value;
- the applicable jurisdiction and State Plan context have been checked;
- the coordinator's written authority and limits are clear;
- emergency, technical, legal, medical, privacy, retaliation, contractor, and AI routes are named;
- reporting channels are accessible and include an approved fallback;
- handoffs require acceptance and a return path;
- completion and effectiveness are recorded separately;
- worker feedback and confidentiality controls are usable;
- records have approved access, retention, correction, and disposal rules;
- no section has been converted into an equipment-operation, lockout or tagout, confined-space, fall-protection, exposure-monitoring, medical, or emergency-command procedure;
- the accountable employer has approved the adapted document under **[LOCAL — EMPLOYER POLICY: document-control process]**.

If any check is unresolved, keep the model in draft, record the gap, and route it to the accountable local owner.

## Connected role pathway

- [ats resume template](https://mtfinstitute.com/insights/occupational-health-safety-coordination-ats-friendly-resume-template/)
- [model job description](https://mtfinstitute.com/insights/occupational-health-safety-coordinator-model-job-description/)
- [role sop operating playbook](https://mtfinstitute.com/insights/occupational-health-safety-coordinator-role-sop-operating-playbook/)
- [Vacancy evidence](https://mtfinstitute.com/insights/occupational-health-safety-coordinator-100-us-vacancies-2026/)
- [Current-practice analysis](https://mtfinstitute.com/insights/occupational-health-safety-coordination-work-changing-2026/)

**Study the Professional Certificate in Occupational Health and Safety Coordination:** [Open the course and enrol](https://mtfinstitute.com/programs/occupational-health-safety-coordination/#enroll)

Canonical URL: https://mtfinstitute.com/insights/occupational-health-safety-coordinator-role-sop-operating-playbook/