What do lifecycle events record, and can they serve as a device history?

Schools and companies are asked the same questions again and again. Who had that tablet in March? When did we replace it? Was it ever reported lost? Without a record, the answer depends on someone's memory or a spreadsheet that fell behind.

Skie keeps the record as devices change state. Each step of a device's life is logged as an event: it was provisioned into a group for a student, it was reassigned to another student, it was replaced by another device, it was marked lost, it was found, Skie was removed from it, or the record was force removed. Every event has a date, and the audit log shows who carried it out.

This is useful in practice. An asset register can be built from it. A parent who says their child never received a tablet can be answered from the record. An insurer or the police can be shown the timeline of a loss. A handover at year end can be checked against it.

What the record is not is a log of private activity. It tracks the status and ownership of the device, not what a student typed or read. Skie does not read messages or call logs. Reassigning clears student linked data while the device's own history remains, so the record is about the hardware's life.

Practical tip: use consistent steps. Always use the replace and reassign flows, not delete and re-add, because the flows preserve the timeline. For further reading see reassigning and replacing.

• Provisioned, assigned, reassigned, replaced
• Lost, found, removed
• Date and person on each event
• About the device, not private activity