Copilot summarized a policy instead of rewriting it
A preservation-heavy long-form rewrite was handed to a tool optimized for inline assistance and short transformations.
What the user wanted
The actual target
Rewrite a policy in a new brand voice without losing any rule, exception, heading, or legal meaning.
What they asked
The instruction
Rewrite this policy in the attached voice. Preserve every heading, rule, exception, and legal meaning. Do not shorten it.
What the AI produced
The observable result
A concise, generic summary that merged exceptions, removed headings, and omitted edge cases.
Why
Why WWW assigns this verdict
The instruction was clear, but the chosen workflow encouraged compression rather than a controlled, section-by-section long-document transformation.
What gave it away
The failure was systematic: sections and exceptions disappeared across the document even though preservation was explicit.
Fix
What to do next
- Work section by section with a checklist of headings and exceptions.
- Run a coverage pass that maps every original requirement to the rewritten document.
- Use a long-context writing model or document editor that can compare source and rewrite side by side.
Repaired instruction
A safer retry
Rewrite the document section by section in the supplied brand voice. Preserve every heading, rule, exception, condition, defined term, and legal meaning. Do not summarize, merge, or omit sections. After the rewrite, provide a coverage table mapping each original heading to its rewritten counterpart and flag any sentence whose meaning may have shifted.
Model recommendation
Stay, retry, or switch?
Use Claude or ChatGPT in a long-document workflow with explicit section-by-section coverage, rather than an inline completion flow.
General lesson
What survives this one case
A good instruction can still fail at the wrong desk. Tool choice matters most when completeness and preservation are more important than fluency.