How to improve a civil engineering firm website

Opening: make the website useful to the people who hire you

Yet many firm websites leave basic questions unanswered. Visitors may see services without knowing which apply to their project, or photos without learning what the firm did. A contact page may offer only a general email address and no guidance about what to include.

Improving a website does not mean turning it into a sales pitch. It means explaining capabilities clearly, presenting evidence carefully, and giving visitors a direct path to a useful next step. Start with audience and objectives, then address claims, project material, site structure, accessibility, content ownership, inquiry handling, measurement, and review.

The site should reflect how the firm operates. Public agencies, developers, utilities, and industrial clients may need different evidence and terminology. A focused region or technical niche should also be clear. The goal is a reliable first impression that supports real conversations.

Start with the audiences and objectives

Before changing pages or commissioning content, identify who the site needs to serve. Audiences may include public agency staff, developers, general contractors, architects, utility operators, prospective employees, and referral partners. Each arrives with different questions.

A municipal project manager may want to know whether the firm has worked with similar agencies and understands their project process. A developer may be looking for site civil engineering, permitting coordination, or utility design. A prospective employee may want to see the firm’s technical focus, locations, and work culture. A referral source may simply need to confirm that the firm handles a certain type of work.

List the main audiences and the decisions they need to make. For each one, ask:

What service or project need brings them to the website?
What evidence would help them judge fit?
What concern might prevent them from reaching out?
What is the most useful next action?

Choose a small set of business objectives. These might include receiving better qualified inquiries, helping existing clients find the right contact, supporting recruiting, or giving referral sources accurate service information. Connect each objective to observable actions. “Improve the website” is too broad. “Make it easier for a public agency client to find our transportation project experience and contact the right office” gives the team a concrete direction.

Avoid organizing the site around internal charts or the way the firm describes itself in proposals. Visitors first want to know whether the firm can help with their need. Organize information around that need, then explain the firm’s qualifications and approach.

Ask a few recent clients or referral sources what they looked for before contacting the firm. Find out what they understood from the website and what they had to confirm by phone. Their answers can reveal missing information the leadership team assumes is obvious.

Make service claims specific and verifiable

Service pages should explain what the firm actually does. Broad labels such as “engineering,” “infrastructure,” or “full service” rarely provide enough context. Describe the work in terms a project owner recognizes, while accurately representing the firm’s role and qualifications.

For each service, describe the project types or tasks the team handles, the clients it serves, and its geographic area. A drainage design page, for example, can say whether the firm performs hydrologic and hydraulic analysis, prepares plans, supports permitting, or provides construction phase services, if those activities are part of its practice. Add useful project types or sectors.

Distinguish work the firm performs directly from work it coordinates through others. Do not suggest the firm provides a specialty just because it has collaborated with a consultant who does. Likewise, do not imply a firmwide license, certification, or geographic authorization based on one individual’s credential.

Review each claim before publishing:

Can the firm point to a current employee, project, or documented capability that supports it?
Is the claim true for the office or team named on the page?
Does it imply a guarantee, approval, or outcome outside the firm’s control?
Is the wording current and consistent with proposals and qualifications statements?
Has the responsible technical leader reviewed it?

Words like “best,” “leading,” “guaranteed,” and “unmatched” make strong claims without helping buyers assess fit. Replace them with concrete descriptions. “Our team prepares roadway drainage plans for municipal capital projects” is more informative than “we deliver world class infrastructure solutions,” provided the firm can substantiate it.

Be precise about outcomes. The firm can describe its experience and services, explain its processes, or present completed work. It should not promise that an authority will approve a project, a schedule will never change, or a design will eliminate all risk. Outcomes depend on conditions beyond the firm’s control. Licensed PE judgment and local codes govern engineering work.

Use project examples with permission and context

Project pages help visitors understand the firm’s work. A list of names or photographs is less useful than a concise account of the challenge, the firm’s role, and the work completed. Keep the account factual and have people familiar with the project approve it.

Before publishing, confirm permission to identify the project and client. Check permission for photographs, plans, and maps, as well as logos and other identifying details. Public funding does not automatically make every image or document free to publish. Contracts, client policies, photographer rights, confidentiality terms, and site security concerns may apply. Ask the client or the firm’s designated reviewer if permission is unclear.

