top of page
Search

How to Write Your First Draft (Without Staring at a Blank Page)

  • Writer: Piers Riley
    Piers Riley
  • Jan 6
  • 3 min read

Opening a tender document for the first time can be daunting.


You read the first question… and nothing comes out. The cursor blinks back at you. You know your business, you know what you do well, yet somehow getting started feels harder than it should.


That moment is common - even for experienced bid writers. And it’s rarely about not knowing enough. More often, it’s because the question feels heavy, unclear, or high-stakes. A blank page usually means one thing: you need structure, not more effort.


This article explains a practical way to move from blank page to first draft - calmly, methodically, and without overthinking.


Why starting a tender response feels hard


Tender questions often ask you to do several things at once. You may need to:


  • Interpret what the procurement team is really asking

  • Decide what information is most relevant

  • Organise your response logically

  • Write in a way that will score well against evaluation criteria


Trying to do all of that in one go can feel like a losing battle, especially under time pressure.


When a task feels vague or open-ended, starting is often harder than the writing itself. If you’ve been staring at the screen for more than a minute or two, that’s usually a signal to pause - and time to build a writing structure.


Structure is your way in


Structure gives your brain something concrete to work with. Instead of trying to answer the whole question at once, you break it into smaller, manageable parts. That immediately narrows your focus and makes progress feel achievable.


In tendering, structure doesn’t slow you down - it speeds you up.


Anchor yourself to the question


Before you write anything, copy the full tender question into a working document or use the response forms that have been provided.


Next, highlight the instruction words, common ones (and what the procurement team is likely looking for) include:


  • Describe: State clearly what you do or what exists, focusing on facts rather than justification.


  • Outline: Summarise the main points or steps without going into detailed explanation.


  • Demonstrate: Provide evidence or examples that prove you can do what you claim.


  • Explain: Show how and why something works by linking actions to outcomes.


Highlighting them early and understanding what is needed gives you direction before you write a single sentence.


Break the question down before you start writing


Many RFT questions contain multiple ideas in one paragraph. Trying to respond to them in one pass often leads to rambling or missed points.

Instead:


  • Split the question into smaller prompts or headings

  • Turn each requirement into its own section


This step is critical. It:


  • Makes the response easier to plan

  • Reduces the risk of missing something important

  • Creates a natural structure for evaluators to follow


How well you break down the question often determines how smoothly the rest of the writing goes.


Build momentum early


Don’t wait for the “perfect” opening sentence - like an artist, put something on the canvas and build from there.


You can tart with:


  • The section you know best

  • The most straightforward part of the question


Once something is on the page, momentum builds. Progress creates clarity.

At this stage, don’t worry about polish. If you stop to perfect wording, you interrupt your flow. Instead:


  • Keep drafting

  • Leave notes where evidence or data will be added later

  • Strengthen the language during review


Your goal here is movement, not perfection.


Use the same approach for technical questions


Methodologies, risk management, and governance sections often feel harder because they sit between bid writing and subject matter expertise.


However, the approach doesn’t change:


  • Break the question down

  • Identify what input is needed

  • Focus on clarity rather than volume


Note - the procurement team will not always be subject matter experts, so make your content easy to understand.


Structure helps evaluators too


Clear structure doesn’t just help you write - it helps your maximise your response score.


Evaluators read large volumes of submissions under time pressure.


When your response:


  • Mirrors the question

  • Is logically organised

  • Is easy to follow


…it becomes easier to assess. That ease of reading builds confidence in your capability and professionalism.


A steadier, more repeatable way to work


A first draft is a working document - not the final product!


Approaching tender questions with structure creates a calmer, more repeatable way of working. It supports:


  • Clearer thinking

  • Better collaboration with SMEs

  • More consistent outcomes


When you work this way, tenders feel more manageable - and results more reliable.


Still not sure what

to do? Get in touch and we can do it for you!


See how we could help you win your next government contract.


It starts by contacting us for a free consultation and a quote. Reach our team on enquiries@kiwibidsupport.co.nz or use our online enquiry form.

 
 
 

Comments


bottom of page