Helpdesk

A support rota that keeps one queue covered all week

A weekly rota with named primaries, a written handover, and backup cover that keeps a single support queue from stalling.

Short answer

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

Best fitRepeatable IT admin
OwnerManager or IT lead
Risk ruleEscalate technical judgment
PilotTwo-week sample workflow
On this pageJump to section

A support queue does not fail all at once. It stalls when the morning owner is in a meeting, the afternoon owner is on leave, and nobody notices that the oldest request is now three days old. A rota makes cover visible before the gap appears. It names who owns the queue, when the handover happens, and who acts when the primary is unavailable. The schedule is a control, not a calendar decoration.

Start from the queue's real demand

Export the arrival times of requests over the past month and plot them by hour and weekday. Note the peaks, the quiet periods, and the days when a single person handles everything. Include the channels where requests arrive, such as email, chat, and the phone. The rota should follow the demand rather than an assumed office pattern. Split the counts by channel so a quiet inbox does not hide a busy phone line.

Check when the technical owner is available for escalations and when the business needs a response. Mark the hours that require live coverage and the hours that can wait for the next shift. Record the volume of urgent requests in each period. A rota built on real arrival data avoids both idle cover and uncovered peaks. Write the escalation window beside each shift so the owner knows when to call.

Define the shifts and the handover point

Set shift boundaries that match the demand curve and the working day of the team. Name a clear handover time when the outgoing owner writes the note and the incoming owner acknowledges it. Avoid overlaps that look helpful but leave both people unsure who is responsible. A single accountable owner per shift prevents duplicated work. Publish the handover time in the queue header so requesters can see when to expect a reply.

Record the handover in the queue rather than a private message. The note should list urgent open items, waiting requests, promised updates, and anything the next owner must watch. The incoming owner confirms the note before the outgoing owner leaves. A handover that is not acknowledged is only a hope. A note that lists only open tickets leaves the next owner to rediscover the urgent ones.

Name a primary and a backup

Every shift should have a named primary and a named backup who can step in without a search. Publish both names in the rota and the queue header. The backup should have the same access and the same briefing as the primary. Cover that depends on one person is not cover. The backup should be named in the rota even when the primary is expected to attend.

Rotate the backup role so more than one person knows the queue. Record who has been trained and when they last covered a shift. Keep the training short and specific to the queue. A backup who has never seen the work will need the primary anyway. Record the date of the last cover shift so training does not drift or the queue changes hands.

Write the handover note standard

Give the team a short template for the handover note. Ask for the count of open requests, the oldest unresolved item, the urgent items, and the next promised update. Add a line for vendor cases and one for anything that needs the technical owner. The template keeps the note consistent across people and weeks. Keep the template to five lines so people fill it in at the end of a shift.

Review a sample of handover notes each month and fix the ones that omit the next action. Praise notes that are short and complete rather than long and vague. Store the notes where the next shift can find them. The standard should make the handover faster, not add a writing task. Share one good note with the team each month as an example.

Cover leave and sick days

Plan leave cover at least two weeks ahead and record it in the same rota. Identify the shifts that lose their primary and assign a named replacement. Check that the replacement has the access and the context to act. A leave request that is approved without cover creates a queue gap. Check that the replacement has access to the same queues and vendor portals.

Keep a small pool of people who can cover an unexpected absence. Tell the queue owner who to call when the primary does not appear. Record the actual cover used so the rota can improve. Sick-day cover should be a known route, not an improvisation. Write the escalation route on the rota so nobody has to search for it, and include the backup name.

Publish the rota where requesters see it

Put the current rota on the support page and in the queue header. Show the hours of coverage and the route for urgent issues outside those hours. Use plain names and avoid internal codes that requesters cannot interpret. People behave better when they know when to expect a reply. Include the time zone when the team covers more than one region.

Update the published rota when a shift changes, not at the end of the month. Tell the front desk and the account team about holiday cover. Add a line to the maintenance notice when support hours change. The published version should match what the team is actually working. Tell the account team when a named contact changes so clients are not given an old name.

Review the rota against response data

Each month, compare the rota with the first response time and the age of unassigned requests. Look for the shifts where requests wait longest and check whether the cause is volume or handover. Ask the people on those shifts what they lacked. The data should test the schedule, not judge the person. Include the volume handled so a slow week is not mistaken for a process failure.

Adjust the shift boundaries or the backup list when the pattern repeats. Record the change and the reason so the next review can see the effect. Keep the rota stable enough for people to plan their week. A schedule that changes every Monday creates its own confusion. Keep the previous rota versions so a repeated problem can be traced and the history is not lost.

Sources and next step

Use the CISA Cross-Sector Cybersecurity Performance Goals and the NIST Cybersecurity Framework 2.0 as primary references for the printer, domain, support rota, licence, and desk move practices discussed in these guides. The NIST SP 800-53 Rev. 5 supports the access and asset records, and the SBA cybersecurity guidance frames the vendor and account ownership checks. Apply your own policies, contracts, and system documentation to the workflow.

Compare this guide with the domain renewal register and the licence true-up worksheet 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

Delegate

Routine intake, status updates, records, screenshots, and documentation upkeep.

Keep ownership

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

1

Define the request

Write what a support rota that keeps one queue covered all week means in your company, where requests enter, and what finished work looks like.

2

Limit the access

Give the assistant only the tool permissions needed for intake, records, status updates, or documentation.

3

Run a pilot

Use a two-week sample period so the manager can review accuracy before expanding the workflow.

4

Review patterns

Summarize repeat issues, blocked requests, and escalation volume so the technical owner can improve the process.

Decision rules

QuestionVA fit signalEscalate 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