The job list that quietly deleted its own work

A field operation I work with opened its follow-up list one morning and it was empty. Not caught-up empty. Wrong empty. Work that still needed doing had simply stopped showing, and nobody had touched it.

Here is what was happening. The list was built to look forward. Every item had a date, and once that date passed the item dropped off, whether or not anyone had actually done it. For a while that looked fine, because most of the dates were still in the future. Then enough time went by that every date was behind, and the whole list emptied at once. The work did not go anywhere. It just stopped being visible, which for a busy desk is the same as gone.

The lesson is small and it is worth a lot. A worklist should clear when the work is done, not when a date passes. Those are two completely different rules, and only one of them protects you. If your list drops items on a schedule, it will quietly lose the exact jobs that slipped: the ones that are late and most need chasing. The items you lose are never random. They are the ones already behind.

The fix was not a bigger date window. I rebuilt the list so an item stays until someone marks it finished. A late job now sits at the top looking at you instead of disappearing. It should feel slightly uncomfortable to see it there. That discomfort is the list doing its job.

While I was in there I found the other half of the problem. A large batch of records carried a start date that was really just the day everything had been imported. It was never a real date. It was an artifact, and the system had been treating it as fact. When a number is load-bearing, check that it means what you think it means before you build anything on top of it.

None of this is exotic. It is the difference between a list you can trust and a list that lies to you politely. If you run a field or route operation, look at whatever holds your follow-ups and ask one question: does an item leave this list because the work is finished, or because a date went by? If it is the date, you are losing work you cannot see, and your team is getting blamed for it.