- Mar 5, 2025
How to write a killer first draft
- Matt Ansell
In this blog I will explain how to start your award entry journey on the right foot. A first draft is an entry that you have worked on, before sharing it with others. It contains your tactics, assumptions, and best guesses. It won’t be word perfect. And it may not (always) be on the right lines. But done well, it will provide a solid foundation and take less time to polish into a winning entry.
Here are my top tips for writing a brilliant first draft.
1. Do Your research
Before you start writing, research past winners of the award. Look at what made their entries stand out and identify patterns or themes. This can help structure your entry in a way that resonates with the judges.
Tip: Few organisers publish the entries of past winners. But many winners will feature a case study or blog on their win.
2. Understand the award and its criteria
Read the award criteria. Carefully! Identify what the judges are looking for. Each award focuses on different aspects, such as innovation, impact, or leadership. Make sure your draft directly addresses these criteria.
Tip: The award criteria will explain what the judges are looking for. Highlight key words or phrases. They will be useful when you create a mock score sheet or review your draft.
3. Follow the Instructions
This is so obvious that I almost omitted it. I have seen strong entries disqualified for failing to follow basic submission instructions. So, pay attention to the guidelines, including word limits, formatting, and deadlines.
Tip: Create a checklist. This will help ensure that you don’t miss anything critical, like submitting supporting documents or sticking to formatting rules.
4. Tell a great Story. And back it up
Strong entries tell a story backed by evidence. It’s much easier to write a first draft when you have both to hand. Use a clear structure, with a beginning, middle and end. And always back your claims with appropriate data.
5. Avoid industry jargon
Speak plain English. Focus on explaining the impact of your work in simple, accessible terms. Well written pieces on technical subjects are much easier to read and understand.
6. Respect the reader’s time
Oh, the times I have spent reviewing drafts where the writer (often the project leader / hero) has taken me on a silver lined journey of complete bullsh*t… Get to the point quickly and avoid long-winded explanations. Use clear headings, short paragraphs, and bullet points (if permitted) to make your entry easy to navigate.
7. Include what makes you unique
Whether it’s an innovative approach, impressive results, or a unique perspective, don’t lose sight of what makes your entry stand out.
8. Iterate your answers
A good first draft may require several iterations. Don’t rush this process. Allow time for reflection in between review. This fresh perspective will help you refine your answers and improve clarity. Trust me. The more you iterate, the stronger your final entry will be.
9. Write your draft in a short timeframe
Not to contradict my earlier comment, but I find that writing a first draft in a short, focused period helps maintain consistency in your writing style and approach. It’s much harder to pick up an entry a week or two after you’ve last seen it, than the day after.
10. Never waste a word
Judges appreciate concise, to-the-point answers, so make every word count. Avoid filler content or unnecessary details that don’t contribute to the overall message.
11. Don’t worry (too much) about word count… yet!
While word limits are important for the final draft, don’t let them hold you back in the first draft. For example, if I am drafting a response with a 500 word count limit, then I’m delighted if the draft is less than 600 words. And happy at sub 750.
12. Be mindful of internal sign-off requirements
If your entry requires internal sign-off, factor that into your timeline. Don’t leave it until the last minute to get approval from key stakeholders, as this can cause unnecessary stress and potentially delay your submission.
In my next blog: Most award entries have a wordcount limit. There is an art to making every word count. And i'll explain how.