Check the source first
Look for portal tasks, confirmation emails, deadlines, interview invites, and current posting instructions.
Follow-up planner
Use this page after you apply but before you send a second message. It compares application platform, timeline, assessment, and interview-handoff signals from the current HireTea public index so your follow-up is timely, specific, and tied to the evidence you already saved.
Quick answer
Start by checking the candidate portal and saved posting. If the process is fast or local, a short status check after 24-48 hours can be reasonable. If the page points to a one-to-two-week timeline, wait several business days. If the role uses planned interview rounds, task deadlines, or recruiter-managed steps, follow the cadence in the invite instead of sending repeated messages.
Look for portal tasks, confirmation emails, deadlines, interview invites, and current posting instructions.
Use the portal, recruiter thread, local hiring contact, or posting channel named by the employer.
A useful follow-up confirms the role, date applied, next-step question, and best contact route.
Timing groups
These groups are planning cues, not promises. A local restaurant can respond faster than a national portal, and a technical or program role can have planned quiet periods. The point is to avoid two common mistakes: following up before checking required tasks, or waiting so long that you miss a schedule, interview, or offer detail.
| Follow-up timing group | Indexed hubs | Example companies | Best next action |
|---|---|---|---|
| Use local-site timing | 16 | Walmart, Target, Kroger, CVS Health, and Costco Wholesale | Check saved evidence first, then send one concise status question only if the current source does not answer it. |
| Check status after 24-48 hours | 3 | McDonald's, UPS, and Dollar General | Check saved evidence first, then send one concise status question only if the current source does not answer it. |
| Use posting-controlled timing | 2 | FedEx and Walt Disney Parks | Check saved evidence first, then send one concise status question only if the current source does not answer it. |
| Wait 5-7 business days | 2 | The Home Depot and Starbucks | Check saved evidence first, then send one concise status question only if the current source does not answer it. |
| Follow recruiter cadence | 1 | Alphabet / Google | Check saved evidence first, then send one concise status question only if the current source does not answer it. |
| Watch task deadlines before sending extra messages | 1 | Amazon | Check saved evidence first, then send one concise status question only if the current source does not answer it. |
Contact route
The best channel is usually the one the employer already gave you. Candidate portals are useful when a status, task, or scheduling step is visible. Recruiter or interview threads are better after a person has already contacted you. Local hiring contacts can matter for franchise, property, store, or restaurant flows, but only when the posting or employer page names that route.
| Channel group | Indexed hubs | Representative companies | What to include |
|---|---|---|---|
| Candidate portal first | 21 | Walmart, Amazon, The Home Depot, FedEx, and Target | Use company, exact role, location, date applied, job ID if available, and one clear next-step question. |
| Local hiring contact when listed | 2 | McDonald's and Chick-fil-A | Use company, exact role, location, date applied, job ID if available, and one clear next-step question. |
| Reply to the interview or recruiter thread | 2 | Walt Disney Parks and Alphabet / Google | Use company, exact role, location, date applied, job ID if available, and one clear next-step question. |
Category view
Category patterns help you choose a practical pace. Retail, restaurant, grocery, warehouse, hospitality, tech, and pharmacy-adjacent hiring can route applicants through different systems. Use the category row as a starting point, then open the company hub and current posting before sending anything.
| Category | Hubs | Common timing | Common channel | Risk to avoid |
|---|---|---|---|---|
| Retail | 13 | Use local-site timing, Check status after 24-48 hours, and Wait 5-7 business days | Candidate portal first | Avoid assuming silence means rejection and Keep message brief and evidence-based |
| Restaurant | 5 | Use local-site timing, Check status after 24-48 hours, and Wait 5-7 business days | Candidate portal first and Local hiring contact when listed | Instructions may be local and Keep message brief and evidence-based |
| Warehouse | 3 | Check status after 24-48 hours, Use posting-controlled timing, and Watch task deadlines before sending extra messages | Candidate portal first | Do not miss portal tasks and Avoid assuming silence means rejection |
| Hospitality | 3 | Use local-site timing and Use posting-controlled timing | Candidate portal first and Reply to the interview or recruiter thread | Instructions may be local and Avoid assuming silence means rejection |
| Tech | 1 | Follow recruiter cadence | Reply to the interview or recruiter thread | Process may have planned gaps |
Company examples
Use these examples to decide whether you should wait, check the portal, or send a brief message. The company page gives broader context; the current posting and employer message control the final channel.
| Company | Application platform | Timeline signal | Follow-up window | Channel |
|---|---|---|---|---|
| Walmart | Walmart careers portal | varies by store | Use local-site timing | Candidate portal first |
| Amazon | Amazon Jobs | application to pre-hire appointment to orientation and Day 1 | Watch task deadlines before sending extra messages | Candidate portal first |
| McDonald's | McDonald's careers, franchise hiring site, or McHire / Olivia depending on location | often fast, varies by franchise | Check status after 24-48 hours | Local hiring contact when listed |
| The Home Depot | Workday | 1-2 weeks | Wait 5-7 business days | Candidate portal first |
| FedEx | FedEx careers portal | varies by hub and role | Use posting-controlled timing | Candidate portal first |
| Target | Target careers portal | varies by store | Use local-site timing | Candidate portal first |
| Kroger | Kroger careers portal | varies by store | Use local-site timing | Candidate portal first |
| UPS | UPS Jobs | can be fast for package handler roles | Check status after 24-48 hours | Candidate portal first |
| CVS Health | CVS Health careers portal | varies by role and store | Use local-site timing | Candidate portal first |
| Costco Wholesale | Costco careers portal | varies by warehouse | Use local-site timing | Candidate portal first |
| TJX Companies | TJX careers portal | varies by store | Use local-site timing | Candidate portal first |
| Lowe's | Lowe's careers portal | varies by store | Use local-site timing | Candidate portal first |
| Marriott International | Marriott careers portal | varies by property | Use local-site timing | Candidate portal first |
| Chipotle Mexican Grill | Chipotle careers portal | varies by restaurant | Use local-site timing | Candidate portal first |
Templates
These are not scripts to paste blindly. Replace the brackets with truthful details from your saved posting and use the channel the employer gave you. A good message is short enough to answer quickly and specific enough that the hiring contact can find the application.
| Situation | Message frame | Use when |
|---|---|---|
| Portal status check | Hello, I applied for [exact role] at [location] on [date]. I wanted to confirm whether any next step is needed from me in the candidate portal. | The portal shows applied or submitted but no new task. |
| Local hiring contact | Hello, I recently applied for [role] at [store/property/restaurant]. I am still interested and wanted to ask whether this location is reviewing applications this week. | The posting names a local route or location-specific contact. |
| Interview follow-up | Thank you for speaking with me about [role]. I appreciated learning about [specific detail]. Please let me know if I should send anything else before the next step. | You already interviewed and are replying to that thread. |
| Offer detail clarification | Thank you for the offer. Before I confirm, could you please clarify the expected schedule, start date, and the pay language for this specific role and location? | The offer or recruiter message leaves a decision detail unclear. |
Before sending
Review your evidence before writing. If the posting says not to call, do not call. If the candidate portal has a task, finish the task before sending a status note. If a recruiter gave a date, wait until that date passes. If a role is seasonal, local, or high-volume, a brief message is fine, but repeated messages can make the exchange harder to manage.
Scheduling links, onboarding tasks, document requests, and interview invites matter more than a generic status.
Use a recruiter or hiring contact only when the employer supplied that route or already contacted you.
Have the role title, job ID, location, date applied, and posting URL ready before asking for an update.
Evidence to save
Save the message date, channel, recipient, role title, job ID, location, and any reply. If the employer changes the timeline, pay wording, schedule, start date, or required task, keep the new instruction beside the original posting. The goal is not to pressure the employer; it is to make sure your own application tracker reflects the latest written instruction before you compare this role with another one.
Download the application tracker to keep follow-up dates beside portal status and source evidence.
Open the comparison worksheet if one employer communicates clearly and another stays vague.
Review application step benchmarks when you are unsure whether the next step should be a portal task or a human reply.
Plan a thank-you note before sending a second message in the same recruiter or interview thread.