Statement of Qualifications (SOQ) Template & Example Structure

Unlike the federal SF330, a Statement of Qualifications has no government-mandated format - the firm controls the layout, and the solicitation controls the rules. That freedom is why a reusable template helps: it gives every pursuit a proven starting structure so your time goes to tailoring, not reinventing the outline.

A standard SOQ outline

1. Cover letter - a short transmittal signaling interest and the single strongest reason you fit
2. Firm profile - who you are, disciplines, and directly relevant experience (kept brief)
3. Relevant project experience - the section evaluators weight most; lead with similar, not largest
4. Key personnel - resumes for the people who will actually lead the work
5. Project understanding / technical approach - only if the RFQ asks for it
6. References, certifications, and required forms

Map each section to the criteria

Tailor the template to each RFQ

Before submitting, re-point the template at this solicitation: reorder sections to match the published evaluation criteria and their weights, swap in the most relevant projects and people, rewrite each project's relevance statement for this owner, and cut to the page limit. A generic capabilities deck loses to a criteria-first SOQ every time. For the craft behind it, see how to write an SOQ that wins.

Common SOQ template mistakes

• Leaving the outline generic instead of reordering to the RFQ's criteria
• Leading with the largest project instead of the most similar
• Naming principals who won't touch the job
• Including price when the solicitation is qualifications-only
• Blowing the page limit - excess pages are often discarded unread

Section by section: what each part should do

A template is only useful if each section has a clear job. Here is what each part of a strong SOQ is for:

• Cover letter - one page. Signal genuine interest, name the single strongest reason you fit this project, and identify your point of contact. Not a place to restate the whole SOQ.
• Firm profile - short. Establish relevant capability and disciplines quickly; resist the urge to recount company history the owner did not ask for.
• Relevant project experience - the longest and most important section. Lead with the most similar projects, and for each state client, scope, your role, the team members involved, and the outcome that matters to this owner.
• Key personnel - resumes for the people who will actually lead the work, with registrations and relevant projects that echo the experience section.
• Project understanding or approach - include only if the RFQ asks; when it does, show you grasp this project's specific challenges, not generic method.
• References, certifications, and required forms - current, complete, and exactly as the solicitation requests.

How long each section should be

Let the page limit and the criteria weights set the proportions. If project experience is the most heavily weighted factor, it should occupy the most pages - a common mistake is a long firm-history section crowding out the project sheets evaluators actually score. Work backward from the limit: subtract required forms and the cover letter, then divide the remaining pages across sections in rough proportion to their scoring weight.

Print and digital considerations

Follow the submission channel the solicitation names. For digital submissions, produce a PDF with selectable text (not a flat scan), respect any file-size and naming rules, and confirm bookmarks or a table of contents if the agency wants them. For print, follow binding, tab, and copy-count instructions exactly. These are administrative details, but the same compliance discipline that keeps a proposal responsive applies to how the SOQ is packaged and delivered.

What you should not templatize

Some things must be written fresh for every pursuit: the win theme, the project-understanding narrative, and the specific relevance of each project to this owner. Templating those produces generic-sounding SOQs that evaluators quietly discount. The rule of thumb is to template the structure and the facts - firm data, resumes, project sheets - but author the argument. A reused relevance statement that could describe any project is a wasted paragraph in the section that matters most.

Keep the library accurate, not just complete

A template full of stale content is worse than a blank page: a lapsed license, an outdated project cost, or a person who left the firm undermines your credibility exactly where evaluators are checking it. Assign ownership for keeping resumes, project sheets, and certifications current, and date-stamp each so you know what to refresh before a deadline rather than discovering the gap after submission.

Turn every pursuit into a better template

Treat the template as something that improves each cycle. After every submission - win or lose - harvest what worked back into the library: a sharper relevance statement, a cleaner project sheet, an updated resume, a graphic worth reusing. Debriefs tell you which sections to strengthen. A template that is maintained this way compounds in quality; one that is copied and never revised slowly decays into boilerplate.

A quick self-check before you submit

• Did you reorder the SOQ to this RFQ's criteria and their weights?
• Is the most heavily scored section the longest?
• Is every named key person shown on at least one featured project?
• Did you cut to the page limit without dropping the strongest content?
• Are all required forms and certifications attached and current?

Where to keep the template and library

A template is only as useful as it is findable. Scattered across personal drives and old proposal folders, it decays into guesswork about which version is current. Keep the outline, the boilerplate, and the source content - resumes, project sheets, certifications - in one place the whole team can reach, with clear ownership for keeping it current. Whether that is a shared drive with strict conventions or purpose-built software, the requirement is the same: one authoritative source everyone builds from, so no two SOQs start from a different set of facts.