TL;DR:
A handoff note answers three questions for every open ticket: what is the status, what is the next step, and who owns it.
Write it for someone who cannot reach you for the next eight hours.
Put time-sensitive items first and keep one line per ticket.
You are about to leave, three tickets are still open, and the person arriving has never seen them. If you hand over only a list of ticket numbers, they will spend the first hour reading every thread to rebuild what you already know. A good handoff note moves that knowledge in five minutes and lets them start on the right ticket straight away.
When a handoff note is worth the time
Any time work continues without you: end of shift, a day off, a move to another queue, or a holiday. The test is simple. If the next person would need to message you to continue, the note is incomplete.
It matters most when a customer is waiting on a promise you made. A promise that lives only in your head is dropped the moment you log off.
Gather what you need before you write
Your helpdesk's list of tickets assigned to you that are not solved. Use whatever filter or view your tool offers for open and pending items.
Any tickets you replied to today where the customer has not answered yet.
Anything you promised with a time attached, such as "I will update you by 9 am".
Where the note will live: a shared document, a team channel, or an internal note field. Use the place your team already checks first.
Step by step: from open tickets to a note
List every open ticket you own: Copy the ticket number, a short customer label and the subject. Do not trust memory; read your own list.
Write the status in one plain line: Say what has happened and what is true now. "Waiting on customer for a screenshot, asked at 14:10" is a status. "In progress" is not.
Write one concrete next step: Begin with a verb: "Check the logs for the 14 Nov payment", "Chase the customer if no reply by noon". If there are two steps, list the first only and mention the second after it.
Name an owner: Write a person's name, or the word "unassigned" with the team that should pick it up. A step with no owner is the step most likely to be missed.
Sort by urgency: Put anything with a deadline or an angry customer at the top. Mark the deadline time with the time zone if the teams are in different ones.
Reread as the other person: Pick one ticket and ask whether you could act on that line without opening anything else. If not, add the missing fact.
Worked example: a handoff for open tickets
Say it is 17:30 and you hold four open tickets. Here is the note you would leave. The names and numbers are made up for the example.
Ticket | Status | Next step | Owner |
|---|---|---|---|
#4821 refund for double charge | Billing confirmed the double charge at 16:40. Customer expects a reply today. | Issue the refund, then email the customer the refund date. Must be sent before 20:00. | Priya (evening) |
#4807 login loop on mobile | Reproduced on one phone. Not reproduced on two others. | Ask customer for phone model and app version, then pass to the app team if it repeats. | Priya (evening) |
#4799 invoice address change | Customer sent the new address. Not yet applied. | Update the address on the account and reply to confirm. | Unassigned, billing queue |
#4790 feature request | Logged with product. Customer thanked us. | None. Close tomorrow if no reply. | Sam (morning) |
Check it against the three questions. Every row has a status, a next step and an owner. The only row with a deadline is first. Two rows fit in a single line each, and the last one clearly says nothing needs doing tonight, which saves the reader from opening it.
Add two lines under the table that apply to the whole shift: anything unusual ("a spike of login complaints since 15:00") and anything you were told but have not verified. Label the second kind clearly so nobody treats a rumour as a fact.
Mistakes that make a handoff useless
Writing "see ticket" instead of the one fact the reader needs. They should not have to open the thread to learn the status.
Leaving out the promise you made to the customer, including the time.
Using shorthand only you know, such as nicknames for customers or internal abbreviations the next shift has not seen.
Mixing finished work in with open work. Finished tickets belong in a separate line or nowhere.
Sending the note and leaving without checking that the person has seen it. In a chat tool, ask for a thumbs-up or a short reply.
Keep the same shape every day: Use the same columns each time. When the note always looks the same, the reader learns where to find the deadline in one second, and you stop deciding what to include.
Doing it faster
Keep a template with the four columns and paste the list of your open tickets into it ten minutes before you finish. Write the status lines as you work during the day, not at the end, by adding a one-line internal note to a ticket whenever it changes. Then the handoff is mostly copying lines you already wrote.
If you want help tidying the draft, DuckyHelper can look at your screen while you write and tell you which row is missing an owner or a next step. You still decide what goes into the note.
Frequently asked questions
How long should a handoff note be?
One line per ticket in the table, plus a few lines for shift-wide items. If a ticket needs a paragraph, put the paragraph in the ticket itself and link to it from the note.
Should I include solved tickets?
Only if something about them could come back, such as a refund that is still processing. Otherwise leave them out so the open items stand out.
Get started
