Building a Reusable Capability Statement That Wins Work

The Problem with Generic Capability Statements

I have reviewed hundreds of capability statements across my career, both writing them and evaluating them. The overwhelming majority are interchangeable. Change the logo and the company name, and they could belong to any firm in the industry. "We deliver projects safely, on time, and on budget." "Our team brings decades of combined experience." "We pride ourselves on strong client relationships."

None of that is wrong. It is just useless. The person evaluating your submission already assumes you can deliver projects. That is the entry requirement, not the differentiator. They are looking for a reason to put your submission on the short pile instead of the long one. Generic statements do not give them that reason.

If your capability statement could have been written by any PMC in the country, it is not a capability statement. It is a brochure. And brochures do not win tenders.

What Decision-Makers Actually Look For

Having sat on both sides of the table, here is what I have learned about what separates the submissions that get conversations from the ones that get filed.

Specific project references with outcomes. Not "we managed a $50M commercial project." Instead: "We administered a $50M commercial project under NZS 3910 with 142 Special Conditions. We tracked 340 contractor obligations, processed 67 variations, and managed 24 payment claim cycles. The project reached Practical Completion within 2 weeks of the contractual date with zero unresolved payment disputes." That tells the reader exactly what you did, how you did it, and what the result was.

Named people with matched experience. Decision-makers hire people, not firms. If your proposed project director has managed three projects of similar size, type, and contractual complexity, say so. Name them. List the relevant projects. Show that you are not just putting forward a CV but matching the right person to the right opportunity.

Demonstrable systems and processes. This is where most firms fall short. "We have robust project management processes" means nothing. "Our obligation tracking system ingests every Special Condition, maps all contractual deadlines, and generates daily priority alerts for the project team" means something. It tells the reader that you have invested in systems that will deliver consistent results regardless of which individuals are on the project.

A clear articulation of your difference. What do you do that your competitors do not? If the answer is "nothing, we are just good at it," then you are competing on price and relationships alone. That works until it does not. The firms that consistently win work at premium rates are the ones that can articulate a specific capability or approach that others cannot offer.

Structure That Respects the Reader's Time

A capability statement should be two to four pages. Not 20. The reader is reviewing multiple submissions, often under time pressure. Respect that.

Page one: who you are and why you are relevant to this opportunity. Two paragraphs maximum. Then your three most relevant project references, each with specific outcomes. This page is your 30-second test. If the reader stops here, they should know whether your firm is worth a conversation.

Page two: your proposed team. Named individuals with their relevant project experience. Not full CVs. Brief profiles that show why each person is the right fit for this project. If you are proposing a project director who managed a similar project, say so in one sentence with the project name and value.

Page three: your approach and systems. What do you do differently? What systems and processes will you deploy on this project? How will you ensure contract obligations are tracked, deadlines are met, and risk is managed? Be specific. "We deploy an obligation tracking system that maps all contractual deadlines" is better than "we have strong contract administration processes."

Page four (optional): additional project references. If you have more relevant experience than fits on page one, include it here. But keep it to the most relevant projects, not every project your firm has ever delivered.

The best capability statement is not the longest. It is the one that communicates the most relevant information in the least amount of the reader's time. Every sentence earns its place by being specific, relevant, and impossible for a competitor to write.

Make It Reusable Without Making It Generic

The tension in capability statements is between customisation and efficiency. You cannot write a bespoke document for every opportunity. But you also cannot send the same generic document to every prospect. The solution is a modular approach.

Maintain a master library of project references, team profiles, and service descriptions. For each opportunity, select the components that are most relevant and assemble a tailored document. Your $80M infrastructure project reference goes into the submission for an infrastructure opportunity. Your NZS 3910 contract administration experience goes into the submission that involves NZS 3910. Your proposed team section features the people who are actually available and relevant.

This approach takes discipline. It means keeping your project references updated as projects reach milestones. It means maintaining accurate team availability. It means having your project outcomes documented with specific numbers, not vague summaries. For a broader view of how to approach the tender process strategically, see our guide on how to win construction tenders.

Systems as a Differentiator

The question procurement teams increasingly ask is: "What technology and systems do you bring to this engagement?" Five years ago, this question was rare. Today, it appears in most formal tender evaluations for projects above $30M.

If your answer is "Microsoft Office and Procore," you are answering the same way as most of your competitors. If your answer describes a purpose-built system that tracks contractual obligations, surfaces risk, and delivers daily priority alerts to the project team, you have a differentiator that is difficult for competitors to replicate.

The firms that will win the most work over the next five years are not necessarily the biggest or the cheapest. They are the ones that can demonstrate, in their capability statement, that they have systems and processes that deliver measurable, consistent outcomes on every project they take on.

For more on how PMC firms can use AI-powered project intelligence as a competitive advantage, read our article on growing a PMC firm with AI project intelligence.