AiOS→HR / People→Professional Services→Operate & Support→HR10
Policy / Handbook Update Drafts
Review current policy language, diagnose gaps, and produce compliance-checked redline revisions with change rationale.
Structured policy redlining turns recurring case patterns and compliance gaps into traceable, approval-ready handbook changes instead of ad-hoc edits.
GenAI Impact
55%
Faster
5.3
Hours saved
9.6
Hours without AI
Based on: 1 policy section (~10 pages) with regulatory cross-references
The mandatory gap-analysis-before-drafting sequence ensures every redlined clause traces to a documented case trend, gap, or compliance requirement, preventing the untraceable ad-hoc edits common in manual policy updates.
The dedicated compliance validation step blocks AI-hallucinated or legally misinterpreted policy language from reaching approval without regulatory cross-check, preventing compliance exposure that Shadow AI policy drafting would miss.
Before You Start
This workflow processes internal policy text, employee relations case trend data, and compliance reference materials. Do not paste these inputs into public or unapproved GenAI tools.
GenAI may misinterpret legal intent or omit required regulatory clauses. Have a compliance reviewer verify every redlined change against the source compliance references before routing for approval.
Who's Involved
HR Policy Analyst
Reviews current policy language, assembles inputs, and coordinates the redline workflow through to approval.
Compliance Reviewer
Validates redlined changes against regulatory requirements and flags legal or compliance risks.
HR Director
Approves the final policy redline pack or escalates unresolved items for further discussion.
Execution Steps
Before you start
Inputs
Prompt
Identify gaps and outdated clauses in current policy
CONTEXT You will be provided with the following source documents: 1. Current Policy or Handbook Section 2. Case Trend Summary 3. Regulatory or Compliance Reference Notes 4. Stakeholder Change Requests TASK Identify and list every clause or section in the current policy that is outdated, unclear, incomplete, or missing relative to the case trends and any compliance signals in the brief. For each gap, state the location (section or clause reference), the issue type, and a brief explanation of why it needs attention. OUTPUT FORMAT Return a markdown table with the following columns: | Section/Clause | Issue Type | Explanation | |---|---|---| Issue Type must be one of: Outdated, Unclear, Incomplete, Missing. After the table, include a one-paragraph summary of the most critical patterns across the identified gaps. CONSTRAINTS Do not suggest replacement language in this step — focus on diagnosis only. Do not fabricate case trends or compliance requirements not present in the provided inputs. Only flag issues that are directly supported by evidence in the source documents.
Outputs
Verification: Verify the AI did not fabricate gap categories or attribute trends not present in the source case summary.
Before you start
Inputs
Prompt
Draft redlined policy text with change rationale
CONTEXT You will be provided with the current policy or handbook section, a gap analysis report listing identified issues, and regulatory or compliance reference notes. TASK For each gap identified in the gap analysis report, draft a redlined revision of the affected policy text. Present the original text alongside the proposed revision and include a one-sentence rationale for each change. OUTPUT FORMAT For each revision, use this structure: ### [Section/Clause Reference] **Original:** [existing text] **Revised:** [new text with changes clearly marked] **Rationale:** [one sentence explaining why the change is needed, referencing the gap or compliance requirement] EXAMPLE ### Section 4.2 — Flexible Work Arrangements **Original:** Employees may request flexible arrangements subject to manager approval. **Revised:** Employees may request flexible arrangements by submitting a written request to their manager, who must respond within 10 business days with a written decision and rationale. **Rationale:** Case trends show disputes arising from verbal-only approvals with no documented response timeline (Gap: Unclear). CONSTRAINTS Do not introduce changes beyond those identified in the gap analysis. Do not remove policy language that is still accurate and current. Do not reference specific organisations, jurisdictions, or proprietary legal frameworks.
Outputs
Verification: Verify each redlined change accurately reflects the identified gap and does not alter policy intent beyond the documented issue.
Before you start
Inputs
Prompt
Outputs
Before you start
Data Handling: Do not include specific employee names or case identifiers from the trend summary in the rationale output.
Inputs
Prompt
Outputs
Verification: Verify the AI did not introduce legal conclusions or compliance interpretations not supported by the reference materials.
Before you start
Inputs
Prompt
Outputs
Verification: Verify the AI did not silently resolve conflicts between stakeholder requests and compliance findings.
Before you start
Inputs
Outputs
Reference
Guardrails
- Source-Backed Changes Only — Every redline must trace to a documented gap, case trend, or compliance requirement; do not include edits based on AI inference alone.
- Original Intent Preserved — Retain existing policy language that remains accurate; only modify clauses the gap analysis identifies as outdated, unclear, or incomplete.
- Diagnosis Before Drafting — Complete the full gap analysis before drafting any redlines to prevent premature edits that miss systemic issues.
Pitfalls
- Accepting AI-drafted redlines without verifying each change against the original policy and compliance references
- Pasting full employee relations case details into the prompt instead of using the anonymised trend summary
- Allowing the AI to introduce new policy clauses not supported by the gap analysis or stakeholder requests
- Skipping the compliance validation step and routing draft redlines directly for stakeholder approval
Definition of Done
- Every redlined change maps to a specific gap identified in the gap analysis report
- The compliance reviewer has validated all redlines against the regulatory or compliance reference notes with no unresolved flags
- The consolidated redline pack includes a rationale summary for every change that a non-specialist stakeholder can understand
- No personally identifiable information or raw case details appear in any generated artifact
Unlock the Full Library
Get full access to all prompts, execution steps, and downloadable examples — for this playbook and the rest of our GenAI capability framework — AGASI AiOS.
We'll send a magic link — no password needed.
AGASI AiOS · HR10 v1.0 · Apr 7, 2026