Keep a repeatable approval record identifying materials cleared for publication, any required client attribution, the approved description of the firm’s role, and reuse limits. Store it with the project content so future editors do not have to reconstruct the approval. If a project cannot be named, use an anonymized description only if the client agreement allows it and it does not reveal protected details.

Make the firm’s contribution clear in every case study. State whether it provided planning, survey, civil design, permitting support, construction administration, or another defined service. Do not imply the firm was prime consultant or responsible for the entire project if its role was narrower. Do not claim sole credit for a project’s success when multiple parties contributed.

A concise project example can follow this structure:

Project context: type of facility, location at an approved level of detail, and client category.
Need: the engineering or delivery issue the project addressed.
Firm’s role: the specific services and phase of work provided.
Result: a factual description of the completed work or documented milestone.

Use captions and alt text for images. Captions can identify the project and explain what the image shows. Alt text should convey useful information to someone who cannot see the image, rather than repeat decorative details. Do not post drawings, maps, or site photographs that expose sensitive infrastructure or personal information without proper review.

Navigation should help visitors answer basic questions: Does the firm handle my kind of project? Where does it work? What experience can it show? Who should I contact? Keep the primary menu short enough for first time visitors to scan easily.

A common structure includes services, markets or project types, and projects. The menu can also include about and careers, with a contact link. Labels should match the firm’s language and clients’ search terms. If “markets” is unclear, “Who we serve” may work better. If the firm has few service lines, one services page with clear sections may be easier to use than many shallow pages.

Organize pages in a hierarchy. The home page can orient visitors and point to the main service and project areas. Service pages can link to relevant projects, and project pages can link back to the services performed and a contact route. This lets visitors follow the information without returning to the menu after every page.

Provide a contact route in the main navigation and at useful points on service and project pages. Match the prompt to the context. Someone reading about site development services may benefit from a project inquiry link, while someone considering employment should see a careers route.

Check the site on phones and desktop browsers. Menu labels and buttons should remain usable on narrow screens, and forms and project images should work well. Long menus, tiny tap targets, and pages without a clear heading make information harder to find.

Treat accessibility as part of basic usability

An accessible website is easier for many people to use, including people who rely on keyboards, screen readers, magnification, captions, or adjusted contrast. It is also clearer for anyone reading quickly on a phone or under poor display conditions.

Use a meaningful heading structure: one clear main heading followed by logically ordered section headings. Headings should describe the content that follows, not serve only as visual styling. Choose link text that explains its destination. “View our stormwater projects” is more useful than “click here.”

Ensure text and interface elements have sufficient contrast, forms have labels, and users can operate navigation and controls with a keyboard. Do not rely on color alone to convey meaning or status. Provide captions or transcripts for meaningful video and audio. Give informative images concise alt text and mark purely decorative images so assistive technology can skip them.

Pay particular attention to forms. Each field needs a visible label, instructions should explain required information, and errors should state what to correct in plain language. A form should not erase entries after an error. Test it without a mouse and with browser zoom increased.

Include accessibility review in publishing, rather than treating it as a one time project. Automated tools can identify some issues, such as missing labels or contrast concerns, but cannot judge whether a page makes sense to someone using assistive technology. Pair automated checks with manual review and user feedback when possible. If the firm needs to review its digital access practices, start with a practical checklist and assign someone to track fixes.

Assign content ownership and approvals

Stale content harms credibility. Old staff biographies, outdated office details, expired certifications, and project descriptions that no longer match the firm’s work can confuse visitors. Assign an owner to confirm that each important page remains accurate.

Assign responsibility by content type. A technical leader can review service descriptions and project roles. Human resources can review career information. A designated business or marketing owner can maintain contact details, office locations, and general company information. The website administrator can manage publishing access, backups, and page updates. One person should coordinate reviews so pages do not fall between departments.

Set review cycles based on how quickly information changes. Contact details and staff listings may need regular checks, while established service descriptions may be reviewed less often. Revisit project material when the firm receives permission or a relevant milestone makes publication timely. Calendar reminders are more reliable than memory.

