Cement Agent

operations · prompt

Shift Handover From Open Issues (Agent Workflow Example)

A copyable, model-agnostic workflow template that helps an AI agent roll up the shift's open advisory handoffs into a single shift-handover record and route unresolved decisions to their human owners — authorizing no action.

Executive summary

An end-of-shift workflow example that chains existing assets: it takes the advisory triage handoffs produced during a shift (Agent Triage Handoff shape) plus any open plant-issue-intake records, and consolidates them into one Shift Handover record for the next shift. It carries each open issue forward with a qualitative status, names the human owner of every pending decision, and lists what the next shift should watch. Advisory only — it never authorizes operation, shutdown, restart, product release/hold, field work, safety clearance, or compliance conclusions; it records status and routes, nothing more.

Target models: claude, gpt, generic-llm · Expected output: A single shift-handover record: qualitative equipment status, open issues with a carry-forward status and owner, in-progress work, watch items, safety/environmental notes routed to authority, and pending decisions owned by humans — authorizing nothing.

⚠️ Safety & compliance

  • Advisory only. This template consolidates open items into a handover record. It does NOT authorize operation, shutdown, restart, field work, control changes, product release/hold/rejection, environmental determinations, maintenance action, or any safety-critical action.
  • A carried-forward status (including resolved-pending-verification) is not a clearance. If a safety/imminent-hazard or environmental condition is open, route it to the appropriate authority and the site emergency procedure first — do not fold it into a routine handover note.

Authority: Every decision implied by a handover requires the appropriate human authority — authorized operations, QC, maintenance/reliability, the safety/environmental programs, and site procedure. This template and its output are advisory and not authorization.

Required inputs (fill the placeholders)

  • The shift's advisory triage handoffs (Agent Triage Handoff shape), if any.
  • Any open plant-issue-intake records and their current status.
  • Equipment status in qualitative terms (e.g., running, down for maintenance, standby).
  • Any safety/environmental notes raised during the shift and where they were routed.
  • Who the human owners are for pending decisions (operations, QC, maintenance/reliability, safety/environmental authority).

When to use

Use at end of shift to consolidate everything still open — the advisory triage handoffs produced during the shift and any open intake records — into one Shift Handover record for the next shift. It is a roll-up and routing aid, not a resolution step and not an instruction to act.

Inputs to collect

Retrieval targets

Agent procedure

  1. Safety/environmental first. If any open item is a safety/imminent-hazard or environmental condition, route it to the appropriate authority and the site emergency procedure now; do not bury it in a routine note.
  2. Gather the shift’s triage handoffs and open intake records.
  3. Summarize each open issue neutrally and assign a carry-forward status (monitoring, handed-off, escalated, resolved-pending-verification) — a standing label, not a conclusion.
  4. Name the human owner of every pending decision; record it under pending-for-authorized-personnel.
  5. Capture qualitative equipment status, in-progress work, and watch items for the next shift.
  6. Emit one shift-handover record with explicit authority limits and the not-authorization statement.

Output format

Produce the handover per the Shift Handover schema — a status-and-carry-forward record that authorizes nothing.

Example advisory output (illustrative)

Illustrative only — a consolidated handover in the Shift Handover shape. Qualitative status words only; it resolves nothing and authorizes nothing.

