Skip to main content

Insights

What should a civil engineering firm's website show cities, DOTs and developers?

What good looks likeBy Whitelam Media7 min read

All insights

Public agencies hire civil engineers on qualifications, and someone on the selection panel will look at your website before the interview. Here is what that panel checks and which pages your site needs to back up your SOQ.

A city engineer has your statement of qualifications (SOQ) on the desk. Before the interview, someone on the selection panel will open your website. They want to check what the SOQ claims: the projects, the people and the licenses. If the site is thin or out of date, it raises doubts you never get the chance to answer.

Civil firms are hired this way because the law asks for it. The federal Brooks Act of 1972 requires federal agencies to buy design services through qualifications-based selection (QBS), and NSPE reports that 46 states have some form of QBS law, with many cities and counties following similar "mini-Brooks" rules. Under QBS, cost is kept out of the initial evaluation and firms are ranked on qualifications and experience. That makes your website part of the evidence. This post covers what to put on it for cities, DOTs and private developers.

What a selection panel checks before the SOQ interview.

Panels score against written criteria, and those criteria tell you what your site should prove. In one recent Louisiana DOTD advertisement, the agency uses a point-based rating system that weights firm experience on similar projects at 3 and approach and methodology at 9, and requires at least one principal of the prime consultant to be a registered professional engineer in Louisiana. A Nebraska DOT request for qualifications gives the interview 40 of 100 points and caps the SOQ at six pages for the consultant. On federally funded work, FHWA guidance limits a local office criterion to no more than 10 percent of the total evaluation, and the same cap applies to DBE participation. Six pages is not much room. Your website is where a panel member goes for the detail that didn't fit.

What the panel scoresExample from a real solicitationPage your website needsWho owns it at the firm
Experience on similar projectsLouisiana DOTD weights it at 3Project pages sorted by client typeProject managers, with marketing editing
Approach and methodologyLouisiana DOTD weights it at 9Service pages that explain how you run the workTechnical leads for each service
Licensed engineers in the stateLouisiana DOTD requires a principal registered as a PE in LouisianaA licensing page listing PEs by stateA principal or office manager
Team strength and the interviewNebraska DOT gives the interview 40 of 100 pointsBios for key staff that match the SOQ resumesEach named project manager
Local officeFHWA caps it at 10 percent of the evaluationOffice pages with address and the services run from thereOperations lead
DBE participationFHWA caps it at 10 percent of the evaluationA teaming page listing certifications and regular partnersBusiness development
Quality and safetySet by each agencyQA/QC and safety pagesQA manager and safety lead

Project pages sorted by client type.

Most civil firm websites show one long gallery of photos. A city engineer looking for stormwater work has to scroll past subdivisions and interchanges to find it. Split your projects by who the client was:

  • Municipal: water and sewer, stormwater, streets, parks, utility relocations and on-call contracts for cities, counties and special districts.
  • Transportation: corridor studies, roadway and bridge design, intersections and construction engineering and inspection for DOTs and local agencies using state or federal money.
  • Private land development: site plans, grading, drainage, subdivisions and entitlement support for developers and builders.

Each project page should carry the same facts in the same order: client type, location, your scope (what you designed, surveyed or inspected), construction value as a range, years, the roles your staff held and what the client got at the end. Name the client only where the work is public record, such as a city or DOT contract. For private developers, describe them ("a regional homebuilder") unless they've agreed to be named.

It helps to mirror the federal form. Agencies use the Standard Form 330, which splits into Part I for contract-specific qualifications and Part II for a firm's general qualifications. If your project pages carry the same facts your SF 330 project sheets do, staff can match one to the other in minutes. Our post on turning a project list into pages that win work walks through the page layout.

Licensed PEs and the states they cover.

Public clients often need a PE licensed in their state, as the Louisiana example above shows. Put that answer on one page. List each licensed engineer, their discipline and the states where they hold a license. Add the license number so agency staff can check it on the state board's own lookup.

Keep it current. When an engineer adds a state, update the page the same week. Many engineers apply for new states through the NCEES Record, which NCEES says is accepted by all U.S. state licensing boards, so multi-state licensing is common and panels expect to see it spelled out. If you're prequalified with a state DOT, list the work categories by name.

QA and safety pages.

Panels ask how you catch mistakes before plans go out for bid. A QA/QC page should say who reviews drawings and calculations, at which stages and how review comments are tracked and closed. Keep it to your real process. A short, true page is worth more than a long one copied from a manual.

Safety matters most for survey crews and construction inspection staff working beside live traffic. Say what training field staff complete, who leads your safety program and how incidents are reported. If clients ask for safety records in the SOQ, make sure the website doesn't contradict them.

Make the site easy for agency staff to forward.

The person who reads your site is often not the person who decides. A procurement officer forwards a link to the public works director, who forwards it to a council member. Make that easy:

  • Give every project and service a short, stable web address that won't break when you redesign.
  • Put the key facts at the top of each page so the link makes sense without context.
  • Make pages print cleanly and read well on a phone.
  • Keep nothing behind a form. Agency staff won't fill one in to read a project sheet.
  • Show the office contact for each region, with a direct phone number.

Firms that work for public agencies are often asked about accessibility, both for their own site and for documents they hand over. It helps to have a clear answer ready. If you also serve cities and counties on their own sites, our ADA website compliance program covers the details.

What to do next.

Start with the table above. Open your own site and check each row: is the page there, is it current and does it match your latest SOQ? Most firms find two or three gaps.

If the site runs on an old WordPress build that nobody wants to touch, our free Website Health Check shows how outdated and exposed it is. Our engineering website design page explains how we build sites for engineering firms, and the engineering firm website cost guide sets out what a rebuild costs. For the search side, see why engineering firm websites lose RFQ traffic and our SEO Growth Program. Nobody can promise you rankings, and we won't. What a good site can do is make sure that when a panel member looks you up, everything they find backs up your SOQ.