1. Inventory is the starting point, not the conclusion
Device inventory describes the endpoints an organisation knows about: laptops, desktops, phones and other relevant equipment. Useful fields include a stable device identifier, model, serial number, operating system and last observed time. A device appearing in inventory does not prove that it is currently online, managed or secure.
Incomplete inventories create practical problems: support cannot identify the right machine, finance buys replacements prematurely and departing employees retain untracked equipment. Define the population in scope and reconcile sources. A management platform, purchasing record and physical stock check can each reveal different parts of the estate.
- Flag missing identifiers, duplicates and records without a recent observation.
2. Separate ownership, assignment and lifecycle
Ownership identifies who legally or financially owns equipment. Assignment identifies its current custodian or intended user. Neither should be inferred automatically from the last signed-in account, particularly for shared machines, loan devices or personally owned equipment.
An asset record adds purchasing, warranty, cost-centre and lifecycle context to technical inventory. Track meaningful states such as ordered, held in stock, assigned, under repair, returned and retired. Specify who may approve each transition. A returned laptop is not automatically ready for another employee: inspection and approved preparation may still be outstanding.
- Record assignment dates and recovery responsibility separately from technical device status.
3. Interpret enrolment and security signals carefully
Enrolment establishes a device’s relationship with a management service. Management status describes what that service currently reports about the relationship. Operating-system information and device security posture provide additional signals, but their meaning depends on provider definitions, update frequency and available permissions.
An old operating-system observation is not proof of the current version. Similarly, an absent encryption field means unknown unless the source establishes otherwise. Keep reported facts separate from assessments and require investigation of stale or contradictory signals. Inventory visibility does not, by itself, provide patching, remote control or universal policy enforcement.
- Display source, observation time and unresolved gaps alongside posture information.
4. Check platform availability at the action level
Lojycal has dispatch capabilities for supported device actions through Microsoft Intune, Jamf and Kandji. This does not establish a live connection in your workspace or identical actions across those providers. Confirm the particular operation, required permissions, credentials, mappings and plan or role restrictions before relying on it.
Apple Business Manager concerns Apple device deployment and organisational assignment; it should not be treated as interchangeable with a device-management service. Confirm any Lojycal connectivity requirement separately rather than assuming availability. Lojycal’s connected records and workflows do not establish that it independently patches or remotely controls endpoints.
- Ask how provider acceptance and the eventual device outcome are distinguished and verified.
5. Use connected records for allocation and purchasing
Linking endpoints to identities and employment records helps teams investigate assignment mismatches and prepare for starters, transfers and departures. Combining these links with asset and procurement information supports replacement planning based on condition, warranty, business requirements and available stock rather than age alone.
In a fictional example, an employee needs a laptop for a new role. The asset register shows a returned machine, but the management source last observed it several weeks ago. The sensible next step is to confirm possession, condition and approved preparation—not to mark allocation complete or order a replacement automatically.
- Record who confirmed physical custody and who approved reuse or replacement.
6. Evaluate with a representative device sample
Pilot with assigned, shared, spare and recently returned devices. Compare technical identifiers with asset records and ask owners to resolve mismatches. Test a supported, authorised action only after reviewing its impact and the destination system’s requirements.
Judge the workflow on whether it makes uncertainty and outstanding work visible. A useful operational view distinguishes a request from provider acknowledgement and a verified outcome, while leaving unsupported work assigned to a responsible person.
- Check how stale observations, missing users and duplicate serial numbers are handled.
- Confirm supported providers and actions for your workspace; review /pricing and discuss requirements through /contact.