Search for job application templates and the results are almost all the same document wearing different fonts. Name, address, phone, education, employment history, references, signature. The template is not the hard part. The hard part is deciding which of those fields actually change a hiring decision, which ones create legal exposure, and what happens to the answers once forty of them have arrived.
A job application form does two jobs at once, and they pull in different directions. It is a screening instrument, which argues for asking more. It is also a record that has to be kept, defended and eventually deleted, which argues for asking less. A template that is only designed for the first job will quietly create work for years on the second.
Decide what the form is for before choosing fields
There are three distinct things an application form can be, and mixing them is the most common reason a template feels bloated.
The first is a filter. A handful of questions that establish whether the person meets a hard requirement: the right to work in the jurisdiction, a licence the role legally needs, availability for the shift pattern, willingness to travel. These questions have right answers, and they should come early so that an unqualified applicant is not asked to spend twenty minutes on the rest.
The second is comparison material. Structured questions that produce answers you can read side by side across fifty applicants. Years in a named skill. A short response to a scenario the role actually involves. A rating of familiarity with a specific tool.
The third is documentation. Legal name, contact details, the signed attestation that the information is accurate, the acknowledgement of whatever policy the organisation requires. These are needed once, at the end, and they change nothing about who gets an interview.
Ordering a form by those three purposes, filter first, comparison second, documentation last, tends to shorten it. Fields that serve none of the three are the ones to cut.
The fields worth asking for
The list below is short on purpose. Anything not on it should have to justify itself.
Full legal name and preferred name, kept as two fields, because the name a person is addressed by in an interview invitation is often not the name on their documents. Email address, with the form validating it, because a typo here means the applicant never hears back and never knows why. Phone number, as an optional field unless the process genuinely uses it. The role being applied for, as a choice rather than free text, so that submissions sort themselves when several roles are open at once.
Right to work in the jurisdiction, as a yes or no, without asking for nationality, citizenship or immigration status. Availability, expressed as the thing the role needs: a start date, a shift pattern, a number of hours. Relevant qualifications or licences where the role legally requires them, with the licence number rather than a scan at this stage.
Work history, and this is where most templates go wrong. Asking for a full chronological employment record on the form duplicates the CV that is being uploaded anyway, and produces a wall of text nobody reads. Asking instead for two or three specific things, the most relevant role held and what it involved, produces something comparable.
One or two open questions tied to the actual work. Not "why do you want to work here", which generates identical answers, but a question with a concrete object: describe how you would handle a particular situation the role contains. These are the answers that separate applicants, and they are worth the space they take.
Finally the file upload, the attestation, and consent to how the data will be handled.
Structure beats free text almost everywhere
Every field left as an open text box is a field that has to be read individually rather than sorted, filtered or counted. Where an answer has a finite set of possibilities, make it a choice. Where a number is wanted, ask for a number rather than a sentence that contains one.
The exception is the small number of questions whose whole value is in how the person writes the answer. Keep two of those. Turn the rest into structure.
The questions to leave out
Several standard template fields are either legally risky or produce information that cannot be used. In the United States, the Americans with Disabilities Act sets the clearest line. The Equal Employment Opportunity Commission's guidance states that an employer may not ask disability-related questions and may not conduct medical examinations until after it makes a conditional job offer. A disability-related question is one likely to elicit information about a disability, which the guidance extends to questions about workers' compensation history, prior sick leave and lawful medications. After a conditional offer, those questions become permissible, provided everyone in the same job category is asked the same things.
What the same guidance confirms is permissible before an offer is worth knowing too: asking the applicant to describe or demonstrate how they would perform specific job functions, asking about education, work history, certifications and licences, and asking whether they can meet the attendance requirements of the role.
| Field commonly found in templates | Better handled by | Reason |
|---|---|---|
| Date of birth | Omitting it, or collecting at offer stage | Serves no screening purpose and signals age |
| Graduation year | Asking for the qualification only | Acts as a proxy for date of birth |
| Health, medical history, sick leave | Post-offer stage, applied to everyone in the role | Prohibited pre-offer under the ADA guidance |
| Photograph | Omitting it entirely | Introduces bias, changes nothing about capability |
| Marital status, dependants | Omitting it entirely | Not job related, invites a discrimination claim |
| Demographic data for reporting | A separate, clearly optional form | Keeps it out of the hiring decision |
Salary history deserves a line of its own, because the rules vary by jurisdiction. A growing number of states and cities in the United States prohibit asking applicants what they currently earn. Asking instead what the applicant is looking for, or publishing the range and asking whether it works, avoids the question entirely and is more useful anyway.
Demographic questions are not banned, and many organisations have good reasons to collect them. The rule is separation. They belong on their own form, marked optional, with the answers kept away from the people making the decision. Putting them in the middle of the application form makes that separation impossible to demonstrate later.
Attachments, and the queue they create
Nearly every application form asks for a CV. Most also ask for a cover letter, and some ask for portfolios, certificates and identity documents. Each of those is a file that has to be received, stored, opened by a reviewer, and deleted on schedule.
Two practical points. First, ask for identity and qualification documents at offer stage rather than on the application, because collecting scans of passports from two hundred applicants to hire one is a data protection liability with no screening benefit. Second, check how the tool stores what is uploaded. A file that can only be opened by someone signed in, from a link that cannot be guessed, is a different proposition from a file sitting in a shared drive folder that anyone with the link can read.
Where this becomes a practical constraint is volume. Structural limits differ by platform, and they are worth checking against the longest form actually in use. Google Forms, for example, publishes a limit of 300 pieces of content per form, counting questions, descriptions, images and videos, and 75 sections. Most application forms are nowhere near that. Multi-stage programmes with conditional branches sometimes are.
One form for every role, or one form per role
Templates are usually written as though the organisation hires for one job. In practice several roles are open at once, and the choice between a single form and a form per role has consequences that show up weeks later.
A single form with the role as a dropdown is easier to publish and easier to maintain. One link goes on the careers page, one set of changes fixes a badly worded question everywhere, and all applications land in one list that can be filtered. The cost is that the questions have to be generic enough to suit every role, which pushes the form towards the least useful version of itself.
A form per role allows the comparison questions to be specific, which is where their value comes from. A question about handling an angry customer belongs on a support application and nowhere else. The cost is maintenance: five forms drift apart, the wording of the consent text ends up different on each, and a change to the process has to be made five times.
The practical compromise is a shared base that gets duplicated. Build the filter and documentation sections once, duplicate the form for each role, and replace only the comparison questions. This only works if the tool copies the whole configuration when it duplicates, including the auto reply, the notification settings and the stages, rather than copying the questions alone and leaving everything else to be rebuilt by hand.
Send an acknowledgement, and say what happens next
An application that vanishes into silence generates email. The applicant writes to ask whether it arrived, and someone has to answer, which costs more time than the acknowledgement would have.
An automatic reply sent on submission solves it, provided it does two things. It should confirm what was received, ideally including a copy of what the applicant wrote, so that a missing attachment is noticed immediately rather than at shortlisting. And it should state a timeframe, even an approximate one, because a stated timeframe is what stops the follow up email. Auto replies that only say thank you achieve neither.
The part the template does not cover
A template ends at submit. The process does not.
Once applications arrive, three things have to be true or the process degrades. Each application has a named owner, visible to everyone looking at the same list, so that two people do not interview the same candidate or write the same rejection. Each application has a stage that a human sets, because received, screened, interviewing and rejected are decisions, not inbox states. Every message sent to the applicant is attached to their record, so that the next person to open it can see what has already been said.
Spreadsheets can hold the first two if someone maintains them. They cannot hold the third, which is why the correspondence ends up scattered across individual mailboxes and why nobody can reconstruct what a candidate was told. A form tool that keeps the reply on the same screen as the answers removes the scattering rather than asking people to be disciplined about it. The use cases worth looking at are the ones that describe an application queue rather than a survey.
Retention is the other half. In the United States, the Equal Employment Opportunity Commission requires employers to keep all personnel or employment records for one year, and for one year from the date of termination where an employee is involuntarily terminated. Under the Age Discrimination in Employment Act, payroll records must be kept for three years. Applications from unsuccessful candidates fall under the first obligation, which means a platform that deletes old responses when a storage cap is reached is working against the requirement. Check the pricing page of any candidate tool for whether stored responses are capped, and check its questions people ask page for what happens to the data on cancellation.
What to change first
Take the template currently in use and delete every field that does not filter, compare or document. Then check whether the tool receiving the answers can hold an owner, a stage and the reply itself, because that is the part the template was never going to provide. If it cannot, that is the thing to replace, and Halict is one of the options built around it.
Q1. What should a job application form actually ask for?
Contact details, the role applied for, the hard requirements the role has such as right to work and any legally required licence, availability, the most relevant experience, and one or two open questions tied to the actual work. Everything else should have to justify its place. Full chronological work history usually duplicates the attached CV and produces text nobody reads.
Q2. Is it illegal to ask about health or disability on a job application?
In the United States, the Equal Employment Opportunity Commission's guidance states that an employer may not ask disability-related questions or require a medical examination until after making a conditional job offer. That includes questions about workers' compensation history, prior sick leave and lawful medications. After a conditional offer those questions are permitted, provided everyone in the same job category is asked the same things.
Q3. Can demographic questions be included on the application form?
They can be collected, but they belong on a separate optional form rather than inside the application, and the answers should not reach the people making the hiring decision. Mixing them into the application form makes it impossible to demonstrate afterwards that they played no part in screening.
Q4. How long do job applications have to be kept?
In the United States the Equal Employment Opportunity Commission requires all personnel or employment records to be kept for one year, and for one year from the date of termination where an employee is involuntarily terminated. Payroll records must be kept for three years under the Age Discrimination in Employment Act. Local rules may require longer, so check the jurisdiction before setting a deletion schedule.
Q5. Should applications go into a spreadsheet?
A spreadsheet is fine for analysis and reporting and poor as a working queue. It has no way to record what was sent to a candidate, which is how correspondence ends up scattered across individual mailboxes. Keeping owner, stage and correspondence on the application record itself, and exporting to a sheet when a report is needed, avoids that.