"It was in the group chat"
Night shift handoffs fail when state lives in heads, photos, or threads nobody searches. Day shift repeats work, customers wait, and safety and quality risks rise. "It was in the group chat" is not continuity — it is one person holds the truth, just spread across forty messages.
WhatsApp and similar tools are fine for human coordination. They are terrible as a system of record: no required fields, no ageing, no audit trail, and a search function that punishes you. The next shift needs a named queue, a status, and an owner — not a photo of a whiteboard taken at 06:00.
Minimum viable handoff
One queue visible to both shifts — tickets, jobs, or ops tasks in the tool you already pay for. Required fields at close-out: status, blocker, next action, customer impact if any. Read receipt in the tool — assigned and seen — not a thumbs-up in chat. Escalation when items age past threshold — owner named, not "someone should have noticed."
If the queue is empty but work clearly continued, your handoff is still broken. People are routing around it. Ask why before you add more fields.
Kill the parallel story
Agree that chat is for ping and the tool is for truth. The shift lead closes or hands off each open item before leaving — five minutes of discipline beats thirty minutes of re-discovery. For urgent verbal flags, still log a one-line task so day shift has something to work from.
This connects to the handover plan for key-person risk, to email is not a workflow when day shift inherits threads instead of tasks, and to naming owners for alerts when ageing items should page someone.
Go-live and training
New shifts fail handoffs in week two if training was a slide — the training that survives go-live guidance explains why. Coach on real close-out under time pressure. Measure items handed off with complete fields — not attendance at a training session.
Safety and quality need the same queue
Handoff gaps are not only customer delay — they are quality and safety risks when the next shift repeats work or misses a hold tag. Treat incomplete handoffs as incidents with a review, not as shift banter. Required fields should include hold reasons and customer commitments made on the previous shift.
For 24/7 ops, read-only dashboards on a wall or tablet beat chat scrollback — open items, age, owner. Keep it boring and visible. Fancy BI can wait until one report the room trusts exists.
Shift overlap — fifteen minutes paid, not optional — is cheaper than duplicated work. Use it to update the queue together, not to retell stories that chat already mangled.
Audit WhatsApp groups quarterly. If work state only exists there, you are one phone loss away from a continuity failure. Migrate facts to the queue and keep chat for "can you cover" and "machine down."
Management must not reward chat heroics. If the fastest responder in WhatsApp is also the person who skips the queue, you are reinforcing the wrong habit. Praise complete handoffs, not fastest thumbs. Consistency from supervisors matters more than another tool.
Book a review — Teesside and the North East when the line needs walking.