QC Shift Handover

Intended users: qc-lab, cement-chemist, process-engineer, finish-mill, ai-agent · Last updated: 2026-06-25

Why QC handover matters

A QC result is only as useful as the context that travels with it. At shift change, that context is easy to drop — and the next shift (or an AI agent continuing the thread) can end up re-starting blind, missing a pending verification, or acting on a value without its history. Good handover transfers status and context, not just numbers, and clearly marks what is still pending versus decided.

This page structures what to communicate; it does not define your plant’s handover frequency, format, or required fields — use your plant’s handover procedure.

What a good QC handover carries

• Unresolved / abnormal results — what’s open, its current status, and what’s been ruled out so far.
• Pending and repeated samples — awaiting test, or in verification/retest, so they aren’t lost or double-handled.
• Instrument / calibration / status notes — anything out of service, drifting, or recently recalibrated.
• Retained samples — what is held and why (e.g., for possible re-test).
• Parameter context — recent history for XRF, XRD, free lime, Blaine, LOI, SO₃, and strength (not just the latest value; see QC Control Charts & SPC Thinking).
• Process events relevant to lab interpretation — material/fuel/feed/mill changes or upsets that frame the numbers (see Kiln Upset).
• Open communications — threads with process, production, safety/environmental, or supervisors.
• Items awaiting an authorized decision — carried as pending, never recorded as decided.

What an AI agent needs to continue safely

To pick up a QC thread without losing the plot, an agent needs: the open/abnormal items and their status, pending/repeat samples, instrument status, retained-sample availability, recent parameter history, and the relevant process events — plus a clear marker of what is pending a human decision. With those, it can summarize and structure; without them, it should ask rather than assume.

Interpretation map

Advisory patterns (each prompts a handover action, not a conclusion):

• Open abnormal result at shift end — hand over with status, what’s been checked, and the next step (verify/escalate).
• Sample pending or in retest — hand over so it’s completed and not duplicated.
• Instrument drift/out-of-service — hand over so results during the window are interpreted with that caveat.
• Process event mid-shift — hand over so the next shift time-aligns results to it.
• Item awaiting decision — hand over as pending and route to the authorized role.

Common mistakes

• Handing over values without context (age, method, trend, sample identity).
• Omitting repeat/pending samples.
• Omitting instrument or method concerns.
• Omitting process context relevant to interpretation.
• Letting AI sound like a decision-maker in the handover.
• Treating handover as authorization — it transfers context, not decisions.

AI-agent workflow

You are a cement QC/lab ADVISOR helping assemble or continue a SHIFT HANDOVER. You are advisory only: you organize context and status for humans. You NEVER authorize feeder, kiln/mill setpoint, separator, grinding-aid, fuel/air, burner, formulation, or production changes; product shipping/spec-release or acceptance/rejection; environmental decisions; safety-critical or field action; or LOTO bypass. You make no legal/compliance conclusions and no decisions. Pending items stay pending and are routed to authorized roles. Your output is context for humans, not authorization.

STEP 1 — GATHER HANDOVER CONTEXT (do not invent): shift/date/personnel; unresolved/abnormal results and status; pending and repeat/verification samples; instrument/calibration/status notes; retained samples and why; recent context for key parameters (XRF, XRD, free lime, Blaine, LOI, SO3, strength) including age/method/trend; process events relevant to interpretation; open communications; items awaiting an authorized decision; plant handover procedure reference if relevant.

STEP 2 — STRUCTURE THE HANDOVER: open items (with status), pending/repeat samples, instrument status, retained samples, parameter context, process events, and a clearly separated "pending decision (route to authorized role)" section.

STEP 3 — FLAG MISSING CONTEXT: list what the next shift/agent still needs (especially sample identity, method, trend) and ask for it rather than assuming.

STEP 4 — CONNECT open items to the relevant review pages (QC workflow, sampling & prep, control charts/SPC, free lime, Blaine & fineness, strength, Kiln Upset).

STEP 5 — KEEP DECISIONS OUT: mark anything awaiting acceptance/release/process action as pending and route it; do not present it as decided.

RULES: distinguish facts, assumptions, and pending items; never record a decision; end with: "Advisory handover only and not authorization. Pending decisions are routed to authorized QC/operations under plant procedure; the next shift verifies suspect data."

Escalation guidance

Advisory pointers (use your plant’s handover and escalation procedure for specifics — not provided here):

• Lab lead / supervisor — unresolved abnormal results, instrument problems, or anything the incoming shift cannot interpret with confidence.
• Process / production — open items where lab context needs the process side (or vice versa) for the relevant window.
• Safety / environmental — any open item touching a safety hazard or emissions/permit matter; route to that authority.
• Carry pending decisions forward — items awaiting acceptance/release/process action are handed over as pending and routed to the authorized role, never closed at handover.
• Repeat / verify — pending or suspect samples are completed and confirmed by the incoming shift before conclusions.