How to Write a Statement of Qualifications That Wins Work

Your firm spent two weeks pulling together an SOQ for a $40 million school district project. You submitted on time. The format was clean. The project examples were solid — at least, the ones you could find on short notice.

Then you didn't make the shortlist. The district selected five firms for interviews, and yours wasn't one of them.

Sound familiar? It happens more often than most firms want to admit. The SOQ is often the first document an owner or selection committee sees from your firm, and too many construction teams treat it as a formality — a paperwork step before the real proposal work begins. In reality, the SOQ is the document that determines whether you even get to write the proposal.

This article is part of our complete guide to construction proposals — check it out for the full proposal lifecycle from RFP analysis through submission.

What owners are actually looking for in your SOQ

When a selection committee reviews twenty or thirty SOQs for a single project, they're not reading every word. They're scanning for signals — specific indicators that tell them this firm understands their project and has the relevant experience to deliver it.

What makes them stop reading:

• A firm overview that runs four pages and covers every market sector you've ever touched
• Project examples that don't match the type, size, or delivery method of their project
• Generic descriptions that could apply to any contractor ("on time, on budget, safely")
• Missing or incomplete responses to specific evaluation criteria listed in the RFQ

What makes them keep reading:

• A concise firm overview that leads with what's relevant to their project
• Three to five project examples selected because they mirror the challenges of this specific opportunity
• Specific metrics and outcomes — not just project names and dollar values
• Clear evidence that you read their solicitation and tailored your response accordingly

The shift from "tell us everything" to "show us what matters for THIS project" is the single most important change most firms need to make in their SOQ approach.

How to structure your SOQ for maximum impact

Most SOQs follow a similar section structure, but the order and emphasis within those sections should change based on the specific opportunity. Here's a framework that works:

Firm overview (1 page max): Who you are, where you work, what types of projects you specialize in. Lead with what's relevant. If the RFQ is for a healthcare project and healthcare is 60% of your work, say that upfront. Don't bury it in the third paragraph.

Relevant experience (the star of the show): This section should dominate your SOQ. We cover this in detail in the next section, but the key principle is quality over quantity. Five well-chosen, well-presented projects beat ten mediocre ones every time.

Key personnel: Brief bios of the people who will actually work on the project — not a company directory. Each bio should connect the person's relevant experience to this project's requirements. If the RFQ emphasizes phased construction, your project manager's bio should highlight phased project experience.

Safety record: Present your Experience Modification Rate (EMR), DART rate, and any safety awards or recognitions. For owners with strict safety requirements (healthcare, education, federal work), this section can be a differentiator or a dealbreaker.

Bonding and financial capacity: Your bonding capacity letter and any relevant financial information. This is a compliance checkbox for most owners — include it, keep it brief, make sure it's current.

The order matters. If the RFQ weights experience at 40%, lead with experience after the firm overview. If key personnel are the top criterion, put your team section front and center. Read the evaluation criteria and organize accordingly.

Selecting and presenting the right project examples

This is where winning SOQs separate themselves from the rest of the stack. The project examples section is the heart of your SOQ, and most firms under-invest in it.

Selection criteria: Choose projects that match as many of these dimensions as possible:

• Project type: Same building type (healthcare, education, civic, etc.)
• Project size: Within a reasonable range of the target project's value
• Delivery method: Same contract type (CMAR, design-build, hard bid)
• Market or location: Same region, especially if local presence matters
• Specific challenges: Active-occupancy renovation, phased construction, compressed schedule, complex stakeholder environment

Presentation format: For each project, include:

• Project name, location, and client
• Project value and delivery method
• A brief narrative (3-5 sentences) focused on what you accomplished and how it's relevant to this opportunity
• One or two compelling photos
• A reference the owner can actually call

The narrative matters more than the photos. A strong narrative explains what made the project challenging and what your team did to overcome those challenges. It connects the dots between past performance and future capability. "This $35 million hospital renovation was completed in three phases over 22 months with zero disruption to patient care" is a narrative. "ABC Hospital — $35M" is not.

When your project records are organized and searchable, pulling the right examples takes minutes instead of days. See our guide to organizing construction project records for a system that actually works.

Teams using a searchable project database like ProjectPortfolio can filter their entire project history by type, size, location, or delivery method — and find the three most relevant examples in under a minute.

Common SOQ mistakes that keep firms off the shortlist

After reviewing dozens of SOQs and debriefing with owners, these are the mistakes that show up most often:

Too long. If the RFQ says ten pages, eight pages of strong content beats twelve pages of filler. Selection committees are reading dozens of these — respect their time.

Irrelevant projects. Including your biggest project instead of your most relevant project. The $200 million stadium doesn't help you win a $15 million school renovation if you've got three relevant school projects you left out.

Generic descriptions. "Completed on time and under budget" describes half the projects in the industry. What was challenging about it? What did your team do specifically to ensure that outcome?

Missing the evaluation criteria. If the RFQ asks for experience with LEED-certified projects and you don't specifically address green building experience, the selection committee won't give you credit for it — even if it's buried somewhere in your project descriptions.

Poor formatting. Dense paragraphs, tiny photos, inconsistent fonts, missing page numbers. An SOQ that's hard to read sends a message about your attention to detail — and it's not the message you want.

Making your SOQ stand out without gimmicks

The best SOQs don't need flashy design or gimmicky presentation. They stand out because the content is specific, relevant, and clearly demonstrates why this firm is the right fit for this project.

Lead with evidence, not claims. Don't say "we're the premier healthcare builder in the region." Show five healthcare projects you've completed in the last three years with specific outcomes and references the owner can verify.

Be specific about your team. Name the people who will work on the project. Highlight their relevant experience. Show the selection committee exactly who they're getting, not just the firm they're hiring.

Connect every section to the evaluation criteria. Read the RFQ's evaluation rubric. Make sure every section of your SOQ addresses something the owner said they're scoring on. If they're weighting safety at 20%, your safety section should be substantial.

Proofread. Then have someone else proofread. Then have a third person proofread. A typo in the owner's name or the project title is the kind of mistake that gets you eliminated before anyone reads your qualifications.

If you're ready to stop digging through shared drives every time an SOQ is due, see how ProjectPortfolio helps teams build proposal-ready experience databases.