Capability statements for civil and construction

A company profile is descriptive. It tells the reader what the business is. A capability statement is evaluative. It tells the reader what the business can be trusted to deliver. The two documents share content but the framing is different. A company profile is written for general use. A capability statement is written for the person assessing the business against a specific project, contract, or procurement process. For prequalification and tender contexts, the capability statement is the document being asked for.

It depends on the business. The final page count is built around what the document needs to do, not a target length. Twelve to sixteen pages is the standard length for a capability statement built for prequalification and EOI submissions. Four to eight page documents struggle to carry the project portfolio, personnel, and safety data that head contractors and procurement teams now expect at this stage. Longer than sixteen page documents start losing the reader.

Once a year as a baseline, and immediately when major projects complete, key personnel change, accreditations are added, or the business moves into a new sector. A capability statement that lists projects from three years ago is signalling that nothing significant has happened since. Procurement readers notice. Native source files are supplied at the end of every project so updates can be made internally where the business has the capacity, or brought back to 'Strate if you need us.

No. A capability statement is structured around commercial credibility. A government tender requires a different level of evidence entirely. Formal accreditations, demonstrated experience on comparable scopes, safety data, and response formats specific to the procurement process. The document that works for a head contractor introduction is rarely the document that wins government work.
For tender and bid submission design, that is a separate engagement built around what the specific opportunity requires.

Both are supplied as a PDF. The difference is what the reader experiences when they open it. A static document is linear — the reader moves through it page by page. An interactive capability statement is built for a different kind of reading experience. Navigation between sections, embedded video, expandable project detail, and interactive elements that let the reader move through the document the way they would move through a website. A director introduction, site footage, or a client testimonial sits inside it rather than being sent separately.
Whether the interactive version is right depends on the business and how it sells. For businesses competing in environments where multiple firms are being compared on paper, the interactive version signals a level of investment and forward thinking that the static document cannot. For straightforward submissions where the content is doing the work, the static document does the job.

Yes, because they do different jobs. A website is read at the reader's pace, in their own time, in their own sequence. A capability statement is read in a single sitting, in a structured order, with a defined conclusion. Procurement and prequalification processes specifically request capability statements because the document is comparable across firms in a way that websites are not. The website carries the brand. The capability statement closes the credibility gap.

They draw from the same source material. The same projects, personnel, and accreditations. But they deploy it differently. The website gives the reader room to explore at their own pace. The capability statement controls exactly what they see and when, read in a single sitting at a specific point in the evaluation process. Where the two repeat each other verbatim the capability statement loses its value as a document. The content comes from the same well. The way it is expressed is specific to each format.

Final copy is the responsibility of the client because the business knows its projects, its people, and its credentials better than anyone. The structure and content framework are developed as part of the design process. Each section is mapped out with guidance on what needs to be included and how much content each page requires. Where copywriting support is needed, we can connect you with trusted specialists.