Community Event Lost Property Log and Handoff
Set up a lost property log for a tournament or community event: separate missing-item reports from found items, track who holds what, and hand off cleanly to the venue.
Contents
Keep two separate records: one for items people report missing and one for items volunteers actually find. Connect them only through a possible-match note that someone checks. Then track who is holding each found item at every moment, who answers follow-up questions, and whether a return has actually happened. An item counts as returned only after a completed handoff to its owner, not when a match looks likely and not when the event team passes the item to the venue.
This guide covers the organizer workflow for amateur tournaments and community events: what to record, how to move an item from report to return, and how to hand open cases to a venue contact when your team leaves. Decisions about storage, privacy, claimant checks and how long you keep records are yours to set with your venue and any governing body. Settle them before the event rather than at the lost-and-found table.
Why reports and finds belong in separate records
A missing-item report is a claim that something is gone. A found-item entry is a fact that something is in your hands. If both go on one list, a volunteer can easily mark a reported phone as found when the phone in the box is someone else's. Convite's guide to lost items after a party separates four situations: a missing-item report, a confirmed find, a possible match still waiting to be checked, and a completed return. That separation works well at events because it stops guesses from turning into recorded facts.
What to record
Xenia's lost-and-found log template, written for short-term lodging, records an item description, contact information, the date and location of discovery, and the actions taken. The record is updated as inquiries come in and as returns progress. Those fields work at events too. You do not need the lodging setup around them. The two tables below are an example layout built from those ideas.
| Report record (one row per missing-item inquiry) | |
| Field | What goes in it |
| Report ID | A short code such as R01, R02 |
| Received time | When the inquiry reached your team |
| General description | Kept general enough that the owner can still confirm details later |
| Last-known place and time | Where and when the person last had the item |
| Contact reference | How to reach the person, stored according to your privacy decision |
| Follow-up owner | The volunteer or lead responsible for this inquiry |
| Found-item record (one row per item in hand) | |
| Field | What goes in it |
| Item ID | A short code such as F01, F02 |
| Description | What the item is |
| Found place and time | Where and when it was picked up |
| Current holder | The person or desk physically holding it now |
| Custody location | Where it is stored, for example the bin at the registration desk |
| Status | Held, possible match, returned, or handed to venue |
Add a separate possible-match field that links a report ID to an item ID, for example R08 ↔ F03. Keeping the link in its own field means you can delete a wrong match without changing either original record.
How an item moves from report to return
- 1. An inquiry creates a report entry. Do not touch the found-item record yet.
- 2. A confirmed discovery creates a found-item entry with its current holder and storage location.
- 3. When a report and a found item plausibly describe the same thing, record a possible match and name who will check it.
- 4. The designated person runs the claimant check you agreed on in advance before anything is released.
- 5. Change the status to returned only after the handoff to the owner is complete. Note the time and who released the item.
Convite's guide recommends deciding ahead of time who handles inquiries and who is allowed to release items. At a tournament, that usually means one named lead per shift or one fixed desk. Without that, the person who answered the original question is not the person holding the bin. In the same spirit, tell claimants only about collection arrangements the current holder of the item has agreed to. Don't promise a pickup time at the venue office unless the venue office has agreed to it.
Handing off open items when the event ends
Teardown is where items get lost a second time. Before your team leaves, write a handoff line for every unreturned found item and every open report. Convite's guide advises keeping confirmed facts separate from open questions during a handover, so the person taking over knows what is certain and what still needs checking. A simple format:
Item ID | Outgoing holder | Receiving holder or venue contact | Transfer time | Receiver acknowledged | Next inquiry contact | Unresolved action
F03 | Registration lead | Venue front desk | 18:40 | Yes | Volunteer lead | Check against report R08
Moving an item to the venue changes its current holder. It does not change its status to returned. Open reports also stay open, and someone still needs to own follow-up. If inquiries should still come to your team after the venue holds the item, say so in the next-inquiry field.
Example: one scarf, two records
This is a made-up example. A parent reports a blue scarf missing during the afternoon round, which is logged as R08. Separately, a volunteer finds a blue scarf near the bleachers, and it goes to the venue desk, logged as F03. Someone links R08 and F03 as a possible match and assigns the desk contact to follow up. The event team packs up before the parent comes to collect it, so they record the transfer of F03 to the venue desk and name who will field further questions. F03 stays marked as handed to venue, not returned, until the desk confirms that the parent has picked it up and passed the agreed check.
Decisions to settle before the event
- Storage: where found items are physically kept and who has access.
- Claimant check: what a person must describe or show before an item is released, and who performs the check.
- Contact information: who can see claimants' phone numbers or emails, and where that information lives.
- Valuables: whether cash, phones, keys or ID go straight to the venue or a designated lead instead of the general bin.
- Retention: how long unclaimed items and the log itself are kept, and what happens afterward.
- Venue and local rules: confirm with the venue whether it has its own lost-property procedure or requirements you must follow.
These are organizer and venue choices. A lodging template or a printed log book can supply useful fields, but it does not set the rules for your event. Where a venue policy, league rule or local requirement applies, it takes precedence over your worksheet.
Related articles
Plan a Community Event Information Desk Enquiry Workflow
Build an information desk enquiry workflow for a community event or tournament: desk reference sheet, enquiry log template, referral steps and a printable desk copy.
Plan and Maintain a Community Event Attendee FAQ
Build an attendee FAQ from approved event information, with a named owner for each answer, publication approval and clear triggers for rechecking.
Prepare a Community Event Committee Handover
A practical handover template for community event and tournament committees: what to record, how to transfer each work area, and how successors confirm ownership.
Define Roles and Responsibilities for a Community Event Committee
A practical way to assign committee roles for a community event or amateur tournament: name an owner for every deliverable, set approval authority, map dependencies and agree when changes get reviewed.
Specify the Information and Presentation for an Event Ticket
Build a ticket design brief for your tournament or community event: confirm the required details, set a clear visual hierarchy and lock down print or digital output needs before design starts.
Compare Volunteer Management Software Against Event Requirements
Compare volunteer management software against your event's real needs with a requirements worksheet, scripted demo tests, like-for-like pricing and fair scoring.
Plan a Community Cleanup Event
A practical guide to planning a community cleanup: define the purpose and area, assign named owners, confirm collection arrangements and send participants a clear, final plan.
Plan Waste Collection and Cleanup for a Community Event
A step-by-step plan for community events and amateur tournaments: reduce materials, map collection points, assign volunteers and close out cleanup with confirmed collection.
Coordinate Community Event Accessibility Requests
A practical template for collecting, answering and confirming accessibility requests at community events and amateur tournaments, with restricted tracking and clear delivery owners.
Plan Accessibility Across a Community Event
An event accessibility checklist for community events and amateur tournaments: build an accessibility plan from publicity to arrival, venue, activities, vendors and emergencies.