Intermediate Address Collection on the BGV Form is a SpringVerify feature that prompts candidates to declare all residential addresses they have lived at within a configurable lookback period — not just their current address — directly on the background verification form at the time of submission. The feature automatically structures and captures this complete residential history, enabling SpringVerify's verification engine to cross-check each address against the appropriate verification method configured for your company. By collecting intermediate addresses upfront, the feature eliminates the back-and-forth typically required when gaps in residential history are discovered later in the verification process.

• Captures residential history gaps upfront: Candidates are prompted to provide all addresses within the defined lookback window at the very first touchpoint, eliminating the need for your HR team to manually chase candidates for missing address details mid-verification.
• Per-company configurable lookback window and verification method: Your organisation can define exactly how far back the address history must go — whether 1 year, 3 years, or longer — and choose the verification method (such as document-based or database verification) that best suits your compliance and operational requirements.
• Complete address history in one submission, fewer insufficiencies downstream: Because all relevant addresses are collected in a single, structured submission, verification teams have everything they need from day one, significantly reducing insufficiency rates and accelerating overall turnaround times.

1. Your SpringVerify account manager enables and configures the Intermediate Address Collection feature for your company, setting the lookback window and preferred verification method.
   
   
   
   
   
2. You initiate a background verification check for a candidate through the SpringVerify dashboard
3. The candidate receives the BGV form link via email or your ATS integration and opens the form.
4. Within the Address section of the BGV form, the candidate is prompted to enter their current address and then sequentially add all intermediate (previous) addresses they have lived at within the configured lookback period.
   
   
   
   
5. The candidate uploads the relevant supporting documents for each address declared, as required by your configured verification method.
   
   
   
   
6. Once the candidate submits the form, SpringVerify ingests the complete address history and routes each address for verification using the method configured for your organization.
7. Your HR dashboard reflects real-time verification status for each address, and the final report consolidates all address verification outcomes in one place for your review.
   
   
   

Q: How many intermediate addresses can a candidate declare on the BGV form?
A: There is no hard cap on the number of intermediate addresses a candidate can add. The form will continue to prompt for additional addresses until the entire configured lookback window is covered with continuous date ranges. Candidates who have moved frequently will simply add more address entries until the period is fully accounted for.

Q: What is the typical turnaround time for verifying multiple intermediate addresses?
A: Turnaround time varies by verification method and the number of addresses declared. Document-based and database verifications for each address are generally completed within 24–72 hours. Field verifications may take 5–7 business days per address. Overall TAT for a candidate with multiple intermediate addresses will depend on the method configured and geographic spread of the addresses. Your SpringVerify account manager can provide estimated timelines based on your specific configuration.

Q: What happens if an intermediate address cannot be verified?
A: If verification for a specific address is unsuccessful — for example, due to a landlord being uncontactable or documents not matching — that address will be marked as Unable to Verify in the candidate report. The final report will clearly indicate which addresses were verified and which were not, along with the reason, allowing your HR team to make an informed adjudication decision. SpringVerify will not automatically fail the entire check based on a single unverifiable address.

Q: What types of documents are accepted as proof for intermediate addresses?
A: Accepted documents for each intermediate address include rental or lease agreements, utility bills (electricity, gas, water, telephone), bank account statements, Aadhaar card (where the address matches the period in question), passport, voter ID, or a notarised affidavit for addresses where formal documentation is unavailable. Documents must clearly show the candidate's name, the address in question, and ideally a date falling within the declared period of residence. Your SpringVerify configuration may specify preferred document types — consult your account manager for the definitive list applicable to your organization.

Q: How does SpringVerify handle the personal address data collected through this feature?
A: All address data collected through the BGV form is stored and processed in accordance with SpringVerify's data privacy policy and applicable Indian data protection regulations. Data is encrypted in transit and at rest, access is restricted to authorized personnel, and candidate data is retained only for the period specified in your organization's agreement with SpringVerify. Candidates are informed of the data usage purpose through the consent declaration on the BGV form before they begin filling it in.

If you have questions about enabling or configuring Intermediate Address Collection for your organization, or if you encounter any issues during setup or candidate submission, our support team is here to help. Reach out to us at support@springverify.com and we will respond within one business day. For configuration changes, escalations, or account-specific guidance, please contact your dedicated SpringVerify account manager directly — they can also arrange a walkthrough of the feature if your team needs a hands-on orientation.