Delivering a first draft to a client without losing control

2 days ago
3 min read

Introduction

A copywriter sends a first draft and waits. What comes back is either two useful notes or a document rewritten in tracked changes by somebody's marketing manager, their director and a colleague who used to work in advertising.

The quality of the writing has surprisingly little to do with which of those happens. It depends on how the draft was framed, what the client was asked to do with it, and whether anybody agreed in advance who gets to decide. A draft sent with no instructions is an invitation for everybody to have a go. The note is the control.

1. Delivering a first draft to a client starts with framing it

The covering note does more work than the document. Spend five minutes writing it.

Say what the draft is for

A structure to react to, not a finished page. Clients who think they are reading final copy edit like proofreaders instead of thinking about the message. Label the version clearly.

Explain the choices you made

Why this angle, why this order, why this length. Copy that arrives unexplained gets judged on taste; copy that arrives with reasoning gets discussed on merit. Three or four lines is enough.

2. Direct the feedback

Open-ended requests produce line edits. Ask for what you actually need.

Ask specific questions

Is the audience right? Is the offer clear? Does the opening earn attention? Three questions produce better answers than "let me know your thoughts". Number them in the email.

Say what not to worry about yet

Wording, headlines, small details. If they know a polish round is coming, they stop rewriting sentences in round one. Say which round handles polish.

3. Agree who decides

This is the single biggest cause of drift. Settle it before the first draft.

One consolidator, not a committee

Ask the client to gather internal views and send one set. Contradictory notes from three people cannot all be implemented and trying looks like incompetence. Ask for one voice.

Set the number of rounds in the quote

Two rounds and a final proof is normal. Agreed at the start it is a term; raised later it looks like resistance. Write it into the proposal.

4. Handle rewrites professionally

Some feedback is right and some is not. Both need handling gracefully.

Distinguish preference from problem

"I do not like that word" is preference. "Our customers do not call it that" is information. Ask which one you are hearing. The answer changes what you do.

Push back once, with reasons

If a change weakens the copy, say so once, explain why, and then do what the client wants. They own the result; you owe them the argument.

5. Close the project properly

Copy projects drift because nothing declares them finished. Declare it explicitly.

Get approval on a named version

One line confirming which draft is final. Without it, a document reopens three weeks later.

Deliver in a usable form and offer the next step

The format the site or designer needs, plus a note on what else could be improved. That is how one page becomes a retainer.

Conclusion

Whether a draft comes back with two notes or a committee rewrite depends on framing rather than on the writing. Say plainly that the draft is a structure to react to, not a finished page, and explain why you chose the angle, order and length — reasoning moves the discussion from taste to merit.

Direct the feedback with three specific questions and say what not to worry about yet, so nobody rewrites sentences in round one. Ask for one consolidated set of notes from one decision maker, and set the number of rounds in the quote. Distinguish preference from information, push back once with reasons and then defer, and close on a named approved version.