Writing for the Evaluator: Bid Document Design, Layout and Readability

Two contractors bid the same council reconstruction. Both are competent, both have done the work, and their methodologies describe a similar approach. One submission is a continuous wall of text in a small font with the answers buried in the middle of long paragraphs. The other follows the criteria in order, opens each response with a direct answer, and puts the staging in a table.

The second scores better, and it is tempting to call that unfair. It is not. An evaluator can only award marks for what they find, and a panel working through eleven submissions against a scoring sheet is not a careful reader hunting for merit. They are looking for the answer to a specific question, and the submission that makes it easy to find is the one that gets credited for having it.

This guide is about the document rather than the content. What goes into each response is covered across the library — methodology, selection criteria, capability statements — and how panels actually score is covered in how government tenders are scored.

The reader you are actually writing for

Almost every weakness in bid presentation comes from imagining the wrong reader. Contractors write for an interested expert with time. The actual reader is different in five ways that all matter.

• They are working to a scoring sheet, not forming a general impression. Marks are allocated against defined criteria, and anything outside them is unscored however good it is.
• They are reading several submissions in sequence. Yours is being compared directly with the one they read twenty minutes ago, on the same question.
• They may not be a civil engineer. Evaluation panels routinely include procurement, finance and asset staff. Jargon that is precise to you can be opaque to a scoring member.
• They are reading on a screen, frequently a laptop, sometimes scrolling a combined PDF of every attachment.
• They have to justify the score. A moderation meeting requires a panel member to point at something. Text they can point at is worth more than text they have to summarise.

Everything below follows from that last point. Your job is not to impress; it is to make scoring easy and defensible.

The first thirty seconds

An evaluator opening your response to a criterion decides very quickly whether this is going to be easy or hard. Three things determine it.

• Can they tell they are in the right place? The heading should carry the criterion’s own words and number. Not your internal name for the section.
• Can they see the shape of the answer? Sub-headings visible on the first screen tell them the response is organised and roughly what it covers.
• Is there air? A dense block of text signals work. Short paragraphs, spacing and a table signal that the answer has been thought about.

The cheapest single improvement available to most civil bids is to name every response heading exactly as the criterion is named in the request, including its number. It costs nothing, it removes any doubt about where the answer is, and a surprising share of submissions do not do it.

Structure: answer in the order asked

The single most common structural error is reorganising the response into an order that suits the bidder. It feels more logical to the writer and it makes the document harder to score.

• Follow the order of the criteria exactly, even where it is repetitive or awkward.
• Answer every sub-part. Where a criterion contains three questions in one paragraph, break them out and answer each. Evaluators mark against sub-parts, and an unanswered one is a zero on that element rather than a lower score overall.
• Do not merge two criteria because the content overlaps. Repeat the relevant material and cross-reference rather than making the panel find it elsewhere.
• Where a returnable schedule or template is provided, use it. Substituting your own format is a compliance risk before it is a presentation one — see non-conforming and alternative tenders.
• Keep a compliance thread. A short table at the front of the response mapping each criterion and sub-part to the page where it is answered is genuinely useful to a panel and signals discipline.

If the structure of the request is genuinely confusing, that is a clarification question, not an invitation to restructure. Ask it in the clarification window.

Lead with the answer

Civil bid responses habitually build up to the answer. Company history, general approach, philosophy, and then — three paragraphs in — the thing that was asked. Invert it.

Weak opener	Strong opener
“TenderBuilt Civil has over 20 years’ experience delivering projects of this nature and prides itself on…”	“Traffic will be managed in three stages, with the northbound lane kept open throughout. Stage 1 is…”
“We understand the importance of quality management on projects such as this.”	“Quality is controlled through six hold points, listed below, each with a nominated inspector and a release record.”
“Our approach to environmental management is comprehensive and tailored.”	“The two environmental risks on this site are the creek crossing at Ch. 340 and the identified acid sulfate soils. Each is controlled as follows.”

The pattern in the right-hand column is the same each time: the first sentence is the answer, and it is specific to this project. The reason it scores is that a panel member can read one sentence and know there is something to credit. The reason it is uncommon is that it requires knowing your answer before you start writing.

A useful discipline: write the first sentence of every response last, once you know what the response actually says, and make it the sentence you would say out loud if asked the question across a table.

Sentences that survive a scoring sheet

• One idea per paragraph, three to five lines. Long paragraphs hide the scoreable content inside them.
• Prefer the active voice. “The site engineer inspects each lot before the pour” is checkable. “Inspections are undertaken prior to pours” leaves the panel wondering by whom.
• Name who does it. Roles, not the company. “Our team” is not evidence of anything.
• Cut the throat-clearing. “It should be noted that”, “in order to”, “with regard to” and “we would like to take this opportunity” add length to a page-limited document and say nothing.
• Be specific in a way that could be checked. Numbers, chainages, frequencies, names and dates are scoreable. Adjectives are not.
• Bold sparingly, and only the thing you want credited. A page with fifteen bold phrases has none.
• Expand an acronym once, then use it. A procurement officer on the panel may not know it, and our glossary exists precisely because the vocabulary is not universal.
• Do not write in the future conditional. “We would implement” reads as hypothetical. “We implement” reads as a system that exists.

A test worth applying to every paragraph: could a panel member point at this sentence in a moderation meeting to justify a mark? If not, it is either evidence in the wrong form or it is filler.

Headings, numbering and navigation

• Use a clear hierarchy and stick to it. Two or three levels is enough in almost every civil response; deeper numbering makes a document feel like a specification.
• Make headings say something. “Stage 2: maintaining access to the shopping centre” is more useful than “Methodology (continued)”.
• Number pages, and include the criterion reference in the footer. Panels annotate and refer back; unnumbered pages make that painful and make your document the awkward one.
• Give each attachment a name matching the reference in the text. “Attachment C — Project references” beats “Appendix 3”.
• Generate the contents page rather than typing it, so page numbers cannot drift out of alignment during the final edit.
• Keep headers and footers consistent, including the project name, so pages printed or extracted separately remain identifiable.

White space, type and the physical page

Presentation choices are not decoration. They change how much of your answer gets read.

• Do not shrink the type to fit a page limit. Where a minimum font size is specified, it is a compliance requirement. Where it is not, reducing type to squeeze in more words trades readability for volume, which is a bad trade in a scored document. Cut content instead.
• Keep line length moderate. Full-width text across an A4 page at small type is hard to track. Generous margins are not wasted space.
• Use one typeface, at most two. Consistency reads as competence.
• Left-align body text. Justified text on a narrow column creates uneven word spacing that slows reading.
• Keep colour functional. A single accent for headings and table rules is enough. Heavy colour blocks cost ink, print unpredictably and can reduce contrast below the point of legibility.
• Check contrast. Light grey text and colour-only distinctions fail for some readers entirely, and evaluation panels are not exempt from vision impairment.
• Control page breaks. A table split across two pages, or a heading stranded at the foot of one, is the kind of small friction that accumulates.

On page limits generally: treat them as a hard constraint and edit to fit. Exceeding a stated limit risks the excess being disregarded or the submission being ruled non-conforming, which is an expensive way to include an extra paragraph.

Tables: when they beat prose

Tables are the most underused tool in civil bid writing, and they suit the content civil contractors have.

Use a table when the content is comparative, repetitive or has consistent attributes:

Content	Columns that work
Risks	Risk · consequence · control · who owns it
Hold and witness points	Activity · hold point · inspected by · record
Staging	Stage · work · duration · access maintained · interface
Key personnel	Role · person · relevant experience · availability
Plant	Item · number · owned or hired · when on site
Environmental controls	Aspect · risk · control · monitoring · trigger
Compliance mapping	Criterion · sub-part · where answered

Three rules make tables work. Keep them narrow enough to read — four or five columns is usually the limit on a portrait page. Repeat the header row where a table runs over a page. And do not hide the answer in a table: if the criterion asks how you will manage traffic, the answer needs a sentence before the table, because a panel member scoring that criterion should not have to synthesise it from a grid.

Conversely, do not tabulate narrative. Reasoning, judgement and explanation belong in prose; forcing them into cells strips out exactly the thinking that differentiates you.

Graphics that earn their place

A good graphic in a civil bid does something prose cannot: it shows a spatial or temporal relationship at a glance. A bad one is decoration that consumes a page limit.

• Worth including: a staging plan showing what is open and closed at each stage; a site layout with compound, access and laydown; a simple programme extract showing the critical sequence; an organisation chart; a traffic staging sketch; a cross-section explaining a construction sequence.
• Rarely worth it: generic stock photography, clip-art process diagrams, a map of Australia with your offices on it, a pyramid of corporate values, and any graphic that restates a list you have already written.
• A marked-up drawing extract beats a drawn diagram. Taking the actual project drawing and annotating it demonstrates engagement with this project in a way no generic figure can.
• Legibility survives the process. Assume your graphic will be printed in greyscale, at A4, possibly reduced. Fine linework, small text and colour-only coding all fail that test.
• Keep the drawing office style out of it. A CAD sheet dropped into a bid at reduced scale is unreadable. Extract and redraw the part that matters.

The general principle, which applies to the whole document: if a graphic needs the reader to zoom, it is not doing its job.

Photographs, and the caption that does the work

Civil contractors have an advantage here that most industries do not: real photographs of real work. They are routinely wasted.

• The caption carries the point, not the image. “Kerb and channel, Smithfield Road” says nothing. “Kerb and channel constructed under traffic on Smithfield Road, with the northbound lane maintained throughout — the same staging proposed here” makes an argument.
• Choose photographs that show the thing being claimed. If the criterion is about working adjacent to live traffic, the photograph should show exactly that.
• Use your own work, and be able to say where and when. Stock imagery is transparent and slightly insulting to a panel that works in the industry.
• Check what else is in frame. Missing helmets, unrestrained loads, an unsupported trench or an untidy site in a photograph you submitted is evidence against you on a different criterion.
• Keep file sizes sensible. Full-resolution photographs are the usual cause of a submission that will not upload — see §13.
• Have permission where the image shows a client’s asset, identifiable people or another party’s work.

Photographs with argumentative captions are one of the highest-return improvements available, and building a labelled library of them as jobs finish is far easier than assembling one during a bid — which is part of what our guide to building a tender content library sets out.

Evidence, appendices and cross-referencing

• Keep the answer in the response. An evaluator scoring a criterion should not have to open an appendix to find the answer. Appendices hold supporting evidence, not the argument.
• Reference precisely. “Attachment D, page 2” rather than “see attached”. Vague references frequently are not followed.
• Extract rather than attach whole documents where a specific page makes the point. A forty-page management plan attached to prove one process is a burden, not evidence.
• Check that page limits exclude appendices before relying on them, because sometimes they do not, and pushing content into an appendix to dodge a limit is visible.
• Make sure certificates are current at the closing date and legible — insurance certificates and licences are routinely submitted expired or as poor scans.

The small errors that cost trust

None of these loses a mark on its own. Together they shape whether a panel believes the rest of the document, and in civil tendering the inference is specific: a bidder careless with its own document may be careless with a set-out.

• The wrong client or project name. The unmistakable sign of a recycled submission, and it happens on a meaningful share of bids.
• Inconsistent numbers between the response, the programme and the schedules — crew sizes, durations, plant counts.
• Dates that do not match the tender programme.
• Mixed terminology for the same thing across sections, which usually means two people wrote it and nobody reconciled it.
• Placeholder text left in. “[insert project name]” is not rare.
• Tracked changes or comments left in the PDF.
• Document properties carrying another client’s name in the metadata.
• Spelling that a check would have caught, particularly in headings, which is where it is most visible.

The systemic fix is to control versions and to have one person responsible for a consistency pass across the whole submission rather than each author checking their own section.

Mechanics: limits, formats and lodgement

These are the errors that cost the bid rather than the marks, and they are entirely avoidable.

Requirement	What goes wrong
Page limits	Exceeded, or met by shrinking type below a specified minimum. Excess may be disregarded
File format	PDF required and a Word file submitted, or a schedule required in a spreadsheet and returned as PDF, breaking the evaluator’s calculations
File size	Portal limits exceeded, almost always because of full-resolution photographs. Compress images before assembling
File naming	A prescribed naming convention ignored, which on some portals prevents upload
Separate files versus combined	One combined PDF where separate returnables were required, or the reverse
Searchable text	A submission scanned as images cannot be searched, which makes an evaluator’s job materially harder
Signatures	Unsigned forms, or a signature block completed by someone without authority
Lodgement timing	Uploading in the final minutes. Portals slow under load and the deadline does not move

The rule that prevents nearly all of it: upload a complete draft well before the deadline, and then replace it. Most portals allow a submission to be revised up to close, which converts a cliff-edge into a rehearsal and surfaces every format and size problem while there is time to fix it. The portals themselves are covered in our guide to where to find civil construction tenders, and the broader failure patterns in common tender mistakes.

The final read-through

One structured read, by someone who did not write it, catches more than any number of passes by the authors.

• Read it as the panel will: criterion by criterion, with the scoring sheet beside you, marking where the answer is.
• Score your own submission. Where you cannot award full marks, the panel will not either. This is the most useful thirty minutes in the whole process.
• Check every sub-part has an answer against the compliance map.
• Read the first sentence of every response in sequence. They should read as a coherent set of answers to the questions asked.
• Print a few pages, or at least view at 100 per cent, to see what the graphics and type actually look like.
• Check the mechanical list in §13 before uploading, not after.

Where the business does not have a second reader, the compliance checklist is a reasonable substitute for the mechanical part, though not for the judgement.

Checklist

• Does every response heading use the criterion’s own wording and number?
• Is the response in the same order as the criteria, with every sub-part answered?
• Does each response open with a direct, project-specific answer?
• Is there a compliance map showing where each criterion is answered?
• Are paragraphs short, active, and specific enough to be checked?
• Have you named roles rather than referring to “our team”?
• Is the type at or above any specified minimum, and readable?
• Are pages numbered, with consistent headers and footers?
• Are tables narrow enough to read, with repeating header rows?
• Does every graphic survive greyscale printing at A4?
• Does every photograph have a caption that makes an argument?
• Is anything in your photographs evidence against you?
• Do appendix references name the attachment and page?
• Are all certificates current at the closing date and legible?
• Is the client and project name correct everywhere?
• Do crew sizes, durations and plant counts match the programme and schedules?
• Is the PDF text searchable, free of tracked changes, with clean metadata?
• Does the file format, size and naming meet the portal’s requirements?
• Have you scored your own submission against the criteria?
• Is a complete draft uploaded well before the deadline?

The short version

• You are writing for a panel working a scoring sheet through several submissions, partly non-technical, reading on a screen, who must justify the mark in moderation.
• Marks are awarded for what is found. Presentation does not replace substance, but poor presentation loses marks the substance had earned.
• Name every response heading with the criterion’s own words and number. It costs nothing and many bidders skip it.
• Follow the order of the criteria exactly, and answer every sub-part separately.
• Lead each response with the answer, specific to this project. Write that first sentence last.
• One idea per paragraph, active voice, named roles, checkable specifics. Cut the throat-clearing.
• Do not shrink the type to fit a page limit. Cut content instead.
• Tabulate comparative and repetitive content; keep reasoning in prose. Never leave the answer only in a table.
• A marked-up extract of the actual project drawing beats any generic diagram. If a graphic needs zooming, it fails.
• The caption carries the argument, not the photograph. Check what else is in frame.
• Keep the answer in the response; appendices hold evidence, referenced by attachment and page.
• Wrong client name, placeholder text and tracked changes cost trust across the whole document.
• Format, file size, naming and searchable text lose bids outright. Compress images and upload a complete draft early, then replace it.
• Score your own submission before lodging. Where you cannot award full marks, neither will the panel.

Sources and further reading

This guide is general information for Australian civil construction businesses and is not procurement or legal advice. Formatting requirements, page limits, minimum font sizes, file formats, naming conventions, size limits and lodgement rules are set by each request for tender and each procurement portal, and they differ between agencies, councils and platforms. Where a requirement in a tender document conflicts with anything suggested here, the tender document governs, and departing from a stated requirement can render a submission non-conforming. Evaluation methods, weightings and moderation practices also differ between buyers. Always work from the request for tender, its returnable schedules and any addenda. Information is current as at September 2026.

• Australian government and council procurement frameworks and their evaluation practices, which establish the criterion-based scoring, moderation and conformance concepts described in §01, §03 and §13. Requirements differ by jurisdiction and by buyer, and the governing document for any bid is that tender’s own conditions of tendering. Sourced in full in our guides to how government tenders are scored and the Commonwealth Procurement Rules.
• Procurement portal and platform requirements for file formats, file naming, size limits and lodgement referenced in §13, which are set by each platform and by the issuing agency. Late or failed lodgement is generally fatal regardless of cause. Sourced in full in our guide to where to find civil construction tenders in Australia.
• Accessibility and legibility considerations referenced in §07, including contrast and reliance on colour alone. Some agencies apply accessibility requirements to documents they receive as well as to those they publish; where a tender states such a requirement, it is a compliance matter.
• Related TenderBuilt guides carrying the primary-source detail referenced above: addressing selection criteria, writing a construction methodology statement, building a tender content library, tender document control and version management, and common tender mistakes.