All documentation

Equipment

Assets and equipment

A register of what was issued to whom, built around the one state that gets missed.

The state this exists for is *held by somebody who has left*

An offboarding checklist asks for the laptop back, but a checklist task is ticked by a person, and the one thing nobody does on their last day is chase hardware. So it is its own state rather than folded into *issued*, and it sorts first on both the register and the person's profile. Burying it in a larger count is how it stops being done.

Issuing and taking back

  • One open assignment at a time. Two people cannot hold one laptop, and allowing it makes *who has this?* unanswerable at exactly the moment somebody is asking because it went missing.
  • A damaged return goes to repair, not back into stock. Putting it straight back on the shelf is how it reaches the next person.
  • Condition decline is reported, never acted on. A system that automatically charged for a scratch would simply stop being told about scratches.
  • Lost and retired override the open assignment, and that assignment stays open. Who had it last is exactly why the record is worth keeping.
  • Nothing is issued with a future date — the register answers who has it now.
  • Being out of warranty is reported without being urgent. It changes what a repair costs, not whether anything must happen today.

Who it is issued to, and who can see it

Assets are issued to a worker, not a login: somebody with no account is issued boots and a locker key like anybody else. Access sits with personal data rather than the staff directory — a serial number is not sensitive on its own, but *who has the expensive laptop* is not a question the staff list should answer.

Two status changes the register refuses

Issued is never set by hand — that is what issuing means, and typing it would produce an asset marked as held by nobody. Back in stock is refused while somebody holds it: record the return instead, which captures the condition it came back in. Marking something lost demands a note, because every other status can be inferred later and that is the one somebody will ask about.

Not built yet

There is no bulk import, which is how a real inventory actually arrives.