Preparing a draft for review

A few minutes of preparation before you ask for a review saves a round of feedback afterwards. Reviewers who know what to look at give focused, useful notes.

Checklist before you send a draft for review

1. 1Upload it as the latest version of the right draft, not a new draft. See Replacing a draft with a new revision.
2. 2Write release notes that say what changed since the last version.
3. 3Handle the previous round. Resolve what you fixed, and reply to anything you did not change.
4. 4Mark the draft internal or client-ready, so clients only see what is ready for them.
5. 5Tag the reviewers you need when you share, and say what feedback you want this round.

Tell reviewers what you need

The most useful line in any review request is the scope. Some examples:

• "Rough cut: structure and pacing only. Graphics and colour are placeholders."
• "Fine cut: everything is fair game except the music, which is licensed."
• "Final check: typos, logos, and legal only. Approve if it is good to go."

Internal review first

Many teams run an internal round before a client sees anything. Keep the draft internal while the team reviews it, fix what they find, then mark it client-ready. Internal discussion can stay hidden from the client's view.