Remembering to follow up with people
Following up gets lost because the task is invisible until the moment you need it: nothing tells you three days have passed with no reply. Fix it by writing the follow up as its own task the same moment you send the original message or make the ask, with a specific date attached, rather than trusting yourself to remember who owes you a response.
Why follow ups disappear more easily than other tasks
Most tasks have something that reminds you they exist: a deadline, an object sitting in your field of view, someone asking about it. A follow up has none of that by default. You send an email, or ask a coworker a question, or leave a voicemail, and then the task, checking if they responded, has no natural moment to resurface. Nothing on your desk or your screen tells you three days have gone by with silence. Unless you build that reminder yourself, it simply does not exist until you happen to think of it, which might be a week too late.
Write the follow up when you send the original message, not after
The fix has to happen at the moment you send the original ask, not later, because later is exactly when the task stops being visible. The instant you send an email asking a vendor for a quote, add a task: "Check if the vendor replied about the quote, in 3 days." This takes ten seconds and it means the follow up exists somewhere it can resurface on its own, instead of depending on you remembering an email you sent among fifty others that week.
A worked example: three requests sent in one day
Say on a Monday you email a client for feedback on a proposal, ask a coworker in Slack for a document you need, and leave a voicemail for a supplier about a delayed shipment. Each of these gets its own follow up task the moment it is sent: "Check on client feedback, if none by Thursday," "Ping coworker again about the document, tomorrow morning if no reply," and "Call supplier again about shipment, Wednesday if I have not heard back." By Thursday, instead of trying to recall which of three people you are still waiting on, your list tells you directly, and you are not relying on a mental tally that started fading Monday afternoon.
If this, try that
If you keep following up too soon and seem impatient
Set the follow up date based on a reasonable response window for that kind of request: a same day Slack message might warrant a next morning check, while a formal proposal to a client might reasonably take a week. Writing the date when you send the original message, rather than when you start to feel anxious about the silence, keeps the timing consistent instead of driven by how restless you feel that afternoon.
If you never follow up at all and requests just die
This usually means the follow up task was never created in the first place, not that you are bad at following through once it exists. Make sending the follow up task a fixed habit attached to sending any request: the two actions happen back to back, every time, without exception, until it stops requiring conscious effort.
If you have too many people to track at once
Keep a single running list titled something like "waiting on," with each entry as a name, what you are waiting for, and the date you last checked. This is different from your regular task list; it is a reference you scan during a set weekly check rather than individual tasks scattered through your days.
If you follow up but never hear back at all
Two follow ups with no response at all usually means the answer is no, or the request has been deprioritized on their end, even if nobody says so directly. Send one final message setting your own deadline, something like "I will assume this is not moving forward if I do not hear back by Friday," and then treat the silence as your answer rather than continuing to wait indefinitely for a reply that may never come.
Keeping the follow up from feeling like nagging
A follow up sent on a predictable schedule, a few days after the original ask, reads as organized rather than pushy, especially compared to a burst of anxious messages sent whenever you happen to remember. If the person on the other end of a follow up is a family member rather than a colleague, the tone shifts but the mechanism does not: replacing reminders from your partner with a system you own covers the same idea from the other direction, when you are the one being followed up with. For requests where the wait itself is the hard part, not the follow up, how to use the hours before an appointment covers that adjacent problem.
Common questions
How long should I wait before following up on an email?
For most business requests, three to five business days is reasonable for a first follow up. Urgent items warrant a shorter window, a day or less, while a formal proposal or contract might reasonably wait a full week before a check in feels appropriate.
What should a follow up message actually say?
Keep it short and assume good faith: reference the original request, the date you sent it, and ask directly if they need anything else from you. There is no need to apologize for following up or over-explain why you are checking in.
Is there a way to track who I am waiting on without a spreadsheet?
A simple running list works fine for most people: one line per person, what you asked for, and the date, kept in whatever task app or notes app you already check regularly. A spreadsheet is only worth it once you are tracking a large number of open requests at once.
This article shares practical organizing ideas. It is not medical advice. For diagnosis or treatment questions, talk with a qualified clinician.