Someone is waiting for a customer approval. Someone else needs a supplier reference. A third person has already asked for the same attachment twice. None of those problems looks large enough to deserve a system. Together, they can keep an entire week from moving.
Incomplete information becomes expensive when nobody can see the difference between work that is progressing and work that is quietly waiting. A small exception list makes that difference visible.
You do not need to copy every email into another spreadsheet. Record the item that cannot move, the exact detail it needs, the person responsible for obtaining it, and the date of the next follow-up. Link to the original record instead of maintaining competing versions.
For example, “waiting on customer” is too vague to help a colleague. “The customer needs to approve the revised delivery address. Jordan will follow up Tuesday” gives someone enough context to act.
Shared visibility is useful. Shared responsibility without a named owner usually produces more waiting. The owner of the follow-up does not have to be the person who supplies the answer. They are the person making sure the question reaches the right place and someone records the result.
Agree on a backup when the owner is away. This matters most for work with a customer commitment attached. A list should make coverage easier, rather than becoming another file that only one person understands.
Constant checking can consume more time than the original task. Set a review rhythm that fits the urgency of the work. A time-sensitive service request may need daily attention. A routine missing attachment may fit into a twice-weekly review.
At each review, decide whether to follow up, move the item forward, escalate a decision, or close it. Avoid changing the next review date simply to make the list look current. A changed date should reflect a real decision.
If the same information is missing repeatedly, the problem may be the way work enters your business. Perhaps the request form never asks for the reference number. Perhaps the approval email links to an outdated document.
Count recurring causes for a few weeks. Then fix the most common one at the source. Add a required question, clarify the instruction, or show an example of a complete request. The point of an exception list is to reduce exceptions over time.
Remove resolved items from the active view while keeping the history your team needs. Separate genuine waiting from work that still needs an owner. Those are different problems and need different decisions.
Start with five current items your team keeps asking about. Write the missing detail, next owner, and follow-up date for each. At the next meeting, use that list instead of rebuilding the conversation from memory. You will know the routine is working when people spend less time asking what happened and more time taking the next useful step.