How to Structure a Tender Response From the RFT Itself

Most contractors start a tender response by opening the last one they wrote.

It is understandable — there is a deadline, there is content that has been through review before, and a blank page at 4pm on a Thursday is nobody's idea of a good time. But it produces a document organised around your previous project rather than around this procurement, and it costs points at the very first read.

The structure you need is already written. It is in the request for tender, and the tender wrote it for the panel's convenience, not yours.

Why the RFT's structure is the right structure

An evaluation panel scores criterion by criterion. Each assessor works down the same list, in the same order, filling in a score and a written justification for each one.

If your response follows that order, scoring you is a straight read. If it does not, every assessor performs a mapping exercise — finding your section 6 to score their criterion 2, then jumping back to your section 3 for their criterion 3 — five times over, for every tenderer.

They will do it. They are professionals. But the material they cannot locate does not get scored, and a document that requires assembly loses arguments in the moderation meeting that a well-mapped one wins.

There is a second reason, less obvious and more valuable: building your structure from the RFT forces you to read it properly. Most missed requirements are not missed because the writer was careless. They are missed because nobody ever built a complete list.

Step 1: Extract the criteria, exactly as written

Go through the tender documents and pull out every evaluation criterion, verbatim. Do not paraphrase and do not tidy the wording — the wording is what the panel scores against, and a paraphrase quietly drops the qualifier you most needed to notice.

Two things to watch:

Criteria are not always in one place. The main criteria are usually in the conditions of tendering or an evaluation annexure. Sub-requirements are frequently elsewhere — in a schedule, a returnable form, or a paragraph of the scope that begins "Tenderers should describe…".

The numbering can skip. Tender documents get assembled by several people under time pressure. It is entirely normal to find criteria lettered (a), (b), (c), then (e), (f) — with no (d) anywhere. Follow what is actually there, not what the sequence implies should be there, and do not assume a gap means a criterion is missing.

Step 2: Break each criterion into its questions

Take each criterion and write out every question it actually asks.

A criterion reading "Demonstrated capability and capacity to deliver works of this nature, including relevant experience, current commitments and available resources" is not one question. It is at least four: what have you delivered like this, how is it relevant, what are you currently committed to, and what resources are available for this job.

Each of those questions earns a heading in your response. If a question has no heading, it will be answered in passing or not at all.

Step 3: Add the sections a panel expects even when the criteria are silent

This is where experience separates a good structure from a compliant one.

Tenders do not always ask for everything a panel wants to see. On a head contract, financial capacity and current workload are standard considerations even where no criterion names them. On an occupied site, stakeholder and access management will be read for whether or not there is a heading for it. On anything with a program, the interface between the methodology narrative and the program itself is always scrutinised.

Include those sections, and mark them as supporting rather than pretending they answer a published criterion. A panel does not penalise a contractor for anticipating the obvious question. It penalises the one who left it hanging.

Step 4: Decide what evidence sits in each section

Before writing a word of prose, list against each heading what will prove the claim: which project, which drawing, which extract from a management plan, which named person, which number.

Doing this first has two effects. It tells you immediately which sections have nothing behind them — which is the cheapest possible time to discover it. And it stops the common failure where the narrative is written in week one, the evidence is gathered in week three, and the two never quite meet.

Step 5: Build the compliance matrix at the same time

One table: every criterion, every sub-requirement, every returnable schedule, every "must address" — with the section and page of your response where each is answered.

It is tedious. It is also the single highest-return hour in the entire tender, because it is the only mechanism that catches a silently missed sub-requirement before lodgement rather than after.

What good structure is not

It is not length. A well-structured 40-page response beats a sprawling 120-page one, because the panel finds everything and reads it while still fresh.

It is not presentation. Graphic design does not move a score. Navigability does — and those are different things.

And it is not a template. A template gives you the same headings for every job. Structure built from the RFT gives you the headings this job needs, which is what a panel is reading for.

Starting from a structure instead of a blank page

Building this properly takes a day of focused work by someone who knows what they are looking for. That is the day most contractors do not have.

The Smart Submission Blueprint does that step. It reads your actual tender documents, extracts the evaluation criteria, and builds the section architecture for this specific tender — headings and sub-headings in order, with what each section needs to contain, the evidence a panel expects to find there, and the common mistakes made in it.

What it deliberately does not do is write your content. A panel can tell the difference between a contractor describing their own job and generated text describing a generic one, and the second scores badly. The words have to be yours. You just never start from nothing.

Your first tender is free — one full evaluation and one complete Smart Submission Blueprint per organisation, at no cost.

---

Frequently asked questions

Should my tender response follow the RFT's order or my own? The RFT's order, using the RFT's own criterion wording and numbering as headings. Every departure forces each assessor to map your structure onto theirs while scoring.

How long should a tender response be? As long as it takes to answer every criterion with evidence, and no longer. Where the tender sets page limits, treat them as hard. Length is not a scoring factor; completeness and navigability are.

What if a criterion asks about something we haven't done before? Answer it honestly with the nearest comparable experience and be explicit about the transfer — what is similar, what is different, and how you will manage the gap. A candid answer scores better than an evasive one, and far better than silence.

Do I need to include sections the tender doesn't ask for? Sometimes. Where something is standard for the work type — financial capacity on a head contract, stakeholder management on an occupied site — include it as supporting material. Label it clearly so it does not look like an answer to a criterion.