Work through the decision
Review the unique deployment event, actual issue/use/return dates and receiver evidence. Record missing components, damage, repair needs and unresolved return quantities. A planned event or an elapsed date does not establish actual use. Update the next-use decision only after the appropriate returned-condition review, preserving the history for future campaigns.
A fictional worked example
In a fictional example, an event booking was cancelled and the equipment stayed in storage. The closeout records cancellation and does not increase reuse. A separate frame that returned damaged receives a repair task instead of being marked automatically available.
Evidence and authority limit
Completed-use records remain user observations within their scope; they do not themselves prove carbon savings.
Put it into practice
Close one fictional cancelled deployment and one observed use with a missing component.
Keep this record: Unique deployment closeouts, evidence references and next-use or repair actions.
- Planned and observed activity remain separate.
- Each use is counted once.
- Returned condition determines the next action.