1. Treat the lifecycle as a chain of accountable decisions
An asset lifecycle starts before a device arrives and continues after an employee returns it. Procurement, registration, assignment, configuration, maintenance, recovery and disposal each create information that the next stage needs. When those handovers are disconnected, equipment can exist physically without a reliable owner, support history or financial record.
The operational impact extends beyond missing laptops. Security teams cannot confidently prioritise unmanaged devices, finance cannot reconcile purchases with holdings, and service teams lose time reconstructing context. Establish a shared lifecycle with explicit transition criteria rather than treating the inventory as a list that somebody occasionally updates.
- Name an accountable lifecycle owner and responsible people for each handover.
- Define states such as ordered, in stock, assigned, under repair, recovered and retired.
2. Connect procurement to asset registration
Procurement should capture the business requirement, approver, supplier, intended cost owner and expected delivery. Separate a purchase request from proof that equipment was received. An invoice confirms a financial transaction; it does not establish that the right device arrived or entered managed stock.
At receipt, create or match the asset record using stable identifiers such as serial number and an internal asset identifier. Record the model, receipt date, location, warranty information and purchase reference where available. Distinguish purchased, leased and loaned equipment because return obligations and financial treatment may differ.
- Check deliveries against the order and document shortages or substitutions.
- Prevent duplicate registration by checking existing identifiers before creating another record.
- Route depreciation and accounting treatment to finance rather than inferring them from device age.
3. Make assignment and configuration separate checks
Assignment records who is responsible for an asset, where it should be and when custody began. It does not prove that the device is configured securely. Configuration needs its own checks, including management enrolment, required applications and relevant security settings, with the source and observation date recorded.
Lojycal can connect inventory, employee workflows, procurement and policy context. Device-management dispatch paths include Jamf, Kandji and Intune, but the available actions depend on the provider, permissions, credentials and workspace configuration. Confirm supported operations for your plan and workspace rather than assuming every connected device can be changed.
- Verify the recipient and record the handover acknowledgement.
- Check configuration evidence separately from the assignment status.
- For supported writes, use preflight confirmation and verify the resulting state through a fresh read.
4. Maintain history through repairs and ownership changes
Maintenance records should explain what happened, who authorised it and whether the asset remains fit for use. Keep repair dates, relevant warranty cases, replacement parts and service restrictions together. A device sent for repair may need a temporary replacement, creating two related custody records rather than one overwritten assignment.
Ownership changes need the same discipline. A departmental transfer can change the custodian, budget owner and location independently. Preserve the previous assignment and check whether configuration or access requirements also change. Do not assume that changing an employee field updates endpoint settings or financial allocation automatically.
- Schedule reviews around warranty expiry, recurring faults and unsupported operating systems.
- Resolve conflicting employee, location and cost-owner information before approving a transfer.
5. Separate recovery, retirement and disposal
Recovery means equipment has been returned or its absence has been explicitly recorded. Retirement means it is no longer intended for service. Disposal is the final transfer, recycling or other approved outcome. Combining these into one status can hide devices awaiting inspection, data sanitisation or collection.
In a fictional example, a departing employee returns a laptop to a regional office. The office records receipt, IT checks its condition and an authorised process handles data sanitisation before reassignment. If the device cannot be reused, the responsible owner approves retirement and retains the applicable disposal evidence. Until those steps are verified, the record should show the remaining work.
- Record missing equipment as an exception with an owner and follow-up date.
- Use approved sanitisation and disposal procedures, including applicable lease-return requirements.
6. Reconcile records and test the complete process
Asset reconciliation compares sources rather than declaring one universally correct. Match physical stock checks, endpoint observations, employee assignments and purchase records. An endpoint last seen months ago is not proof of current custody; a manual count is not proof of secure configuration. Preserve discrepancies and investigate them.
Evaluate Lojycal with a bounded sample spanning stock, assigned equipment, repairs and retired assets. Check which fields are imported, manually maintained or verified, and who can change them. Accurate records support security investigations, financial reconciliation and operational planning, but their usefulness depends on coverage, freshness and accountable review.
- Measure unmatched records, overdue handovers and unresolved exceptions before expanding scope.
- Agree reconciliation frequency, escalation ownership and evidence requirements with IT, finance and security.