Custom intake pages let SpringVerify configure additional data collection steps inside your Add Candidate and Edit Candidate flows — on both the Super Admin and Company Admin portals.
Instead of collecting only the default candidate details, your team can now capture any additional information your organization needs — department codes, cost centre IDs, offer letter details, employment type, or anything else — at the point of candidate creation. No spreadsheets, no follow-up emails, no separate trackers.
Every organisation collects candidate data differently. A fintech onboarding a relationship manager needs different information than an IT firm hiring a contractor. Until now, the BGV form collected only what SpringVerify asked for. Custom intake pages change that.
What it solves in practice:
Custom intake pages are configured by the SpringVerify team on your behalf via the Super Admin portal. This is not a self-serve feature for Company Admins — your team cannot build or edit pages directly.
To get custom intake pages set up for your account: Contact your SpringVerify CSM or account manager. Share what fields you need, which portal they should appear on (Super Admin, Company Admin, or both), and whether they should be mandatory or optional. Your CSM will configure the pages and confirm when they're live.
There is no engineering effort or deployment required on your end.
When adding a candidate: Custom pages appear as additional steps between the Candidate Details step and the Select Package step. Your team fills them in as part of the normal candidate creation flow — nothing changes about how the rest of the process works.
When editing a candidate:
Custom pages appear as additional sections after Basic Information on the candidate profile.
Your CSM can configure any combination of the following field types:
| Field Type | Best Used For |
|---|---|
| Date | Offer date, joining date, document expiry |
| Phone Number | Alternate contact numbers |
| Secondary email addresses | |
| Short Text | Employee ID, cost centre code, department name |
| Long Text | Notes, remarks, additional instructions |
| Number | CTC, notice period in days |
| File Attachment | Offer letters, ID copies, supporting documents |
| Radio Buttons (single-select) | Employment type, work location, gender |
| Checkboxes (multi-select) | Applicable policies, role-based flags |
| Label only (no input) | Disclaimers, instructions, hyperlinks — no response required |
Each field can be configured to appear on:
A page only appears in a portal if it has at least one visible field configured for that portal. If all fields for a portal are removed, the page hides itself automatically.
Fields can be set as mandatory or optional.
Optional fields can be left blank with no consequence.
Mandatory fields must be filled to proceed — with one exception:
| Role | Can Skip Optional Fields? | Can Bypass Mandatory Fields? | Notes |
|---|---|---|---|
| SpringVerify Super Admin | ✅ Yes | ✅ Yes | Uses "I don't have this" option |
| Company Admin (Admin role) | ✅ Yes | ✅ Yes | Bypass is tracked and visible on candidate profile |
| Company Admin (HR role) | ✅ Yes | ❌ No | Must fill all mandatory fields to proceed |
| Candidate | ✅ Yes | ❌ No | Candidate-facing BGV form coming in a later release |
Bypasses are always logged — your CSM and Super Admin users can see when a mandatory field was skipped and by whom.
All changes to custom intake pages and their fields are automatically logged:
This makes custom intake pages fully auditable — useful for compliance, internal reviews, and any situation where you need to know exactly what was captured and when.
Can our Company Admin build or edit custom pages themselves?
Not currently. Custom pages are configured by the SpringVerify team on your behalf. Contact your CSM to add, edit, or remove pages and fields.
How long does it take to set up?
Typically a single session with your CSM. There's no engineering effort or deployment required on your side — changes go live immediately once configured.
Can we have different pages for different roles within our Company Admin portal?
Yes. Visibility controls can be set per field, so certain fields can be shown only to Admin-role users and hidden from HR-role users, or vice versa.
What happens if a mandatory field is skipped?
Admin-role users can bypass using "I don't have this" — but the bypass is tracked and visible on the candidate profile. HR-role users cannot bypass mandatory fields.
Can candidates fill in custom fields on their BGV form?
Not yet. Candidate-facing custom fields on the BGV form are coming in a later release.
Is there a limit on the number of custom pages or fields?
No hard limits. Speak to your CSM about what you need and they'll set it up.
Are custom intake pages available to all SpringVerify clients?
Yes. Contact your account manager or CSM to get it activated for your account.
Write to us at support@springverify.com or reach out to your SpringVerify account manager directly.