Helpdesk operations
A support shift handover note that names the open risks
A shift handover note that lists changed tickets, open risks, vendor waits, owners, and the next promised update instead of a diary of activity.
Start with repeatable IT work that has a clear owner, clear access limits, and a review cadence. Keep risky technical decisions with the manager or provider who owns the system.
Delegation playbook
On this pageJump to section
A handover note is read when the next person is already busy. It should name the risks that need attention, not replay every ticket the previous shift touched. The useful note is short, specific, and tied to an owner and a time. It gives the incoming agent a safe starting point without forcing them to reconstruct the day. Write it for the person who will read it first, not for the record.
Write it before the shift ends
Start the handover note thirty minutes before the end of the shift rather than in the last five minutes. Open the queue and the incident list beside the note so nothing is copied from memory. Write the note in the shared tool where the next shift already works. A note written after the laptop is closed is usually a list of names with no context.
Leave the note open while the last calls finish and add anything that changes. If a call is still running at the end of the shift, hand it over in person as well as in writing. Record the time of the handover and the person who received it. The note is complete when the next agent can act without calling back.
List the tickets that changed state
List the tickets escalated, reopened, or closed without user confirmation during the shift. Note the ticket number, the current owner, and the next action. Skip the routine resolutions that need no follow-up. A handover that lists every closed password reset hides the three items that matter. Add the time of the last user reply so the next shift knows the wait.
Mark the tickets that are waiting on a user, a vendor, or an approval. Give the date and time of the last contact and the next promised update. Flag any ticket that will breach its target before the next shift ends. The incoming agent should see the deadline without opening every record. A ticket that will breach before noon should sit at the top of the list.
Name the risks, not the activity
Write one line for each risk that could affect users or data before the next handover. Examples include a failing backup, a certificate that expires at the weekend, or a site with no network redundancy. Say what is being done and who owns it. A list of activities is not a risk list, even when it is long. Name the system and the user group that would feel the failure first.
Rank the risks by the time they would take to hurt the business. Put the item that could fail tonight above the item that can wait for the weekly review. Note the trigger that would make the risk urgent. The ranking helps the next agent decide what to read first. Add the date the risk was accepted when the business chooses to wait.
Include the vendor and approval waits
Record the vendor cases that are waiting for a response and the date of the last chase. Give the case number and the name of the engineer if one is assigned. Note the contract response time when it affects the escalation. A vendor wait that is invisible in the handover becomes a missed deadline. Record the next chase date so the follow-up does not depend on memory.
List the approvals that are blocking work, such as a purchase, a firewall rule, or an access request. Name the approver and the date the request was sent. Do not ask the next shift to guess who has the decision. A clear approval list prevents duplicate requests and awkward follow-ups. Put the approval reference beside the work item so the next shift can quote it.
Point to the evidence and the owner
Link each open item to its ticket, log, or document instead of describing it again. Name the person who owns the next action, even when that person is not on the shift. Add the time of the next planned update. Evidence plus an owner is what turns a note into a plan. A link is faster to check than a paragraph written from memory.
Use the same fields in the same order every day so the next reader can scan quickly. Keep the language plain and avoid abbreviations that only one team uses. Remove personal comments about users or colleagues. A handover note may be read in an audit or a dispute long after the shift. Keep the note free of private jokes and comments that could embarrass someone.
Read it at the start of the next shift
Read the handover note at the start of the shift before opening the queue. Confirm the items that need immediate action and acknowledge the rest. Ask a question in the note rather than waiting for the previous agent to wake up. A note that is never read is only a diary. Mark the items you have read so the team can see the handover was received.
Check the open risks against the live systems and update the note if something changed overnight. Tell the previous owner when an item is closed or reassigned. Keep the note for the agreed retention period. The habit of reading is what makes the writing worthwhile. Send a short reply to the previous owner when an item is closed, moved, or cancelled.
Keep one template and one location
Store the template in the same workspace as the ticket queue and link it from the shift checklist. Keep the sections short: open risks, changed tickets, waits, owners, and next updates. Add a line for anything the next shift must not do, such as restarting a server during a migration. A template that is easy to find is used under pressure.
Review the template with the team once a quarter and remove the fields nobody reads. Ask the incoming agents which section they open first. Add the one detail that prevented a repeat question. A shared template makes the handover faster for everyone. Ask the incoming agents which section they open first and keep that section short and easy to scan.
Review handover quality monthly
Read five handovers from the past month and check whether each open item had an owner and a time. Look for risks that appeared in one note and vanished without a closure. Ask the next shift whether they had to call the previous agent for context. The answers show where the note is failing. Record one example of a handover that prevented a repeat call.
Share one strong example with the team and explain why it worked. Update the checklist when a new system or vendor is added. Keep the review short and focused on the next shift. A handover process improves when the people who read it help write the standard. Ask the team to add one lesson from the month to the shared checklist.
Sources and next step
Use the CISA Cross-Sector Cybersecurity Performance Goals and the NIST Cybersecurity Framework 2.0 as primary references for the lost laptop, new device build, shift handover, service account, and remote session practices discussed in these guides. The NIST SP 800-53 Rev. 5 supports the access and audit records, and the NIST SP 800-61 incident handling guidance supports the containment and evidence steps. Apply your own policies, contracts, and system documentation to the workflow.
Compare this guide with the lost laptop response checklist and the service account rotation log before changing a live process. If the coordination is recurring and your technical owner can define the boundaries, review the IT virtual assistant service areas and contact ITVirtualAssistant to discuss a limited pilot.
Operating brief
What this guide should help you decide
Routine intake, status updates, records, screenshots, and documentation upkeep.
Approvals, risky system changes, security decisions, and final technical judgment.
How to use this guide
Use this page to decide what an IT virtual assistant should handle first. If the task is recurring, documented, and easy to review, it is usually a better first delegation candidate than work that requires live technical judgment.
Treat the article as an operating brief, not just a topic overview. The goal is to turn loose IT work into a named workflow with inputs, outputs, permissions, review cadence, and a handoff rule that protects the business while reducing manager load.
Workflow
Recommended operating workflow
Define the request
Write what a support shift handover note that names the open risks means in your company, where requests enter, and what finished work looks like.
Limit the access
Give the assistant only the tool permissions needed for intake, records, status updates, or documentation.
Run a pilot
Use a two-week sample period so the manager can review accuracy before expanding the workflow.
Review patterns
Summarize repeat issues, blocked requests, and escalation volume so the technical owner can improve the process.
Decision rules
| Question | VA fit signal | Escalate when |
|---|---|---|
| Is the work repeatable? | The same request appears weekly and can be described in steps. | The request changes business policy or system design. |
| Can quality be reviewed? | The manager can inspect the output without redoing the work. | Only a senior technical person can judge correctness. |
| Is access contained? | The assistant can work with read-only or role-limited access. | Admin rights, customer data, or security settings are involved. |
Delegation checklist
- Write the intake source, expected output, and manager review cadence.
- Confirm the assistant has only the permissions needed for the workflow.
- List the events that require escalation before work continues.
- Track examples for two weeks before changing the workflow.
- Save examples of good and bad outputs so the assistant has concrete references.
- Review the workflow monthly and remove permissions that are no longer needed.
Example first-week agenda
Day one should cover the workflow owner, tools, allowed actions, forbidden actions, and escalation language. By the end of week one, the assistant should have produced a small sample of completed work, a list of unclear requests, and a manager-reviewed improvement note.
What to review before delegating
Confirm the owner, access level, review cadence, and escalation path before assigning any recurring IT workflow to a remote assistant.
What should an IT virtual assistant handle first?
Start with repeatable, reviewable work such as ticket summaries, account records, documentation updates, and checklist follow up.
Get free IT support review