The most reused document you own
It goes everywhere your tenders go.
The capability statement opens prequalification applications, lands you on panels, gets you past Tier 1 procurement teams, and sits behind half the bids you’ll lodge this year — which is exactly why a tired, brochure-style PDF quietly costs work. Evaluators skim for evidence: scope, value, client and outcome on every project, current prequal levels, real plant, named people.
TenderBuilt builds the document from your actual delivery record — written, structured and set in a format designed to be read, then handed over with editable source files so it stays yours.
What you get
Every section an evaluator looks for.
- Company snapshot — structure, leadership, key personnel CVs
- Capability matrix — trades, project values, geographies
- Plant & equipment register with photographs
- Project portfolio — 8–12 case-study tiles with metrics
- Accreditations & prequalifications, ISO statements
- Insurances summary & certificates appendix
- Editable InDesign / Word source files, with an annual refresh
| Item | Detail |
|---|---|
| Document | 12 – 16 pages |
| Project tiles | 8 – 12 case studies |
| Handover | Print + digital + editable source files |
| Refresh | Annual — projects, prequal levels, plant |
Fees are fixed at scoping and confirmed in a written work-order — see the pricing page or raise it on the call.
How it runs
From working session to handover.
Working session
One structured session on your projects, plant, people and the work you actually want to win — the document is positioned around that, not around everything you’ve ever done.
Evidence gather
Project records, photos, completion details, insurances, accreditations and prequal levels collected against a checklist, so nothing stalls at draft stage.
Write and set
The full document written and laid out in a format built for skim-reading evaluators — capability matrix, project tiles with metrics, systems and insurance summaries.
Review and handover
Your mark-ups worked through, then print and digital versions delivered with the editable source files — and an annual refresh to keep projects, prequal levels and plant current.
See the standard
What a working capability statement looks like.
The worked example below is an illustrative, section-by-section build on a representative civil contractor — the same structure every TenderBuilt capability document follows.
Questions
Before you brief us.
Do you write it or design it too?
Both. The document is written from your delivery record and set in a layout built for evaluators, then handed over as print and digital versions plus the editable InDesign and Word source files — it stays yours to update.
We already have one — can you rework it?
Yes. Existing content, photos and project records all feed the build; in practice most reworks become a restructure around evidence, because that’s usually what the old document is missing.
How often should it be refreshed?
Annually as a baseline — new projects, current prequal levels, updated plant — or straight after a significant win or a new registration worth showing. The annual refresh is built into the service.
Will one document work for every bid?
The base document is designed to carry you through panels, prequalification and general enquiries. For a specific RFT, the tender response service tailors the capability content to that brief — a stock attachment is never the ceiling.
What does it cost?
A fixed fee agreed at the scoping call and confirmed in a written work-order before anything is written — the pricing page covers how fees are structured across every service.