Asset Check-Out best practices
The mechanics of checking assets in and out are simple. The policy around them is what decides whether equipment comes back.
Requirements
- Available on: Orbit, Odyssey, Cosmos
- Roles: Owner, Admin, Manager, and Employee can check out and check in. Viewers cannot.
Decide what belongs in check-out
Check-out is for things that leave and come back. Tools, test equipment, laptops for a conference, keys, vehicles for a job.
Assignment is for durable responsibility. The laptop someone works on every day is assigned, not checked out daily.
Getting this wrong in either direction is the most common problem:
- Checking out what should be assigned produces a permanent overdue list nobody can act on
- Assigning what should be checked out loses track of who physically has it
Remember that check-out never touches assignment. An asset assigned to the workshop and checked out to a technician is still the workshop's asset.
Write the policy down before you scale
Four decisions, agreed once:
- What is checked out — by category, or by value threshold
- Who can check things out — anyone from Employee up, or a smaller group
- How long a default loan is — and who can extend it
- Who chases returns — a named person, not "the team"
A policy nobody wrote down is a policy nobody follows.
Set return dates you believe
The return date is what makes overdue mean anything.
Set it to when you actually expect the item back, not a comfortable date far in the future. A date nobody believes produces alerts nobody acts on, and once people learn to ignore the overdue list it stops working entirely.
For open-ended loans, set a review date and extend by checking in and out again — that leaves a record of the extension rather than silently ignoring an overdue item.
Use purpose and notes properly
Purpose should say what the item is for: "Site survey — Ashton Road", "Training course, week of the 14th". Six weeks later, "why does Sam have the thermal camera?" is a question the purpose field would have answered.
Avoid "misc", "as needed", and blank — they turn the checkout report into noise.
Notes should record condition on the way out and any accessories included. If it comes back damaged or incomplete, that note is the only record of how it went out.
Use sessions for grouped loans
When several items go out together for one purpose — a field job, a training course, a site inspection — use a checkout session.
The set is tracked as a unit while each item stays individually returnable, which matters when the van comes back before the test equipment does.
Build a return habit
Weekly: whoever owns follow-up reviews what is checked out and what is overdue.
Act on the approaching-return alerts, not the overdue ones. A reminder the day before is far cheaper than a chase a fortnight after.
Chase by person, not by asset. Open the Person to see everything they hold — one conversation usually covers several items.
Handle returns properly
Look at the item when it comes back. Check-in is the moment to notice damage, missing accessories, or a flat battery.
If something comes back damaged: check it in first, change the status, raise a corrective work order, and report an incident if it was an accident — before the repair, so the snapshot captures the asset as it is.
Do not check in items that have not come back to clear an overdue list. That destroys the record.
Use the data
Checkout history tells you things worth knowing:
- Items constantly out may need a second one bought
- Items never checked out may not be needed at all
- Repeated late returns from one person or team is a conversation, and the data supports it
Common mistakes
Checking out instead of reassigning. Permanent responsibility is assignment.
Comfortable return dates. They make overdue meaningless.
Nobody owning follow-up. Shared responsibility means nobody chases.
Blank purpose fields. The reports become unusable.
Checking items in to tidy the list. The list is only useful if it is true.
Related articles
Need Help?
If you have questions not covered in this article, our support team is here to help.
Contact Support