The asset lifecycle

Sixteen states, the rules about what may follow what, and why the register stays accurate without anybody doing data entry.

The states

draft, procured, received, in_stock, ready, reserved, assigned, under_repair, damaged, exchange_initiated, replacement_issued, return_initiated, recovered, retired, disposed, archived.

Each action has a set of states it may be performed from. An illegal move is refused with a message naming the legal ones, so the register cannot drift into a state nobody can explain.

Why it stays accurate

Because the work updates it. An employee reports a fault from the help centre and picks their device from the list of what they hold, so the ticket is already linked to the right asset. The engineer sends it for repair and the asset moves to under_repair. A replacement is issued and dispatched; the employee confirms receipt with a photo; the ticket resolves itself. Nobody typed into a spreadsheet at any point.

Handover documents

Every assignment has a handover PDF one click away, with the employee's details, the configuration, the condition and signature lines, ready to print and sign. Returning it produces the return document the same way.

What an entitlement will never block

Returning an asset, completing an offboarding, closing a damage case and exporting your data all work regardless of your plan limits. Blocking those to make a billing point would break your actual operation, and we are not willing to do it.