Operations
Part of Community management operations: workflows and review
Community management operating workflow: shift handover
A community management operating workflow built around the handover: what the next owner needs, moderation records and audits of dropped cases.
A shift handover decides whether the next operator continues a case or starts it again. In a community management operating workflow, the handover is the written bridge between owners. It names the urgent work, what the member has been told and who acts next, so nobody has to reconstruct a case from memory.
What to take away
- A handover note carries urgent work, waiting dependencies, member commitments, system issues and decisions due.
- Name the next owner and mark what the member has already been told.
- Record moderation decisions with material, rule, action and decision maker, and offer an appeal route.
- Keep notes leanremove unnecessary personal detail and limit access by role.
- Audit abandoned items to find the routing gap that let them disappear.
What the handover note carries
A handover note lists five things: urgent work, waiting dependencies, member commitments, system issues and decisions due. If one is missing, the next operator either rebuilds it from memory or asks the member to explain again. Record all five at shift or week end.
| Item | What to write | What goes wrong without it |
|---|---|---|
| Urgent work | The case, its category and who has already been contacted | A high-risk case waits unnoticed in another queue |
| Waiting dependencies | What the case is waiting for and who owes it | A waiting case looks abandoned |
| Member commitments | What the member was told would happen next | The member is promised the same thing twice, or never |
| System issues | The fault, any workaround and who is fixing it | Work vanishes after a failed integration |
| Decisions due | The decision, the rule involved and who takes it | Decisions are made by whoever notices first |
The note is only as good as the queue behind it. Keep outstanding work in a shared queue, such as a ticketing board or a monitored shared inbox, rather than in personal inboxes that the incoming operator cannot see.
Start the next shift from the note
The incoming operator reads the note before touching the queue. Check service status, unresolved urgent cases, administrator changes and planned activity, then confirm which specialists are available. Do not begin by clearing the easiest notifications while a high-risk case waits in another queue.
Open the shift checks
- Check service status
- Review unresolved urgent cases
- Read handover notes
- Confirm administrator changes
- Check planned activity
- Confirm specialist availability and limits
Any temporary limit on the service belongs in the note too. If a specialist is away or a queue is paused, the next operator should hear it from the note rather than discover it when a member complains.
Mark the category so the case can be routed
Each open case in the note carries its category, so the next owner routes it without rereading the whole thread. Separate contributions into ordinary participation, support need, expert question, rule concern, technical problem, data request and potential incident.
Classify and route contributions
- Ordinary participation
- Support need
- Expert question
- Rule concern
- Technical problem
- Data request
- Potential incident
For example, a safeguarding report about a private message goes straight to the safeguarding lead, while a question about where to find the code of conduct goes to the routine queue. The category sends the work somewhere. It is never a label for the member.
Record what the member was told
Tell the member what will happen next and write it in the note, because the next operator inherits the promise. Avoid promising an answer time the service has not accepted. If a conversation moves to a private route, explain why and preserve only the information needed there.
Respond or route
Is the contribution within the operator's competence?
Handle welcome, navigation or rule reminder
Route to accountable expert
A welcome, navigation answer or reminder of a published rule may be routine. Product, health, financial, legal or other specialist questions should reach the accountable expert, and the note should say which expert now holds the case.
Moderation records that survive a handover
Assess content against the current participation rule and context, then record the material, report, rule, action, decision maker and communication. Use proportionate action and protect access to sensitive evidence. A decision without those fields cannot be explained after the shift changes.
Moderate with a record
- Record the material
- Record the report
- Record the rule
- Record the action
- Record the decision maker
- Record communication
- Provide appeal or correction route
The difference between a weak entry and a usable one shows in each field.
| Field | Weak entry | Usable entry |
|---|---|---|
| Material | "Bad post" | The post and thread, kept where access is restricted |
| Rule | "Against the rules" | The participation rule that applies, named |
| Action | "Dealt with" | The post hidden and the member told why |
| Decision maker | "The team" | The named operator who decided |
| Communication | "Told them" | What the member was told, and through which route |
Appeals and reversals
Provide the agreed appeal or correction route and put it in the record. A reversal should update the visible outcome and the internal quality record, rather than disappearing as an informal message that the next operator never sees.
How quickly an appeal is answered is a decision for the service, not for one moderator. Agree it through the service standards before promising a member anything, and note in the record which appeals are still waiting.
Audit what never reached the handover
Audit abandoned items as well as completed ones. Work may disappear after a tag change, staff departure or failed integration, and a handover note cannot list what nobody noticed.
Periodically reconcile the queue with reports, expert requests and member follow-up. Then correct the routing rule that allowed the gap. Change categories, rules or staffing through an accountable review, and train affected people before the change goes live.
Escalation contacts and illegal content
The service's safeguarding lead or duty manager owns the escalation contact list and keeps it current, checking it at each handover. Material that may involve imminent harm, safeguarding, illegal content or account compromise needs an immediate contact.
Operators also need authority to preserve relevant evidence without conducting their own legal investigation. For services within the Online Safety Act, Ofcom's current illegal content duties page explains requirements around assessment, safety measures, reporting, complaints and records (checked 15 May 2025). Scope and the appropriate process require service-specific review.
Keep handover notes lean
Shared notes should hold what the next owner needs and no more. Remove unnecessary personal detail and limit access by role. Duplicate requests for information increase effort and can expose more detail than the case needs.
When ownership changes, the new operator should be able to continue without asking the person to retell a difficult experience. The Information Commissioner's Office's accountability framework can help organisations examine governance and records (checked 15 May 2025).
For personal data, apply the UK GDPR and Data Protection Act 2018. Route a subject access request (SAR) to the organisation's data-protection contact and follow its established process rather than resolving it in a public thread. These requirements do not prescribe a community queue, so the team must decide what evidence is necessary and proportionate.
Before you hand over
- Write up the five handover items.
- Give every open case a new owner.
- Mark each case's category and the member's last update.
- Finish any half-written moderation record.
- Flag waiting appeals and reversals not yet recorded.
- Strip personal detail the next owner does not need.
Common questions
What belongs in a handover note?
Five things: urgent work, waiting dependencies, member commitments, system issues and decisions due. Add who takes over and what the member has heard so far.
How should a moderation decision be recorded?
Write down what was moderated, why, what was done, who decided and what the member was told. If an appeal reverses the decision, change the visible outcome and the internal quality record as well.
Why audit abandoned items?
Cases can vanish after a tag change, a departure or a failed integration. Matching the queue against reports, expert requests and member follow-up shows which routing rule let one slip.
