Skip to content
In preparationWe’re preparing a reusable WordPress plugin offer.Register your interest
Forms

Online candidate registration forms: a guide for recruitment agencies

By Recruitment Connected · Updated · 5 min read

In short

A recruitment agency candidate registration form should collect enough information to start a relevant conversation: contact details, work interests, location, availability and experience. Decide which fields your agency actually needs at registration, explain how the information will be used, and give candidates a clear next step. Plan later checks and onboarding as separate tasks where appropriate, with their own timing, access and review process.

Need help with this? Digital forms for recruitment agencies

Online registration and e-registration: what does your agency need?

E-registration is an online route for candidates to give an agency their initial details. A useful process also explains who reviews a registration, how missing information is corrected and where an accepted record goes. Decide those steps before turning the paper form into a set of fields.

This guide is for recruitment agencies designing a form. Recruitment Connected provides website and forms services; candidates looking for work should register directly with their chosen recruitment agency.

Compare candidate registration systems and review workflows

Start with the decision your registration form needs to support

Before choosing fields, write down what a recruiter should be able to do with a new registration. For an industrial desk, that might be finding someone available for early shifts within a particular area. For a specialist permanent role, it might be arranging a conversation about relevant experience. Those are different briefs.

A general registration form also serves a different purpose from an application for a named vacancy. Keep the vacancy reference attached to a specific application. Someone registering for future opportunities should be able to describe the work they want without choosing an unsuitable job first.

Candidate registration form fields to consider

Use the following as a discussion checklist, then remove anything your team cannot explain a need for at this stage:

  • Name and contact details: the details your team will use to respond, with required fields clearly marked.
  • Work interests: relevant roles, sectors and preferred type of work, such as temporary or permanent opportunities.
  • Location and travel preferences: enough detail to discuss suitable work, with a full address requested when your process needs it.
  • Availability: a start date, notice period or shift preferences where these affect the work you offer.
  • Relevant experience and qualifications: a short summary or role-specific questions that help the recruiter prepare.
  • CV upload: included where useful for the roles you handle, with clear file requirements and an alternative route if the candidate cannot upload one.

For each proposed field, agree whether it is required or optional, who uses the answer and where it goes. A field that is essential for one desk may be unnecessary for another.

Separate first registration from later onboarding

Map the journey into stages: an initial registration, a recruiter conversation, any role-specific checks and the paperwork needed for an agreed placement or employment arrangement. Some steps may overlap, but each should have a reason and an owner.

Bank details, payroll declarations and signed agreements need their own handling decisions. Ask when your agency actually needs each item, who should be able to see it and how it will be reviewed. Moving an entire paper pack onto the first public form usually makes the design harder to explain.

Try the onboarding form and recruiter review examples

Should candidates upload a CV, complete fields, or both?

Choose the approach around the information your recruiters use. A CV may provide useful context for professional roles. A short set of questions may be more practical when you need to discuss shift availability and relevant tickets or experience. Avoid making someone type a full employment history and upload the same information without a clear reason.

If you accept files, explain the supported formats and size limit before the upload control. Test the route from a phone, including a file stored in a cloud account. Decide what happens when the upload fails, and give the candidate a way to continue or get help.

Make the online registration form work on a phone

A useful test is to complete the form yourself on a small screen, then ask someone unfamiliar with the process to try it. Check these details:

  • Give each field a visible label; placeholder text disappears when someone starts typing.
  • Explain unfamiliar terms beside the question, and show what an acceptable answer looks like.
  • Use relevant input types, such as email and telephone fields, and avoid unnecessary formatting rules.
  • Show errors beside the affected field and preserve the answers already entered.
  • Check the form with a keyboard as well as touch, including the upload and submission controls.
  • After submission, confirm what happened and explain the next step without promising an unagreed response time.

Plan candidate information and right-to-work checks separately

The ICO's data minimisation guidance says personal information should be sufficient for its purpose, relevant and limited to what is needed. Review the reason for each question rather than collecting details because they might be useful later. Link clear privacy information from the collection point and agree how records will be reviewed and removed when no longer needed.

Submitting a registration form or uploading an identity document does not, by itself, complete a right-to-work check. GOV.UK explains the checking routes and requirements. Establish who is responsible for the check in your working arrangement and follow the current official guidance before someone starts work. This article is a form-planning guide, not an approved compliance template.

Connecting candidate registration to Giig or another recruitment system

Write a field map before building a connection. For each answer, name the destination field, the permitted values and the rule for missing or duplicate information. Also decide who checks a new registration before it is used by a recruiter.

A Giig connection depends on your account access and the supported operations. Agree which registration details can be sent, how failures are reported and whether CV files can be handled. Keep payroll documents and other restricted information under their separately agreed access rules. Recruitment Connected is independent and is not affiliated with or endorsed by Giig.

Read the Giig and WordPress integration guide

A practical brief to send your website or forms developer

  1. Describe who is registering and what your recruiter needs to do next.
  2. List the required and optional questions, with a reason for each one.
  3. Confirm the CV upload route and the help available if it fails.
  4. Name the reviewer, system destination and process for duplicate registrations.
  5. Separate later checks, declarations and agreements from the initial form where appropriate.
  6. Agree the privacy information, access rules and record-review arrangements.
  7. Test a complete registration, a correction, a failed connection and the confirmation message.

Recruitment Connected can assess your existing candidate registration form and scope an online workflow around your approved questions, review steps and system access. Start with the form your team uses today and the part of it that causes the most chasing.

Download the blank candidate registration planning brief (plain text)

Sources

FAQ

Common questions.

Start with the information needed for a relevant recruiter conversation: contact details, work interests, location, availability and useful experience. Decide the actual required fields around your agency's process and the roles it handles.

Only ask for information in both places when there is a clear purpose. A CV can provide context while a few structured questions capture the details your team needs to search or discuss roles. Test an alternative route for candidates who cannot upload a file.

That can be assessed against your website, Giig account permissions and the operations your account supports. The fields, file handling, duplicate checks and failure process should be agreed before a connection is built.

No. A registration submission or document upload alone does not complete the required check. Establish responsibility for the check and follow the current GOV.UK right-to-work guidance.

Want help with this?

Tell us where you are starting, and we will work through it with you.