Model your projects as records (market, service, location, size, delivery method, client, dates, team) and build the portfolio from them. Write each project page around the problem, your role, the approach and the outcome. Link people and projects both ways. Keep pages fast and accessible, and in a redesign, redirect every old address.
The same records feed proposals and SF 330 submissions, so the website and the bid library stay in step.
Start with a project database
An AEC portfolio is data before it is design. Store each project as a record with fields clients filter by, so one project can appear on every relevant market and service page without being written twice:
- Market: healthcare, education, water, transport, industrial, and so on.
- Service: architecture, structural, civil, MEP, construction management, design-build.
- Location and size: city, region, and a size measure that suits the work.
- Delivery method: design-bid-build, design-build, CM at risk, as relevant.
- Client, dates, team and status: with a consent flag for naming the client.
Project pages that prove fit
Panels score relevance. For US federal design work, panels score firms on criteria the agency publishes; the codified FAR 36.602-1 lists specialized experience and technical competence, past performance and knowledge of the locality among common ones, and many agencies now apply the FAR Overhaul's Part 36 deviation, which moves these procedures to 36.102 and 36.202. A project page should show those in the first screen: the client and location, the problem, your firm's role and services, the approach and the constraints you handled, the outcome in the client's terms, and the people who led it. Add drawings, diagrams or before-and-after views as well as photos. Write captions and alt text that describe what the image shows; Google's image guidance asks for descriptive filenames, titles and alt text, with images placed near the text they relate to.
People pages linked to projects
Clients hire people. Give each leader a page with their role, licenses and credentials as their licenses allow, the markets they work in, and links to the projects they led; on each project page, link back to them. Keep titles exact: only licensed staff carry professional titles. Team pages also serve the second audience, recruits, who read them closely.
One record for the website and the bid library
The project record that feeds the website can feed proposals too. GSA's SF 330 form asks for example projects and key personnel in Part I and general qualifications in Part II; if your records hold the same fields, project sheets and SF 330 sections can be produced from them and kept current in one place. Our engineering proposal writing guide covers the bid side.
Market and service pages
Build a page for each market and service you want more of, each explaining the problems you solve for that client type and pulling in the matching projects and people from the database. These pages answer the searches clients make and give panels a quick way to check relevance. Keep each one specific to the market; a page that could swap in any other market's name helps no one.
Fast, legible and accessible
AEC sites are heavy with images, which slows them down. Google's Core Web Vitals ask for the main content within 2.5 seconds, a response to interaction in under 200 milliseconds and a layout shift score under 0.1, so size and compress images and load them as needed. Keep text legible on photos: W3C's contrast guidance asks for at least 4.5:1 for normal text. The Justice Department's ADA web guidance says the ADA applies to businesses open to the public and to state and local governments, many of which are AEC clients. For those governments, the Justice Department's Title II web rule sets WCAG 2.1 Level AA, with compliance dates moved by an April 2026 interim final rule to 26 April 2027 for entities of 50,000 people or more and 26 April 2028 for smaller ones and special districts.
Redesign without losing search history
Old project pages often carry years of links and search history. Map every old address to its new one before launch and use permanent redirects; Google's site move guidance says 301 and other permanent redirects do not cause a loss in PageRank, that a medium-sized site can take a few weeks or more to show the new addresses, and that a sitemap speeds discovery. Check Search Console after launch. Our website redesign service runs these moves.
How to measure an AEC website
Inquiries and RFP invitations that mention the site, project and market page views by visitors from target client organizations where you can see them, time to find a relevant project, and Search Console queries by market. Count shortlists and wins in the markets the site promotes, year on year.
What we do and do not do
PromotEdge International is an international strategy, technology, marketing and design company, and our delivery team is in India. We design and build AEC websites, project databases and redesigns through our web design and website redesign services. We offer no architecture, engineering or construction services. Power and electrical clients we have worked for include Vikram Solar, Skipper Limited and Power Mech Projects. That work was for their business in India and was delivered by our team there. Our engineering and industrial marketing page describes the work.
Facts we rely on: see our company facts for what we state about ourselves and where each fact comes from.