Equipment accountability
Track issued equipment and its holder. Review an item before it returns to service.
Record the handover and the assignment it supports
An equipment item has a stable identity, current state, condition, and event history. Issue and transfer record the holder and handover time. The next event cannot be dated before the last saved change.
Only an Available item in Good condition can be issued. Transfer needs an Issued item in Good condition and a different holder. The holder must belong to the equipment’s organization.
A linked deployment must belong to that holder, remain open, and match the selected incident. The incident must be open and within the manager’s access. A team link must identify a team in that incident.
A held item can be linked to the holder’s open deployment without inventing another handover. Exercise and operational equipment remain separate. The return due date cannot precede the handover.
Return or recover the item, then inspect it
Returning an Issued item clears its holder and assignment links and moves it to Inspection. Recovering a Missing item follows the same inspection path. Neither action makes the item immediately ready to issue.
Inspection records the condition and permitted next state. Available requires Good condition. An item still Issued, Missing, or Retired cannot be inspected back into service through this action.
A defect report marks the condition Damaged. A held item keeps its custody; an unissued item moves to Repair. Reporting the defect does not erase who still has it.
Marking an item Missing keeps its holder and deployment links. Outstanding Issued or Missing items still linked to a deployment block final completion. Recovery, an appropriate transfer or return, or an approved loss must resolve the remaining custody.
Review a loss against the exact missing-item record
A loss request applies only to a Missing item. It needs a published, effective loss-review rule for the organization and a case reference. Operational property cannot use the exercise-only rule.
The reviewer must have loss-review authority and be different from both the request’s author and the holder. The decision must name the current request event; a changed item requires a new review.
Before approval, supporting files are checked again for release, access, and the saved hash. A changed or withdrawn file prevents approval against the earlier evidence.
Approval retires the item and clears its holder, deployment, incident, and team links. Returning the request leaves the item Missing. Every request and decision stays in the item’s history.
Approve a replacement, then issue a matching reserve item
A replacement starts with a held item whose condition is not Good. A missing item can qualify because its condition is Unknown. There cannot already be an unresolved replacement request.
Another person reviews the request. Approval does not itself hand over a new item. Fulfillment selects a different item in the same organization and category, then uses the normal issue checks.
The issued replacement uses the current holder and assignment links of the original item. A replacement that is unavailable or not in Good condition cannot bypass issue rules.
Fulfillment is recorded once. The original item still needs its own return, repair, recovery, or loss decision. A broader incident resource request can ask for equipment, but it does not replace this item-level custody record.
Reconstruct custody from saved events
The equipment view shows current custody and its supporting events. A historical report can reconstruct the item at an earlier cutoff, while a change report shows events within the selected period.
Report scope and protection still apply to the item and supporting files. A private file is not exposed just because the item is visible. Downloads check the reader’s access and the file evidence again.
Exercise equipment retains its separate use kind in reports. A saved report keeps its result at build time; later handovers appear in new reports instead of changing the earlier file.