What to Do When Job Applications Sit in Progress
An "in progress" application status rarely means someone is actively reviewing your resume. In most company portals, that label simply confirms that the system received your submission and has not triggered an automated rejection rule.
Treating passive portal statuses as real momentum creates a false sense of productivity. Waiting for a dashboard to update leaves your search stalled in silence. Real momentum comes from active steps you take after submitting, paired with clear rules for when to move on.
Why portal statuses give a false sense of progress
Applicant portals are designed for internal workflow tracking, not candidate communication. A requisition can stay open for months while an internal candidate transfers, the department budget freezes, or recruiters sift through hundreds of profiles. As long as the job posting remains open in the software, your portal status will display as "active," "submitted," or "in progress."
Watching those statuses change will not move your search forward. As noted in the original discussion notes, candidates often wonder whether checking these portals helps or merely distracts from actual job-hunting tasks.
What to do within 48 hours of applying
Once you click submit, take ownership of the application instead of waiting for an automated email:
- Log the details immediately. Record the title, compensation range, team, and date submitted. Using a dedicated tool like Destava's application tracker keeps your pipeline clear so you know exactly which leads require follow-up and which have gone cold.
- Identify the actual decision-maker. Search LinkedIn for the department lead, team lead, or dedicated recruiter for that business unit. A note sent to a specific human gets read; a submission into an intake box sits in a queue.
- Send a concise introduction. Keep it under four sentences. State what role you applied for, highlight one concrete achievement relevant to their team, and express interest in connecting.
For example, if you applied for an engineering lead role, send a short note like this:
"Hi Sarah—I applied for the Senior Backend Engineer role on your platform team this morning. Over the last two years, I led the migration of our payment service to Go, reducing API latency from 220ms to 45ms. I know your team is scaling transaction infrastructure right now, and I would welcome the chance to share how my experience fits what you are building."
How to follow up five business days later
If you have heard nothing after five business days, follow up once. Do not ask for a generic status update or repeat your entire resume. Offer a clean point of contact and make replying effortless:
- Forward your original note or reply in the same message thread so the context is immediately visible.
- Add one new detail. Mention a recent project, open-source contribution, or specific company initiative that caught your eye. You can use the Writing Hub to draft quick, tailored follow-up notes that stay focused on the employer's current priorities.
- Give them an easy out. A sentence like "If the team has already moved forward with other candidates, no worries at all—just wanted to confirm before closing out the role on my end" shows professionalism and often prompts a fast, honest reply.
When should you consider an application closed?
Establish a firm cutoff rule so you do not carry false hope. If an employer has not reached out after three weeks from your submission date—and after you have sent one direct follow-up—mark that role as closed in your tracker.
Closing stale applications protects your mental energy. If a recruiter reaches out after a month, treat it as an unexpected bonus, not an expected outcome. Focus your time on active conversations, targeted outreach, and upcoming interviews rather than refreshing portals that have gone cold.