Applicant Flow Log
An applicant flow log is a record of everyone who applies for a job and what happened to each person. It captures when they applied, which role they applied for, and whether they were screened out, interviewed, offered, or hired.
HR teams use it to check hiring patterns and to answer questions from an agency, a lawyer, or a leader. It is easy to confuse with an applicant tracking system. The log is the record, and the system is one tool that can produce it.
Why Do Employers Keep an Applicant Flow Log?
The main reason is proof. If a candidate says they were treated unfairly, a clear log shows how every applicant for that job was handled. Without it, you are answering from memory.
The EEOC also sets a basic retention rule. Under 29 CFR 1602.14, employers must keep application forms and other hiring records for one year from the date the record was made or the personnel action taken, whichever is later.
If a charge of discrimination is filed, the rule is stricter. You must preserve all relevant personnel records until the charge or lawsuit is finally resolved, including records on other candidates for the same position.
What Does an Applicant Flow Log Include?
There is no single required template, so build one that answers the questions you expect to face. Most logs include the same core fields.
- Applicant name or a unique applicant ID.
- Job title or requisition number, and the date of application.
- Where the candidate came from, such as a job board or referral.
- Voluntary self-identification of gender, race, ethnicity, disability, or veteran status, where you collect it.
- Each step reached, such as screen, interview, offer, or hire, with dates.
- The final outcome and the reason for any rejection.
The reason code matters most. A rejection marked only as 'not a fit' is hard to defend. A note such as 'lacked required license' is specific and tied to the job.
How Long Should You Keep an Applicant Flow Log?
The right period depends on who you are. Most private employers fall under the EEOC rule, and federal contractors have extra rules for disability and veteran hiring data.
| Rule | Who it applies to | Retention |
| EEOC recordkeeping | Employers covered by Title VII, the ADA, and GINA | One year from the record or action, longer if a charge is filed |
| Section 503 annual data comparison | Federal contractors | Three years |
| Section 503 general personnel records | Federal contractors | Two years, or one year for smaller contractors |
Contractors must compute applicant and hire counts each year and keep them for three years, as set out in 41 CFR 60-741.44. Some states set longer periods, so many employers simply keep logs for several years.
How Is an Applicant Flow Log Different From an ATS?
An applicant tracking system manages the hiring work: posting jobs, collecting applications, moving candidates between stages. A flow log is the summary record of who applied and what happened to them.
A good system can generate the log. A spreadsheet can too. What matters is that the record is complete, consistent across jobs, and kept for the right length of time.
Watch for one common gap. If candidates reach you by email, referral, or a job fair and never enter the system, they will be missing from the log.
How Do You Keep an Applicant Flow Log Without Creating Risk?
Keep demographic answers separate from the application itself, and make them voluntary. Section 503 rules for contractors require the self-identification invitation to be separate from the application.
Limit who can see those answers. Many employers keep them away from hiring managers so they play no part in the decision. Use them only to analyze patterns after the fact.
Record the same fields for every applicant. A log that tracks some jobs in detail and others loosely invites questions about why.
How Does HR Cloud Fit Into the Applicant Flow Log?
HR Cloud's recruiting page says the platform keeps every application, message, note, file, and status attached to the candidate record. It also describes custom hiring stages and dashboards for candidate sources and pipeline movement.
The page does not describe an applicant flow log, EEO or OFCCP reporting, or self-identification forms. If you need those, confirm what you can export before you rely on the system, and plan a separate process for the demographic data.
Discover how our HR solutions streamline onboarding, boost employee engagement, and simplify HR management
Book Your Free DemoFrequently Asked Questions
Q: What is an applicant flow log?
A: It is a record of everyone who applied for a job and the outcome for each person, including dates, steps reached, and the reason for any rejection.
Q: Is an applicant flow log required by law?
A: Employers must keep hiring records under the EEOC rule. Federal contractors have additional duties for disability and veteran applicant data. A specific log format is not mandated by those rules.
Q: How long do I need to keep applicant records?
A: The EEOC rule is one year for most employers, and longer if a charge is filed. Federal contractors keep certain annual applicant data for three years.
Q: Should the log include race and gender?
A: Only if you collect voluntary self-identification. Keep it separate from the application and limit who can see it.
Q: Can an applicant tracking system serve as the log?
A: Yes, if it captures every applicant and can produce the fields you need. Check that candidates who arrive outside the system are still recorded.
Q: What is the most common mistake with applicant flow logs?
A: Vague rejection reasons and missing records for candidates who applied by email or referral. Both make the log hard to defend.
Ready to streamline your onboarding process?
Book a demo today and see how HR Cloud can help you create an exceptional experience for your new employees.
Book Your Free Demo

