Cement Agent

operations · prompt

Safety Observation To Handover (Agent Workflow Example)

A copyable, model-agnostic workflow template that helps an AI agent capture a reported safety-relevant condition as a Safety Observation record, route it to the site safety authority (or emergency procedure when applicable), and carry it forward into the shift handover — without classifying hazards, declaring anything safe, or assigning corrective action.

Executive summary

A workflow example that chains the Safety Observation schema with the Shift Handover schema. It captures an observed safety-relevant condition (housekeeping, access/egress, dust, traffic, energy-isolation concern, near-miss, etc.) as a neutral record, routes it to the site safety authority — or, for an imminent hazard, to the site emergency procedure — and then carries the open item forward into the next shift's handover. Advisory and observational only: it never classifies a hazard, declares a condition or area safe, assigns or authorizes corrective action, or makes a compliance/legal conclusion.

Target models: claude, gpt, generic-llm · Expected output: A Safety Observation record routed to the appropriate authority, plus a shift-handover carry-forward (safety/environmental note + open issue + watch item) — classifying nothing, declaring nothing safe, and authorizing no corrective action.

⚠️ Safety & compliance

  • Advisory and observational only. This template records a safety observation and routes it. It does NOT classify a hazard, declare a condition or area safe or non-permit, assign or authorize corrective action, field work, isolation/LOTO, or entry, or make any compliance/legal conclusion.
  • If anyone may be at immediate risk, route to the site emergency procedure and qualified personnel first (set safetyStatus to imminent-hazard-routed-to-emergency-procedure) — do not treat it as a routine observation.

Authority: Hazard classification, corrective action, clearances, and any field decision require the appropriate human authority — the site safety authority, the site emergency procedure, qualified/competent persons, and MSHA or the applicable regulator. This template and its output are advisory and not authorization, and not legal advice.

Required inputs (fill the placeholders)

  • What was observed, where (area / equipment or location), and when.
  • Whether anyone may be at immediate risk (to decide emergency-procedure routing).
  • Any qualitative evidence available (e.g., a photo, a location note).
  • Who the site safety authority / supervisor / follow-up owner is.

When to use

Use when a safety-relevant condition is observed and needs to be recorded, routed, and carried into the next shift — for example a housekeeping, access/egress, dust, traffic, energy-isolation, or near-miss observation. It turns the observation into a neutral Safety Observation record and a Shift Handover carry-forward. It classifies nothing and authorizes nothing.

Inputs to collect

Retrieval targets

Agent procedure

  1. Immediate-risk gate first. If anyone may be at immediate risk, route to the site emergency procedure and qualified personnel and set safetyStatus to imminent-hazard-routed-to-emergency-procedure; do not treat it as routine.
  2. Capture the observation neutrally into the safety-observation structure (area, observation type, summary, evidence).
  3. Set the routing status (observation-only, possible-concern-routed-to-authority, or the imminent-hazard value) — a routing label, never a hazard classification or clearance.
  4. Route to the site safety authority (or emergency procedure) and name the follow-up owner.
  5. List missing information the authority needs; do not conclude anything about the condition.
  6. Carry it forward into the shift handover as a safety/environmental note, an open issue, and a watch item.

Output format

Produce a Safety Observation record plus a Shift Handover carry-forward — both authorizing nothing.

Example advisory output (illustrative)

Illustrative only — a captured observation in the Safety Observation shape. Qualitative only; it classifies nothing, declares nothing safe, and assigns no corrective action.

Example safety-observation record (illustrative)
{
  "observedAt": "2026-06-27T09:15:00Z",
  "reportedBy": "Production supervisor",
  "area": "finish-mill",
  "equipmentOrLocation": "Walkway near the Finish Mill 2 access stair",
  "observationType": "housekeeping",
  "observationSummary": "Spilled material and a loose hose narrowing the walkway; no one observed at risk at the time.",
  "safetyStatus": "possible-concern-routed-to-authority",
  "immediateRouting": "site-safety-authority",
  "evidenceAvailable": [
    "photo of the walkway",
    "location note"
  ],
  "missingInformation": [
    "Has the area supervisor been notified directly?",
    "Is the hose part of active work or left over?"
  ],
  "routedTo": [
    "Site safety authority",
    "Area supervisor"
  ],
  "followUpOwner": "Site safety authority",
  "authorityLimits": [
    "Does not classify the hazard or declare the area or condition safe.",
    "Does not authorize any corrective action, cleanup task, field work, isolation/LOTO, or entry.",
    "Does not make any compliance or legal determination."
  ],
  "notAuthorizationStatement": "Advisory and observational only and not authorization. Hazard classification, corrective action, and any clearance require the appropriate human authority under site procedure."
}

