# Event equipment issue-and-return register

Event / date: ____  Register owner: ____  Version: ____  Approved storage locations: ____

Use one row per physical item or sealed kit. A planned booking is not proof of physical dispatch or return. Store this register with the operations team, not on a public event page.

## Baseline and movement

| Item/kit ID | Description and accessories | Owned by | Qty expected | Start location | Condition at issue | From → to / time | Released by | Accepted by | Return destination / due |
|---|---|---|---:|---|---|---|---|---|---|
| A01 | | Venue / organizer / supplier | | | | | | | |
| A02 | | | | | | | | | |

Add a new movement row whenever custody or location changes. For sealed kits, attach an accessory manifest. Access to each storage location is controlled by: ____.

## Return and exceptions

| Item/kit ID | Qty physically counted | Accessories counted | Actual location | Condition | Return receiver / time | Exception type | Follow-up owner / due | Resolution evidence |
|---|---:|---|---|---|---|---|---|---|
| A01 | | | | | | Missing / damaged / delayed / none | | |
| A02 | | | | | | | | |

[ ] Compare received against the dispatch baseline. [ ] Keep damaged gear marked and out of service under your team's process. [ ] Confirm supplier-owned items under supplier terms. [ ] Close exceptions only after evidence of physical return or other agreed resolution.

## Consumables (separate from returnable equipment)

| Supply | Qty issued | Qty used | Qty returned | Restock owner and target |
|---|---:|---:|---:|---|
| | | | | |

Final handback acknowledged by: ____  Date/time: ____  Open exceptions and next review: ____