Define the scope
Agree the role-relevant checks, purpose, permitted sources, locations, expected inputs, and decision ownership.
Verification methodology
How ZenNextVerify conducts background verification
Our methodology keeps the agreed scope, candidate information, source context, evidence, quality review, and reported outcome connected at check level.
Reviewed methodology
Reviewed by the ZenNextVerify Verification & Quality Team
Last reviewed 3 October 2026
Collect authorised information
Obtain consent and collect only the candidate details and documents needed for the selected checks.
Verify each claim
Keep every employer, qualification, address, identity record, or other claim attached to its exact verification check.
Review findings and evidence
Compare provided and verified information, assess supporting evidence, and return incomplete work for correction when required.
Report a traceable outcome
Release check-level findings, relevant remarks, approved annexures, and a report reference that can be checked online.
Scope and authorisation
Start with the purpose—not with every available check
The employer and ZenNextVerify define which checks are relevant to the role, what information is required, which sources or methods are permitted, and who will review the outcome.
Candidate consent and clear notice are obtained where required for the selected checks. The intake should collect only the information needed for that scope; candidate documents do not belong in a public enquiry form.
Before verification begins
- Defined employment-screening purpose
- Role-relevant service selection
- Candidate notice and consent where required
- Agreed source, jurisdiction, and method
- Named review and decision ownership
Check-specific approach
What each verification check reviews
Open a service to see its usual inputs, review scope, source approach, workflow, dependencies, and possible outcomes. The final method is confirmed for the actual engagement.
Employment VerificationValidate a candidate's stated work history with a structured, employer-specific verification trail.
Information usually required
- Candidate consent and employment details
- Experience or relieving documentation, where applicable
- HR or authorised employer contact details
- Any client-specific verification scope
What may be reviewed
- Employer name and location
- Employee identifier, where available
- Designation and department
- Joining and leaving dates
- Employment type and current status
- Reason for leaving, where permitted
Verification approach
- 1.Capture each employer as a separate candidate record.
- 2.Assign the exact employment record for independent verification.
- 3.Compare provided and verified values field by field.
- 4.Quality-review the evidence and release the final finding.
Source approach
An authorised employer representative, official employment record, or another approved employment source is used according to the agreed scope.
Common dependencies
- Employer response policy and availability
- Accurate employer and employment-period details
- Older or archived employment records
Possible check outcomes
Verified detailsCorrected detailsUnable to verifyInsufficient information
Explore Employment VerificationEducation VerificationConfirm academic credentials against institution or authorised-source records.
Information usually required
- Candidate consent
- Degree, diploma, marksheet, or certificate
- Roll or registration number
- Institution and course details
What may be reviewed
- Institution and campus
- Course or qualification
- Specialisation, where relevant
- Enrolment or roll number
- Study period and completion year
- Result or award status, where available
Verification approach
- 1.Review the submitted academic record for completeness.
- 2.Identify the institution and permitted verification channel.
- 3.Compare the response with the candidate-provided details.
- 4.Record evidence and complete an independent quality review.
Source approach
The institution, university, authorised records office, or an approved education-verification channel is approached for the scoped credential.
Common dependencies
- Institution response channel and calendar
- Correct roll, registration, course, and campus details
- Availability of older academic archives
Possible check outcomes
Credential confirmedData discrepancyRecord not foundUnable to verify
Explore Education VerificationAddress VerificationVerify current or permanent address information through the approved method for the case.
Information usually required
- Candidate consent
- Complete address with postal code
- Permitted proof of address
- Contact details needed for the approved method
What may be reviewed
- Address and locality
- City, state, and postal code
- Residence status, where in scope
- Period of stay, where available
- Landmark or location context
- Source response and supporting evidence
Verification approach
- 1.Validate that the submitted address is complete.
- 2.Select the approved physical or remote verification method.
- 3.Document the source response and address observations.
- 4.Review evidence before the result is released.
Source approach
The approved physical, remote, documentary, or location-supported method is used for the exact current or permanent address in scope.
Common dependencies
- Complete address, postal code, and contact details
- Candidate or respondent availability
- Local access and the verification method agreed with the client
Possible check outcomes
Address confirmedAddress discrepancyInsufficient detailsUnable to verify
Explore Address VerificationCriminal VerificationConduct a consent-led search within the approved jurisdiction and verification scope.
Information usually required
- Explicit candidate consent
- Identity and address details required for the approved search
- Defined jurisdiction and client scope
- Any legally required supporting document
What may be reviewed
- Search jurisdiction
- Permitted court, police, or approved source
- Search criteria and date
- Whether an in-scope record match was found
- Finding notes and source evidence
Verification approach
- 1.Confirm consent, identity inputs, and jurisdiction.
- 2.Use only the approved verification source and search criteria.
- 3.Record the search date, result, and supporting evidence.
- 4.Apply quality review before client-visible release.
Source approach
A permitted court, police, or approved source is searched within the documented jurisdiction, criteria, and search date.
Common dependencies
- Correct identity and address history
- Jurisdiction and source availability
- Sufficient identifiers to distinguish similar names
Possible check outcomes
No in-scope match foundRecord match requires reviewUnable to searchInsufficient information
Explore Criminal VerificationIdentity VerificationCheck identity information while keeping document numbers masked in operational views.
Information usually required
- Candidate consent
- Permitted identity document
- Candidate name and relevant identity details
- Client-defined verification scope
What may be reviewed
- Name and document type
- Masked document number
- Date of birth, where in scope
- Document validity indicators
- Match or discrepancy outcome
Verification approach
- 1.Collect identity details through a controlled intake.
- 2.Mask sensitive document identifiers in operational displays.
- 3.Run the approved identity verification method.
- 4.Review the response and record a clear result.
Source approach
The permitted identity document or approved verification response is matched against the candidate information collected for the check.
Common dependencies
- Readable and valid permitted document
- Consistent candidate identifiers
- Availability of the approved verification method
Possible check outcomes
Identity confirmedIdentity mismatchDocument invalidUnable to verify
Explore Identity VerificationReference VerificationCapture a structured professional or personal reference response with traceable context.
Information usually required
- Candidate consent
- Referee name, designation, and contact details
- Relationship to the candidate
- Client-approved questionnaire
What may be reviewed
- Referee identity and relationship
- Professional context
- Period of association
- Responses to agreed questions
- Contact attempts and response status
Verification approach
- 1.Validate the referee details and approved questionnaire.
- 2.Contact the reference through the agreed channel.
- 3.Record responses faithfully with relevant context.
- 4.Review completeness before releasing the finding.
Source approach
The nominated referee is contacted through the agreed channel and responses are recorded against the client-approved questionnaire.
Common dependencies
- Accurate referee contact details
- Referee availability and willingness to respond
- A clear relationship to the candidate
Possible check outcomes
Reference completedPartial responseReferee unavailableUnable to verify relationship
Explore Reference VerificationDatabase VerificationSearch an approved database using documented criteria, scope, and search date.
Information usually required
- Candidate consent where required
- Accurate identity or entity search details
- Approved database and purpose
- Client-defined search scope
What may be reviewed
- Approved database name or category
- Search criteria
- Date of search
- Match or no-match response
- Relevant result notes and evidence
Verification approach
- 1.Confirm the permitted database and search purpose.
- 2.Validate the minimum search inputs.
- 3.Run and document the search with its timestamp.
- 4.Quality-review the result before release.
Source approach
The approved database is searched using the documented criteria, purpose, and timestamp for the engagement.
Common dependencies
- Accurate search identifiers
- Database availability and permitted access
- The coverage and update cycle of the selected source
Possible check outcomes
No match foundPotential match for reviewSearch unavailableInsufficient criteria
Explore Database VerificationCourt Record CheckReview court records within an agreed jurisdiction, with identity matching and source-backed findings.
Information usually required
- Candidate consent and approved search scope
- Full name, date of birth, and relevant identity details
- Address history or jurisdictions to search
- Additional identifiers needed to distinguish similar names
What may be reviewed
- Agreed courts and search jurisdiction
- Candidate identifiers used for matching
- Case references and available case status
- Search date and source records
- Potential matches that need clarification
Verification approach
- 1.Confirm the identity inputs and courts included in the scope.
- 2.Search permitted court sources using the agreed criteria.
- 3.Review potential matches and retain source references with the search date.
- 4.Quality-review findings and unresolved identity matches before release.
Source approach
Permitted court sources are searched within the agreed jurisdiction, then potential matches are reviewed against available candidate identifiers.
Common dependencies
- Correct courts and jurisdictions
- Availability and searchability of court records
- Enough identifiers to resolve possible name matches
Possible check outcomes
No in-scope match foundPotential match requiring reviewRecord identified within scopeUnable to complete the search
Explore Court Record CheckPolice Clearance Check (PCC)Review a police clearance certificate or authorised response against the candidate and agreed requirement.
Information usually required
- Candidate consent
- Clearance certificate or application details, where available
- Identity and address details needed for the agreed process
- Purpose, jurisdiction, and client requirements
What may be reviewed
- Candidate details on the supplied certificate
- Issuing authority and relevant jurisdiction
- Certificate or application reference
- Issue date and stated scope
- Available authority response and supporting evidence
Verification approach
- 1.Confirm the clearance requirement and relevant issuing authority.
- 2.Review the submitted certificate and candidate details.
- 3.Use the available permitted channel to request or confirm the response.
- 4.Record the evidence, limitations, and quality-reviewed outcome.
Source approach
The supplied certificate or authorised response is reviewed against the relevant issuing authority, jurisdiction, and agreed requirement.
Common dependencies
- Issuing-authority process and response time
- Certificate or application reference where available
- Identity, address, purpose, and jurisdiction requirements
Possible check outcomes
Certificate details confirmedClarification requiredAuthority response pendingUnable to verify
Explore Police Clearance Check (PCC)UAN CheckCompare candidate-authorised UAN-linked employment records with the work history supplied for verification.
Information usually required
- Candidate consent and employment history
- Candidate-authorised service-history or supporting records
- Relevant employer names and employment periods
- A defined comparison scope; no account password or OTP
What may be reviewed
- Candidate details on the authorised record
- Available employer or establishment entries
- Available joining and leaving information
- Differences from the declared employment history
- Source, review date, and record limitations
Verification approach
- 1.Agree the employment records and periods to review.
- 2.Collect candidate-authorised records through the approved channel.
- 3.Compare available entries against the declared employment history.
- 4.Record differences and obtain clarification before the reviewed outcome is released.
Source approach
Candidate-authorised UAN-linked records are compared with the declared employment history through the approved collection process; passwords and OTPs are not requested.
Common dependencies
- Candidate-authorised service-history records
- Employer names and employment periods
- Completeness of the records available for review
Possible check outcomes
Available records consistentDifference requiring clarificationRecords incomplete or unavailableUnable to verify
Explore UAN CheckSocial Media VerificationReview agreed public profiles for role-relevant information, with identity checks and human review.
Information usually required
- Candidate consent and clear notice of the review scope
- Known public profile URLs or handles
- Client-approved role-relevant review criteria
- Defined platforms and review period
What may be reviewed
- Public profile links and identity consistency
- Information within the approved review criteria
- Source links, observation dates, and relevant context
- Potential impersonation or ambiguous profile matches
- Items requiring candidate clarification
Verification approach
- 1.Agree the platforms, review period, and permitted criteria.
- 2.Check that the public profiles can reasonably be linked to the candidate.
- 3.Record only in-scope observations with source context.
- 4.Human-review ambiguous findings and allow clarification before release.
Source approach
Only agreed public profiles are reviewed against documented, role-relevant criteria. Private content and sensitive-trait inference are excluded.
Common dependencies
- Known public profile links or handles
- A reasonable identity match to the candidate
- Public availability of in-scope content during the review period
Possible check outcomes
Review completed within scopeClarification requiredProfile identity uncertainPublic information unavailable
Explore Social Media VerificationCIBIL CheckReview a candidate-authorised credit bureau report for an agreed, role-relevant employment purpose.
Information usually required
- Explicit candidate consent
- Candidate identity and PAN details through the secure workflow
- Current contact and address information
- Documented role-relevant purpose and agreed report scope
What may be reviewed
- Candidate identity match on the authorised report
- Credit bureau or authorised provider
- Report reference and review date
- CIBIL score reported by the source
- Differences or limitations requiring review
Verification approach
- 1.Confirm the permitted purpose and explicit candidate consent.
- 2.Match the candidate identity through the approved secure process.
- 3.Obtain or review the authorised credit bureau report.
- 4.Record the report reference, score, limitations and quality-reviewed outcome.
Source approach
A candidate-authorised credit bureau report is obtained or reviewed for a documented, role-relevant purpose through the approved secure process.
Common dependencies
- Explicit consent and documented purpose
- Accurate identity and PAN details
- Availability of the authorised credit-bureau report
Possible check outcomes
Review completedIdentity discrepancyFurther review requiredReport unavailable
Explore CIBIL CheckEvidence and annexures
Keep proof connected to the finding it supports
Evidence is handled at verification-check level so one file or photograph is not mistaken for support for an unrelated finding.
- Evidence remains linked to the exact verification check and submission it supports.
- Candidate-provided details and source-confirmed details remain distinguishable in the working record and report.
- Quality reviewers select which relevant evidence is client-visible; internal working material is not automatically released.
- Address-verification photographs can be presented as captioned annexures when they form part of the approved method.
- An upload is not mandatory where the approved method and finding do not require a document.
- Unrelated files and sample material are not used as case evidence.
Candidate detail, source response, and reviewer decision remain distinct
A submitted document is an input, not an automatic verification result. The report should identify what the candidate provided, what the source or approved method established, and how the finding was reviewed.
Finding framework
How check and case results are represented
Colour codes summarise a reviewed outcome; they do not replace the check details, source context, or employer's fair assessment.
Check result
Green
The information available for the check is consistent with the agreed scope and no material discrepancy was identified.
Check result
Amber
A difference, exception, or contextual point needs employer review or candidate clarification.
Check result
Red
A material discrepancy or in-scope adverse finding was recorded and should be reviewed in its reported context.
Check result
Unable to verify
The available source or approved method did not establish the claim despite the documented process.
Check result
Insufficient information
The minimum information needed to complete the check was not available or remained incomplete.
Case-level result
- A case-level result is suggested from the reviewed check results: Red takes precedence, followed by Amber.
- Unable-to-verify, insufficient-information, or missing check outcomes lead to Review required.
- A case is Green only when every included check is Green.
- An authorised reviewer can override the suggested case result only with a recorded reason.
Quality control
A separate review before standard report finalisation
Vendor completion and quality approval are different workflow stages. QC examines whether the finding is complete, consistent, supported, and ready for client reporting.
Review 1
Completeness
Check that the selected scope, mandatory fields, source context, findings, and result are present.
Review 2
Consistency
Compare candidate-provided values with verified values and ensure discrepancies are described accurately.
Review 3
Evidence relevance
Confirm that selected annexures belong to the exact submission and support the reported finding.
Review 4
Correction
Return unsupported or incomplete work with field- or document-level correction items and review the response.
Review 5
Approval
Approve the check result, recording a reason whenever QC changes the submitted result.
When a source does not respond
Uncertainty is recorded—not converted into a positive result
Response time and record availability can sit outside the verification team's control. The workflow preserves what was attempted and what remains unresolved.
- 1Confirm that the case contains the minimum details needed for the approved method.
- 2Record contact or search attempts and the source response available at that time.
- 3Request candidate or client clarification when missing information can reasonably unblock the check.
- 4Use Unable to verify or Insufficient information when the claim cannot be established; do not silently mark it verified.
- 5State the source context in the finding so the employer can interpret the outcome fairly.
Reporting and authenticity
A report should be understandable and traceable
The released report presents the approved snapshot without exposing candidate data through its public verification page.
- Candidate, client, case, and report identifiers
- The checks included in the agreed scope
- Candidate-provided and verified details where relevant
- Check-level results, source or method context, and material remarks
- Approved annexures placed with the verification they support
- A reviewed case-level result and clear completion context
- A public report reference and QR code for released-report verification
When a valid correction creates a new released report, version history remains traceable and the public reference identifies the officially released report metadata.
Privacy and access
Sensitive information follows purpose and responsibility
Verification work requires controlled access throughout intake, assignment, evidence review, reporting, and retention.
Purpose and consent
The selected checks, information collected, and permitted sources must relate to an agreed employment-screening purpose.
Role-scoped access
Clients see their organisation's records; vendors see assigned work; operations, administration, and QC access reflects their responsibility.
Sensitive identifiers
Operational views use masked identity-document values where the full value is unnecessary.
Controlled documents
File type, size, case relationship, role, and visibility determine how a document can be uploaded or accessed.
Audit and report history
Important workflow actions, result changes, corrections, report versions, and releases remain traceable.
Retention by agreement
Retention and deletion periods should follow the client agreement and applicable obligations rather than an unsupported universal promise.
Candidate clarification
A difference should be reviewed in context
Where the process identifies a material difference or unresolved identity match, the employer should consider the reported context and any appropriate candidate clarification before acting.
Decision responsibility
ZenNextVerify reports findings—not hiring decisions
The employer remains responsible for the final employment decision, including role relevance, its policy, fair treatment, candidate clarification, and applicable legal requirements.
Plan a verification scope around the role
Share your hiring roles, locations, volumes, and review process. We will help map the relevant checks, inputs, method, and reporting workflow.
Business emails
Call us