Policy and handbook updates with Claude Cowork

TL;DR. When a regulation, comp policy, or company practice changes, propagate the update across handbook, intranet, and onboarding pack without an HR partner spending two days on global find-and-replace. Roughly one day per major policy update saved. Tracked changes mode is non-negotiable; silent rewrites are the failure mode that damages trust most.

Job to be done#

Propagate a defined policy change across all affected employee documents with tracked changes, an exec summary, and an audit list of what was touched.

Who runs it#

HR partner with light legal review.

Inputs (inbox/)#

• Current handbook + supporting policy docs
• The change brief: what's changing, effective date, jurisdiction
• House style guide

Outputs (output/)#

• handbook-v[n].docx — updated handbook with tracked changes
• change-summary.docx — one-page exec summary of what changed and where
• affected-docs.xlsx — list of every doc touched, with status

Prompt seed#

Read /inbox/current-handbook.docx and /inbox/change-brief.md.
Identify every section affected by the change.
Produce /output/handbook-v[n].docx with tracked changes; never silently rewrite.
Generate /output/change-summary.docx covering:
  what changed, why, effective date, jurisdiction, who reviewed.
List every doc you touched in /output/affected-docs.xlsx with status
(Updated / Needs Legal Review / Out of Scope).
Conservative: when ambiguous, flag for human review, don't assume.

Quality bar#

• Tracked changes mode always — never silent edits.
• Effective date and jurisdiction explicit on every change.
• Common trip-up: extending a US-jurisdiction change to UK content. Always specify scope.

Time saved (typical)#

About one day per major policy update.

Upgrade path#

• Connector to the knowledge base if the handbook lives there (Notion, Confluence).
• A policy-rev skill standardising the workflow per change type.

Tinkso's take#

Tracked changes mode is non-negotiable. Cowork's silent rewrites of HR policy is the exact failure mode that damages trust most. Make the rule visible in CLAUDE.md and reinforce it in the prompt every time. Tracked changes always is one of those rules that costs nothing to enforce and saves a quarter the first time it would have been violated.