11 min read
You applied two weeks ago. The portal still says Received. You're not sure whether silence means no or whether your note vanished in a flooded inbox. A follow-up can reopen the file. A vague one gets archived because the recruiter can't tell which req you mean.
Name the role, cite the apply date, ask one yes or no question, and stay under 120 words. That's the bar. Everything below shows you how to hit it without sounding desperate or sending a wall of text nobody'll read on a phone between screens.
Before you draft anything, check your resume for free against the posting you followed up on. Recruiters reply faster when the file already cleared parser checks. A polite email cannot fix a resume that never imported with the right job title.
Job searching while you're waiting on payroll elsewhere is stressful. You don't need a novel. You need a searchable subject line and a body short enough to answer between calendar alerts. I've archived stacks of just checking in notes in Greenhouse because they didn't say which opening the sender meant.
Below: quick wins, five steps with templates, edge cases, mistakes, and when to stop. You'll also see before and after examples from real inbox patterns, not pep talks about patience. If you're not sure the resume cleared screen, we'll cover that before touch two.
Quick Wins
- Subject line: job title, your name, apply date. Recruiters search that string.
- Body under 120 words with one question: still under review for this req?
- Wait ten to fourteen business days unless the posting names a shorter window.
- One recipient, one thread. Second touch one week later, then stop.
When a status email actually helps
Corporate reqs run through Workday, Greenhouse, Lever, or iCIMS before a human triages. Silence often means backlog, not rejection. A short note helps when your file is qualified but buried, when the recruiter lost the thread, or when the portal never updated after a manual screen.
It does not help when you applied late to a req that already moved to interviews, when your resume failed knockout questions, or when the posting was a ghost job collecting resumes with no active hire behind it. Know which case you're in before you spend emotional energy on draft six.
What recruiters need to answer you: which job, when you applied, and one clear question. Without those three pieces, your email competes with forty other threads titled Following up or Application status. Those go to archive unread.
A composite operations analyst applied through Greenhouse on March 3. She sent any update? on day nine. No reply. On day fifteen she sent Operations Analyst req 8842, Jordan Lee, applied March 3. Still under review for this role? Recruiter replied same afternoon with screen scheduled. Same candidate. Different subject line. The body was shorter the second time too.
Edge case: you only have a no-reply careers@ address. Send one email there with the same subject formula. If bounce or silence after two touches, treat the req as closed and spend energy on openings where you can name a human contact.
Edge case: you already interviewed and you're waiting on next steps. Do not use the cold-application template. Reference the interview date, thank them once, and ask whether the team is still moving forward on timeline. Same 120-word cap. Different opening line.
Edge case: internal referral said they'd flag your resume. Email the referrer first with the apply date and req number. Let them nudge inside Slack before you email the recruiter cold. Two external pings plus an unprimed referral reads messy.
Read why rejection emails are generic when you get a templated no. That outcome is common. It rarely means your follow-up failed. It means the req closed or you were screened out earlier than the note suggested.
How to ask for an update on application status in five steps
Work the steps in order. Pull facts from your tracker before you open a blank email. Draft once. Send once. Log it. A second touch is allowed. A third on the same req is not.
Step 1: Confirm timing and pull req details
Open your application log. You need exact job title as posted, company name, apply date, portal status, and req or job ID if the confirmation email listed one. If the posting said we review within two weeks, wait two weeks plus three business days.
Check the employer portal before you email. Sometimes Workday moves from Received to Review without email notice. If status changed, you do not need a follow-up. If it still says Received after your wait window, proceed.
Before: Sent follow-up on day four because anxiety spiked. Recruiter had not opened the req queue yet.
After: Waited twelve business days, confirmed portal still Received, then emailed with March 8 apply date in the subject.
Step 2: Find the right inbox
Reply on the application confirmation thread when possible. That thread already links your candidate record. If no person is named, use the talent mailbox on the posting once. Do not CC the hiring manager, VP, and three alumni you found on the company site the same morning.
Before: Emailed hiring manager on LinkedIn and recruiter on email same hour with different job titles typoed.
After: One email to talent partner on the Greenhouse receipt. Subject matched the req title exactly as posted.
Step 3: Draft a searchable subject and a under-120-word body
Subject format: [Job Title] application, [Your Name], applied [Month Day]. Body structure: one line naming the role and date, one line of fit proof pulled from bullet one on your resume, one yes or no question, one thank you. No bullet lists. No life story.
Before: Subject: Checking in. Body: 280 words on passion, culture fit, and three questions about team size, stack, and remote policy.
After: Subject: Senior Data Analyst application, Priya N., applied April 2. Body: 78 words asking if the req is still under review. One proof line: built Looker dashboards that cut weekly reporting time for a 12-person ops team.
Step 4: Send once during business hours and log it
Send Tuesday through Thursday morning in the employer time zone when you can. Update your tracker with send date and set a reminder seven days out for one optional second email. If they reply, stop the reminder.
Do not read receipts. Do not send a second note because you saw them active on chat apps. Recruiters batch inbox work. A same-day double send erases the professionalism you built in step three.
Before: Three follow-ups in five days with escalating urgency.
After: One note on day thirteen. Second on day twenty only after silence. Moved on after that.
Step 5: Fix the file if silence follows a strong match
If you meet the posting on paper and still hear nothing after two touches, assume the resume never presented cleanly. Run the checker, confirm job title import, and verify three required terms appear in Experience. Re-upload only if you changed the file. Mention the re-upload in a fresh thread, not as a third bump on the old one.
A composite marketing coordinator matched eight of ten listed skills but used a two-column Canva export. Parser dropped half the Experience section. After rebuild to single-column PDF and one follow-up with req ID, she got a phone screen. The tone was fine the whole time. The file was not.
Copy-paste email templates
Swap bracketed fields. Keep word count under 120. These are starting points, not scripts to recite verbatim if they push you over the limit.
Template A: First follow-up after applying
Subject: [Job Title] application, [Your Name], applied [Month Day]
Hi [Recruiter Name],
I applied for [Job Title] at [Company] on [Month Day] through [Workday/Greenhouse portal]. My background includes [one proof line from bullet one].
Is this req still under review? Happy to share anything else useful.
Thank you,
[Your Name]
[Phone]
Template B: Second follow-up one week later
Subject: Re: [Job Title] application, [Your Name], applied [Month Day]
Hi [Recruiter Name],
Following up once on my [Month Day] application for [Job Title]. If the role has moved forward with other candidates, I understand. If still open, I remain interested.
Thank you,
[Your Name]
Template C: After interview, waiting on next steps
Subject: [Job Title] interview follow-up, [Your Name], [Interview Date]
Hi [Interviewer or Recruiter Name],
Thank you again for speaking with me on [Interview Date] about [Job Title]. I enjoyed learning about [one specific topic discussed]. Is the team still on track for next steps this week?
Best,
[Your Name]
Copy-paste the block that matches your stage. Trim adjectives until you fit under 120 words. If you need a fresh cover letter for a parallel req while you wait, generate a cover letter with the same job title string you used in the subject line so nothing contradicts on upload.
Follow-ups that get ignored
Generic subject lines. Checking in and Any news? do not search. Recruiters cannot match you to a req. Use title, name, date.
Multiple questions in one email. Salary, remote policy, timeline, and team size in one note reads like a pre-interview. Ask one thing. Save the rest for the screen.
Guilt or urgency language. I really need this job or Please respond ASAP puts pressure on someone who did not create your financial situation. Stay neutral and brief.
Following up before the posting window closes. If they said three weeks for decisions, day five email trains them to deprioritize you.
Reattaching the same resume every time. Clogs storage. Fix the file once, re-upload in the portal, mention it in one line if needed.
Blasting LinkedIn DMs and email simultaneously. Pick one channel per week. Duplicate pings from three surfaces feel like spam even when each message is polite.
Before: Four-paragraph essay on why the company mission changed my life. No job title in subject.
After: Three sentences. Role named twice. One question. Under 120 words. Recruiter replied with scheduling link.
Read how to build a US application funnel when you're managing twenty open reqs. A tracker prevents you from sending the wrong company name in a follow-up copy-paste error.
Fix the file before you nudge again
Run your resume and the posting through HireFlow's free ATS resume checker . Silence after a polite follow-up often traces to a parser miss, not email tone. Confirm job title, employer names, and three required skills imported before you send touch two.
If the req still wants a letter and you have not submitted one, use the cover letter generator to draft a single page that mirrors the job title in your follow-up subject. Matching strings across letter, resume, and email reduces confusion when the recruiter pulls your file.
Tools will not force a reply from a closed req. They keep a qualified application from dying quietly because the upload was unreadable. Pair a clean file with a short note and you have done what is in your control.
Send one clean note tonight
How to ask for an update on application status comes down to searchable specifics, not frequency. Name the role, cite the apply date, ask one yes or no question, and stop under 120 words. Wait ten to fourteen business days unless the posting says otherwise. One recipient. Two touches max.
Open your tracker. Pick one req past the wait window. Paste Template A. Trim until it fits. Send Tuesday or Wednesday morning. Log the date. Then move on to the next application instead of refreshing sent mail.
You're not rude for following up once. You're hard to help when the recruiter cannot tell which opening you mean. Make that impossible.
Read more
Frequently asked questions
Wait ten to fourteen business days after you apply unless the posting names a shorter window. Add three business days if they said two weeks for review. Check the portal first. If Workday or Greenhouse still shows Received with no movement, one polite email to the recruiter is fine. A second note one week later is the ceiling for the same req.
Start with the recruiter or talent partner listed on the confirmation email. If none is named, reply to the automated receipt when it allows replies, or use the careers contact on the posting. Do not cold-email five people at once. One inbox, one thread, one question.
Put the job title and your name in the subject. Example: Operations Analyst application, Jordan Lee, applied March 12. Recruiters search subject lines in Outlook and Greenhouse mail. Checking in alone matches hundreds of other threads and gets archived.
Yes, once. First follow-up after the wait window. Second follow-up one week later if you got no reply. After that, assume the req moved on or the role filled quietly. More than two touches on the same opening reads as pressure, not persistence.
Only if they asked for a new version or the portal rejected your upload. Otherwise paste one proof line from bullet one in the body. Reattaching the same PDF clogs inboxes and does not fix a parser miss. Fix the file first, then mention you re-uploaded if you did.