Lost and Found Register Template for Operations

A cleaner hands a pair of headphones to reception. One shift puts them in a drawer; the next receives two enquiries about similar headphones. A note saying “black headphones, Tuesday” cannot establish which item was found, where it went or whether either person should receive it.

This lost and found register template links four records: the found item, the loss enquiry, each ownership claim and the custody history. It is designed for venue, facilities and front-desk teams handling ordinary personal belongings. The complete resource is below; copy the text into your approved document or record system. No download or specialist software is needed.

Set the operating rules before accepting entries

A register records decisions; it does not establish legal ownership or authorize disposal. Have the responsible policy owner approve the applicable holding, reporting, identification and disposal rules for your location. Do not borrow another venue’s deadlines. An elapsed review date is a prompt for a decision, not permission to give an item away.

Assign a desk coordinator to keep records complete, a custodian to control physical storage, and an authorized reviewer to decide disputed or exceptional claims. One person may perform several roles in a small venue, but record which role they are acting in. Name a backup for each role.

REGISTER SETUP — complete before use
Venue/site and register owner:
Coordinator / backup:
Storage custodian / backup:
Claim reviewer / backup and contact route:
Policy owner and approved policy/version reference:
Items accepted; excluded/special items and referral route:
Approved storage areas and access permissions:
Accepted ownership checks and proxy-collection rules:
Holding/review rules by item category and applicable authority:
Disposition approver and required evidence:
Record-access, evidence-retention and deletion rules:
Shift reconciliation time and discrepancy escalation route:
Review-response target and overdue escalation owner:

If a policy field is unresolved, record the blocker and obtain a decision before the affected action. For suspected hazardous, illegal or otherwise exceptional items, use the venue’s specialist reporting route rather than treating the ordinary register as handling instructions.

Copy the linked register records

Use a unique found-item ID such as F-2026-0042. Give loss enquiries and claims their own IDs. A person can report a loss before any item is found; never create a fictional found-item entry merely to complete a form.

Keep the report of a missing belonging separate from the physical item received. Record every claim decision, including refusal, without deleting the item’s custody history. The linked records below are a recommended operational design, not a universal regulatory form.

1. Found-item record: one entry per physical item or inseparable set

FOUND ITEM
Found-item ID:
Site; found location; found date/time/time zone:
Recorded date/time; recorder:
Finder name or staff reference; approved contact reference:
Category; ordinary description; visible condition:
Restricted distinguishing details / evidence reference:
Contents or components counted; sealed-package reference if used:
Received from / received by / receipt date-time:
Current storage reference; current custodian:
Policy category; policy/version reference:
Next policy review date-time; review owner:
Item status: Held / Claim review / Release authorized /
  Disposition review / Closed-returned / Closed-other
Location discrepancy: Yes / No; incident reference if Yes:
Linked enquiry IDs; linked claim IDs:
Last custody event ID:
Next action; owner; due date-time:
Outcome evidence reference; closure reviewer/date-time:

Required at intake: ID, found location and time (or an explicitly recorded estimate), description, recorder, receiver, storage, custodian and next action. Label unknown facts as unknown; assign someone to resolve them. Do not turn the finder into the presumed owner.

Keep enough distinguishing detail private to support a meaningful claim check. Store claimant contacts and sensitive evidence in restricted records under the approved policy, not on a public notice board. Do not enter passwords, payment-card numbers or unnecessary identity-document copies into this general log.

2. Loss enquiry: one report of something missing

LOSS ENQUIRY
Enquiry ID; received date-time; staff owner:
Claimant name; approved private contact reference:
Claimant's own item description and distinguishing details:
Reported loss location and approximate date-time:
Supporting information/evidence reference, if supplied:
Potential found-item IDs (blank if none):
Enquiry status: Unmatched / Possible match / Linked to claim / Closed
Next search/contact action; owner; due date-time:
Closure reason; claimant update date-time:

Capture the claimant’s description before disclosing restricted item details. A possible match is a lead, not an ownership decision. One enquiry may have several candidate items; keep them separate until a reviewer resolves the match. Close a duplicate enquiry by linking it to the retained enquiry, not by deleting the history.

3. Claim review: one claimant and candidate-item pair

OWNERSHIP CLAIM
Claim ID; enquiry ID; candidate found-item ID:
Claim received date-time; reviewer:
Ownership facts supplied before staff disclosed private details:
Approved check used; evidence reference; result and limitations:
Competing claim IDs or conflict: None / Details:
Collector: Claimant / Authorized proxy
Proxy authority reference and check result, if applicable:
Decision: Pending / More information / Approved / Refused / Withdrawn
Decision reason; reviewer; decision date-time:
Information requested; responsible person; response/review due:
Release authorization reference; approved collector and method:
Authorization restrictions or recheck conditions:
Claimant informed date-time; next action/owner/due:
Release event reference (blank until handover actually occurs):

Keep a refused claim without closing or discarding the found-item record. A later claimant may provide better evidence. Do not instruct staff to unlock a device or access private content to identify an owner; use the approved verification method and escalate uncertainty.

4. Custody and outcome history: append an event for every movement

CUSTODY / OUTCOME EVENT
Event ID; found-item ID; event type:
  Intake / Internal transfer / Release / Approved other outcome /
  Reconciliation / Correction
Event date-time/time zone; recorded date-time; recorder:
From custodian/location; to custodian/location:
Physical item ID and components checked; observed condition:
Sender acknowledgement; receiver acknowledgement:
Claim/authorization/policy decision reference, when relevant:
Delivery or collection method; receipt/tracking reference if applicable:
Discrepancy or failed handover; incident reference:
Next action; owner; due date-time:
Correction of event ID and reason, if applicable:

