Philippines staffing guide · Published
Set a shift-change handover note for a delegated queue
A handover note is not a status report. Put open decisions first, record the state of each queue, and separate facts from guesses so the next owner can act.
The short answer
Treat the handover note as a working instrument. Lead with open decisions, give each queue a clear state, label guesses, and keep the note short enough to read at the start of a shift. Then fix the repeat blockers instead of rewriting the note forever.
A shift note is not a status report
A status report explains what the team did during the shift. A handover note explains what the next owner must know to continue safely. Those are different documents, and confusing them leaves the next person with a list of completed items and no idea where the work stands.
The note should open with open decisions, blocked items, and anything that changed after the written guide was last updated. A good note assumes the reader is competent but has no memory of the day.
Write the note for a reader who was not present and may not share the same context. Use the queue name, the record identifiers, and the exact state of each open item. Avoid summaries such as all good or mostly done, because they cannot be checked by the next person.
A useful note lets the next owner continue without calling the previous owner at home. It should also make clear which items are safe to leave until the next shift.
Put open decisions first
Start with the items that need a decision from someone with authority. Include the record, the question, the deadline, and the person who owns the answer. If no decision is pending, say that plainly instead of leaving the section blank.
The next owner should be able to scan the first five lines and know whether anything is waiting on the client side. Put the oldest item at the top even when a newer item feels more urgent.
Separate new decisions from old ones that are still open. An item that has waited three shifts is a different problem from an item raised an hour ago. Give each open decision the date it was raised and the last action taken.
That small habit exposes a stalled approval before the customer notices the delay. It also gives the manager a factual basis for asking why the wait is growing.
Record the state of each queue
For each queue, record the volume completed, the volume still open, and the oldest open item. Add the reason the oldest item is open if the reason is known. This gives the next owner a quick picture of pressure without reading a dashboard.
It also creates a daily record that a manager can review when a deadline slips. Keep the counts in the same order every day so a change is easy to see.
Do not paste raw system exports into the note. A long table pushes the decisions off the screen and hides the few items that need attention. Link to the report and summarize the exceptions by code.
The next owner can open the report if they need the detail, but the note should stand on its own. If a number needs a long explanation, the explanation belongs in the queue review, not the handover.
Separate facts from guesses
Write what happened, what was checked, and what remains unknown in separate short blocks. A guess belongs in the note only when it is labeled as a guess and paired with the check that would confirm it. This prevents the next owner from treating a suspicion as evidence.
It also protects the coordinator who flagged the risk early. A labeled guess is useful; an unlabeled one travels as fact.
Use the same vocabulary the queue uses in its trigger codes and status fields. Consistency matters more than elegant prose, because the next owner may be reading the note at the start of a night shift. If a term is ambiguous, add one line to the glossary rather than inventing a new phrase.
The note should reduce interpretation, not create it. Share the glossary with every new coordinator during onboarding.
Keep the note short and searchable
Aim for one screen of text plus links to the underlying records. Use headings that repeat every shift so the reader knows where to look. Put the date and shift in the title, and name the author so follow-up questions have a destination.
A searchable archive of these notes becomes a useful record of how the queue actually behaves. It also shows whether the same blocker returns after a process change.
Do not copy the full case history into the handover. The history lives in the case record, and duplicating it creates two versions that will disagree. Link to the record and state only the current position and the next action.
If the case record is too thin to support that, fix the record instead of compensating in the note. The handover should point to evidence, not replace it.
Close the loop at the start of the next shift
The incoming owner should acknowledge the note and confirm which items they are taking. This takes less than a minute and prevents two people from working the same case. If an item is unclear, the incoming owner should ask before changing its state.
A handover is complete only when the next person can act on it. An acknowledgment without action is just another message.
At the end of the week, review the notes for repeated blockers. A blocker that appears in three shifts is a process problem, not a handover problem. Fix the source, then shorten the note because fewer exceptions need explanation.
The goal is not a perfect note but a queue that needs less explanation over time. Measure that by the length of the note and the number of follow-up questions.
Questions to copy for the sales call
- "Which open items need a decision before the next shift starts?"
- "What is the oldest open item, and why is it still open?"
- "Which statement in this note is a guess rather than a checked fact?"
- "What did we repeat in three notes this week that should be fixed upstream?"
Sources
- SBA: Hire and manage employees: Guidance on setting expectations and management routines for a role.
- NIST Cybersecurity Framework 2.0: Useful for separating detection, response, and recovery duties in a handoff.
- GAO: Assessing Data Reliability: A practical reference for distinguishing verified facts from assumptions.
Common questions
How long should a handover note be?
One screen plus links is a practical target. If it runs longer, the open decisions are probably buried or the case record is missing information.
Should the note be written at the end of every shift?
Write it whenever ownership changes. If the queue runs continuously, that means every shift change rather than only at the end of the day.
Who reads the note besides the next owner?
The queue manager and the provider supervisor should have access. Keep the audience small enough that sensitive case details are not spread across the company.