HR forms that people actually finish: the complete guide for people teams

HR runs on forms more than almost any other function. A single hire touches an application, a right-to-work check, an offer acceptance, an onboarding checklist, a payroll setup, an equipment request and a probation review — and that is before anyone books a day off. When those forms are badly designed the cost is not abstract: candidates drop out mid-application, managers approve leave over email, and someone in payroll spends Friday afternoon chasing a missing bank detail.

This guide covers the five HR forms that carry most of the load, what to ask on each, where teams usually get it wrong, and how to keep the whole set compliant without turning every request into a PDF.

Start with the process, not the fields

Most broken HR forms are broken because they were written as a list of things HR wants to know, rather than as one step in a process that has a beginning and an end. Before writing a single question, answer three things:

1. Who fills it in, and on what? Candidates and field staff are on phones. Managers are usually on a laptop between meetings. If a form needs a desktop and a scanner, it will be filled in late or not at all. 2. Who acts on it next, and what do they need? A leave request that does not capture the covering colleague creates a second conversation. An expense claim without a cost code creates a finance ticket. 3. What happens on submit? Notification to a manager, a row in a tracker, a confirmation to the employee. If nothing happens automatically, the form is just a slower email.

A useful rule: every question should either change a decision, satisfy a legal requirement, or be needed to process the request. Anything else is optional at best.

Job applications: shorter than you think

Application length is the single biggest lever on candidate drop-off. Long forms select for people with time, not people with talent. The pattern that works is a short first stage — identity, contact, role, CV, right to work, availability — followed by role-specific questions only where they genuinely filter.

What to include:

• Name, email, phone, and the role applied for (pre-filled from the job link). - CV or portfolio upload, with a generous file size and clear accepted formats. - Right-to-work or eligibility confirmation, as a plain yes/no with a follow-up. - Notice period and earliest start date — the two answers hiring managers ask for immediately. - One or two open questions that actually get read. Three or more get skimmed.

What to leave out of stage one: full employment history that duplicates the CV, referee contact details you will not use until offer stage, and salary expectations if the range is already advertised.

Equal opportunities data is a separate form. Diversity monitoring questions should be optional, clearly explained, and ideally collected on their own page so it is visually obvious that they are not part of the assessment. Never make them required.

Onboarding: one checklist, several audiences

Onboarding fails when it is one giant form. In practice there are three audiences and three timelines: the new hire (personal details, payroll, emergency contact, policy acknowledgements), IT and facilities (equipment, accounts, access), and the manager (buddy, first-week plan, objectives).

Use conditional logic instead of one long list. If the role is remote, ask for the delivery address for equipment and skip the desk allocation. If the hire is a contractor, skip payroll and show the invoicing details section. If the role involves driving, show the licence and insurance fields. The employee only sees the ten questions that apply to them rather than the sixty that exist.

Two details that pay for themselves immediately:

• Bank details and national insurance / tax reference on their own step, with a short note explaining who sees them. This is the single most abandoned part of onboarding, and reassurance measurably helps. - Policy acknowledgements as separate checkboxes, each with a link to the document and a timestamped record. One "I agree to all policies" box is convenient and nearly useless as evidence.

Leave requests: capture the decision, not just the dates

A leave form is an approval workflow wearing a form's clothing. The dates are the easy part. What makes it work is everything around them: leave type (annual, sick, parental, unpaid, study), the manager who approves it, cover arrangements, and whether the request crosses a blackout period or a month-end close.

Design notes that reduce back-and-forth:

• Show the calculated number of working days as soon as the dates are entered, so nobody argues later about whether the bank holiday counted. - Make the covering colleague required for absences over a threshold, and optional below it. - Route by leave type: sickness needs a different approver and a different retention rule than annual leave, because it is health data. - Send the confirmation to the employee as well as the manager. A silent approval is the most common reason people ask HR "did that go through?".

Performance reviews: symmetrical and specific

Review forms work best when the employee and the manager answer the same questions independently, then discuss the gaps. That symmetry is what turns a form into a conversation rather than a verdict.

Keep the structure tight: a handful of objectives with a rating and evidence field for each, a short section on how the work was done, one question on development and support needed, and a forward-looking section with next-period goals. Free-text boxes should have a prompt above them ("Give one example where…"), because unprompted boxes produce either a sentence or an essay, never anything useful in between.

Ratings deserve a warning. If a scale has five points and no labels, everyone uses three and four. Label every point, and describe what the top of the scale actually looks like in your organisation.

Expense claims: get it processable first time

An expense claim exists to be paid, so design backwards from finance. Every line needs date, category, amount, currency, cost centre or project, and a receipt image. Mileage needs start and end locations and a rate. Anything over the approval threshold needs a manager sign-off before it reaches finance at all.

Two mechanics remove most rejected claims: require the receipt upload on the same step as the amount, and validate the total against the sum of the lines so nobody submits a claim that does not add up.

Compliance and data handling, in plain terms

HR forms collect some of the most sensitive data an organisation holds. A few non-negotiables:

• Collect only what you need, and say why. A short line under each sensitive question does more for trust than a linked privacy policy nobody opens. - Separate special category data. Health information, sickness reasons and diversity data should be captured separately from general HR records, with tighter access and its own retention period. - Keep an audit trail. Timestamps, submitter identity and version history matter the day someone disputes what they agreed to. - Restrict who can see submissions. Application data, salary information and sickness records rarely need the same audience. - Set a retention rule and stick to it. Unsuccessful applications typically do not need to be kept for years.

Templates to start from

• Weekly timesheet form template — week commencing date, per-day start, end and break times, auto-calculated daily and weekly totals, an overtime flag past a threshold, project or cost code, employee declaration and approver routing.

A quick pre-launch checklist

Before you publish any HR form, run through this:

• Fill it in on a phone, start to finish, as the person who will use it. - Check every required field is genuinely required. - Confirm the notification lands with the right approver, and the confirmation lands with the employee. - Check conditional sections appear and disappear correctly for each role type. - Confirm sensitive fields are visible only to the people who need them. - Add the form link where the process actually starts — the job ad, the intranet page, the manager's checklist — not just in a folder.

Every form in this guide already exists as a free template you can copy and edit: adjust the questions, the branching and the branding, and publish it to a link or embed it on your intranet. Start with the one causing the most email this month, and fix the next one when that has settled.