Create requests
Start a request with candidate identity, contact and check-specific details. Review the information before submission to reduce avoidable delays.
Guidance for employers, operations teams and candidates using DigiVerifier to create requests, provide consent, upload documents, track checks and review completed reports.
Start with the candidate details required for the selected checks. The exact inputs depend on the verification package.
Start a request with candidate identity, contact and check-specific details. Review the information before submission to reduce avoidable delays.
Common inputs include name, phone number, email, employment or education details, address information and consent from the candidate.
Upload supporting documents only when they are required for the selected verification. Clear files and matching details help the review move faster.
Track open requests, identify cases waiting on candidate action and review completed reports from the platform workflow.
Candidates are asked to provide consent before verification checks proceed. The consent step helps keep the process transparent.
Information is used for the verification requested by the organization and handled through controlled workflows.
A typical workflow moves through request submission, candidate consent, verification activity, report generation and completion.
DigiVerifier supports automated verification workflows and can discuss integration options where an enterprise needs requests to connect with existing HR or recruitment systems.
Yes. Bulk request workflows are useful for campus hiring, lateral hiring batches, recruitment drives and large onboarding programs.
Organizations can discuss user access needs during onboarding so HR, recruitment, operations and compliance stakeholders can follow the appropriate workflow.
Completed reports are made available through the DigiVerifier workflow. Delivery and integration expectations can be configured during implementation discussions.
An organization you are joining or working with has initiated a background verification request. DigiVerifier may contact you to collect consent, confirm information or request supporting documents.
Your information is used for the verification workflow requested by the organization. The information required depends on the checks being performed.
If submitted details are incorrect, contact the requesting organization or DigiVerifier support with the corrected information and enough context to identify your case.
Check that the link has not expired, the file format is supported and the entered details match the request. If the issue continues, contact support with your name, email and the company requesting verification.
DigiVerifier is designed for repeatable verification operations. Ask about bulk uploads, user access planning and integration options during onboarding.
Prepare your verification policy, expected monthly volume, check packages, candidate communication process, report review owners and any system integration requirements. This helps implementation stay focused.
Common causes include incomplete candidate details, pending consent, unclear documents, mismatch between submitted information and records, or a check that needs additional review.
Retry with a clear file, check the file size and format, and make sure the document belongs to the requested check. If the issue continues, contact support with the request details.
Confirm that the request has reached completion and that the right team member is reviewing it. If the report is still unavailable, contact support with the candidate name and request reference.
If something in the process is not working, or a result does not look right, email us and a member of our team will help.