Keep approved bios, project summaries, image permissions, service descriptions, and brand assets in a shared location with clear filenames and dates. Record who approved a claim and when. This supports continuity when roles change and reduces the chance that editors copy outdated statements from old proposals.

Content ownership includes access control. Limit publishing permissions to people who need them, and make sure the firm can access its domain and hosting. Confirm access to analytics accounts and keep content management account access current. If updates depend on one employee’s personal login or undocumented knowledge, the firm carries avoidable operational risk.

Make inquiries easy to submit and easy to handle

A confusing contact process can lose an opportunity even when the right visitor reaches the site. Provide a clear way to contact the firm and set expectations for what happens next. Offer a general contact option, direct office information where relevant, and a project inquiry form if it helps route requests.

Ask only for information that helps the firm respond. A project form might request the visitor’s name and organization, preferred contact method, project location, type of need, timing, and a brief description. Do not make it so long that a prospective client must prepare a full scope before starting a conversation. Allow attachments only if the firm has a process for receiving and storing them securely.

Tell visitors what not to submit. They should not use a general website form for emergencies, confidential information, or files requiring secure transfer. If the firm handles sensitive project material, direct visitors to an appropriate channel. Do not request detailed engineering documents through a form not intended to handle them.

Assign an owner and a backup for the form. Decide who receives inquiries, how requests reach the appropriate office or service lead, and how the firm records their disposition. Test the form after updates, including confirmation messages and notifications. A form that appears to work but sends messages to an inactive mailbox is worse than no form at all.

A useful acknowledgment confirms receipt and gives a realistic next step. Avoid promising a response time unless the firm can meet it consistently. The person handling the inquiry should be able to see the original message, identify its source, and record whether it became a conversation, proposal request, referral, or another type of contact.

Use analytics to answer business questions

Analytics can show whether the site helps people find relevant information and take useful actions. Start by deciding what the firm needs to learn. Measures may include service page visits, project case studies viewed, form submissions, phone or email link use, and careers page visits. Raw traffic alone does not show whether the site supports business objectives.

Define important actions before reviewing reports. A qualified project inquiry, for example, may be more meaningful than a general contact form submission. If possible, record the inquiry type and service or office involved. This helps leadership see which parts of the site support the work the firm wants to pursue.

Keep tracking proportionate. Collect only data the firm has a business reason to use, limit access to those who need it, and review applicable privacy obligations with qualified counsel. Avoid collecting sensitive information through analytics or embedding tools the firm has not reviewed. Explain relevant data practices in the site’s privacy information.

Review trends over a consistent period and interpret them in context. Traffic changes may reflect a hiring campaign, conference, referral, search result change, or technical issue. Compare page activity with actual conversations and proposal opportunities where records allow. Ask whether visitors reached the right information and whether inquiries matched the firm’s capabilities.

If people often land on a service page but rarely proceed to relevant projects or contact information, inspect the page. It may need a clearer explanation, stronger internal links, or a more visible contact route. Treat metrics as prompts for investigation, not proof of cause.

Set a review cycle and keep improving

Set a maintenance rhythm with periodic reviews of key pages and a faster route for urgent corrections, such as a changed office address, staff departure, or outdated licensing statement. Check technical function as well as wording: links, forms, images, page loading, mobile display, and account access.

Use a short review agenda:

Are service claims still accurate and approved?
Are project permissions and descriptions on file?
Do contact details and staff information remain current?
Can visitors find priority services, relevant projects, and inquiry routes?
Do forms reach the right people and return a useful acknowledgment?
What do analytics and recent inquiries suggest should change?

Make changes based on evidence from clients and staff, as well as inquiry patterns and site behavior. Record significant edits and approvals. This creates a useful history and helps the firm avoid repeating decisions.

An effective website is a working business resource. It explains capabilities, provides credible evidence, respects project and client permissions, and helps prospective clients take the next step. The firm does not need to publish everything it has ever done. It needs to publish the right information, keep it accurate, and make it easy to use.

For website planning, visit CivilEngineers.com websites. For broader reading, browse the CivilEngineers.com resources and guides.

General education only, not engineering, legal, tax or investment advice. Licensed PE judgment and local codes govern.