“Black bag” is easy to write and difficult to act on. A useful description helps staff distinguish similar items, find the right record, and ask sensible questions when someone makes a claim. It should be specific without collecting unrelated personal information.

Describe what staff can observe

Start with the item category, approximate size, color, material, and visible identifying features. Add the date, time, and place it was found, using a location name another shift will recognize. Separate observations from assumptions about the owner.

For example: “Small navy fabric backpack, silver zipper pulls, frayed left strap; found beside lobby seating.” This is more useful than “probably belongs to a visitor.”

Separate public descriptions from claim details

If your team posts a found-item notice, keep that notice broad enough that a claimant can still describe a meaningful detail independently. The internal record can contain a distinguishing mark that is not repeated in the notice.

Do not publish a complete description and then treat someone’s repetition of it as proof. Use the organization’s established verification process, and record the basis for the decision without copying unnecessary sensitive information.

Keep the description connected to storage

A control number or QR label helps distinguish the record from similar entries. Attach labels in a way appropriate to the item, and keep small pieces together according to your team’s storage process. Record the current holding location.

  • Describe the item before placing it among similar property.
  • Check that the label opens the intended record.
  • Update the record if staff discover a useful new distinguishing detail.

For devices or documents, follow your organization’s handling rules. Do not search through private contents simply to make the description longer.

Review the record as a colleague would

Before closing intake, ask whether another staff member could select this item from several similar ones using the description. If not, add an observable feature rather than a guess.

When there is uncertainty, document it plainly: “Brand not visible” or “Found time reported by visitor; exact time unknown.” The record should show what staff know, what was reported, and what has not been established.

PUT IT INTO PRACTICE

Capture observable features, a reliable found location, a record identifier, and a storage location. Keep claim verification meaningful.

Bring your workflow to a demo ↗