Endpoint operations
A laptop refresh cycle that starts with the asset record
A refresh cycle that uses the asset register, support dates, repair history, and user needs to decide which laptops to replace and when.
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
Laptop refresh plans usually start with a budget line and a list of old serial numbers. The asset record is a better starting point because it shows who has the device, what it runs, and when support ends. A refresh that ignores the record replaces the loudest complaints and misses the quiet machines that are already out of support. The cycle should connect the asset register, the warranty calendar, and the user's actual work.
Read the asset record before the budget
Open the asset register and confirm that every laptop has an owner, a purchase date, a model, and a support end date. Mark the records that are incomplete before setting any replacement target. Ask the asset owner to correct the gaps rather than guessing from the device name. A refresh list built on incomplete records will be challenged as soon as finance asks for evidence.
Match the register against the device management console and note the machines that appear in one source but not the other. A laptop missing from the console may still be in daily use, and one missing from the register may already be gone. Reconcile the two lists before the planning meeting. Record the reconciliation date so the next reviewer knows how fresh the numbers are.
Rank devices by support risk
Group the fleet by operating system version, model, and support end date. Flag the devices that will lose security updates within the planning year. Add the devices that already run an unsupported release, because those carry risk today rather than next year. Keep the ranking criteria fixed between reviews so the list can be compared over time. Record the result in the ticket with the date and the owner.
Add the user's role and travel pattern to the ranking. A device that travels daily and runs line-of-business software deserves earlier attention than a spare machine used for email. Note the applications that will not run on the replacement model. A hardware decision that ignores the software stack creates a second project after the purchase. Keep the note with the process record so the next person can find it.
Check the warranty and repair history
Pull the warranty status and the repair history for each candidate. A device with two battery replacements and a mainboard repair is a different risk from one with no faults. Note the cost of the last repair and whether the vendor covered it. Keep the vendor case numbers beside each entry so a claim can be traced without searching old email.
Check the warranty terms for accidental damage, battery coverage, and the claim window. A device that is out of warranty but still supported may be cheaper to keep for another year. Record the date each warranty ends and set a reminder before it closes. A claim started after the window is a cost the company did not plan for. Apply the same check to every device in scope before closing the task.
Ask the user what the device must do
Send a short survey to the users on the candidate list. Ask which applications they use, how often they travel, and what currently slows them down. Keep the questions specific so the answers can be compared across the fleet. A refresh that ignores the user replaces a working device and leaves the real constraint in place. Note any exception and the name of the person who approved it.
Interview two or three users with unusual requirements, such as engineering tools or accessibility settings. Confirm that the proposed model supports those needs before it reaches procurement. Note any peripheral or dock that will need replacement as well. Add the accessory cost to the same business case so the total is visible. Store the evidence where the team can open it during a review.
Build a staged replacement plan
Sort the approved replacements into three groups by risk and budget. The first group covers devices that are out of support or failing. The second covers devices that will leave support during the year. The third is a discretionary pool for growth and unexpected failures. Name the owner who can move a device between groups when circumstances change, and record the change in the refresh plan.
Schedule the swaps across the year rather than in one week. A steady pace keeps the support desk available for the migration work and gives users a predictable date. Avoid the end of the financial year, when approvals and deliveries slow down. Share the schedule with finance and the team leads before the first order is placed. Compare the result with the previous week before changing the process.
Prepare the migration before the swap
Confirm that the user's files are backed up and that the new device can sign in to the same applications. Test the dock, the printer, and any specialised peripheral before the handover. Book a thirty-minute slot with the user rather than dropping the device at the desk. A migration planned with the user takes less time than one done around them.
Write a short handover note that lists the old device, the new asset tag, and the data that moved. Record any application that needed a manual sign-in or a licence transfer. Ask the user to confirm that the device works for a full day before the old one is wiped. Keep the old device until that confirmation is recorded in the asset ticket.
Retire the old device cleanly
Wipe the old device only after the backup is verified and the user has confirmed the replacement. Remove it from the management console and the asset register on the same day. Record the wipe method, the date, and the person who performed it. A retired device that stays enrolled can still receive policy and appear in reports. Write the decision into the runbook for the next person on duty.
Return or recycle the hardware through the approved route and keep the receipt. Remove any labels that identify the company or the user. Confirm that the storage is encrypted or destroyed according to policy. A device that leaves without a record is a data risk and an accounting gap, so close the asset row only when the disposal evidence is attached.
Review the cycle each quarter
Compare the number of devices replaced with the plan and note where the schedule moved. Check whether the same model or department appears in every review. Ask the support desk which devices are generating the most tickets. A refresh plan that ignores the ticket history will keep replacing the wrong machines. Check the record against the live system before marking the item complete.
Update the support end dates and the warranty register before the next budget round. Adjust the thresholds if the fleet has changed or the vendor terms have moved. Give finance the remaining risk and the cost to close it. A quarterly review keeps the refresh a managed cycle rather than an annual emergency. Keep the checklist with the process guide so it is easy to repeat.
Sources and next step
Use the CISA Cross-Sector Cybersecurity Performance Goals and the NIST Cybersecurity Framework 2.0 as primary references for the device lifecycle, patch window, ticket triage, offboarding, and backup checks discussed in these guides. The NIST SP 800-53 Rev. 5 supports the access and audit records, and the NIST SP 800-34 contingency planning guidance supports the backup and restore checks. Apply your own policies, contracts, and system documentation to the workflow.
Compare this guide with the laptop refresh cycle and the first-hour ticket triage routine 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 laptop refresh cycle that starts with the asset record 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