Updated September 2026: in 2019, on a tight-deadline opportunity, I filled a deck with standard content and sent it only to the delivery person, stating clearly that it was a draft based on the onsite team's topics. That note later protected me when my manager reviewed the deck critically. I have rewritten it into advice on labelling drafts to protect yourself.
I quickly filled the slides with standard material and shared them with the delivery person alone. In the email, I wrote that it was only a draft based on the topics the onsite team suggested, and that it could be customised further. I did not realise how important that line would be until my manager reviewed the deck and started questioning the slides.
Why label a draft explicitly?
Because people judge work by the standard they assume it should meet. A draft judged as a final version looks poor. A clear label sets the right expectation and creates a record of what was intended, which matters if the work is later criticised.
What should a draft note say?
- That it is a draft, and which version.
- What it is based on, such as the onsite team's topics.
- What still needs input or customisation.
- When the next version will be ready.
Who should receive a draft?
The people who will shape it next, as I did by sending it only to the delivery person. Sending early drafts widely invites premature judgement. Share with a wider group once the content is closer to final.
How do you respond when a draft is criticised as if final?
Point calmly to the draft note: "This was shared as a first draft on Monday based on the onsite topics; here is what is being added." Most reviewers adjust once they see the context.
Is labelling just self-protection?
Partly, but it also helps the work. A clear list of what is missing tells reviewers where their input is most useful. It turns criticism into contribution.
Should you keep drafts on record?
Yes. Save each version with a date. It shows progress and makes it easy to show what was shared when.