AI Prompts for HR Documentation: Structured Output for Job Descriptions, Reviews, and Offer Letters

An HR document can be perfectly formatted and still be wrong for the role, employee, candidate, location, or decision.

A master prompt should generate from an approved document payload, preserve source identity, and return missing information instead of guessing.

Job-Description Contract

{
  "role_profile_id": "approved-id",
  "title_and_level": {},
  "essential_functions": [],
  "nonessential_functions": [],
  "approved_qualifications": [],
  "work_context": {},
  "compensation_fields": {},
  "required_reviews": []
}

Generate separate title, summary, responsibilities, qualifications, work context, compensation or benefit fields where applicable, and required statements. Link each substantive requirement to the approved role record.

The model should report a conflict when the role profile and hiring request differ. It should not choose the more restrictive requirement or copy language from a similar position.

Performance-Review Contract

Use the exact employee, role, review period, reviewer authority, approved criteria, goals, documented evidence, and employee input. Require citations to evidence IDs for factual statements.

Keep five states distinct: evidence, employee statement, manager observation, manager judgment, and final approved rating. Generated wording belongs only in the draft state.

Do not ask the model to infer attitude, loyalty, leadership potential, disability, or intent. Avoid personality labels when the record supports a specific observable behavior.

Offer-Letter Contract

Offer letters vary by jurisdiction, worker classification, role, compensation plan, policy, agreement, and organization practice. Use a current HR or counsel-approved template.

{
  "candidate_and_requisition_ids": [],
  "approved_offer_record": {},
  "template_id": "approved-version",
  "jurisdiction": "approved-code",
  "contingency_fields": [],
  "missing_required_fields": [],
  "approved_for_send": false
}

Compensation, start date, title, manager, location, schedule, classification, contingencies, expiration, and signature authority must come from approved systems. The model should not negotiate, calculate pay, choose terms, or represent that contingencies are complete.

Templates Are Controlled Records

Assign each template an owner, document type, audience, jurisdiction, effective date, required fields, optional clauses, prohibited edits, and retirement state.

Do not keep approved language only inside a prompt. Store it in a controlled source that HR and counsel can review without changing prompt logic.

When a template changes, identify every workflow and pending draft that uses it. Do not silently rewrite an offer already approved under an earlier version.

Accessibility and Translation

Create accessible document structures and provide approved language alternatives. Qualified reviewers verify translated consequential communications, especially where rights, deadlines, benefits, or employment terms are involved.

Do not infer a person's preferred language or accommodation need. Use the approved record and established request process.

Preserve Edits and Approval

Store the generated draft, HR or manager edits, approval, final artifact, delivery, and any corrected version separately. This shows what the model proposed and what the accountable person accepted.

Reviewer edits can inform a later template or prompt revision, but should not silently alter policy or become training data without authorization.

Render and Retain the Official Version

Generate structured content first, then apply the approved document template. Test page breaks, tables, long titles, names, dates, signatures, accessibility tags, and required language so rendering does not hide or truncate a term.

The HR system or document repository should identify which artifact is the official record, who may access it, how long it is retained, and how a corrected version relates to the original. A chat transcript is not a substitute for the signed or issued document.

For unsigned drafts, make the status visible on every exported format. The model should not create a signature, approval mark, or issue date.

No Direct Employment Side Effects

The output should never directly update an applicant-tracking or HR information system, issue a rating, send an offer, post a role, or notify an employee. Code checks the current record and approvals before each allowed action.

Retries need idempotency. A repeated request must not send two offers or create competing versions of an official review.

Test Before Use

Test a wrong role level, missing approval, location change, compensation mismatch, expired template, disputed evidence, inaccessible document, long name, multilingual content, confidential data leakage, and a request to create unsupported reasons.

Read Master Prompts for HR for employment boundaries and Master Prompt Versioning for controlled document updates.

HR Owns the Final Document

HR, hiring managers, compensation and accessibility specialists, and counsel own the content within their roles. Candidates and employees own their statements and decisions. Developers own source mapping, permissions, validation, rendering, versioning, and sending controls.

The prompt removes repeated assembly. It does not authorize the employment action.

Browse HR documentation contracts in the CyWire marketplace.

This article is technical information, not human-resources, employment, compensation, accessibility, privacy, tax, or legal advice.