A rider leaves a laptop on a bus at the end of the evening peak. She calls the customer service line the next morning. The agent checks the shared spreadsheet and finds nothing. The laptop is on a shelf at the garage, in a bag with a paper tag. Nobody at the garage has typed it in yet. The rider hears "we will call you if it turns up," and that call never comes.
Most agencies run lost and found with some version of this setup. It works on a slow day with one clerk who remembers everything. It fails when volume grows, shifts change, or items move between locations. This post looks at where the usual process fails and what a stronger process looks like.
How lost and found usually runs
The details vary from agency to agency, but the parts are familiar.
- A found-item log. Often this is a shared spreadsheet. Sometimes it is a paper binder at each garage. Operators turn items in at the end of a run, and a clerk writes them down when there is time.
- A shelf or a bin. Items stay at the garage where the bus pulled in. Valuables may go to a locked cabinet or a central office.
- Rider reports by phone. The rider calls the main customer service number. The agent writes the report in a call note, an email, or a second tab of the spreadsheet.
- Calls back and forth. The agent calls or emails the garage. The garage calls back later. The agent then tries to reach the rider. Each step waits on another person.
Where the process breaks
The report and the item live in different places
The rider calls the call center. The item arrives at the garage. These two facts sit in two records, and nobody compares them on a schedule. A match happens only when one person sees both by chance. In a busy week, nobody has time to look.
The descriptions do not agree
Riders and operators describe the same item in different words. A rider reports a "dark backpack with a laptop inside." The operator logs a "black bag." A search for "backpack" in the spreadsheet misses it. A clerk who reads every row can catch this. That approach stops working as the log grows.
Nobody owns the rider's report
A found item has a physical home. A rider's report often has no home at all. It sits in a call note with no owner and no follow-up date. If the item arrives two days later, nothing prompts anyone to call the rider.
Items reach the end of the hold period unclaimed
Most agencies hold found items for a set period and then dispose of them. With an incomplete log, an item can reach that date while a matching report sits open elsewhere. The agency then donates or discards an item that a rider asked about. Riders remember that outcome.
Nobody can answer basic questions
How many items came in last month? How many went back to their owners? How long did riders wait for an answer? A spreadsheet answers these questions only if every location filled it in the same way. In practice, each location has its own habits.
What a better process looks like
A better process does not need more staff. It needs a clear structure that every location follows.
- Keep one record for the rider's report. Capture the item type, color, brand, and any marks. Add the route, direction, approximate time, and a way to reach the rider. Take the report the same way for phone, web form, and email. Give the report an owner and a status.
- Keep one record for each found item. Log the item when it reaches the garage, not at the end of the week. Record the vehicle, the route, and the current storage location. Put a tag number on the item that matches the record.
- Compare the two sets of records every day. Check each new found item against every open report. Check each new report against the items on hand. Compare several fields, not one keyword, so different descriptions can still match.
- Confirm ownership before release. Ask the rider for a detail that the public description leaves out, such as the contents of a bag. Record who picked the item up, and when.
- Tell the rider what happened. Contact the rider when a likely match appears. Contact the rider again if the report closes without a match. A short "we did not find it" message is better than silence.
- Set a retention and disposal rule. Decide how long each class of item stays, and what happens next. Give IDs, cash, and devices with personal data their own rules. Write the rule down, and log each disposal against the item record.
The last step protects the agency as much as the rider. When a rider asks about an item months later, the record shows what happened to it and why.
Small changes that help right away
Not every agency can change its whole process at once. These steps help even with a spreadsheet.
- Use a short, fixed list of item types, such as bag, phone, laptop, keys, wallet, and clothing. Free text alone makes searches unreliable.
- Ask operators to note the route and block when they turn in an item. That detail narrows a search quickly.
- Give each rider a reference number when they report a loss. The rider can then follow up without telling the whole story again.
- Pick one person to review open reports each week. That person closes old reports and sends each rider a short message.
- Count items returned, not only items logged. The return count shows whether the process works.
Lost and found is also a feedback channel. A rider who never hears back sees the same failure as an unanswered complaint. We cover that problem in Closing the Loop: Why Riders Stop Sending Feedback.
Where Pulse Feedback fits
Pulse Feedback handles lost and found in the same system as complaints, commendations, and inquiries. Riders report lost items through the agency's rider portal. Drivers and staff log found items. Pulse Feedback scores every found item against every open lost report automatically. Staff review the top matches instead of reading every report. The matching works even when descriptions differ, such as a rider's "dark carrying sleeve" and a driver's "black neoprene sleeve."
To see the match screen, visit the Pulse Feedback page or contact us for a demo.
