Prepare an employment verification letter
Draft a letter from permitted employment facts. HR authorizes release.
How this works
Draft a letter from permitted employment facts. HR authorizes release. Use this for routine requests for a factual employment letter. The workflow should reduce repeated transcription while avoiding unnecessary disclosure or unsupported claims about an employee.
Retrieve only the fields permitted for the stated purpose, populate the approved template, and leave missing facts visible for HR. The resulting letter remains a draft until the authorized issuer checks its contents and release destination.
Before you start
Approved letter template
Obtain the relevant template and required signature or issuing-role block.
Permitted field policy
Confirm whether job title, dates, status and compensation may be included for this request.
Verified HR record
Use the authoritative employment record and its effective date.
Prepare the inputs
- request
- Required
employee ID, purpose and requested recipient
Confirm the requester can obtain the requested employee's information.
- employment_record
- Required
title, start date, current status and permitted optional facts
Do not infer current employment from an old contract alone.
- template
- Required
versioned document with placeholders
Identify required placeholders and avoid adding unsupported clauses.
- release_rules
- Required
permitted fields and issuing authority
Record fields withheld or awaiting confirmation.
Implementation, step by step
Validate the request
- Confirm requester identity through the existing HR process and identify the employee record.
- Clarify the letter's purpose and destination without collecting unrelated personal details.
Checkpoint: The request has a verified employee ID and scope.
Retrieve permitted facts
- Read the authoritative employment fields and their effective dates.
- Exclude compensation or personal identifiers unless the approved request requires them.
Checkpoint: A minimal fact sheet lists evidence and omitted fields.
Populate the draft
- Fill the approved template using exact titles and dates from the fact sheet.
- Retain placeholders or a separate issue list when required facts are missing; do not invent values.
Checkpoint: The draft is complete enough for HR to review.
Check document consistency
- Compare every factual clause with the fact sheet and inspect the rendered document.
- Check date formats, employee identifier handling and any template-specific signature requirements.
Checkpoint: A reviewed draft and explicit omissions are available.
Prepare release handoff
- Provide HR with the draft, recipient and facts requiring confirmation.
- If release is authorized, record the actual issued document and receipt; otherwise keep status awaiting release.
Checkpoint: Draft and issued copies cannot be confused.
Decisions along the way
Compensation requested but not permitted
Omit it and ask HR to resolve the disclosure scope.
Employee status conflicts across records
Hold the affected statement and identify both record timestamps.
Recipient is unspecified
Prepare the permitted generic draft but do not address or send it to a guessed party.
What you will produce
employment-letter.docx
DOCXA template-based letter marked draft until HR releases it.
Include: employee_reference · verified_facts · issue_date · issuer · status
letter-review.json
JSONA minimal audit record of what was verified and disclosed.
Include: request_id · field_sources · omissions · recipient · release_status
Check the result
- Compare names, title and dates directly with the authorized HR record.
- Confirm no optional sensitive field entered without a stated purpose.
- Inspect the final layout for leftover placeholders or template notes.
- Verify issued status only when an authorized release actually occurred.
When something goes wrong
HR connector unavailable
Use a permitted dated export or prepare a blank template and missing-fact list.
Template contains stale wording
Ask the template owner to confirm the version before issuing.
Request references multiple employees
Split requests and access checks rather than combining personal records.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Synthetic: prepare a basic employment letter.
Inputs
Request E14 asks for employment dates and title. Verified record shows start 12 March 2023, title Operations Analyst, active status as of 5 July 2026. Salary is available but not requested.
Expected result
Synthetic result: draft a letter confirming the title, start date and current verified status as of 5 July. Exclude salary and leave release_status=awaiting_HR.
Run a small pilot
Start small
Process a small sample of routine requests with HR reviewing every draft.
Record the baseline
Record manual preparation time and factual or disclosure corrections.
Agree success criteria
Agree acceptable accuracy and review effort before expanding eligible letter types.
Stop or revise
Stop release preparation when identity, record authority or permitted fields are unclear.
Keep the scope clear
- The workflow cannot certify unsupported employment facts or sign for an issuer.
- Drafting a letter does not authorize disclosure to its proposed recipient.
Check before using
HR verifies facts, recipients and release authority.
Business activities
- Support and develop employees
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Employee record · Approved template
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow