What a Capability Statement Should Actually Include

5 hours ago

4 min read

A capability statement is often the first thing an owner, GC, or prime contractor sees from your firm. Here is what belongs on it, what to cut, and how to make it work for construction and infrastructure pursuits.

What is a capability statement, and who reads it?

A capability statement is a short document, usually one or two pages, that tells a buyer who you are, what you do, and why you are qualified to do it for them. In construction and infrastructure, it gets used in a lot of places: prequalification packages, vendor registrations, teaming conversations, trade shows, and follow-ups after a first meeting.

The people reading it are busy. A procurement manager sorting subcontractor submissions or an owner's rep building a shortlist won't read every word. They will scan for fit.

That is the job of a capability statement: make fit obvious in under a minute.

What should go at the top of a capability statement?

Start with a clear, plain statement of what your firm does and for whom. One or two sentences. Not a mission statement, and not a list of values.

Compare these two openings:

"We are committed to excellence, safety, and building lasting relationships."
"We are a self-performing electrical contractor serving data center, healthcare, and industrial projects across Texas."

The second one tells the reader exactly where you fit. They can decide in seconds whether to keep going.

Right below that, include your core identifying details:

Legal company name and any DBAs
Primary contact name, title, phone, and email
Office locations and service area
Relevant codes (NAICS, and CAGE or UEI if you pursue public work)
Certifications (MBE, WBE, HUB, DBE, SBE, or others that apply)

Buyers often need these details for their own records. Make them easy to find.

Which capabilities and services should you list?

List what you actually want to be hired for, not everything you have ever done.

Many firms try to show range and end up looking unfocused. If three services drive most of your work, lead with those. Group the rest under a short "additional services" line.

Be specific with your language. "Concrete" is vague. "Cast-in-place structural concrete, tilt-wall, and site paving" tells a GC what they can call you for. "Commissioning support" is better with a note about which systems you work on.

If you self-perform, say so. If you have in-house design, preconstruction, or prefabrication, say so. These are real differentiators in construction, and they often get buried.

How should you show past performance?

Past performance is the proof. It is also the section most firms either skip or overload.

On a one or two page document, pick three to five representative projects. For each one, include:

Project type and market sector
Location
Your scope of work
Size, value range, or other relevant scale indicator (if you are allowed to share it)
A short note on what made it notable, such as schedule, phasing, an occupied facility, or a technical challenge

Choose projects that match the work you are chasing. If you are pursuing mission-critical work, lead with mission-critical projects, even if your biggest job was a retail center. Relevance beats size.

Always check your contracts and confirm with clients before naming them or sharing project values. When you can't name the owner, describe the project type and scope clearly. That still carries weight.

What makes a capability statement easy to scan?

Design matters here, but not in a decorative way. Good layout helps the reader find what they need quickly.

A few practical points:

Use clear section headings. Readers should be able to jump straight to past performance or certifications.
Keep paragraphs short. Bullets work well for services and project details.
Include one or two strong project photos. Real photos of your work are more convincing than stock images.
Use your brand colors and fonts consistently. It should look like it came from the same company as your website and proposals.
Leave white space. A crowded page signals a crowded message.

Also think about format. Have a print-ready PDF, but make sure it reads well on a phone, since many people will open it from an email.

What should you leave off a capability statement?

Cutting is just as important as adding. Leave out:

Long company history paragraphs
Generic claims like "quality," "integrity," and "customer focus" without anything to back them up
Every certification or license your firm has ever held, if most are not relevant to the buyer
Outdated project photos or projects that no longer represent your work

If a line doesn't help the reader decide whether you fit, it is taking up space that something useful could use.

Should you have more than one version?

In most cases, yes. A single generic capability statement tries to speak to everyone and ends up speaking to no one in particular.

Consider a version for each major market or buyer type you pursue. A data center version might emphasize schedule performance, safety, and experience with phased or fast-track delivery. A public sector version might put codes, certifications, and bonding information up front. The core facts stay the same. The emphasis changes.

Keep a master file and build tailored versions from it, so updates happen once.

Ready to tighten yours up?

A capability statement is a small document that does a lot of quiet work. When it is clear and specific, it opens doors. When it is generic, it gets set aside.

If you want a quick read on how your pursuit materials hold up, try the free Proposal Self-Check on my site. And if you'd like help building a capability statement that fits the work you want, I'd be glad to talk. Discuss a Project anytime.