Employment Verification Request Form

What this template is for

Use it before HR or payroll responds to a named employment-verification request from a landlord, lender, agency or another employer.

Use the document when the organisation needs a dated record that a later reader can understand without guessing what happened. It separates facts from conclusions, gives the affected person a response path, and limits free text so the form does not collect sensitive material merely because a blank field was available.

The document is drafted for ordinary US private-sector use. It does not replace a state-mandated notice, government form, collective bargaining procedure, benefit-plan notice, technical audit protocol or regulator-prescribed document.

What the source document leaves out

The Jotform source is written as a printable artefact rather than as a controlled operational record. It does not adequately explain who may approve the document, whether a signature is acknowledgement or agreement, what evidence should be attached, where the completed record belongs, or what happens when law or a contract gives the affected person a stronger right.

That omission matters because these documents are usually used at the point where facts are disputed: a termination, a warning, a release, an employment check, a software licence or an audit. A polished PDF cannot repair an unclear decision trail.

Do not use it as permission to obtain a consumer report, medical record, criminal record or financial history. It is a request and consent record, not a background-check authorisation unless separately adapted for the FCRA procedure.

How this improved version is structured

The form separates requester identity, employee identity, purpose, consent, fields requested, recipient, delivery method, verification and retention.

The document uses named headings rather than numbered self-references. Optional blocks can be turned on or off by the workbench, so a sentence that points to “clause 7” would eventually point at the wrong text. Named clauses remain stable when optional content changes.

The page explains the document itself: the purpose, drafting choices, evidence, compliance checks, clause meaning and common misuse cases. It does not claim that downloading or signing the document creates legal compliance.

US legal and compliance points

The FTC and EEOC explain that employment background reports trigger FCRA and nondiscrimination obligations. The request form therefore distinguishes a simple employer-held fact verification from a consumer-report process and tells the user not to merge them.

Federal guidance is only one layer. States and cities may add rules about final pay, personnel records, wage deductions, leave, privacy, restrictive covenants, background checks, energy reporting, consumer warranties or professional qualifications. The master therefore includes a state-law/work-location field and tells the user exactly where the federal source stops.

The template avoids overclaiming. It does not say that the document is attorney-approved, valid in every state, sufficient for every employer or a substitute for professional advice. It is a structured starting point that makes missing research visible.

Recordkeeping and privacy

The request contains identity and employment information. Restrict access, verify the recipient, avoid copying unnecessary identifiers and record exactly what was disclosed.

Keep the completed document only where it belongs. A disciplinary or termination record may belong in a personnel file; a medical restriction may require separate confidential storage; a licence belongs with the product and customer records; technical audit data may contain building-security or commercial information. Mixing these files creates access, retention and disclosure problems.

Limit narrative fields to facts, requested terms, approvals, findings and next actions. Do not use the document as a place to store passwords, medical diagnoses, protected characteristics, unsupported opinions or settlement promises.

When not to use it

Do not use it for a broad background investigation, medical certification, immigration form, payroll change, subpoena response or agency request that has its own procedure.

Do not use the template to waive non-waivable rights, punish protected activity, evade wage payment, misrepresent a person's employment, grant rights you do not own, make an unsupported safety claim, or present an indicative audit as a certified engineering report. Do not use it where another form or procedure is mandatory.

If the facts are disputed, high-value, safety-critical, medical, union-related, immigration-related, involving harassment or discrimination, involving a minor, or likely to lead to litigation, obtain appropriate review before the document is sent or signed.

Clause-by-clause guide

Requester identity

Records the organisation, contact and role of the person asking for information.

Purpose and recipient

States why the data is wanted and who will receive it.

Consent

Creates a record of employee authorisation where required or chosen by policy.

Requested fields

Limits the response to dates, title, status, compensation or other selected fields.

Delivery and verification

Sets a secure delivery channel and confirms the recipient before sending.

Disclosure record

Records what was sent, by whom and when.

US compliance checklist

The request is a control point: if the scope is not clear, the response should wait.

• Authenticate the requester

  Use a known channel or independent callback before releasing employment data.

• Define the purpose and fields

  Do not accept a request that leaves the recipient, purpose or information scope blank.

• Record consent or authority

  Use the organisation’s disclosure policy and applicable law to determine whether employee consent is required.

• Do not confuse it with an FCRA form

  A consumer-report authorisation and adverse-action process has separate requirements.

  FTC — background checks: what employers need to know

• Exclude unnecessary sensitive data

  Do not request medical, genetic, family or identity information for ordinary verification.

  EEOC — disability-related inquiries and medical examinations

• Retain a disclosure trail

  Keep the request, response and delivery record according to the employment-record policy.

  EEOC — recordkeeping requirements

How to complete this template

1. Confirm the document and decision owner. Check that this document is the right record and identify the person authorised to approve it. If a regulator, court, union agreement, customer contract or professional standard requires a prescribed form, use that form first and retain this document only as supporting detail.
2. Gather only necessary facts. Enter names, dates, roles, scope, amounts, conditions and next steps for the document. Keep facts separate from conclusions. Do not add diagnoses, protected characteristics, confidential credentials, speculation or copied material that does not belong in the record.
3. Check law and policy before signing. Use the checklist to test federal requirements, then check the state or local rule, handbook, policy, collective agreement, benefit plan and contract that actually govern the matter. Treat a blank state-law field as a prompt for research, not as permission to assume federal law is enough.
4. Give the affected person a fair response route. Give the employee or recipient a chance to correct factual errors, ask questions and raise a protected request or objection. Record whether a signature acknowledges receipt, accepts terms, authorises work, or merely confirms that the document was delivered.
5. Store, review and supersede carefully. Put the completed document in the correct file, restrict access to people with a business need, set a review date where the arrangement continues, and replace or withdraw it when the facts, policy or law changes. Keep medical or other specially protected information separately where required.

Frequently asked questions

Related templates

• Employment Contract Template (US)