Two recruiters working the same opening will often run it differently — one phone-screens everyone, another sends half straight to a hiring manager. That inconsistency is exactly what lets good candidates slip away and drags time-to-hire out for weeks. A hiring process flowchart fixes it by making the path explicit: requisition, post, screen, interview, offer, onboard — the same way every time.
This guide maps a complete recruitment process you can adapt, plus the common branches and the mistakes that quietly break a hiring workflow. For the format basics, see What Is a Flowchart?.
The Hiring Process, Step by Step
Here is a standard recruitment flow. Each numbered step is a shape in the diagram; the decisions are where it branches.
1. Create the job requisition (JD). The entry point — the hiring manager defines the role, responsibilities, and requirements. This is the Start terminator. Nothing should be posted before the requisition is approved.
2. Post the opening. Publish the role to job boards, your careers page, and referral channels. The wider and more targeted the reach, the better the candidate pool.
3. Screen resumes. Review incoming applications against the requirements. This is the first filter that separates qualified candidates from the rest.
4. Resume qualified? (decision).
- Yes → move to the phone screen.
- No → reject and archive the application (with a polite rejection note).
5. Phone screen. A short call to confirm basics — interest, availability, salary expectations, and a quick skills check before investing interview time.
6. On-site / technical interview. The core evaluation — one or more rounds with the team, technical exercises, or a panel, depending on the role.
7. Passed interview? (decision).
- Yes → proceed to the background check.
- No → reject the candidate and notify them.
8. Role-specific checks and offer conditions. Place checks at the stage permitted by the applicable jurisdiction and employer policy. Some checks may follow a conditional offer. Record required consent, review authority and the process for an unresolved result rather than assuming every check happens before any offer.
9. Send the offer. Extend a written offer with compensation, start date, and terms.
10. Offer accepted? (decision).
- Yes → onboard the new hire.
- No → return to the candidate pool or reopen the requisition and post again.
11. Onboard. Provision accounts, schedule orientation, and start the new hire. This is the End terminator for a successful path.
Those reject branches in steps 4, 7, and 10 are what separate a real recruitment flow from a wish. Start from the flowchart template to draw this process and adapt it to your team's stages.
Common Variations
Not every hiring team uses the same flow. A few common branches to add:
- Multiple interview rounds. Many roles add several "Passed round N?" decisions in sequence — recruiter screen, hiring manager, panel, then final — each with its own reject branch.
- Bulk / high-volume hiring. For seasonal or call-center roles, the screen and phone steps are often replaced with automated assessments that batch-filter applicants before any human review.
- Referral channel. Referrals frequently skip the open posting and feed directly into the resume screen, sometimes with an expedited track.
- Hiring committee scoring. Instead of a single "Passed interview?" decision, interviewers submit scores that feed a committee review, which makes the pass/fail call.
Worked example: hire for one approved support role
Use a hypothetical support vacancy to test the flow. The hiring manager defines the work, required capabilities and approved headcount. Recruiting confirms the role description and process owner before sourcing begins. These are example responsibilities, not a substitute for the employer’s hiring policy.
The first handoff contains the approved role, assessment criteria, compensation decision owner and interview plan. Without these inputs, a recruiter may collect applicants while the manager is still changing the job. A “ready to post?” gate makes that uncertainty explicit.
Candidates then enter the same documented assessment route for that role, with appropriate arrangements handled through the responsible team. A referral is a sourcing channel, not evidence that the person has already met the criteria. If a different assessment route is justified, record its reason and approval rather than hiding it behind an expedited arrow.
At the interview stage, each assessor records job-related evidence against the agreed criteria. “Good fit” without a definition is not a useful decision label. The final decision belongs to the authorized owner, supported by the assessment record, rather than an automatic average of arbitrary scores.
Suppose the manager wants an offer but the compensation approval is missing. The candidate should not be shown as hired. Route the case to the approver, assign the next communication and keep the unresolved condition visible. If the candidate withdraws during the wait, record withdrawal separately from employer rejection.
Model offers, checks and exceptions explicitly
An offer can be drafted, approved, sent, accepted or declined. These are different states. Where the employer uses a conditional offer, show what conditions remain and who confirms them. Do not let “accepted” silently mean every start requirement has been completed.
Check requirements vary by location and role. The flowchart should point to the applicable policy and authorized reviewer; it should not prescribe one global background-check sequence. Sensitive records belong in the access-controlled hiring system, not in a public diagram or a card visible to every interviewer.
Add distinct paths for candidate withdrawal, no response, a role being paused and a decision needing review. Each path needs an owner and communication step. An unresolved case should not loop forever through “follow up” simply because the diagram has no closed state for it.
For a missing interview report, return to the assessor with the specific information needed. For a disputed check result, use the employer’s approved review process. These are not interchangeable “reject” branches, and the diagram should not collapse them into one outcome.
Use swimlanes for handoffs, not every job title
A compact diagram may use lanes for recruiting, the hiring manager, assessors and the authorized approval function. Put a task in the lane of the role responsible for completing it. If two roles share a decision, explain who owns the final result and what the other role supplies.
Label a handoff with the record being passed: assessment summary, approved offer or onboarding request. The receiving team should be able to tell whether the information is sufficient without asking the author to narrate the drawing.
Keep detailed interview questions and personal candidate information outside the process map. The chart describes how the organization works; the hiring system contains the individual cases. This separation also makes the diagram easier to reuse for the next vacancy.
Validate and maintain the hiring flow
Walk through an accepted offer, a declined offer, a withdrawn application, a paused role and a pending review. Ask the next role in each lane what evidence allows them to act. If they cannot answer, the gate or handoff is incomplete.
Define any metrics before comparing results. “Time to hire” can begin at different events in different organizations. Use a consistent start, finish and population, and separate withdrawals from assessment decisions so the chart does not support misleading conversion rates.
Record a process owner and revision date. Review the map when approval authority, local requirements or assessment stages change. CodePic can document the flow and provide a PNG or read-only review link; it does not screen candidates, make employment decisions or execute background checks.
Common Mistakes
No reject branches. If the diagram only shows the happy path to an offer, it lies. Real hiring rejects candidates at every decision — screen, interview, and offer.
Using one universal check sequence. Background, medical and credential checks have different requirements. Have the authorized HR or legal owner confirm the permitted timing, notices and review route for the location and role.
Skipping the phone screen. Sending unvetted resumes straight to on-site interviews wastes the team's time. The phone screen is a cheap, fast filter — keep it.
Unlabeled decision branches. Every diamond ("Resume qualified?", "Offer accepted?") needs labeled exits, or new recruiters guess where candidates go.
Frequently Asked Questions
What is a hiring process flowchart?
A hiring process flowchart maps how a candidate moves from job requisition to onboarding — posting, screening, interviews, background checks, and offers — so every hire follows the same consistent path.
How do you show rejection in a hiring process flowchart?
Use a decision diamond like "Resume qualified?" or "Passed interview?" with a "No" branch that routes to a reject or archive step, while the "Yes" branch continues down the pipeline toward an offer.
Ready to map your own recruitment process? Open the flowchart template — adapt the requisition, screening, and interview steps to your team, no signup required.
Related Reading
- Types of Flowcharts — process, swimlane, and more
- What Is a Flowchart? — the format basics
- How to Make a Flowchart — the general tutorial
- Flowchart Symbols Guide — every shape explained
