Skip to content

Shift Handover Log

Instructions: Complete all mandatory sections (★) before briefing the incoming shift. Save this log in the ticketing system or shared drive after both leads sign off.


Header Information

Field Value
Date YYYY-MM-DD
Shift ☐ Morning (08:00–16:00) · ☐ Afternoon (16:00–00:00) · ☐ Night (00:00–08:00)
Outgoing Lead [Name]
Incoming Lead [Name]
Handoff Time HH:MM

★ 1. Shift Summary

Overall Status: ☐ Quiet · ☐ Normal · ☐ Busy · ☐ Critical

Narrative Summary:

Provide a 2–3 sentence overview of the shift. Highlight any escalations, notable events, or management directives received.


★ 2. Active Incidents (Requiring Attention)

ID Severity Category Description Current Status Owner Next Action ETA
#___ Critical/High/Med/Low Phishing/Malware/etc Brief description Triage/Investigation/Containment/etc [Name] What needs to happen next When

Total Active: _ | Critical/High: _ | Awaiting Escalation: ____


★ 3. System Health

System Status Notes
SIEM Ingestion ☐ Normal · ☐ Degraded · ☐ Down
EDR Connectivity ☐ Normal · ☐ Degraded · ☐ Down
SOAR Playbooks ☐ Normal · ☐ Degraded · ☐ Down
TI Feed Updates ☐ Normal · ☐ Delayed · ☐ Down
Ticketing System ☐ Normal · ☐ Degraded · ☐ Down
Network Sensors ☐ Normal · ☐ Degraded · ☐ Down
Email Gateway ☐ Normal · ☐ Degraded · ☐ Down

Known Issues:

Describe any ongoing system degradation, scheduled maintenance, or license expirations.


★ 4. Pending Tasks / Follow-ups

# Task Related Ticket Priority Assigned To Due
1 High/Med/Low
2
3

★ 5. Intelligence & Advisories

New Threat Intelligence

Source Summary IoCs Added? Action Required?
☐ Yes · ☐ No ☐ Yes · ☐ No

Vulnerability Advisories

CVE Affected Systems Severity Patch Available? Action
☐ Yes · ☐ No

6. Escalations (if applicable)

Escalated To Reason Time Response Received? Status
☐ Yes · ☐ No

7. Change Advisories (if applicable)

Change ID System Description Window Impact on Alerts?
☐ Yes · ☐ No

8. Compliance Deadlines (if applicable)

Deadline Regulation Description Days Remaining Owner
PDPA / ISO 27001 / etc

★ Shift Statistics

Metric Count
Alerts Processed
Incidents Opened
Incidents Closed
Escalations Made
False Positives Identified
Average Response Time (MTTA) min

★ Sign-off

Outgoing Lead Incoming Lead
Name
Signature
Time

⚠️ Both leads must sign off to confirm that the briefing was conducted and all mandatory sections were reviewed.


Completed Handover Example

## Shift Handover — 2026-02-16 (Day → Night)

### Outgoing Analyst: John D. (Shift A)
### Incoming Analyst: Sarah T. (Shift B)

### Open Incidents
| Ticket ID | Severity | Status | Summary | Action Needed |
|:---|:---:|:---|:---|:---|
| INC-2026-089 | P2 | Investigating | Suspicious PowerShell on HR-PC-042 | Waiting EDR isolation approval |
| INC-2026-091 | P3 | Monitoring | Failed VPN logins from unknown IP | 12 more hours monitoring |

### Alert Queue Status
- Current queue: 14 alerts (7 low, 5 medium, 2 high)
- 2 high alerts need immediate triage

### System Health
- SIEM: ✅ Normal | EDR: ✅ Normal | Ticketing: ✅ Normal
- Log source gap: Firewall FL-02 offline since 14:30 (IT notified)

### Notes for Incoming
1. IMPORTANT: INC-089 — SOC Manager approved isolation, proceed when evidence captured
2. New Sigma rule deployed for CVE-2026-1234, may generate initial FPs
3. Scheduled maintenance for SIEM at 03:00, expect 15-min search delay

Common Handover Mistakes

❌ Mistake Impact ✅ Best Practice
Verbal-only handover Details forgotten, context lost Always write in template + brief verbally
Not mentioning system issues Incoming analyst misses data gaps Always check and report log source health
Incomplete incident summary Time wasted re-investigating Include: what happened, what's done, what's needed
Forgetting pending approvals Containment delayed List ALL pending approvals/waiting items
No alert queue status Queue overflows Always report queue depth and priority counts

References