Skip to content

policy-process-rewrite.md

Latest commit

 

History

History
78 lines (52 loc) · 2.42 KB

policy-process-rewrite.md

File metadata and controls

78 lines (52 loc) · 2.42 KB
Raw

Policy Or Process Rewrite

Who this is for: Operations, HR, compliance-adjacent teams, team leads, and anyone turning unclear internal guidance into a reviewable draft.

Work problem: Policies and processes often become hard to follow because they mix background, rules, exceptions, and steps. This workflow rewrites for clarity while preserving a change log and review boundary.

Inputs

What you need before running this:

  • Existing policy, process, or SOP text.
  • Intended audience and use case.
  • Required rules, terms, approvals, and non-negotiable language.
  • Reviewer list or approval path.

Copy-ready Codex instruction

Rewrite this policy or process for clarity.

Preserve the meaning of the original unless I explicitly ask for a policy change. Do not invent legal, HR, compliance, security, or operational requirements. If something appears ambiguous, mark it for reviewer confirmation.

Audience:
[write]

Original text:
[paste or attach]

Non-negotiable language:
[paste exact language that must remain]

Desired format:
[policy, SOP, checklist, FAQ, manager guide, employee guide]

Reviewers:
[list if known]

Produce:
1. Plain-language rewritten draft.
2. Change log: original issue, rewritten approach, and whether meaning changed.
3. Ambiguities: items requiring owner or legal/compliance review.
4. Reader checklist: what the target reader should do.
5. Approval checklist: who should review before use.

Do not label this final or approved.

Expected output

A good run produces:

  • A clearer draft without silent policy changes.
  • A change log that reviewers can inspect.
  • Ambiguities and approval needs.
  • Reader-facing checklist or steps.

Human review checklist

Before using the rewrite:

  • Compare the draft against the original.
  • Confirm no rule changed accidentally.
  • Get review from the accountable policy owner.
  • Get legal, HR, security, finance, or compliance review where needed.
  • Mark the document as draft until approved.

Failure modes

Where this workflow can go wrong:

  • It may simplify away important exceptions.
  • It may change meaning while improving readability.
  • It may make compliance-adjacent text sound approved.
  • It may miss required wording if not provided as non-negotiable.

Source boundary

This workflow does not provide legal, HR, compliance, or security advice. It rewrites supplied text for clarity and produces review notes for the accountable humans.