Employment Verification
Verification returned within 4 business hours
Employment verification requests are a background-processing chore that hits HR daily. Mortgage lenders, landlords, immigration lawyers, background-check vendors all ask the same three facts (title, dates, salary) and each request takes 15-30 minutes to respond to. Half the time HR gets pinged for verifications on ex-employees they don't remember; the other half, requests sit in an inbox for a week and the employee's mortgage application slips.
An hour-by-hour walkthrough.
Step by step.
- 01
Detect verification requests + verify requester
Email + web form + verification-network signals. Employee consent link back to authorize (or verify against signed release on file). Requester verified against known verification services.
Email · Verification networks (Work Number · Truework) · Consent flow - 02
Look up employment data with correct scope
Active employees: full package (dates, title, salary, bonus). Ex-employees: dates + title only per policy. Immigration cases: enhanced package with legal language.
Workday · BambooHR · Payroll · Policy engine - 03
Generate + send verification response
Signed letter on letterhead (email) or API-push to verification networks (Work Number, Truework). Response within 1-4 hours vs. 3-7 days manual.
Letter templates · Verification network APIs · Email - 04
Handle sensitive cases via HR review
Immigration attestations, visa renewals, unusual requests draft-only; HR reviews language + signs. Legal review for atypical requests (custody proceedings, litigation subpoenas).
Slack · Teams · HR review queue - 05
Log every response for audit + trend
Response filed in employee record. Trend surfaces (which lenders, patterns of mass verification, ex-employee inquiry volume). Feeds policy refinement.
Personnel file · Audit log · Analytics
What you connect to make this run.
Workday · BambooHR · HiBob · Rippling
readEmployment history + current status + salary. Read-only for verification purposes.
The Work Number · Truework · Certify
read+writeVerification-network APIs for automated push. Faster + more secure than email; used where lender is on the network.
DocuSign · Adobe Sign
read+writeEmployee consent capture for verification releases. Ensures every verification has documented employee authorization.
Email · Letter templates
read+writeFallback for requesters not on verification networks. Templated letters on letterhead with digital signature.
Before and after, honestly.
Answers about this playbook.
What about international employees needing verification for foreign purposes?
Country-specific templates + language. Some jurisdictions require notarization or apostille; those escalate to HR for handling with the applicable authority.
How does it handle requests without employee consent on file?
Consent link sent to employee first; verification proceeds only after employee approval. Prevents unauthorized disclosure.
What about salary-history bans (California, others)?
Jurisdictional scope applied. Salary omitted for outbound verifications where prohibited by law even if requested.
Can we handle verification for gig-worker / contractor status?
Yes — contractor verifications use different template (independent contractor, not employee). Prevents misclassification implications.
What about mass verification requests during background-check season?
Batched processing supported. Background-check vendor with 50 employees to verify gets a bulk-response with all approved employees at once.
See it run on your data.
Free plan, no credit card. Connect the systems this playbook needs and run it against a past event first.