Engineering firm website content checklist

An engineering firm site has to name each discipline, show completed projects in terms a buyer understands and prove the firm is licensed, insured and safe to hire. Approved case studies and certificates are the slow items.

7 pages35 requests23 requiredAnswered by the principal engineer or business development manager

Where to start

  1. People, safety and quality. Certificates and licence numbers have to be checked and take the most chasing from other people.
  2. Projects. Approved case studies and photos take the longest and define the look of the site.
  3. Disciplines. Discipline descriptions set the navigation and the message for buyers.
  4. Sectors. Sector pages draw on the projects and disciplines above, so write them once those are in place.
  5. Careers. This page is optional and short, so collect it last from the person who reads applications.

The checklist

Home

Buyers include architects, developers and public bodies, so the home page has to state the disciplines and sectors in words each of them recognises.

  • Firm name as it should appear Short text, requiredUse the name on proposals and drawings, including any 'Consulting Engineers' or 'Associates' suffix. Give the legal name separately for the footer.
  • One-line description of the firm Short text, requiredDisciplines, sectors and region in under 20 words. For example: 'Structural and civil engineering for schools, housing and public works across Yorkshire.'
  • Hero image Image upload, requiredA completed project or a site shot with engineers in safety gear, at least 2400 pixels wide. Make sure everyone shown agreed to appear.
  • Main call to action Single choice, requiredPick the first step for a new client. The header button and the first screen follow from it.Request a proposalView projectsSpeak to an engineerDownload a capability statement
  • Capability statement File uploadThe short PDF you send to prospects and procurement teams. Send the current version with its date.

Disciplines

Each discipline needs a plain description of what the engineers do and for whom, and many firms only have the text from their tender documents.

  • Disciplines offered Multiple choice, requiredTick the disciplines where the firm has a licensed lead who can sign off on work. Leave off any you only subcontract.StructuralCivilMechanicalElectricalEnvironmentalGeotechnicalFire protectionProcessTransport
  • Description of each discipline Long text, requiredAbout 150 words per discipline: what the engineers do, which stage of a project they join and the clients they work for.
  • Lead engineer for each discipline Short text, requiredThe name of the person who answers technical enquiries for each discipline. The page links to that bio.
  • Software and methods Long textDesign software, modelling or survey methods you use. Include only what would help a buyer compare you with another firm.
  • Typical clients Multiple choice, requiredTick who hires you most often. The home page will use the first two.DevelopersArchitectsLocal governmentUtilitiesManufacturersContractorsPrivate owners

Projects

Case studies are what a buyer reads before making a call, and most engineering firms have projects but no approved write-ups.

  • Case study write-ups Long text, requiredFor each: client type, the challenge, what the firm designed and the result, in about 250 words. Use words a non-engineer can follow.
  • Project facts sheet File upload, requiredA spreadsheet with project name, location, year, discipline, client type, value band and status for each project to be shown.
  • Site and completed-project photos Image upload, requiredSix to twelve images per project, at least 2000 pixels wide, with no visible safety breaches and no unrelated people.
  • Diagrams and models File uploadClean images of structural models, flow diagrams or site plans, with any client-confidential data removed.
  • Figures approved for publication Long textProject value, area or capacity numbers the client agreed you can publish, with the date. Leave blank if there is no written approval.
  • Client permission to publish each project Yes or no, requiredConfirm each client has agreed to the project being shown. List any that are under a confidentiality agreement.

Sectors

Buyers search by sector, and sector pages work only where the firm has real depth to describe.

  • Sectors you serve Multiple choice, requiredTick only sectors with at least three completed projects. A sector page with one project reads as a stretch.HousingEducationHealthcareCommercialIndustrialWater and utilitiesTransport and highwaysEnergyHeritage
  • Sector introductions Long text, requiredAbout 120 words per sector on the problems clients face and how the firm helps, with a named project as an example.
  • Frameworks and approved supplier lists Long textPublic sector frameworks or buyer lists the firm is on, with the name and the years it covers. Include the reference number.

People, safety and quality

Procurement teams ask for licences, insurance, safety statistics and certificates before they ask for a price, so the page has to hold them.

  • Principal and senior engineer biographies Long text, requiredAbout 120 words each: discipline, years in practice and notable projects. Keep the format the same for everyone.
  • Team portraits Image upload, requiredOne portrait per person, same background and framing, at least 1500 pixels on the short side.
  • Professional licences and registrations Long text, requiredEach engineer's licence or registration number and the jurisdictions it covers, as printed. Check the rules where the firm operates.
  • Management system certifications Multiple choice, requiredTick only certificates that are current. Send the certificate itself so the expiry date can be checked.ISO 9001 qualityISO 14001 environmentalISO 45001 health and safetyChartered status of the firmOther scheme
  • Safety statement Long textA short statement on safety practice with any figures, such as incident rates, dated and signed off by the person responsible.
  • Insurance details to show Yes or noConfirm whether professional indemnity and public liability details may appear on the site, and who holds the certificates.

