What is a capability statement — and where is it actually used?

A capability statement is a concise, evidence-led document that demonstrates your business can deliver a defined scope of work. For a civil contractor it is part credentials dossier, part plant register, and part proof-of-track-record — distilled into a format a procurement officer can scan in two minutes and a technical evaluator can score against published criteria.¹

It is not a single-use document. In Australian civil construction it does the heavy lifting across at least five distinct procurement moments:

• Prequalification and registration schemes — supporting your application to road-authority and council prequalification systems. (See our guide to civil contractor prequalification in Australia.)
• Expressions of Interest (EOIs) — where a one-page capability summary is often the entire ask before shortlisting.
• Tier 1 and head-contractor supply chains — when you approach a major contractor to be added to their subcontractor database for a pipeline of work.
• Panel and standing-offer arrangements — where it anchors the experience and resourcing sections.
• Full tender responses — attached as a capability annexure that supports your methodology statement and experience criteria.

Because it travels so widely, the capability statement is the one marketing asset where polish and procurement rigour have to meet. A statement that reads like a glossy brochure will be ignored by an evaluator looking for evidence; a statement that reads like a compliance form will be ignored by a Tier 1 estimator looking for a reason to call you.

Why does the capability statement matter so much for civil SMEs?

Australian government procurement does not award work to the lowest price. Every Commonwealth, state, and council purchase is governed by the value-for-money principle, which weighs financial and non-financial benefit together rather than defaulting to the cheapest quote.² In practice, the quality-versus-price split on a typical civil construction tender runs around 60–70% non-price to 30–40% price, with relevant experience and past performance alone accounting for 20–30% of the total score.³ Your capability statement is the primary evidence base for that experience weighting.

For SMEs specifically, the leverage is even greater. The Commonwealth Procurement Rules direct agencies to weight small-and-medium-enterprise participation within their non-price criteria, and recent reform has pushed SME and local-content considerations further up the scoring sheet.⁴ A capability statement that clearly establishes your size, locality, and delivery record lets an evaluator award those marks without having to dig. (For the detail on how each criterion is weighted, see our guide on how government tenders are scored.)

The blunt commercial reality: a contractor with the right plant, the right certifications, and a strong project history will still lose work if the capability statement fails to surface those facts in the form and order the evaluator expects.

What do evaluators actually look for?

Across government and Tier 1 procurement, capability is assessed in four recurring categories. Strong submissions provide evidence against all four rather than over-indexing on one.¹

Capability category	What the evaluator is testing	Evidence that scores
Technical	Can you physically do this scope of work?	Relevant trade experience, plant and equipment register, key personnel competencies, work-type breadth
Financial	Are you a safe commercial bet at this contract size?	Turnover band, contract-value track record, financial assessment level, banking/bonding capacity
Compliance	Will you meet legal and policy obligations?	ISO certifications, insurances, licences, WHS record, prequalification levels
Delivery	Have you actually delivered comparable work, on time?	Project case studies with outcomes, references, on-time/on-budget metrics

An evaluator scoring a prequalification or experience criterion is looking for a fast, defensible “yes.” That means the document has to answer three questions almost instantly: Is this contractor the right size and type for this work? Do they hold the certifications and capacity this contract requires? Can they prove they have done it before? Every section below exists to answer one of those three questions.

What should a civil construction capability statement include?

Based on guidance from specialist tender consultancies and government procurement templates, a complete civil construction capability statement should cover the following sections, broadly in this order.¹⁵

1. Company overview and point of difference

Open with a single, strong sentence that states what you do, where you operate, and why you are a credible choice. Lead with credentials, not adjectives. A civil example: “An ISO 9001, ISO 14001 and ISO 45001-certified civil contractor with a 15-year record delivering road, drainage, and bulk earthworks packages for councils and state agencies across NSW and QLD, maintaining a Lost Time Injury Frequency Rate below 2.0.” That one line establishes work type, geography, certification, longevity, and safety performance before the reader reaches paragraph two.⁶

2. Core competencies (work types)

List the specific civil work types you self-perform — bulk and detailed earthworks, road construction and resurfacing, stormwater and drainage, kerb and channel, utilities trenching, concrete structures, site preparation. Be precise: “drainage” is weaker than “stormwater drainage to 1800mm RCP, including pit construction and CCTV verification.” Precision signals genuine capability and helps an evaluator match you to the scope.

