How does employee verification work in EmployDB?

Verification on EmployDB replaces reference phone calls with consented facts. Verified employers issue structured records as part of normal HR work — employment dates, positions, promotions, training, certifications, awards. When a recruiter wants to verify a candidate, they send a request naming exactly which data they need.

The employee is in charge from there: they approve or deny the request, choose which scopes to grant, and can revoke access at any time. Approved access expires automatically, and every single view is logged and visible to the employee. There is no candidate database to browse — without an approved request, a recruiter sees nothing.

What can never be shared

Salary, disciplinary records, medical information, and internal HR notes are structurally excluded — the network has no sharing scope for them. And because only fixed, factual event types exist, opinions like "difficult to work with" are impossible to record, protecting employers legally and employees personally.

What this replaces in practice

For a recruiter, a verification request replaces days of phone tag with a same-day answer once the candidate approves — and the answer is a verified employer's record, not a former colleague's recollection. For the employee, it replaces the anxiety of unknown reference calls with a consent screen: they see who asked, what for, and decide.

For the previous employer, it removes the legal tightrope of reference conversations entirely: the record was issued once, factually, at the time of the event. Nobody improvises on a call, so nobody can be quoted.