← All articles & guides
Practical guides

Lost and Found Log Template: The Fields Your Next Shift Needs

A useful lost-and-found log lets a colleague locate the object, understand its status and carry on the conversation. Whether you use a spreadsheet or software, give each item one stable reference and keep public information separate from private evidence.

The essentials

  • Use one row or record per physical item, with a unique reference.
  • Separate where it was found from where it is stored now.
  • Log claim and return events without overwriting their history.

Start with this item record

Use the following fields as a starting template. The example is synthetic and can be adapted to your venue’s terminology. Keep the actual register restricted to the staff who need it.

On a small screen, scroll the table sideways to see all columns.

Suggested lost-property register fields
FieldExampleWhy it matters
Item referenceLF-0042Connects the record, photograph and storage label.
Item descriptionNavy backpackHelps the team search consistently.
Date and time found17 Sep 2026, 14:20Records discovery rather than data-entry time.
Found locationLobby seatingHelps compare a claim with the discovery.
Current storageCabinet B, shelf 2Lets another shift retrieve the object.
Logged byStaff referenceIdentifies who can clarify the intake.
Private identifying detailsDistinctive interior markSupports ownership checks; do not publish.
Photo referenceLF-0042-photo-1Keeps images attached to the correct item.
Current statusAwaiting claimShows what needs to happen next.
Review dateDate set by venue policyPrompts a documented review of unclaimed property.

Use a separate claim and handover record

One item can attract more than one enquiry. Avoid squeezing every conversation into the description cell or overwriting the previous claimant’s details. Link each claim to the item reference and record the request date, private evidence, reviewer, decision and agreed next step.

For the completed return, record the handover date, staff member and collection or shipment reference. If the item moves to another desk before collection, log the transfer too. The current location should describe where it is now; the history should explain how it got there.

Define status labels before the team uses them

Choose labels with a shared meaning. “Found” can mean logged and stored; “claim under review” means ownership has not yet been confirmed; “ready for collection” means an approved return is waiting; “returned” means the physical handover has happened.

Do not use “closed” for every outcome. A returned item, a duplicate entry and a disposed item describe different events. Keeping them distinct makes later reporting more useful and avoids a colleague telling a guest that an item was returned when it was only archived.

Keep the register private and publish selectively

A staff register can contain evidence and contact details that should never appear in the guest catalogue. Do not share the whole spreadsheet as a public lost-and-found page. Publish an appropriate photo and description through a separate guest-facing view.

When photographing a bag or wallet, check for visible identity documents and labels. When recording a claimant, keep the information relevant to returning the item and use the venue’s retention process for the record.

Try a five-minute retrieval rehearsal

  1. Create a synthetic record and label a sample object.
  2. Ask a colleague to find it using only the register.
  3. Move it to another approved storage location and update the record.
  4. Add a test claim, review it and record a completed handover.
  5. Check that a third colleague can explain what happened without asking either of you.

If the process is becoming difficult to maintain across photos, sheets and messages, see six signs you have outgrown a spreadsheet. vFound combines the staff record with your own venue webpage so the public catalogue can stay separate from the private work.

About this article

Prepared by vFound, the photo-first lost and found platform for venues. Our guides explain practical workflows and the features available in vFound. Examples are illustrative, not customer case studies. Send a correction or question.