On this page
A weekly executive follow-up sweep that prevents silent stalls

An executive asks a vendor for a revised proposal on Monday. The assistant sends the request, the vendor replies that they are working on it, and the thread goes quiet. Three weeks later the executive asks why the proposal never arrived.
A weekly follow-up sweep catches that stall. It is not a reminder service and it is not a second inbox. It is a short pass over the threads that were sent, answered, or promised, with a clear next action for each one.
Sweep the sent folder, not just the inbox
The inbox shows what arrived. The sent folder shows what the executive is waiting for. Search sent mail for requests from the last three weeks and check whether each one received a substantive reply.
A reply that says "working on it" is not a resolution. It is a promise, and it belongs on the follow-up list with a date.
Define what counts as open
A thread is open when the executive still needs something from it: a document, a decision, a confirmation, or a date. A thread that was answered but needs no action is closed, even if the last message was brief.
Write the definition down so two assistants sweep the same way. Without it, one person closes a thread when the reply arrives and another leaves it open for a month.
Give every open thread an owner and a date
Each row in the sweep needs the counterparty, the request, the date it was sent, the last response, and the next action. The owner is the assistant or the executive, depending on who can move it.
The date is the trigger for the next contact. A row without a date will be swept again next week and look the same, which is how a stall becomes invisible.
Escalate on the second silent week
One reminder is normal. Two silent weeks is a signal. At that point, the assistant should escalate to a second contact at the counterparty or tell the executive that the request is stuck.
A third identical reminder rarely changes the outcome and trains the counterparty to ignore the first two. The sweep should include an escalation path, not only a reminder template.
Close threads that resolved elsewhere
Many stalls are false. The answer arrived in a call, a chat, or a meeting, and the email thread was never closed. The sweep should check those channels before sending another reminder.
Record how the thread closed. That note prevents a future assistant from reopening a question that was already answered and makes the sweep faster next time.
Who owns the sweep
The assistant usually owns the sweep, but the executive owns the relationship. When a counterparty is senior or sensitive, the assistant should prepare the reminder and let the executive send it.
Record who sent the follow-up. A sweep that always writes in the executive's voice can damage a relationship when the message is poorly judged.
When the executive is the blocker
Some threads stall because the executive has not provided the decision or the document. The sweep should surface those rows to the executive with a clear ask, not send another reminder to the counterparty.
Separate "waiting on them" from "waiting on us" in the row. The distinction changes the action and prevents a misleading reminder.
Tone of the reminder
A good reminder is short, specific, and easy to answer. Restate the request, the date it was sent, and the date needed. Do not imply blame or add a long history.
Offer a way to close the thread if the request is no longer relevant. A counterparty who can say "we no longer need this" will reply faster than one who has to explain a delay.
Tracking without a new tool
A label in the mail client or a small shared sheet is enough. The sweep does not need a new platform, and a heavy tool will be abandoned during a busy week.
Use the same fields every week and keep the list to one screen. The value is the routine, not the software.
A worked example
A vendor proposal is requested on the second, acknowledged on the third, and silent after that. The sweep on the ninth shows no substantive reply, so the assistant sends a short reminder with the decision date.
On the sixteenth, still no reply. The assistant escalates to the account manager and tells the executive the request is stuck. The proposal arrives on the eighteenth, and the thread closes with a note. The sweep did not create urgency; it made the stall visible before the deadline.
Keep the list short enough to work
A sweep that produces eighty rows will not be actioned. Limit it to threads where the executive is genuinely waiting and the date has passed or is about to pass.
Everything else stays in the normal mail flow. The sweep is a safety net for commitments, not a full review of correspondence.
Review the pattern monthly
Look at the threads that stalled for more than two weeks. A cluster with one counterparty is a relationship or process issue; a cluster in one topic is a workflow issue.
Share the pattern with the executive in one line. It helps them see which requests need a different route, and it shows the value of the sweep beyond the individual reminders.
A note on shared inboxes
When the executive's mail is delegated, the sent folder may live in a shared mailbox. The sweep should include the delegated account, not only the executive's personal mail.
Check that the assistant has access to the account the request was sent from. A sweep that misses a delegated account will leave the most sensitive threads out of the review.
When to stop
A thread that has had two reminders and no reply should leave the weekly list and move to an escalation list. Keeping it in the sweep produces the same row every week and hides the lack of movement.
Record the escalation and the date. The thread is still open, but the next action belongs to a different person.
What the sweep does not do
The sweep does not replace the executive's own follow-up on sensitive relationships, and it does not chase every open question in the organisation. It covers the commitments the executive made or received.
It also does not judge whether the request was reasonable. That is a separate conversation. The sweep's job is to make sure the request does not disappear.