3. Licensing, certifications and compliance

Set out your management-system certifications (ISO 9001 quality, ISO 14001 environmental, ISO 45001 WHS), contractor licences, and prequalification levels. If you hold or are working toward the certification “trifecta” that gates larger government work, say so explicitly — see our guide to the ISO prequalification trifecta for civil contractors. Include insurances (public liability, professional indemnity, workers’ compensation, contract works) with cover limits.

4. Plant and equipment register

For civil contractors, the capability statement doubles as a plant register — and evaluators treat it that way. Detail major plant by type and capacity (excavators by tonnage, rollers, graders, trucks, water carts), note ownership versus hire, and reference any GPS machine-control or maintenance regime. Owned plant of the right capacity is direct evidence you can resource the program without scrambling.⁵

5. Key personnel

Name your principal delivery staff — project manager, site supervisor, leading hand, safety and environmental personnel — with their tickets, qualifications, and years of experience. For panel and Tier 1 work, a short organisational chart helps. Personnel typically carry a 10–20% slice of non-price scoring on government work, so this section earns marks directly.³

6. Project experience / case studies

The single most scored section. Three to six recent, relevant projects with client, value, scope, and a measurable outcome. (Detailed guidance in section 7 below.)

7. Financial capacity

State your annual turnover band and the contract-value range you routinely deliver. If you hold a financial assessment level under a scheme such as the Buy.NSW Financial Assessment scheme, quote it — it tells an evaluator the contract ceiling you are pre-cleared for.

8. References and contact

Two or three contactable referees from recent comparable projects, plus clear company contact details, ABN, and registered business name. Make sure the named referees know they may be called.

The structural test. Before you finalise the document, check that a reader who only skims the headings and the first line of each section can still answer: what you build, where, to what certifications, with what plant, and on what projects. If the skim doesn’t deliver those five facts, the structure is wrong — not the content.

How long should a capability statement be?

There is no single right length — there is a right length for each use. The practical rule used across Australian procurement is to keep a tiered set of versions:¹

• One page — for EOIs and first-contact approaches to Tier 1 contractors, where the reader wants a fast filter, not a dossier.
• Two to eight pages — the standard range for most subcontractor and panel submissions, with room for a proper plant register and three to six case studies.
• Extended / tender annexure — a fuller version tailored to a specific tender’s experience and resourcing criteria, cross-referenced to your methodology.

Length is a function of evidence density, not page count. Eight pages of generic capability marketing will score worse than two pages of specific, quantified, project-backed claims. When in doubt, cut adjectives and add facts.

How do you turn claims into evidence that scores?

The difference between a capability statement that wins and one that gets filed is almost always the shift from assertion to evidence. Evaluators score what they can verify, not what you declare.

Weak (assertion)	Strong (evidence)
“We have extensive civil experience.”	“We have delivered 47 civil packages over 12 years, including a $1.4M road reconstruction for [Council].”
“We are committed to safety.”	“ISO 45001 certified; LTIFR below 2.0 across the last three financial years; zero notifiable incidents in 24 months.”
“We own modern plant.”	“Owned fleet: 3× 20–30t excavators, 2× smooth-drum rollers, GPS machine control on all graders.”
“We deliver on time.”	“On the [Project] drainage upgrade, completed two months ahead of program despite 24-hour delivery constraints.”

Facts, figures, dates, and dollar amounts are the strongest currency in any tender document — they are specific, checkable, and impossible to dismiss as marketing. The discipline is simple: for every claim, ask “could a sceptical evaluator verify this?” If not, attach a number or a project to it.

How to write project case studies that win

Your project experience section is where the capability statement earns the bulk of its marks, because it is the only part that proves — rather than promises — delivery. Use a consistent structure for each case study:

1. Project name, client, and value — establish relevance and scale immediately.
2. Scope — the specific civil work types delivered, with quantities where they impress (volumes of earthworks, lineal metres of pipe, area of pavement).
3. Challenge — the constraint that made it hard: live traffic, environmental sensitivity, restricted access, a compressed program.
4. Approach — what you did about that constraint, in a sentence or two.
5. Outcome — the measurable result: ahead of program, zero environmental breaches, no lost-time injuries, defect-free handover.

