Most candidates who land on a job page never finish applying. Many of them leave at the form. The recruitment website CV upload step is where good traffic goes to die: too many fields, a file picker that fails on a phone, a consent box nobody understands, and no sign that anything was received.
This guide covers how to build a candidate registration form that people complete and that your consultants can use. You will get a field-by-field approach to form length, advice on mobile and cloud uploads, when to offer LinkedIn apply, how to capture consent properly, how to push data into your ATS, and what a good confirmation email contains.
What a candidate registration form should do
A candidate registration form is the page or panel where a candidate gives you their details and CV so you can consider them for a role or for future roles. It has one job: get a usable, consented candidate record into your database with as little effort from the candidate as possible.
Separate two journeys. An application is for a specific job. A registration is for general interest. They can share a form, but the wording, the consent and the follow-up differ. If you blur them, candidates get confused and your data gets messy.
Keep the candidate registration form short
Every extra field costs you completions. The CV already holds most of what you need, so ask for the minimum and parse the rest. As a typical range, forms with four to six visible fields complete noticeably better than forms with ten or more, though results vary by sector and seniority.
- Full name
- Email address
- Mobile number
- CV upload (required for applications, optional for quick registration)
- Consent checkbox, unticked by default
Move everything else to later. Salary expectations, notice period, right to work, location and sector preferences can be asked in a follow-up step, a profile page or a consultant call. Ask them once the candidate has already committed.
- Forcing account creation and a password before applying
- Asking candidates to retype their work history after uploading a CV
- Mandatory fields that are not needed to assess the candidate
- CAPTCHA puzzles that fail on mobile; use invisible spam checks instead
- Error messages that wipe the form when one field is wrong
Make CV upload work on mobile
A large share of job-seekers browse and apply on a phone, but their CV often sits somewhere awkward. If your upload button only opens a local file picker, many will give up. Test this on a real iPhone and a real Android handset, not just a browser emulator.
- Support for Google Drive, OneDrive, Dropbox and iCloud Drive through the native file picker
- Accepted formats of PDF, DOC and DOCX, with the limit stated next to the button
- A file size limit generous enough for real CVs, typically at least 5MB
- A clear progress indicator and a visible filename once the file is attached
- A fallback to apply with a LinkedIn profile or by emailing a CV later
Also let candidates apply without a CV when it makes sense. A short form that captures name, email and phone, then asks for the CV in the confirmation email, recovers people who are on a train or have no file to hand.
Where LinkedIn apply options fit
Offering a LinkedIn-based apply route can cut effort for candidates who keep their profile up to date and have no current CV. It is an option, not a replacement. Some candidates dislike sharing a social profile, and profile data is often thinner than a CV.
Keep the standard CV upload visible alongside it. Check what data actually arrives in your ATS, and that you still capture consent in your own words. Profile data does not remove the need for a lawful basis and a clear notice. Check current LinkedIn platform terms before you build, as access to apply tools changes.
Capture consent properly
Under UK GDPR you need a lawful basis for processing candidate data and you must be open about what you do with it. Many agencies rely on legitimate interests for recruitment, and some use consent, especially for sharing details with clients or for marketing. Take advice from your own data protection lead or solicitor on which applies to you.
- Link to a plain-English privacy notice next to the submit button
- Say who will see the CV: your consultants, and clients only when relevant
- State how long you keep data and how a candidate can ask for deletion
- Use separate, unticked boxes for job alerts and marketing
- Record the timestamp, form version and wording agreed with each submission
Storing proof of consent matters as much as asking for it. If the record never reaches your database, you cannot show what the candidate agreed to.
Send applications straight into the ATS
If a CV lands in a shared inbox and someone copies it across, you lose speed and accuracy. Candidates get slow replies and duplicates pile up. The form should write directly to your ATS through its API or a supported integration.
- Create the candidate record, or update an existing one, using email as the match key
- Attach the original CV file and run CV parsing
- Link the application to the correct job and source
- Save consent fields, timestamps and the privacy notice version
- Alert the owning consultant, and log failures so no application is silently lost
Test it with real submissions weekly. Integrations fail quietly when an ATS field changes or a token expires. A simple check, such as submitting a test application every Monday, catches problems before candidates do.
Confirmation emails and on-page messages
After submit, show a thank-you message on the page and send an email within a minute. Silence makes candidates apply twice or assume the form broke.
- A clear subject line naming the job or your agency
- What happens next and a realistic timeframe
- The name and contact details of a real consultant or team
- A link to update their details or withdraw consent
- An invitation to add missing items, such as a CV, if they skipped it
Track the thank-you page as a conversion event in your analytics so you can see where candidates drop out, by device and by source.
Next steps
Start with an audit. Submit a test application on your phone, count the fields, check the consent wording and confirm the record appears in your ATS with the CV attached. Fix the biggest friction first, usually field count or mobile upload. If you want help, our work on job pages at /services/job-pages and on ATS integration at /services/ats covers exactly this kind of build.
Frequently asked questions
How many fields should a candidate registration form have?
Aim for four to six visible fields on the first step: name, email, phone, CV upload and consent. Ask for salary, notice period and preferences later, once the candidate has committed. Your CV parser should fill in work history so nobody types it twice.
Should a CV upload be mandatory on a recruitment website?
For a specific job application, usually yes. For general registration, make it optional and ask for it in the confirmation email. This captures candidates who do not have a CV to hand on mobile, and you can still follow up to complete their record.
Do I need consent to store a CV under UK GDPR?
You need a lawful basis and a clear privacy notice. Many agencies rely on legitimate interests for core recruitment, and use consent for marketing or sharing with clients. Confirm your approach with a data protection adviser, and store a record of what each candidate was told.
