An Asset Management SOP (standard operating procedure) is the written, step-by-step document that tells an IT team how to handle each asset at every stage of its life, from the moment it arrives to the day it is disposed of. IT asset managers and service desk leads search for one when they need to standardize how IT Asset Management (ITAM) is done in practice, prepare for an audit or train new technicians.
This guide includes a complete IT Asset Management SOP example for registering a new laptop, ready to copy and adapt. It also covers how an SOP differs from a policy, how to write your own, the free template, which procedures to document first and how to keep each SOP in sync with the asset record in IT Asset Management software.
IT Asset Management SOP example: registering a new laptop
The example below is a complete SOP for one of the most common ITAM procedures: taking a new laptop from delivery to disposal. It follows the same stages as the example in our downloadable template, so you can use either one as a starting point.
Each step says who does it, what they do and what must be recorded. That last part is what makes the SOP auditable, because every step leaves evidence in the asset record.
SOP header
The header tells the reader, in a few lines, what the procedure covers and who answers for it. Keep it at the top of the document so anyone can confirm they are reading the right SOP.
| Field | Content |
| SOP title | ITAM SOP: Registering a new laptop |
| Purpose | Make sure every company laptop is received, labeled, recorded, assigned, retired and disposed of the same way, so the ITAM database always shows what exists, where it is and who has it. |
| Scope | All company-owned and leased laptops, from delivery to disposal. Personal devices (BYOD) are out of scope. |
| Trigger | A laptop delivery arrives against an approved purchase order. |
| Procedure owner | IT Asset Manager |
| Roles | IT Asset Manager (owns the SOP and the records), service desk technician (receives, labels and deploys), procurement (purchase order and vendor), end user (accepts the device), security team (approves data sanitization) |
| Review frequency | Every 12 months, and whenever the ITAM tool, the hardware standard or a related policy changes |
| Related frecquency | IT Asset Management policy, acceptable use policy, data sanitization standard, employee equipment agreement |
Procedure
The procedure has seven steps, and each one ends with a record update. If a step can't be completed, the exception line says who takes over.
- Receive and inspect the device against the purchase order.
- Who: service desk technician.
- What: check the delivery against the purchase order raised during hardware procurement: model, quantity, serial numbers, charger and accessories. Inspect each laptop for damage.
- Record: purchase order number, vendor, delivery date, invoice and warranty start date.
- Exception: if a model or serial number doesn't match, hold the device and send the case back to procurement before going on.
- Label it with an asset tag.
- Who: service desk technician.
- What: attach a durable asset tag (QR code, barcode or radio-frequency identification (RFID) tag) in a visible spot that survives daily use. Our guide to IT asset tagging covers tag types and placement.
- Record: the tag ID, linked to the laptop's serial number.
- Note: if your ITAM tool generates the label from the asset record, do step 3 first and label the laptop right after.
- Register it in the ITAM database.
- Who: service desk technician, checked by the IT Asset Manager.
- What: create the asset record with the minimum data set: asset type, manufacturer, model, serial number, tag ID, purchase date, cost, warranty expiration, location and status (In stock).
- Record: a complete record with a unique asset ID.
- Exception: if the serial number already exists in the database, stop and ask the IT Asset Manager to investigate the duplicate.
- Assign and deploy it to the user.
- Who: service desk technician and end user.
- What: install the corporate standard image, test the device and hand it over. The user signs the employee equipment agreement on delivery.
- Record: owner, location, status (In use) and the signed delivery document.
- Update the record on every change.
- Who: the technician who makes the change.
- What: handle transfers, repairs, upgrades and reassignments through a service request, and update the record before the request is closed.
- Record: what changed, when, who made the change and the request number.
- Retire it.
- Who: IT Asset Manager.
- What: retire the laptop when it reaches End of Support, when its lease ends or when repair costs more than replacement. Collect it from the user and remove its access to company systems.
- Record: retirement reason, retirement date and status (Retired).
- Dispose of it and keep the certificate.
- Who: IT Asset Manager, with approval from the security team.
- What: wipe the storage following the data sanitization standard, such as the National Institute of Standards and Technology (NIST) guidelines in NIST SP 800-88 Rev. 2, and hand the device to a certified IT Asset Disposition (ITAD) vendor. Our guide to End-of-Life equipment covers the disposal options.
- Record: certificate of destruction or recycling, disposal date and status (Disposed).
- Exception: no laptop leaves the building without the security team's sanitization approval.
Document control
Document control closes the SOP with its version history. Auditors check it to confirm the procedure is reviewed and that someone approved each change.
| Version | Date | Reviewed by | Change details |
| 1.0 | January 2026 | IT asset manager | First approved version |
| 1.1 | July 2026 | Service desk lead | Added the security approval in step 7 |
What is an IT Asset Management SOP?
An IT Asset Management SOP is a written, step-by-step procedure that tells the IT team exactly how to register, assign, move and retire each asset, and who does each step. It sits below the policy, which sets the rules, and next to best practices, which recommend an approach without prescribing the steps.
Most ITAM teams end up with several SOPs, one per recurring task, all following the same format. The same logic applies to other IT teams, as our guide to the service desk standard operating procedure shows.
Standard Operating Procedure vs. Best practice
An SOP gives a structured set of repeatable steps to deliver one specific process or outcome. A best practice document makes recommendations about how to manage, control and protect the IT environment, without prescribing the exact steps.
In short, the SOP tells ITAM professionals how to carry out a task, with detailed steps and diagrams where they help. The best practice tells them what they should aim for, at a higher level, and usually informs how the SOPs are written.
SOP vs. policy
A policy sets the high-level rules, the regulatory and compliance requirements and the governance that apply to everyone involved in the ITAM practice. Our guides to the IT Asset Management policy and the Hardware Asset Management policy cover what each one includes.
The SOP turns those rules into instructions for the people who carry out the tasks every day. A policy might say that every device must be wiped before disposal; the SOP says who wipes it, with which method and where the certificate is stored.
Why do you need an IT Asset Management SOP?
Without a written procedure, each technician registers, assigns and retires assets their own way, and the asset database drifts away from reality. An IT Asset Management SOP gives the team four concrete benefits:
- Consistency: every asset goes through the same steps, whoever handles it. Clear roles reduce errors, duplication and rework, and the knowledge stays with the team when people change roles.
- Audit readiness: a documented practice gives auditors clear trails, proof of ownership and evidence of licensing. It also supports Governance, Risk and Compliance (GRC) requirements such as license agreements, support contracts and data protection rules.
- Security: defined steps for assignment, transfer and disposal reduce the risk of lost devices, data breaches and unauthorized assets on the network. Our guide to IT security risk in IT Asset Management explains how inventory gaps turn into exposure.
- Cost control: accurate records help prevent duplicate purchases, recover idle devices and avoid noncompliance fines, which supports smarter IT budgeting.
How do you create an Asset Management SOP?
Writing an SOP is a short project with a clear sequence. Follow these steps for each procedure you document:
- Define the format. Check whether your organization has a corporate style for documentation and use it, so every SOP has the same look and structure.
- Ask technical teams where to focus. The technicians who handle assets every day know which tasks need an SOP and which activities must be captured.
- Set clear process goals. State the purpose of the SOP so everyone knows what outcome it should produce.
- List all components needed. Identify the prerequisites, tools, roles and documents the procedure depends on.
- Make it adaptable. Draft the first SOPs in outline format, so they are easy to change after the first reviews.
- Request a review from technical colleagues. They confirm that every key activity is captured and that the steps are in the right order.
- Follow industry standards and check regulations. Align the SOP with the regulations that apply to your organization and with references such as ISO/IEC 19770-1, the international standard for IT Asset Management systems.
- Make it available to colleagues. Publish the SOP in your Knowledge Management system or portal so it is easy to find and use.
- Build review cycles. Set a review date in the document control table and treat each review as part of continual improvement.
The seven parts of the ITAM SOP
Our free template follows a seven-part structure that works for any ITAM procedure. These are the parts, in the order they appear in the document:
- Title page: names the SOP and the team that owns it, with the right logos in place.
- Table of contents: lists every heading in the procedure, ideally with links so readers can jump to each one.
- Scope: explains what the SOP covers and any operating limits that need to be called out.
- Introduction: gives a short overview of the topic and the ITAM practice, and names the procedure owner.
- Procedure: the actual content of the SOP, organized as stages and activities.
- Further reading: links to supporting documents and related processes, such as security, finance and environmental policies.
- Document control: a short table with the version history, the review dates and the details of each change.
Download the Asset Management SOP template
The template gives you the seven parts above as an editable document. It also includes a filled-in example, an SOP for updating information in the IT asset database, which covers these stages:
- Trigger: the events that start the procedure.
- Receive asset.
- Tag asset.
- Asset capture.
- Asset deployment.
- Update asset.
- Asset retirement.
- Asset disposal.
Fill in the form below and the template arrives in your inbox. Adapt the example to your own roles, tools and records before you publish it.
Key points in the asset lifecycle for SOPs
Acquisition, transition and disposal are the three stages of the asset lifecycle where standardized procedures matter most. They are standard stages, and the exact steps and timing vary by asset type: a software license doesn't follow a laptop's path.
SOPs make sure no step is missed during these moments. They also make sure every action is documented for future reference.
Acquisition
Acquisition is where the asset record is born, so mistakes here follow the asset for years. The SOP should make sure each new asset arrives with these details:
- Purchase details: purchase date, vendor and cost.
- Asset identification: a unique identifier logged in your Asset Management system.
- Initial tracking: location, assigned user and warranty details from day one.
- Documentation: purchase orders, invoices, warranties and service agreements, attached to the asset record.
Transition
Transitions are the moments when records most often fall out of date. The SOP should describe how each change is approved and recorded:
- Transfers: the steps to move an asset between departments, users or locations, including any approvals.
- Upgrades and repairs: how hardware changes and software updates are documented, and their effect on the asset's lifecycle.
- Status and location: how the asset's status, owner and physical location are updated during every transition.
Disposal
Disposal carries the highest legal and security risk of the lifecycle. The SOP should cover these three points:
- Regulatory compliance: how disposal meets environmental regulations, including specialized methods for electronic waste.
- Data security: how data is wiped before disposal and how the wipe is verified.
- Proof of disposal: certificates of destruction or transfer of ownership, attached to the asset record and easy to retrieve during an audit.
Which IT Asset Management SOPs to write first
Most ITAM teams need a small set of SOPs to cover the tasks they repeat every week. Start with the ones that create or change asset records, because they keep the database accurate:
- Asset intake: receiving, labeling and registering new hardware.
- Assignment and onboarding: preparing and delivering equipment to new employees.
- Transfers: moving assets between users, departments or locations.
- Periodic audit: checking the records against what physically exists, as in a hardware audit.
- Software license requests: approving, assigning and recovering licenses.
- Retirement and disposal: taking assets out of service, wiping them and keeping the proof.
Once these are written and in use, add SOPs for less frequent tasks, such as lease returns or loaner devices. Each new SOP should reuse the same format and roles, so technicians only learn the structure once.
How to run your IT Asset Management SOP in InvGate Asset Management
An SOP is followed when the asset record follows it. InvGate Asset Management is ITAM software that offers an enterprise experience without the complexity or the price of one, with an intuitive interface, a no-code approach and fast deployment. The SOP itself lives in your knowledge base, and each asset's record keeps the evidence every step produces.
This is where each step of the example SOP lives in InvGate Asset Management:
| SOP step | In InvGate Asset Management |
| 1. Receive and inspect | Create assets from native Purchase Orders and attach the invoice and warranty to the asset record. |
| 2. Label | Generate and print a QR code from the asset record; scanning it opens the live record. |
| 3. Register | Populate the inventory through the Agent, network discovery, integrations or CSV import, and create assets from Product Catalog entries with their standard properties already filled in. |
| 4. Assign and deploy | Set the owner and location, and create a delivery document from your own template; the document is attached to every asset it includes. |
| 5. Update | Every change is logged in the asset's Activities, and an automation template keeps each asset's location in line with its owner's. |
| 6. Retire | Change the asset's status, with lifecycle stages defined per asset type. |
| 7. Dispose | Attach the certificate of destruction to the asset record, next to the rest of its history. |
Pending steps stay visible without manual searches. Smart Tags apply themselves to every asset that meets a condition, such as laptops in use with no owner or no location, and Smart Recommendations flags data quality gaps like missing acquisition costs or dates.
Physical audits by location, run from a phone with QR codes or RFID tags, confirm that the records match what is on the shelves. And because assets can be created straight from a purchase order, registration starts from the data the order already holds, a flow our guide to IT purchase order tracking covers in detail. Together, these capabilities cover the full IT asset lifecycle in one place.
How Grupo Gigante gave its inventory processes a formal structure
Grupo Gigante, a Mexican group with retail and real estate brands, runs a single IT division that supports about 2,500 employees. A 2022 internal audit raised 11 observations, and change and inventory processes had no formal structure.
The company went live with InvGate Service Management and InvGate Asset Management about three months after signing. Devices are now linked to their assigned employees from onboarding, and audit observations went from 11 to 0, as the Grupo Gigante case study details.
Bottom line
An Asset Management SOP turns the rules in your policy into steps your team can repeat, audit and improve. Start with the procedures that create or change asset records, and make sure each one is part of your ITAM strategy.
The SOP works best when the tool records each step as it happens. Start a free trial of InvGate Asset Management to run your first IT Asset Management SOP on it, or talk to Sales to see how it fits your processes.
Frequently Asked Questions
These are the questions IT teams ask most often when they write their first IT Asset Management SOP. Each answer is short and points back to the section that covers the topic.
What are the three types of SOP?
The three common SOP formats are step-by-step, hierarchical and flowchart. Step-by-step suits linear tasks, hierarchical suits complex processes with sub-steps, and flowcharts suit tasks with decisions.
What is an SOP example?
The laptop registration procedure in this article is a complete IT Asset Management SOP example. For SOPs from other IT and business areas, see these SOP examples.
What is the difference between a plan and an SOP?
A plan sets objectives and what needs to be done at a high level. An SOP gives the step-by-step instructions for how a specific task is carried out to reach those objectives.
Who should own the IT Asset Management SOP?
The IT Asset Manager usually writes and maintains it, with input from the technicians who follow it. The IT manager or the head of the ITAM practice approves each version.
How often should you review an IT Asset Management SOP?
Review it at least once a year. Also review it whenever the ITAM tool, the hardware standard or a related policy changes.