A worked example in the civil voice: “Bulk earthworks, drainage infrastructure, and concrete foundations for a passenger-terminal enabling package. Under strict operational constraints, we coordinated 24-hour deliveries during low-traffic windows, implemented dust suppression beyond the environmental requirement, and finalised the works two months ahead of schedule.”⁵ Note that the most persuasive detail is not the construction technique — it is the evidence of control: managing constraints, protecting the environment, and beating the program.

Choose case studies that mirror the work you are bidding for. A council assessing a stormwater upgrade wants to see drainage projects, not your largest car park. Relevance beats prestige.

The most common capability statement mistakes

The failures that cost civil SMEs are consistent and avoidable:

• Brochure, not evidence. Pages of mission statements and stock photography with no quantified track record. Evaluators score evidence; they ignore adjectives.
• One generic version for every purpose. The same eight-pager sent to a one-page EOI and a Tier 1 estimator. Maintain tiered versions and tailor the experience section to the work.
• Burying the plant and certifications. The two facts a civil evaluator most wants — owned plant and current certifications — hidden on page six. Surface them early.
• Vague work-type descriptions. “Civil works” instead of the specific scopes you self-perform. Precision is capability.
• Stale content. Out-of-date insurances, lapsed certifications, or your best recent project missing entirely. A capability statement decays — see below.
• No measurable outcomes in case studies. Describing what you built without proving it went well. The outcome line is the point.

For the broader set of errors that cost civil contractors across an entire submission, see our guide to common tender mistakes.

How to maintain and version your capability statement

A capability statement is a living asset, not a one-off project. The contractors who get the most from it treat it like part of their tender content library:

• Keep a master version with every project, then cut tailored versions from it for each opportunity.
• Refresh quarterly: add completed projects, retire old ones, update insurances, certifications, turnover, and safety statistics.
• Maintain tiered lengths (one-page, standard, extended) so you are never rebuilding under deadline.
• Store the underlying evidence — certificates, insurance schedules, reference contacts, project photos with captions — alongside the document so claims can be substantiated fast.

This is the difference between scrambling to assemble credentials in the final 48 hours before a deadline and dropping a polished, current capability statement into a submission in minutes.

Key takeaways

The capability statement is the most leveraged document a civil construction SME owns: it appears in prequalification, EOIs, panels, Tier 1 supply chains, and full tenders, and it is the primary evidence base for the experience and capability criteria that decide most awards. Because Australian procurement is built on value for money rather than lowest price, and because experience and past performance alone can carry 20–30% of the score, a well-built capability statement converts your real track record into marks an evaluator can award without effort.³

The winning version is specific where the losing version is generic: precise work types, an owned-plant register, current certifications surfaced early, and project case studies that prove delivery with measurable outcomes. Keep it current, keep it tiered, and tailor the experience section to every opportunity. Build it once, properly, and maintain it — and it will earn its keep across every submission you make.

Need a capability statement that scores?

References

1. EstimateOne, A Complete Guide to Writing a Winning Capability Statement. https://estimateone.com/insights/winning-capability-statement-guide/
2. NSW Government, Tender Evaluation Criteria — value for money, info.buy.nsw. https://www.info.buy.nsw.gov.au/buyer-guidance/source/select-suppliers/evaluation-criteria
3. Australia Tender Alerts, Government Tender Evaluation Criteria Explained. https://australiatenderalerts.com/guides/tender-evaluation-criteria-explained/
4. Australian Government Department of Finance, Commonwealth Procurement Rules (SME participation and non-price criteria). https://www.finance.gov.au/government/procurement/commonwealth-procurement-rules
5. GovBid, Sample Capability Statement & Template (Australia). https://www.govbid.com.au/blog/sample-capability-statement
6. Dweebi, How to Create a Construction Company Capability Statement. https://dweebi.com.au/blog/construction-company-capability-statement/

TenderBuilt — Tender Writing Specialists for Civil Construction. NSW | QLD | VIC. This article is general guidance for Australian civil construction SMEs and does not constitute procurement or legal advice.