Asset management
Reconcile IT Asset Tags After a Move
A three-list reconciliation that catches missing, duplicated, and reassigned assets after an office move, with an evidence trail for finance and security.
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
Office moves are where asset registers go soft. Devices are unplugged, carried, and replugged by people who are not thinking about serial numbers. The register keeps its old locations and everyone assumes someone else updated it.
A reconciliation after the move is cheaper than an audit six months later. It also catches the devices that left the building and the ones that were never returned from a repair.
Export the three lists that matter
Pull the asset register, the device management inventory, and the network inventory. Each list has a different bias: finance knows what was bought, the management tool knows what checked in, and the network knows what is connected.
Add the return log if the move involved leased equipment. Four lists are still manageable in a spreadsheet.
Freeze the export time for each list. Comparing a Monday register to a Friday inventory produces false discrepancies.
Match on serial and user, not tag alone
Asset tags are stickers. They fall off, get reused, and are sometimes read incorrectly over the phone. Match on serial number first, then on assigned user and hostname.
Where the serial is missing, flag the row rather than guessing. A guessed match is worse than an open item because it closes the question with bad evidence.
Normalize the data before comparing: trim spaces, uppercase serials, and standardize hostname suffixes.
Investigate duplicates and ghosts
A duplicate serial usually means one device was entered twice, but it can also mean a cloned image reused a serial in the management tool. Check the warranty record to distinguish.
A ghost is a device in the register with no management check-in and no network presence. Ask the assigned user and their manager before writing it off.
A device present on the network but absent from the register is the highest priority. It is either unmanaged or mislabeled, and both need a decision.
Correct the register with evidence
For each change, record the old value, the new value, the source of the evidence, and the person who approved it. A bulk update without a change log is not a reconciliation.
Update location, assigned user, and status together. Changing the location while leaving the previous user assigned creates a record that looks current and is not.
Attach photos or export snippets for disputed items. The next person to touch the register should not have to repeat the investigation.
Close with a spot check
After the corrections, sample ten devices physically and confirm the register matches. Include at least one device that changed hands during the move.
Report the counts: matched, corrected, unresolved, and missing. Send the unresolved list to the asset owner with an owner and a date for each.
Schedule the next reconciliation before the next move, not after it.
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 reconcile it asset tags after a move 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