Endpoint operations
A printer fleet map that ends the which-printer questions
A register that ties every printer to a queue name, a floor plan, and a support owner so staff stop guessing which device failed.
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
When a staff member says the printer is broken, the first question is often which printer, and nobody knows. A small office can accumulate devices from three suppliers, two floors, and a dozen past projects, each with a different name. A fleet map records what each device is, where it sits, and who depends on it. Building the map takes an afternoon and saves repeated guessing at the helpdesk.
Count the printers people actually use
Start with the print queue on each computer rather than the list from the supplier. Export the installed printers from a sample of laptops on every floor and note which queues appear most often. Walk the office and photograph each device with its label visible. Count the devices that staff use weekly, then mark the ones that only appear on old machines.
Include scanners, label printers, and multifunction units because users describe all of them as printers. Note the model, the serial number, and the supplier or lease reference. Record whether the device is owned, leased, or borrowed from a serviced office. A map that lists only the big copier will miss the small printer that stops a finance task every month.
Record identity before location
Give each device a stable name that does not depend on the room it currently occupies. Use the asset tag or serial number as the key, then add a friendly label that staff recognise. Record the network name, the fixed address if one is assigned, and the queue name shown on computers. These identifiers let a new assistant find the device without walking the floor.
Attach the supplier, the contract end date, and the support phone number to the same record. Note the toner or consumable part numbers and where spares are kept. If the device is managed by a third party, record the portal and the account owner. Identity comes first because location changes whenever a team reorganises. A contractor who inherits the device should be able to find the record without asking the person who ordered it.
Map printers to floors and teams
Draw a simple floor plan and mark each device where it sits, including the shared area and the locked room. List the teams that depend on each device and the tasks that would stop if it failed. Mark the nearest alternative for each group so a failure has an obvious fallback. The plan does not need to be architectural, only clear enough to guide a person on site.
Note the network segment and the wall port for each networked device. Record whether the device uses Wi-Fi or a cable and whether that connection is stable. Add the power outlet and any surge protection so a move does not overload a circuit. These details matter most during a desk move or a power outage. When a device moves between floors, the wall port and segment change even though the machine does not.
Publish a short reference sheet
Turn the map into a one-page sheet with the device name, location, queue name, and support contact. Keep the full register in the documentation system and link it from the sheet. Give the sheet to the front desk, the operations lead, and the person who handles tickets. Staff should be able to answer the which-printer question without calling IT. Staff should be able to answer the which-printer question without calling IT.
Label each device physically with its asset tag and a short support code. Place a small card near shared printers with the queue name and the reporting route. Update the card when the device changes, not at the next annual review. A reference sheet is only useful if the label on the machine matches the record. A card that is printed once and never replaced becomes another stale label.
Add new printers through one intake step
Require a short request before any new printer is purchased, leased, or connected. Ask for the team, the location, the intended use, and the supplier quote. Check whether an existing device can serve the need before approving another contract. This step stops a team from adding a device that nobody supports. The request should also record who approved the purchase and where the invoice is filed.
When a device is approved, add it to the register and the floor plan on the same day. Configure the queue, test a print job, and record the driver version. Tell the team how to report a fault and who owns the contract. A device that arrives without a record becomes the next unexplained queue on a laptop. The queue test should include a scan job if the device is also used for scanning.
Review the map after every move
Treat a desk move as a trigger to update the printer map, not a separate project. Ask the move lead for the new seating plan and check which devices stay, move, or leave. Reassign the queue names and update the floor plan before staff return. A move that skips this step produces a month of wrong directions. The move lead and the support owner should sign off on the updated plan before staff return.
Retire devices that are no longer used and remove their queues from the computers. Cancel the contract or return the lease on the recorded end date. Archive the record with the removal date and the reason. The register should show what exists now, with history kept separately. Keep the removal record with the finance file so the lease close is easy to prove.
Test the map with real tickets
Pick five recent printer tickets and check whether the map would have answered the first question. If the ticket names a device that is missing or mislabelled, fix the record. Ask the person who handled the ticket whether the support contact was correct. The test shows whether the map reflects daily work. Ask the person who raised the ticket whether the map gave the right device and contact.
Repeat the test after a move or a supplier change. Add the results to the quarterly review and note the fixes. A map that passes the test saves time on every future printer call. Keep the test short so it actually happens. The aim is a map that a new assistant can use on the first day, not a perfect drawing.
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
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 printer fleet map that ends the which-printer questions 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