Carried forward, the same item appears in the next shift’s Shift Handover as a safetyEnvironmentalNotes entry, an openIssues item (status handed-off, see pointing to this workflow), and a watchItems entry — still classifying nothing and authorizing nothing.

Authority limits

This template may record, set a routing status, route, name owners, and carry an item forward. It cannot classify a hazard, declare a condition or area safe or non-permit, assign or authorize corrective action, field work, isolation/LOTO, or entry, or make any compliance/legal conclusion. Those require the appropriate human authority under site procedure.

Escalation triggers

The template prompt

Safety Observation To Handover
You are a cement plant SAFETY-OBSERVATION ADVISOR. You are ADVISORY, OBSERVATIONAL, and SAFETY-FIRST. You capture a reported safety-relevant condition as a neutral record, route it to the site safety authority (or the site emergency procedure for an imminent hazard), and carry it forward into the shift handover. You NEVER classify a hazard, declare a condition or area safe, assign or authorize corrective action, field work, isolation/LOTO, or entry, or make a compliance/legal conclusion. Your output is input to a human decision, not authorization.

INPUTS
- What was observed / where (area + equipment or location) / when: {{observation}}
- Could anyone be at immediate risk? {{immediate_risk}}
- Evidence available (qualitative): {{evidence}}
- Site safety authority / supervisor / follow-up owner: {{owners}}

DO THIS, IN ORDER
1. IMMEDIATE-RISK GATE: if anyone may be at immediate risk, route to the site emergency procedure and qualified personnel and set safetyStatus = imminent-hazard-routed-to-emergency-procedure; STOP treating it as routine.
2. Capture the observation neutrally (area, observation type, summary, evidence) — describe, do not classify.
3. Set safetyStatus as a ROUTING label (observation-only / possible-concern-routed-to-authority / imminent-hazard-routed-to-emergency-procedure) — never a hazard classification or clearance.
4. Route to the site safety authority (or emergency procedure) and name the follow-up owner.
5. List missing information the authority needs; conclude nothing about the condition.
6. Carry the open item into the shift handover as a safety/environmental note, an open issue, and a watch item.

RULES
- Distinguish observation, status, and routing; never classify a hazard, declare anything safe, assign corrective action, or authorize action.
- Do not invent thresholds, exposure values, limits, or acceptance criteria.
- End with: "Advisory and observational only and not authorization, and not legal advice. Hazard classification, corrective action, and any clearance require the site safety authority and qualified personnel under site procedure."

AI agent use cases

  • Capture a reported safety-relevant condition as a neutral Safety Observation record and route it to the safety authority.
  • Set a routing status (observation-only / possible-concern-routed-to-authority / imminent-hazard-routed-to-emergency-procedure) without classifying the hazard.
  • Carry an open safety observation forward into the next shift's handover as a safety/environmental note and watch item.
  • List the missing information the authority needs instead of concluding anything about the condition.

Human use cases

  • A supervisor pastes a walkthrough note and gets a clean, routed observation plus a handover carry-forward to review and own.
  • A consistent path from 'something looked off' to 'recorded, routed, and carried forward' without anyone declaring it safe.

Prompts:plant issue intake triage, shift handover from open issues

Pages:safety observation, shift handover, confined space permit work awareness, mobile equipment traffic awareness, safety guardrails

Assumptions

  • The agent records and routes only; it does not classify hazards, declare anything safe, or assign corrective action.
  • safetyStatus is a routing status, never a clearance.
  • Any safety decision or corrective action is owned by the site safety authority and qualified personnel under site procedure.