Text / review handoff guide

Hand off a text review with changes and open questions

When confirmed edits and unanswered questions travel as one block, unreviewed content can look approved. Separate confirmed changes, open questions, owner and due date before asking for review.

Import a table into Excel

Separate four parts

Part	Role	Review
before / after	Original and revised text	Preserve the source
Confirmed diff	Edits ready to accept	Show the basis
Open questions	Answers still required	Name an owner and due date
Request	Next action for the reviewer	Do not treat silence as approval

If questions remain open, do not describe the text as published or approved.

Reproduce the review with fixtures

Keep before.md and after.md unchanged, then use diff.md to separate confirmed edits from open questions. request.md is the owner-facing template.

## Confirmed changes
- Keep the original CSV unchanged.

## Open questions
- Who owns unknown rows?

Verify and request review

Keep before.md and after.md unchanged.
Extract only edits that are confirmed by the diff.
Name an owner and due date for each open question.
Send request.md and checklist.md, then hand off the final text after answers arrive.

This guide is static browser-local material. Text and input are not sent to an external server.

Do not treat unanswered items as approved

If a question is blank, the owner is unknown, or the before/after mapping cannot be explained, do not close the request. Confirm with the source author.