Eight days after the interview, nothing. Twelve days after the application went in, no acknowledgement at all. The natural reading of that silence is that the answer is no and nobody wanted to say it. That reading is wrong often enough to be worth testing, and the test is a single short email.
The same silence looks entirely different from the receiving end, and both views are useful. Anyone who has handled a hiring round or a grant intake knows that a stack of submissions with no owner produces exactly this experience for the people in the stack, without a single decision having been made about any of them. Understanding why that happens makes it much easier to write a follow up that lands, and much easier to stop producing the silence if the shoe is on the other foot.
What the silence usually is on the other side
Four things account for most of it.
Nobody owns the submission. An application arrives in a shared mailbox. Three people can see it. None of them is responsible for it. Every one of them assumes somebody else has picked it up. This is the most common cause by a wide margin, and it is invisible from outside.
The decision is stuck one step above the person you dealt with. The hiring manager has decided. The budget holder has not signed off, is on leave, or wants to see two more candidates first. The person who interviewed you has nothing to say yet and has chosen to say nothing rather than say that.
The stated timeline was aspirational. "We should know by the end of next week" is usually a genuine estimate rather than a commitment, and estimates made before a process starts slip. The slip is rarely communicated, because whoever gave the estimate does not consider it news.
The process has no step for saying no. Many intake processes are built to move successful submissions forward and simply leave the rest where they are. Nothing is sent because nothing in the workflow triggers a send.
None of those four is about the merit of the submission. That matters for tone: a follow up written to overcome presumed rejection sounds defensive, and defensiveness reads as weakness in exactly the situations where it is least affordable.
How long to wait, by situation
The useful question is not how many days have passed but whether a real event has occurred that justifies a message. A stated date passing is an event. A week ending is not.
| Situation | Wait before the first follow up | Trigger to use |
|---|---|---|
| After a first interview | 5 working days, or 2 after any date given | The date they named |
| After a final interview | 3 to 5 working days | The date they named |
| Application with no acknowledgement at all | 7 to 10 days | The absence of any receipt |
| Quote or proposal sent to a client | 5 working days | Their own stated review timing |
| Document or form sent in for processing | 5 working days | The published turnaround time |
| Referral or introduction made on your behalf | 7 to 10 days | The referrer, not the target |
| Second follow up after no reply to the first | 7 to 10 days after the first | Nothing new needed, but say it is the last |
The most valuable line in that table is the second column of the interview rows. If a date was given, that date is the permission to write, and referencing it removes any question of whether the follow up is premature. "The panel mentioned decisions would go out this week" is a fact, not a nudge, and an email built on a fact is easy to answer.
Where no date was given, five working days after a first interview is the widely used floor, and there is a reason it sits there rather than at two. Most interview processes involve several candidates scheduled across more than a week, and a follow up sent before the last interview has happened arrives before anybody could possibly have an answer.
For an application that has produced no acknowledgement whatsoever, the calculation changes. That is not a decision pending, it is a submission that may never have arrived. Seven to ten days is long enough to rule out ordinary delay and short enough that the role or the round is probably still open.
The four parts of a follow up that gets answered
A follow up is not a shorter version of the original message. It is a different message with a different job.
A reference point that proves this is a continuation. The date of the interview or submission, the name of the role or the reference number, and the name of the person spoken to. This does two things: it locates the thread for a recipient who handles dozens, and it demonstrates that the sender has kept their own records straight.
One piece of new substance, if there is any. A relevant thing that has happened since, a link to something finished, an answer to a question that was left hanging in the room. This is what separates a follow up from a reminder. Where there is genuinely nothing new, do not invent it. An empty paragraph of enthusiasm is worse than two sentences of clarity.
One question with a closed answer. Not "any update?" but "is the decision still expected this week?" or "is the role still open?" An open question invites a reply that has to be composed. A closed question can be answered in four words on a phone, and four word replies are the ones that actually get sent.
A next step on the sender's own side. A stated intention to follow up once more in a fortnight, or a note that another offer is in play, or that the quote will be withdrawn on a date. This is what turns an item with no urgency into an item with some. It has to be true.
After a first interview
Subject: Following up, operations coordinator interview 15 September
Thank you again for the conversation on 15 September about the
operations coordinator role. The point about the intake backlog has
stayed with me, and the attached one page note sketches how the
current queue could be cleared in the first month.
Is the decision still expected this week, as mentioned on the day?
Happy to wait as long as the process needs. A short note either way
would be appreciated when there is one.
After an application with no acknowledgement
Subject: Application for the March intake, submitted 3 September
An application for the March intake was submitted through the
website form on 3 September, under the reference shown in the
confirmation screen.
No acknowledgement has arrived since. Could you confirm whether it
was received, and whether the round is still open?
If a different address or a different form is the right route, that
would be useful to know.
The last one
Subject: Closing this off, operations coordinator role
Two notes have gone out since the interview on 15 September, so this
is the last of them.
If the role has been filled or the search has paused, no reply is
needed and there are no hard feelings. If it is still live, the
interest here has not changed and a note any time in the next month
would be welcome.
That third one works because it is true and because it removes the social cost of a late reply. A surprising share of long silences break when the other side is offered a way to answer without having to apologise for the delay.
Two follow ups, then close the loop yourself
The purpose of a follow up is information, not persuasion. Once two messages have produced nothing, the information is in: this channel is not going to answer on a predictable schedule. Acting on that is more productive than a third attempt.
Closing the loop yourself means deciding what happens in the absence of a reply and proceeding. For a job search, that means the role moves to a dormant list and the week's effort goes elsewhere, with a single note in the calendar a month out. For a quote, it means the price expires on the date stated and the follow up said so. For a document sent in for processing, it means escalating through a different route, usually a phone number or a named individual rather than a shared mailbox.
There is one exception worth making. Where a specific future event is known, such as a hiring round that reopens in January or a grant cycle that runs twice a year, a note timed to that event is not a follow up at all. It is a new first contact with a reason to exist, and it tends to work far better than a third chase would have.
Where to send it, and what to put in the subject line
Channel choice is decided before wording, and getting it wrong wastes the message.
Reply inside the original thread when there is one and when the other side has written at least once. The attachments, the dates and the names are all there, and a recipient who searches for the role title later finds the whole exchange in one place. Where the only prior contact was a form submission and an automatic receipt, there is no useful thread to revive, so a fresh message with a descriptive subject line does more.
The subject line should contain the thing that lets a busy recipient route the message without opening it. That means the role or programme name, and the date of the interview or submission. "Following up" contains neither and is the subject line most likely to be skimmed past, because it describes the sender's activity rather than the reader's task.
Avoid sending the same follow up across two channels at once. A message on a professional network sent the same afternoon as an email reads as pressure, and it also makes the exchange harder for the recipient to keep together. Where a second channel is genuinely worth trying, use it after the email has been given time, and say in it that an email was sent, so the two do not arrive as separate demands.
One small practical point on delivery. If a follow up produces an automatic out of office reply, that is useful information about timing rather than a dead end. Note the return date and plan the next step around it instead of writing again in three days into an empty mailbox.
If the silence is coming from your side
The receiving end of this is fixable, and the fix is structural rather than a matter of discipline.
Silence at scale is almost always produced by submissions that have no owner and no status. When a form drops into a mailbox, there is nothing to look at that answers the question "which of these is waiting on us, and for how long?" Answering that question by reading down an inbox works for five submissions and fails at forty. The people in the stack then experience exactly the eight day silence described at the top of this page, and a proportion of them withdraw, follow up in frustration, or both.
Two changes remove most of it. The first is an acknowledgement that goes out automatically the moment a form is submitted, containing what was received and what happens next, with a date. That alone eliminates the largest single category of follow up email, the one that asks whether anything arrived at all. The second is giving every submission a named owner and a visible stage from the moment it lands, so that a submission sitting in one stage for nine days is something you can see rather than something the submitter has to point out. Tools built for handling responses after the form is sent treat that as the default rather than as a report to be run.
The knock on effect is smaller than expected on the inbox and larger than expected on the people waiting. A rejection sent on day ten costs one template and a click. Not sending it costs the goodwill of every applicant who is still checking, plus the time spent reading and answering their follow ups.
What to change first
If you are waiting, rewrite the question. Replace "any update?" with a question that can be answered yes or no, and attach it to a date somebody already named. That one edit does more than any amount of tone adjustment.
If the silence is coming from your side, start with the automatic acknowledgement and a visible stage for every submission, because those two remove the bulk of the follow up traffic before it is written. Seeing what that looks like on real responses takes a few minutes in the Halict demo.
Q1. How long should you wait to follow up after an interview if you have not heard back?
Five working days after a first interview is a sound floor, and two working days after any date the interviewer named. The date matters more than the count. If the panel said decisions would go out by Friday and Friday has passed, that passing is the reason to write, and referencing it makes the message impossible to read as impatience.
Q2. How many follow up emails should you send before giving up?
Two is enough in most cases, with the second one saying plainly that it is the last. A third rarely produces information the first two did not, and the effort is better spent deciding what happens in the absence of a reply. Keeping a note to make fresh contact when a known future event arrives, such as a round reopening, works better than continuing to chase the current silence.
Q3. Does a follow up email make you look desperate?
Not when it carries a reference point, one closed question and a stated next step. What reads as desperation is a message with no new substance, an apology for writing, or a third and fourth attempt at short intervals. A single message that references a date the other side named is ordinary professional correspondence, and most people on the receiving end treat it as such.
Q4. What should you do if there was never any acknowledgement of the application?
Treat it as a possible delivery failure rather than a decision, and ask two things: whether the submission was received, and whether the process is still open. Seven to ten days is a reasonable wait. If the form gave a reference number or a confirmation screen, quote it, because that is the detail that lets the other side find the record quickly.
Q5. How can a team stop generating this kind of silence?
Send an automatic acknowledgement on submission that states what was received and when to expect news, then give every submission a named owner and a visible stage. The first removes the follow ups that ask whether anything arrived, and the second makes a submission that has sat untouched for nine days visible to the team rather than only to the person waiting.