Most dropped balls are things you asked someone else to do and then trusted would happen. Here are four ways to catch the silence, and how to pick the right one.
By the Loop team · Updated September 10, 2026 · 6 minute read
The short answer: every email that asks someone for something needs a due date and a place you’ll see it again. A label or flag handles light volume. A spreadsheet handles a team that needs a shared view. A BCC tracker handles both without extra typing, because the act of sending the email is what logs it.
An open ask has no natural reminder. Your inbox shows you what arrived, and a request you sent sits in Sent where nobody looks. If the other person goes quiet, nothing happens. That silence is the whole problem, and every method below is a different way of turning silence into something you notice.
In Gmail, create a label called Waiting and apply it to sent emails that need a response. Check the label each morning. You can also snooze the sent message so it returns to your inbox on a chosen day.
Outlook lets you flag a sent message with a due date. Flagged items show up in To Do, so they sit next to your other tasks.
A sheet with columns for the ask, who owes it, date sent, and due date gives a team one list everyone can see. It’s the fastest way to get visibility across people.
Tools like Loop give you an email address to BCC when you send a request. The tool records the ask, sets a due date, and reminds you if nobody responds. Loop also closes the item automatically when the recipient replies on the thread and sends one digest each morning.
| Method | Works best for | Where it breaks |
|---|---|---|
| Inbox labels or snooze | A few asks a week, just you | Nothing reminds you when a reply never comes |
| Flags and to-do integration | Outlook users who live in their inbox | Flags pile up and go stale; hard to share |
| Spreadsheet | Teams that need a shared list today | Someone has to type every row and update it |
| BCC tracker | Frequent asks, teams, anyone away from a desk | You have to remember the BCC (save it as a contact) |
Whatever tool you use, the pattern is the same. Give every ask a date at the moment you send it. Look at open asks once a day, at the same time. When you nudge, reply on the original thread so the history stays together. When something is answered, close it right away so the list stays honest.
Pick one place every open ask goes, and a daily moment you look at it. For a few asks a week, a Gmail label or Outlook flag works. Once you're past a handful a day, or other people need to see the list, use a BCC tracker that sets due dates and closes items when people reply.
Three business days is a sensible default for most work requests. Use one or two days for anything time-sensitive, and a week for large asks like proposals or legal review.
Yes. BCC-based trackers such as Loop only receive the emails you copy them on. They never connect to Gmail or Outlook.