Preserve earlier events when correcting an entry. A transfer is not complete merely because somebody sent a message: the receiver must acknowledge the item. Until then, keep the last confirmed custodian and flag the pending movement. The UTSA lost-and-found procedure asks claimants to describe the property accurately and present identification. That is an institutional example of a release check, not a requirement to copy its identification rules or holding period into your own policy.

Apply status rules that prevent premature closure

A location discrepancy is a separate blocking flag, not a successful outcome. Freeze release instructions, notify the designated custodian/reviewer through the site’s incident route, and reconcile the last confirmed event. Never invent a return entry to make the count balance.

Worked example: similar belongings, different claims

Fictional example: At a conference venue, finder Maya brings black headphones to desk coordinator Alex at 10:20 on November 10, 2026, America/Chicago time. Alex creates F-2026-0042, records the hall and approximate find time, notes a private distinguishing mark, and hands the item to custodian Ren. Ren acknowledges storage at Locker-B/12 in event EV-201.

Enquiry E-0081 describes black headphones but supplies no distinguishing detail. Claim C-0101 remains More information; reviewer Sam asks for evidence by the venue’s next review point. The item remains in Claim review. Alex does not reveal the private mark to help the person produce a matching answer.

A second enquiry, E-0082, supplies a matching private detail and an earlier photograph. Sam assesses both claims under the venue’s approved method, records why C-0102 is Approved and why C-0101 is Refused, and informs both claimants appropriately. The found item is now Release authorized—not Closed-returned.

At collection, Ren checks the collector against the authorization, confirms the same item and components, and records the recipient’s acknowledgment under event EV-202. Alex links that event to C-0102, reconciles the empty storage slot and changes the item to Closed-returned. The refused claim stays linked. If the second person had not arrived, the item would still count as held.

Reconcile each shift and review the right counts

1. Outgoing coordinator: list all open physical items, pending movements, unresolved claims and actions due before the next handover.
2. Receiving custodian: compare item IDs and storage positions with the physical items. Record the count and discrepancies; do not expose private ownership evidence in a shared handover sheet.
3. Incoming coordinator: accept the action list, owners and deadlines. Escalate missing items or unknown custody to the designated reviewer immediately under the site procedure.
4. Reviewer: decide unresolved claim conflicts and policy-review cases. Record a named next action rather than leaving “follow up” as the only instruction.

Use these definitions for a manual summary or an approved reporting tool. They are proposed operating measures, not claims about performance improvement:

• Open physical items: count distinct found-item IDs not in Closed-returned or Closed-other. Count an inseparable set once if that is how it was registered.
• Unmatched enquiries: count enquiry IDs with status Unmatched. Do not add these to physical inventory.
• Pending claims: count claims marked Pending or More information. Several claims against one item are several claims but only one physical item.
• Overdue actions: count incomplete actions whose due time is earlier than the current time in the recorded time zone. Report missing due dates separately as incomplete data.
• Custody discrepancies: count open item IDs whose discrepancy flag is Yes; track the oldest unresolved event as well as the total.

In the worked example, before handover there is one open physical item, not two because two people claimed it. After the acknowledged return, that count becomes zero. A refused claim is a resolved decision, not an additional physical item or a returned belonging.

Adapt the resource without weakening the checks

For several sites, prefix IDs by site and record sending and receiving custodians for transfers. Keep the original found-item ID when central storage takes over; add a local reference rather than creating an unrelated second item. Separate public-facing descriptions from restricted matching details.

For proxy collection or shipping, use only methods allowed by the approved policy. Record the authorization, destination check, recipient and handover evidence that the policy requires. A courier tracking number alone does not prove the ownership claim was valid. Keep any delivery dispute open with an owner.

For a bag containing several items, record the approved inspection/counting method and whether contents are one set or individually registered. If records are split, link parent and child IDs and make the counting rule explicit. Never count both a container and all its registered contents as separate unresolved cases without explaining the metric.

Do not use this register for issuing company equipment. The asset handover form addresses known company-property transfers; this resource addresses found personal belongings and uncertain ownership.

Where Workhint fits

Workhint’s Workflow Engine describes routing approvals to defined roles and requiring details, files or notes before work progresses. Those building blocks are relevant to a desk-to-reviewer claim handoff.

The Workflow Automation Software solution describes configuring structured forms, review stages, owners and next actions. A team could use this register as a requirements brief for intake and claim-review configuration while keeping physical custody under its venue procedure.

Validate the proposed record links, permissions, history, reminders and closure checks before relying on a configuration. These pages do not establish automatic ownership verification, device inspection, courier integration or compliance with local lost-property law. The inline register remains usable independently of Workhint.

FAQ

Is a lost-item report the same as a found-item record?

No. A report describes something a person cannot find; it may never match an item in storage. A found-item record starts with physical receipt. Link them through a claim without treating a possible match as a verified owner.

How long should items be held?

Use the rules approved for your location and item category. This template deliberately supplies no universal holding period. The policy owner must resolve the applicable requirements and authorize any later disposition.

Can the finder collect an unclaimed item?

Do not infer an entitlement from an empty claimant field or an elapsed date. Record the request and obtain an authorized policy decision before any handover.

What if staff approve a claim but cannot find the item?

Flag a custody discrepancy and stop the release step. Reconcile the last acknowledged movement, assign an incident owner and keep the item open until its actual location or authorized outcome is established.