Engineering Capability Statement Template (Free + Example)
Download this template - free
Create a free SUNAGO account to download this template (Word & PDF) from your Templates library - and generate your own, pre-filled from your live project data.
An engineering capability statement is the one-page document clients and public agencies use to shortlist engineering firms before requesting a full proposal. This template leads with what an engineering buyer checks first - your disciplines, professional licensure, and the design codes you work to - then presents your relevant projects. It is free to download: create a free account to get the PDF and the editable Word version.
Get the engineering capability statement template - free to download:
- The print-ready PDF - A4 and US Letter.
- The editable Word version - the .docx, and the option to generate your own engineering capability statement from your live project data.
Every file is free. Create a free account to download - that is the only step.
Once you have the editable version, prefer Google Docs? Upload the .docx to Google Drive and open it with Docs. Every file ships with a filled-in example from a fictional engineering consultancy.
What an engineering capability statement must include
Engineering buyers screen on competence and licensure: is this firm qualified to stamp the work, and have they done our type of project? The template answers those first, following the five-section format from the capability statement guide, ordered for engineering:
| Section | Engineering-specific content |
|---|---|
| Header + disciplines | Firm name, disciplines practiced, states/jurisdictions of licensure |
| Core competencies | Services plus the design codes and standards worked to (IBC, Eurocode, AASHTO) |
| Past performance | 3-5 projects by sector: client, value, your engineering role, outcome |
| Differentiators | Number of licensed PEs, specialist certifications, ISO 9001, delivery record |
| Company data | UEI, CAGE, NAICS (541330 and related), registrations, certifications |
How to fill in the engineering capability statement template
- List your engineering disciplines and licensure. State the disciplines you practice and the jurisdictions where your firm and PEs are licensed - the first relevance check for an engineering buyer.
- Write core competencies as services plus design standards. Describe the services you deliver and the codes you work to, so a buyer can confirm you meet their requirements.
- Enter three to five relevant projects by sector. For each, add client, sector, construction value, your engineering role, and a measurable outcome. Tag by sector so evaluators find the relevant ones fast.
- Prove differentiators with credentials and QA. Back differentiators with evidence: number of licensed PEs, specialist certifications, ISO 9001 quality management, or a documented on-time delivery rate.
- Complete the company-data and codes block. Add UEI, CAGE, and NAICS codes, professional registrations, and any socioeconomic certifications for federal work.
- Export to PDF and keep it to one page. Export on A4 or Letter with background graphics on. If it runs long, trim project descriptions rather than cutting licensure or discipline coverage.
Engineering capability statement example
The template ships with a complete example from Meridian Engineering Consultants, a fictional 45-person civil and environmental firm:
Disciplines: Civil · Environmental · Water resources · Licensed in CA, OR, WA, NV (12 PEs) Core competencies: Municipal water & wastewater process design (to Ten States Standards) · Stormwater and hydraulic modeling · Construction-phase engineering & commissioning Past performance - Northgate Water Reclamation Facility Upgrade Client: City of Northgate Utilities · Value: $18M construction · Role: Prime consultant, design & CPE · Outcome: 12→17 MGD capacity, 3.2% under estimate, zero permit violations.
The example works because it names disciplines, states of licensure, PE count, and the standards worked to - every relevance check an engineering evaluator makes, answered in the top third of the page.
What the engineering buyer checks first
Before reading project narratives, an engineering client or agency filters on:
- Discipline match - do you actually practice the engineering they need?
- Licensure in the jurisdiction - a firm without PEs licensed where the project sits cannot stamp the work.
- Sector-relevant experience - water utilities want water projects; DOTs want transportation projects.
- QA and standards - the codes you work to and whether you hold ISO 9001 or equivalent.
Source each section from your project data
Engineering credentials change as staff earn licenses, projects complete, and certifications renew. Rather than re-editing the file, keep a structured record per project (client, sector, value, role, outcome) and per staff member (discipline, PE status, jurisdictions), then regenerate the statement. Those same records feed an engineering portfolio and your reference forms, so one update propagates everywhere.
Common mistakes on an engineering capability statement
Avoid the errors that get engineering firms passed over before their projects are read:
- Burying licensure. State the disciplines and the jurisdictions where your PEs are licensed near the top. A buyer whose project sits where you cannot stamp will move on regardless of your experience.
- Listing services without standards. “Structural engineering” is a category. Naming the codes you work to (IBC, Eurocode, AASHTO) proves you work to the buyer’s requirements.
- Mixing sectors indiscriminately. Group or tag projects by sector so a water utility sees water projects first. An unsorted project list makes the evaluator do your relevance filtering.
- Claiming a PE count without context. “12 PEs” is stronger when paired with disciplines and jurisdictions. Raw headcount without licensure detail is easy to discount.
- One statement for every client type. A DOT, a private developer, and a federal agency weight discipline coverage and certifications differently. Maintain one dataset and generate targeted versions.
Or build and regenerate it free
The free capability statement builder stores your firm’s disciplines, licensure, and project data once and regenerates a current engineering capability statement on demand - add a project or a newly licensed PE once, and the document stays accurate. Create a free account to download the template and generate your statement from your own project data. For related sectors, see the construction capability statement template, more examples by industry, or the general template.
Frequently asked questions
What should an engineering capability statement include?
An engineering capability statement leads with disciplines and professional licensure, then lists core services and the design codes you work to, three to five relevant projects by sector with values and your engineering role, differentiators backed by credentials and QA certifications, and your company codes. It fits on one page.
Is this engineering capability statement template free?
Yes. Every file is free: the print-ready PDF and the editable Word version cost nothing. Creating a free SUNAGO account is the only step - it unlocks the download and lets you generate the statement from your own project data. The file keeps a small footer credit link you may keep or delete, and ships with a filled-in example from a fictional engineering consultancy.
What NAICS code is used for engineering services?
541330 (Engineering Services) is the primary code most engineering firms use, sometimes with secondary codes such as 541370 (surveying and mapping) or 541620 (environmental consulting). List the primary code plus the secondaries that match your disciplines.
How is an engineering capability statement different from a portfolio?
The capability statement is a one-page firm summary that opens the door; an engineering portfolio is a multi-page document with a spread per project for buyers who want depth. Firms typically submit the statement first and provide the portfolio on request or as an annex.