Quick Reference

Escalation may be required when an issue has significant customer, operational, safety, reputational or management relevance.

• More than one customer reporting the same problem
• Any indication of safety or security relevance
• Situations where another team must act to resolve it

Check approved internal guidance before taking action.

Confirm the queues in scope, the active issues carried over, and the monitoring priorities for the shift.

• Latest handover entry
• Active issues still open
• Any operational updates issued since your last shift

Sample guidance only — replace with approved internal instructions.

Look for repetition in wording, timing or route across a period rather than judging a single post.

• Two or more similar reports within a short window
• Same theme appearing across shifts
• Volume rising against a normal baseline

Facts, timings, references, what is being requested and by when. Keep it short and structured.

• One-line summary first
• Evidence links rather than long pasted text
• Named requested action

Use the approved internal escalation template where one exists.

Separate what is described from what is requested, then gather the confirmed detail before forming any view.

• Confirm references and dates
• Identify the systems holding the records
• Check which guidance applies

Priority, issue, current status, action required, owner and next update — in the same structure every time.

• Order by priority, not chronology
• Every open item needs an owner
• Write actions as instructions

Log the theme, first observed time, approximate volume and any action taken, then keep it visible across shifts.

• Use a consistent category
• Note whether it has been shared with partner teams
• Update rather than duplicate entries

Placeholder format — align with approved internal reporting standards.

In this prototype, handover entries are shown on the Team Knowledge page. Operationally this would point to the approved internal location.

Internal Knowledge Article — Handover Location (placeholder)

Start with your shift lead. For system access, use the placeholder systems contact; for case guidance, use the placeholder case owner contact.

• Team Contact — Shift Lead (placeholder)
• Team Contact — Systems Support (placeholder)
• Team Contact — Assistant Manager (placeholder)

SOPs sit in the internal document library. This prototype shows them as Internal SOP Link placeholders.

Replace all placeholders with approved internal links before use.