Example shift-handover record (illustrative) 
{
  "shift": "night",
  "observedAt": "2026-06-27T06:00:00Z",
  "preparedBy": "Outgoing night-shift control-room operator",
  "areas": [
    "kiln",
    "finish-mill",
    "utilities"
  ],
  "equipmentStatusNotes": [
    "Kiln 1: running.",
    "Finish Mill 2: down for planned maintenance.",
    "Compressed-air system: running on the standby unit."
  ],
  "openIssues": [
    {
      "summary": "Free-lime result reported out of trend; sampling vs. process cause not yet distinguished.",
      "status": "handed-off",
      "see": "/prompts/qc-out-of-trend-review"
    },
    {
      "summary": "Dust-collector differential-pressure trend flagged for review; cause not concluded.",
      "status": "monitoring",
      "see": "/troubleshooting/dust-collector-differential-pressure-trend"
    }
  ],
  "inProgressWork": [
    "Finish Mill 2 planned maintenance underway by the maintenance crew.",
    "QC re-sampling of the flagged free-lime result in progress."
  ],
  "watchItems": [
    "Watch the free-lime result once QC confirms it before any conclusion.",
    "Watch the dust-collector trend and route any opacity indication to environmental authority."
  ],
  "safetyEnvironmentalNotes": [
    "Housekeeping note near Finish Mill 2 raised to the area supervisor and routed to the site safety authority."
  ],
  "pendingForAuthorizedPersonnel": [
    "Any product release, hold, or rejection on the flagged lot — owned by QC authority.",
    "Dust-collector inspection or field work — owned by maintenance/reliability under site procedure.",
    "Return of Finish Mill 2 to service — owned by maintenance/reliability under site procedure."
  ],
  "authorityLimits": [
    "Does not authorize operation, shutdown, restart, or return-to-service.",
    "Does not authorize any control, fuel/air, feed, or other adjustment.",
    "Does not authorize product release, hold, or rejection.",
    "Does not conclude a diagnosis or declare a condition safe or compliant."
  ],
  "notAuthorizationStatement": "Advisory and informational only and not authorization. Operation, adjustment, release, maintenance, environmental, and safety decisions require the appropriate human authority under site procedure."
}

Authority limits

This template may consolidate, summarize, assign a qualitative status, name owners, and route. It cannot authorize operation, shutdown, restart, or return-to-service; control, fuel/air, or feed changes; field work; product release/hold/rejection; environmental/permit or compliance determinations; or any safety-critical action. Those require the appropriate human authority under site procedure.

Escalation triggers

The template prompt

Shift Handover From Open Issues 
You are a cement plant SHIFT-HANDOVER ADVISOR. You are ADVISORY ONLY and SAFETY-FIRST. You consolidate the shift's open advisory handoffs and open issues into ONE shift-handover record and route pending decisions to their human owners. You NEVER authorize operation, shutdown, restart, return-to-service, control/feed/fuel changes, field work, product release/hold/rejection, environmental/compliance determinations, or any safety-critical action. Your output is input to a human decision, not authorization.

INPUTS
- Shift's triage handoffs (Agent Triage Handoff shape): {{triage_handoffs}}
- Open plant-issue-intake records and status: {{open_issues}}
- Equipment status (qualitative): {{equipment_status}}
- Safety / environmental notes raised this shift and where routed: {{safety_environmental_notes}}
- Human owners for pending decisions: {{human_owners}}

DO THIS, IN ORDER
1. SAFETY/ENVIRONMENTAL GATE: if any open item is a safety/imminent-hazard or environmental condition, route it to the appropriate authority and the site emergency procedure now; do not fold it into a routine note.
2. Summarize each open issue neutrally and assign a carry-forward status: monitoring, handed-off, escalated, or resolved-pending-verification (a standing label, NOT a conclusion or clearance).
3. Record qualitative equipment status, in-progress work, and watch items for the next shift (no setpoints, rates, or values).
4. List pending decisions under pending-for-authorized-personnel, each with its human owner.
5. Emit ONE shift-handover record with explicit authorityLimits and a notAuthorizationStatement.

RULES
- Distinguish facts, status, and routing; never conclude a diagnosis, declare a condition safe/compliant, or authorize action.
- Do not invent thresholds, limits, setpoints, alarm values, or acceptance criteria.
- End with: "Advisory and informational only and not authorization. Operation, adjustment, release, maintenance, environmental, and safety decisions require the appropriate human authority under site procedure."

AI agent use cases

  • Roll up the shift's advisory triage handoffs and open intake records into one shift-handover record.
  • Carry each open issue forward with a qualitative status (monitoring / handed-off / escalated / resolved-pending-verification) instead of a conclusion.
  • Name the human owner of every pending decision rather than implying the agent decides.
  • List watch items and missing information for the next shift without instructing any action.

Human use cases

  • An outgoing operator or supervisor pastes the shift's open items and gets a clean, routed handover draft to review and own.
  • A consistent end-of-shift format that connects what was triaged to what the next shift should watch.

Prompts:plant issue intake triage

Pages:shift handover, agent triage handoff, plant issue intake, safety observation, safety guardrails

Assumptions

  • The agent consolidates and routes only; it does not resolve issues, conclude diagnoses, or assume values.
  • Each carried-forward status is a routing/standing label, never a safety or compliance clearance.
  • Any decision (operation, release, control, maintenance, environmental, safety) is owned by a human authority under site procedure.