Turn monitoring events into an on-call handover
Compile a complete alert history for a defined shift and distinguish repeated triggers from currently active problems. Add the outgoing engineer’s notes for the next person.
How this works
Compile a complete alert history for a defined shift and distinguish repeated triggers from currently active problems. Add the outgoing engineer’s notes for the next person.
A shift handover must account for the complete event window without confusing trigger count with incident count. Current monitor state and the outgoing engineer’s explanation are separate evidence, especially when an alert recovered and then fired again.
Before you start
Defined operating scope
Service ownership changes between shifts while some alerts remain unresolved.
Required source material
Obtain Shift dates and environment scope; Triggered events, current status, and engineer notes. If connectors are unavailable, use authorized files with the same fields.
Decision and exception rules
A recovery event is followed by a new trigger. List the monitor as currently active and retain both transitions.
Prepare the inputs
- shift_window
- Required
Start, end and timezone
Use half-open boundaries to avoid counting events in two shifts.
- environment_scope
- Required
Services and environments
Exclude unrelated staging events unless requested.
- events
- Required
Paginated trigger and recovery records
Track pagination completion and stable event IDs.
- engineer_notes
- Required
Incident causes, actions and open work
Attribute explanations to the engineer who supplied them.
Implementation, step by step
Establish the working record
- Confirm the selected records, effective versions and responsible owner.
- Check shift_window, environment_scope, events, engineer_notes before beginning. Record the source version and the selected scope; an unavailable value stays unknown rather than becoming an inferred fact.
Checkpoint: The input record identifies the selected shift_window and any missing required fields.
Confirm the reporting period and check for an existing handover page
- Confirm the shift window and locate the existing handover by a stable period key to avoid duplicate pages.
- Reconcile distinct event counts and verify the final retrieved page.
Checkpoint: A saved intermediate result for: Confirm the reporting period and check for an existing handover page.
Retrieve all event pages and group triggers by monitor
- Retrieve every event page, deduplicate event IDs and group triggers by monitor while retaining chronological transitions.
- Compare active-issue list with current monitor state, not only the last recovery in the window.
Checkpoint: A saved intermediate result for: Retrieve all event pages and group triggers by monitor.
List current alerts separately from historical events
- Read current monitor state separately from historical recoveries; list active problems and recent recovered events in different sections.
- Reconcile distinct event counts and verify the final retrieved page.
Checkpoint: A saved intermediate result for: List current alerts separately from historical events.
Add engineer notes and save an updated handover without duplicating the period
- Add the engineer’s cause and action notes, mark unknown explanations and update the existing handover revision when rerun.
- Compare active-issue list with current monitor state, not only the last recovery in the window.
Checkpoint: A saved intermediate result for: Add engineer notes and save an updated handover without duplicating the period.
Package the result and unresolved work
- The outgoing engineer supplies causes and resolutions; the assistant must not infer them from recovery events alone.
- Do not infer fixes or causes from an alert’s recovery alone.
Checkpoint: A shift handover with alert counts, event references, and unresolved follow-ups. Unresolved items remain visible in the review record.
Decisions along the way
A recovery event is followed by a new trigger.
List the monitor as currently active and retain both transitions.
Event pagination is incomplete.
Label counts partial and finish retrieval before presenting totals as complete.
No engineer explanation is available.
State cause unknown rather than deriving a cause from the recovery timestamp.
What you will produce
prepare-on-call-handover-result.json
JSONA shift handover with alert counts, event references, and unresolved follow-ups. Label proposed and completed states separately.
Include: shift_key · monitor_id · trigger_count · current_state · event_references · engineer_notes · open_followups · status · evidence_reference · review_note
prepare-on-call-handover-review.md
MarkdownKeep the evidence and unresolved decisions needed to apply this result, including exceptions involving engineer_notes.
Include: source_reference · question · owner · next_action
Check the result
- Reconcile distinct event counts and verify the final retrieved page.
- Compare active-issue list with current monitor state, not only the last recovery in the window.
- Inspect shift_window and environment_scope in both the original and output; confirm that record identity and interpretation survived the transformation.
- The outgoing engineer supplies causes and resolutions; the assistant must not infer them from recovery events alone.
When something goes wrong
A recovery event is followed by a new trigger.
List the monitor as currently active and retain both transitions. Retain the affected evidence and recovery status.
Event pagination is incomplete.
Label counts partial and finish retrieval before presenting totals as complete. Retain the affected evidence and recovery status.
No engineer explanation is available.
State cause unknown rather than deriving a cause from the recovery timestamp. Retain the affected evidence and recovery status.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Turn monitoring events into an on-call handover for the following bounded example; prepare the result for review.
Inputs
Synthetic example: Shift 08:00–16:00 UTC has monitor M-2 trigger at 10:00, recovery at 10:20 and trigger at 15:50. Engineer notes only cover the first incident.
Expected result
Synthetic expected result: Report two triggers, current state active, first episode resolved per engineer note, latest cause unknown. Keep 15:50 follow-up visible for the incoming shift.
Run a small pilot
Start small
Trial a representative batch containing the ordinary case and the exception demonstrated above.
Record the baseline
Record current preparation time, review effort and correction types for the same records.
Agree success criteria
Agree acceptable review and error limits; measure handover preparation time; active incidents or context omitted in review.
Stop or revise
No engineer explanation is available. Pause affected records and apply this recovery: State cause unknown rather than deriving a cause from the recovery timestamp.
Keep the scope clear
- Do not infer fixes or causes from an alert’s recovery alone.
- Updating the handover does not authorize production intervention or notifying unrelated teams.
Check before using
The outgoing engineer supplies causes and resolutions; the assistant must not infer them from recovery events alone.
Business activities
- Coordinate meetings and follow-ups
- Keep digital services running
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Shift dates and environment scope · Triggered events, current status, and engineer notes
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow