How to Win More Tenders: 7 Documentation Mistakes to Avoid

Generic capability statements copied from the website. An ‘About Us’ section that describes the company’s history, values, and service offering without connecting any of it to the specific requirements of this contract. Boilerplate language about commitment to quality, safety, and client satisfaction that has appeared, word-for-word, in the last twelve submissions. A response that could have been sent to any tender — because it essentially was.

Evaluators review dozens of submissions, often simultaneously. A generic response is immediately identifiable — and it signals two things that are both damaging. First, that the submitter did not read the requirements carefully enough to tailor their response. Second, that the submitter does not consider this specific contract important enough to invest in a targeted response. Neither impression is survivable in a competitive evaluation.

Every section of your response must be explicitly mapped to the requirements of this specific tender. Use the client’s language. Reference their stated objectives and evaluation criteria directly. Show, in each section, that you have read and understood what they are actually trying to achieve — not just what you want to tell them about yourself. A useful test: read each section and ask whether it could appear, unchanged, in a response to a different client. If yes, rewrite it.

A question asks for your specific approach to managing subcontractor quality — the response describes the general quality management framework. A question asks how you will manage cost variations — the response explains the project governance structure. A question asks for your approach to community stakeholder engagement — the response describes your HSE management plan. Related. Adjacent. But not responsive.

Evaluation rubrics are structured question by question, criterion by criterion. When a response does not directly address the question asked, the evaluator cannot score it against that criterion — regardless of how good the surrounding content is. An adjacent answer is, for scoring purposes, effectively no answer. Evaluators are not permitted to infer what the submitter meant to say, only to score what was written.

Before writing any section, identify the exact deliverable the question is asking for. Write a one-sentence summary of what a perfect answer to this specific question looks like. Then answer that question first — directly and explicitly — before providing supporting context. A useful structure: state your approach in the first sentence, explain how it works in the body, and provide evidence of its effectiveness at the close. Never bury the direct answer in the middle of a paragraph.

“We have extensive experience in complex infrastructure projects.” “Our team is committed to delivering on time and within budget.” “Safety is our highest priority.” “We have a proven track record of client satisfaction.” Every one of these statements appears in hundreds of tender submissions every week across Australia. Not one of them, as written, is verifiable. Not one of them can be scored.

Evaluators are trained to discount unsubstantiated claims precisely because they appear in every submission. A claim that cannot be verified cannot be differentiated — and if it cannot be differentiated, it cannot contribute to a score. Worse, a submission full of unverified superlatives signals that the writer either has no specific evidence to offer, or did not think the evaluator would notice the difference. Both readings are damaging.

Every significant claim must be accompanied by evidence. Replace ‘extensive experience in complex projects’ with a named project, its scope, the specific challenge it presented, the outcome delivered, and — where possible — a client contact willing to verify the account. Replace ‘committed to on-time delivery’ with your on-time delivery rate across the last twelve months, and name the measurement methodology. Replace ‘safety is our priority’ with your lost-time injury frequency rate and the management system that underpins it. Specificity is the only currency evaluators accept.

“We will develop and implement a project management plan.” “A risk register will be maintained throughout the project.” “Quality inspections will be conducted at key milestones.” These statements describe outputs — documents and activities that will exist — without explaining the method for producing them, the process for executing them, or the controls that ensure they work. They are shells that look like answers until you read them carefully.

Method statements are where evaluators assess delivery capability — not intent, not aspiration, but the actual ability to manage and execute the work. A response that names a deliverable without explaining the method for achieving it cannot be scored on delivery capability. It answers the question ‘what will you produce?’ when the evaluator asked ‘how will you do this?’ The distinction is the entire point of the question.

A strong method statement names the specific methodology (PMBOK, ISO-aligned, Agile), sequences the key activities and their interdependencies, assigns accountability for each activity by role (not by name), describes the monitoring and reporting mechanisms, identifies the most significant risks and the specific controls that address them, and explains what happens when something does not go to plan. If your method statement could describe any project by any company, it is not a method statement — it is a placeholder.

Insurance certificates that expired before the submission date. Professional indemnity coverage that does not extend to the scope of the contract being tendered. Licences and registrations that cover a different category of work than the contract requires. A WHS management plan that still carries the name of a previous project. An ISO certificate that lapsed and has not been renewed. Or, most simply: a mandatory attachment that was not submitted because nobody checked the compliance register before hitting send.

In many Australian government and infrastructure tenders, compliance failures are grounds for automatic disqualification — the response is not evaluated on merit at all. The procurement rules are explicit: non-compliant submissions are excluded before the scoring process begins. In private sector tenders the consequence is less formal but no less damaging — a compliance gap signals operational risk, which raises questions about whether this organisation is capable of managing the contract requirements it is claiming to meet.

Build a compliance register that is specific to each tender — a live document that lists every mandatory attachment required by the RFT, the current status of each document (valid / expiring / expired), the person responsible for sourcing or renewing it, and the date it was confirmed as attached. Review this register as a mandatory step in every submission process, no later than forty-eight hours before the deadline. Treat a missing or expired mandatory document as a tender-ending event — because evaluators will.

Three different font sizes across the body of the document. A heading style that changes halfway through because a different team member wrote the second half. Tracked changes visible in the submitted PDF because nobody ran the final acceptance before converting. Tables that split across page breaks with headers that do not repeat. A cover page that still carries the name of the client from the last tender it was adapted from. Section numbering that does not match the requirements document — because the template came from a different RFT structure.

Presentation quality functions as a proxy signal for operational quality. Consciously or not — and research on evaluator behaviour suggests it is often not conscious — evaluators form a first impression from how the document is assembled before they read the first word of content. A disorganised, inconsistently formatted submission signals a disorganised team. It raises the question: if this is how they manage a document they had weeks to prepare, how will they manage a project?

Establish a standard tender template with locked styles for body text, headings, tables, and captions — applied at the start of every response, not assembled from multiple contributors’ drafts at the end. Assign one person the role of document owner for every submission: they apply the template at the outset, reconcile contributor sections as they are received, and conduct the final formatting review before submission. The final review must occur at least twenty-four hours before the deadline — never the night before.

The request for tender is released and the bid/no-bid decision takes two days. Another day passes while someone is assigned to lead the response. Contributors are identified in week one and chased in week two. The method statement is drafted in the final forty-eight hours by the person most available, not most capable. The compliance register is assembled the night before. The document is reviewed once, quickly, and submitted with tracked changes still visible.

Late starts produce all of the above mistakes simultaneously — because there is not enough time to avoid any of them. The response is generic because there was no time to tailor it. The evidence is thin because there was no time to find it. The method statements are shallow because there was no time to think them through. The formatting is inconsistent because there was no time to reconcile it. And the compliance register was not checked because there was no time to build one. Rushed responses show — and evaluators know one when they see it.

Implement a bid calendar that begins the moment an RFT is released. Day one: bid/no-bid decision with clear criteria (can we resource this? do we meet the threshold requirements? is the margin viable?). Day two: contributor responsibilities assigned and acknowledged. Day three: compliance register started. Mid-point review: draft sections reviewed against requirements, evidence gaps identified and closed. Forty-eight hours before submission: full document review — formatting, compliance, cross-referencing. Submission day: no new content — only final checks. A tender submitted without panic is a tender that gives you every chance of winning.