Reviewed: 9 October 2026. Interview follow-up should use the employer's stated channel, the actual conversation and the current application status. This guide contains original practice messages. No messages were sent, and no response or selection outcome is implied by a draft.
Record the next step before choosing a follow-up
Ask who will communicate the outcome, what happens next and whether an expected response time can be shared. Note any request for supplementary material and the appropriate channel. An employer's specific instructions are more useful than a fixed calendar rule copied from another hiring process.
Harvard's interviewing guidance supports asking about next steps and expected response and recommends a thank-you email within 24–48 hours. Treat that as institutional guidance, not a universal mandatory deadline or evidence that a message increases your offer probability.
A useful record separates a promised update from an estimate and a request from an approval. “The recruiter expects an update next week” is not the same as “I have been selected.” Positive interview feedback does not change that distinction.
Work from one complete original interview record
All people, roles and dates in the following case are fictional. Tara interviews for a documentation-support role on 12 October 2026. The recruiter asks her to use the existing email thread for any follow-up. The interviewer says the team expects to provide a status update by 19 October and asks for a short, non-confidential example of how she checks document versions.
Tara has an original practice example she created herself. It records a draft labelled version one and an approved version two, with a fictional date correction. It contains no employer files, interview test questions or personal data. The work location remains unresolved. No offer has been issued.
The case record is:
| Field | Supplied fictional information |
|---|---|
| Interview | 12 October, documentation-support role |
| Channel | Existing recruiter email thread |
| Expected update | By 19 October |
| Requested material | Short non-confidential version-checking example |
| Unresolved point | Work location |
| Current status | Interview completed; outcome pending |
The table is not a live application. Its dates support the practice sequence rather than setting a general timetable for Indian employers.
Write a complete thank-you and requested-material message
An original message could read:
Subject: Documentation-support interview — Tara
Dear Recruitment Team,
Thank you for discussing the documentation-support role with me
on 12 October. The conversation helped me understand the emphasis
on checking document versions before handing them over.
As requested, I have attached a short original practice example.
It uses fictional records and distinguishes a draft from an approved
version. It does not contain a previous employer's materials.
I understand that a status update is expected by 19 October and
that the work location is still being confirmed. Please let me know
if you need further information from me.
Regards,
Tara
Attachment: Original version-checking practice example
Use “attached” only when the correct file is actually attached. If you have not prepared or checked the file, say what is pending instead of retaining that sentence. A promised document and a supplied document are different states.
The message summarises the conversation and requested evidence. It does not say Tara is a perfect match, that the location is agreed or that she will join. It also follows the requested channel rather than contacting other employees through guessed addresses.
Follow the communicated timeline when requesting status
Suppose the fictional expected update date passes and Tara has received no update. She can ask through the same thread:
Dear Recruitment Team,
I am following up on the documentation-support interview on
12 October. We discussed an expected status update by 19 October,
but I have not received an update yet.
I remain interested in the role. Could you let me know whether
there is an updated timeline or anything further you need from me?
Regards,
Tara
This is a status request. It does not demand an immediate offer or infer rejection from silence. It states the date as an expectation discussed in the supplied case, not a contractual promise.
If no date was discussed, change the wording: “Could you share the expected next step or response timeline?” Do not invent a missed deadline. If the employer requests no follow-up through a particular channel, respect that instruction and use the permitted process.
Change the plan when a real update arrives
Now suppose the fictional recruiter replies: “The review is continuing. We expect an update by 23 October.” Tara should record the new expectation and stop using the old date as if the team had provided no information.
A brief response is: “Thank you for the update. I have noted the revised expected timeline. Please let me know if you need anything further from me.” The application remains pending. A timeline update is not a shortlist, offer or acceptance.
Avoid automatically sending the same overdue-status message every few days regardless of the reply. Repeated messages do not create new evidence and may bypass the process the recruiter specified. Continue assessing other opportunities while recording this one's actual state.
If the recruiter cannot provide a date, record that uncertainty. Do not convert “we will contact you” into a new date chosen by you and later accuse the employer of missing it.
Correct a factual error without inventing an achievement
Suppose Tara notices that her example's filename says version one while the file itself contains the intended version-two exercise. She should not claim the attachment was flawless or send a different example without explanation.
A complete original correction message is:
Dear Recruitment Team,
I noticed an incorrect version label in the filename of the
practice example I sent. The file contained the intended
version-two exercise, but its filename said version one.
I have attached the same exercise with the corrected filename.
The contents are unchanged. Please use this correctly labelled
copy when reviewing the requested example.
Regards,
Tara
Attachment: Correctly labelled version-two practice example
That wording depends on the supplied fact that the contents are unchanged. If the contents also changed, identify the change instead. A correction message must describe the actual error and replacement, not minimise a material difference.
An unsolicited lengthy new portfolio is different from a requested correction. Check whether additional material is wanted and suitable before sending it.
Keep message status separate from application status
A draft is not sent. A sent message is not proof of receipt. A reply is not proof of selection. An offer, clarification and acceptance each need their own evidence.
An original tracker could record “thank-you drafted,” “correct attachment checked,” “message sent” and “response received,” but only mark an event completed when it occurred. Do not mark “offer expected” as “offer received.”
In this guide no message was actually sent, so the sample sequence remains a practice exercise. If you use it in a real application, replace the fictional facts and check every status against your own record.
The final-interview guide helps distinguish confirmed role terms from pending ones. The business-letter guide shows attachment and authority checks in another correspondence setting.
Respond to no reply or a declined application accurately
If a permitted status request receives no reply, record “no reply received.” Silence does not establish the reason. Avoid guessing private contact details or sending the same request through several channels to force an answer.
If the recruiter supplies a decline, record the application as declined. A concise optional acknowledgement can thank them for the update. If you ask for feedback, treat it as a request the employer may not fulfil, not an entitlement or proof that the decision will change.
If you receive an offer, review the actual terms and decision deadline. Do not reuse a status-request template as a negotiation message without examining the new situation. Different evidence calls for a different next action.
Common interview-follow-up questions
Must I send a message exactly twenty-four hours later? No universal requirement is established here. Consider the actual instructions and applicable guidance.
Should I contact the interviewer elsewhere if the recruiter is silent? Follow the stated channel and process. Do not guess addresses or bypass instructions.
Does a reply mean I am selected? Only the reply's actual content establishes its meaning. An update can leave the outcome pending.
Can I share a previous employer's document? This exercise uses original fictional material. Establish permission and suitability before sharing real materials.
Will follow-up guarantee a higher offer rate? No such evidence or outcome guarantee is supplied here.