An Airtable lost-and-found workflow can give venue staff one place to record found items, review claims and document collection. Use a miniExtensions Form to collect a claimant’s description without exposing the private details that staff need to assess the claim. A matching response is a reason to investigate, not proof of ownership.
Consider fictional Westbridge Arts Centre. Staff find a black bag after an evening workshop. Three people contact reception about missing bags that week. A shared inbox makes it difficult to know which claim was reviewed, what was actually established and whether an item has already been collected.
Separate the item from each claim
Create a Found items table with Item reference as autonumber, Found date as date, General area as single select, Item category as single select and Public summary as text. Keep Distinguishing details, Storage location, Staff notes and any detailed photographs in staff-only fields. Suggested item states are Held, Collection arranged, Returned and Closed under retention policy.
Create a separate Claims table with Claim reference, Submitted time, Claimant name, Contact email, Approximate loss date, General area and Claimant description. Add a staff-managed link to Found items, Review owner, Review state and Decision note. Several claims can refer to one item, and a claim can remain unmatched while staff investigate.
Finally, use Collection records for the linked item, approved claim, staff member, actual handoff time and outcome. These tables are a proposed operating model, not a built-in ownership-verification system. Avoid storing copies of identity documents or sensitive contents merely because an attachment field is available.
Ask claimants to supply the identifying detail
Connect a miniExtensions Form to Claims. Ask the person to describe what they lost in their own words, including useful distinguishing features. Explain that staff will review the information and contact them using the supplied address. Do not promise an immediate match or tell the person where held items are stored.
For a standalone form without a Login/Lookup page, configure Share to allow new records and disable updates to existing records. The creation and editing documentation distinguishes these controls from child-form and login workflows. Keep the staff-only item link and review fields out of the claimant form.
For the black bag, the form might ask about its contents or an unusual marking without revealing the answer. Tell people not to submit passwords, payment-card numbers or unnecessary personal documents. Let the reviewer decide whether further information is needed through the venue’s usual process rather than collecting everything up front.
Publish only a deliberately limited notice, if needed
A public notice is optional. Reception may prefer to accept claims without publishing an inventory. If notices are useful, create a dedicated Public notices table containing only approved summaries such as “Bag found near the workshop rooms this week,” a public reference and contact instructions. Staff deliberately copies the limited description into that table.
A miniExtensions Interface can display information without login, but everyone using it sees the same data. That behavior is described in the Interface documentation. Do not use it for private claims. Make the public notice surface read-only and inspect every expandable or linked record, not just the visible list.
Never publish the exact unusual marking, bag contents, claimant contact details or storage shelf. Those details would make unsupported claims easier and expose information unnecessarily. A public reference is a routing aid, not an ownership credential. Remove or update the notice when the underlying item is no longer available.
Give a named staff member the review decision
Reception reviews new claims in Airtable, compares the supplied description with held items and assigns an owner. For the fictional bag, one claimant mentions a distinctive stitched patch that staff recorded privately. The reviewer links that claim to the item and follows the venue’s established ownership-check procedure before approving collection.
Keep review states explicit: New, More information needed, Approved for collection, Not substantiated and Withdrawn. Record a concise factual reason for the decision rather than speculation about the claimant. The status does not automatically send an email; the assigned reviewer communicates the next step through the normal contact channel.
If two credible claims concern the same item, pause the handoff and escalate to the responsible manager. Do not award it to whoever submitted first. Separate “we found a possible match” from “we approved this person’s collection,” and retain the unresolved claim rather than overwriting it with another person’s details.
Record the actual handoff, not just an appointment
An agreed collection time is not evidence that an item was returned. At reception, staff completes the required check, confirms which physical item is being released and records the actual outcome. Only then should the item move to Returned. A missed appointment remains an open collection arrangement until staff decides what happens next.
Use the venue’s existing rules for retention, disposal and special items. This workflow does not establish legal ownership, authorize disposal or replace the procedures for documents, hazardous objects or matters requiring authorities. Keep access to claims limited to staff who need it and review retention of claimant information separately from item storage.
Check the boundaries before accepting real claims
Try fictional cases for an unmatched claim, two claims against one item, a withdrawn claim, a failed collection and an item already returned. Inspect the public form and any notice page as an unauthenticated visitor. Confirm that no private distinguishing detail, claim or storage location is reachable through linked records or alternate views.
These are proposed checks, not tests performed for this article. The practical outcome is an accountable chain from found item to reviewed claim to physical handoff. The system organizes staff judgment; it should never turn a plausible form submission into automatic permission to release property.