Careers

Engineering firms struggle to hire, so the careers page needs to say what the work is like and how to apply.

  • Open roles Long textTitle, discipline, location and a short description for each. If none are open, say so and offer a way to send a CV.
  • Graduate or apprenticeship programme Yes or noSay whether you run one. If yes, add the dates, how many places and how to apply.
  • Benefits and working pattern Long textHybrid working, professional fees paid, study support and similar. List what is real and in writing.
  • Contact for careers Short text, requiredA name and email for who reads applications and replies.

Contact and brand

New enquiries come from a short form or a call, and brand files are needed to finish the layout.

  • Office addresses and hours Long text, requiredEach office address as on your letterhead, with the hours and whether visitors need an appointment.
  • Proposal enquiry form fields Multiple choice, requiredPick the details the team needs to scope a proposal. Each added field reduces how many people finish.NameCompanyPhoneEmailDiscipline neededProject locationBudget rangeProgramme dates
  • Logo files File upload, requiredSVG, EPS or PDF vector files in colour and one colour. Include any accreditation badges you may show.
  • Brand colours ColourThe main colour from your drawings and proposals as a hex code, plus any secondary colour.
  • Brand fonts FontThe typeface in your proposals and title blocks. If it is licensed, ask the supplier about web use.
  • Privacy and cookie policy approved Yes or no, requiredEnquiry forms and applications collect personal data. Say whether a policy exists or a template should be drafted for review.

What clients get stuck on

Project descriptions only an engineer can read

Ask the engineer to explain the project in two minutes to someone outside the field, then write from that. A buyer in procurement will not read a paragraph of load figures.

Safety statistics that change every quarter

Agree which figure goes on the site, who signs it off and when it is next reviewed. A stale number on a safety page is the first thing a procurement officer checks.

Certificates that have expired

Ask for the actual certificate and read the dates before listing any standard. An expired ISO certificate on a public page is worse than none.

Drawings under client confidentiality

Ask which projects and drawings are public. Sealed or contract drawings often cannot be shown, so plan the project pages to work with photos and simple diagrams.

Site photos without a release

Photos taken on site often show workers, other contractors or unsafe practice. Ask the project manager to approve each set and confirm everyone shown agreed to appear.

Copy the checklist

Plain Markdown you can paste into a doc or an email.

# Engineering firm website content checklist

## Home
- [ ] Firm name as it should appear (Short text, required)
- [ ] One-line description of the firm (Short text, required)
- [ ] Hero image (Image upload, required)
- [ ] Main call to action (Single choice, required)
- [ ] Capability statement (File upload)

## Disciplines
- [ ] Disciplines offered (Multiple choice, required)
- [ ] Description of each discipline (Long text, required)
- [ ] Lead engineer for each discipline (Short text, required)
- [ ] Software and methods (Long text)
- [ ] Typical clients (Multiple choice, required)

## Projects
- [ ] Case study write-ups (Long text, required)
- [ ] Project facts sheet (File upload, required)
- [ ] Site and completed-project photos (Image upload, required)
- [ ] Diagrams and models (File upload)
- [ ] Figures approved for publication (Long text)
- [ ] Client permission to publish each project (Yes or no, required)

## Sectors
- [ ] Sectors you serve (Multiple choice, required)
- [ ] Sector introductions (Long text, required)
- [ ] Frameworks and approved supplier lists (Long text)

## People, safety and quality
- [ ] Principal and senior engineer biographies (Long text, required)
- [ ] Team portraits (Image upload, required)
- [ ] Professional licences and registrations (Long text, required)
- [ ] Management system certifications (Multiple choice, required)
- [ ] Safety statement (Long text)
- [ ] Insurance details to show (Yes or no)

## Careers
- [ ] Open roles (Long text)
- [ ] Graduate or apprenticeship programme (Yes or no)
- [ ] Benefits and working pattern (Long text)
- [ ] Contact for careers (Short text, required)

## Contact and brand
- [ ] Office addresses and hours (Long text, required)
- [ ] Proposal enquiry form fields (Multiple choice, required)
- [ ] Logo files (File upload, required)
- [ ] Brand colours (Colour)
- [ ] Brand fonts (Font)
- [ ] Privacy and cookie policy approved (Yes or no, required)

Questions about this checklist

How technical should an engineering firm's website be?

Write for the buyer who commissions the work, usually a developer, architect or public officer, and keep one technical layer behind it for engineers. Use plain language on the main pages and link to a detailed capability statement.

Can an engineering firm publish drawings and calculations?

Rarely. Drawings and calculations often belong to the client and may be sealed or confidential. Show photos, simple diagrams and approved figures, and ask each client in writing before anything technical goes online.