An architecture practice adding healthcare projects to its services needs more than a new homepage menu item. Prospective clients need to see which building types the team can take on, where it works, what experience supports the offer and who handles inquiries. A property owner moving into a new region faces a similar task: existing pages may show buildings, availability or contacts that no longer reflect the operation.
Start preparing the website while the expansion is being planned. That gives the team time to make accurate information easy to find without publishing claims it cannot yet support.
Define what is actually changing
Before editing the site, make a short inventory of the expansion. Is it a new service, a new market, greater delivery capacity or a change in legal or operational responsibility? Each calls for different information. Adding construction-stage support to an architectural service, for example, calls for a clear scope and handover process. Opening a regional office calls for an accurate address, coverage area and contact route.
- Services: Which activities can clients commission now, and which are still planned?
- Geography: Where can the team work, and do local licensing or permitting arrangements differ?
- Projects: Which completed work shows relevant experience, and what can be disclosed?
- Operations: Who receives inquiries, issues proposals and maintains published information?
- Timing: Which changes take effect now, and which depend on staffing, approvals or opening dates?
Use that inventory as a shared reference for everyone editing the site. It helps prevent a service being advertised before the people, permissions or processes needed to deliver it are in place.
Audit the pages a new client will encounter
Expansion claims rarely appear on just one page. Check the homepage, service descriptions, project profiles, team biographies, contact details, downloadable documents and inquiry forms. Search for old location names, service lists, staff titles and statements such as “we work exclusively in…” that may no longer be true.
Then try to find the new service as a visitor who does not know the firm. Is its scope easy to reach? A page buried under an unrelated category may be published but hard to find. A top-level menu item has the opposite problem if it leads to a page with too little detail to answer basic questions.
For each affected page, record its owner and whether it should be retained, revised, redirected or removed. This matters when several property listings or project teams repeat the same facts in different places. For a maintenance approach after launch, keeping property and project information current addresses how published details can stay aligned with operational changes.
Give each new offering a clear scope
A new offering needs to say what the business does, who it serves, where it works and which project stages it covers. If an architecture bureau is adding educational facilities, “school design” alone tells a client little. Spell out whether the team can provide feasibility studies, concept design, documentation for approvals, technical coordination or construction-stage services—and include only work it can actually undertake.
Be equally clear about boundaries. Say whether specialist engineering, accessibility consultation or cost planning is handled in-house, coordinated through external consultants or procured separately. Do not imply that compliance with every local requirement follows automatically. Building rules, procurement procedures and professional registration vary by jurisdiction and project type; the appointment and design process must account for project-specific checks.
Match the evidence to the claim. A completed commercial building does not, on its own, demonstrate experience with operating healthcare facilities. If the team has no directly relevant completed project, describe transferable work precisely—such as coordinating complex user groups or planning phased occupation—rather than presenting an adjacent project as an identical precedent.
Make project information usable for evaluation
For each relevant project, give its location, building type, appointment scope, current status and the team’s actual role. State if a proposal was never built or the firm joined for only one stage. A rendering of an unbuilt scheme should not be presented as a photograph of a completed facility. Get permission before publishing client identities, plans or sensitive operational details.
Check location claims and contact routes
Entering a new market does not necessarily mean opening an office. “Serving clients in Bristol” is different from “Bristol office.” List a physical address only if it is a business location people can use as described. If meetings are by appointment or the team works remotely, say so.
Test every route a new-market inquiry could take: forms, email links, phone numbers and downloadable request documents. Form fields should gather information useful for triaging a building project, such as location, building type, project stage and anticipated decision date. Do not ask for detailed budgets or confidential drawings before the client understands how that information will be handled.
Give each inquiry type a responsible person or team. When a regional lead changes, update both the contact page and the internal routing rule. Otherwise, a well-written expansion page can still send inquiries to an unmonitored mailbox.
Prepare the site for more content and traffic
More services and locations often mean more project pages, staff profiles and documents. Before adding them, check that the content management system supports consistent templates and clear ownership. A reusable project template, for instance, can prompt editors to provide the status, location, team role and image permissions every time.
Test new pages on ordinary mobile connections, especially if they contain large drawings or visualizations. Use appropriately sized files and readable text alternatives for meaningful images. Check that forms, downloads and navigation work with a keyboard and on narrow screens; clients should not need a desktop computer to reach essential information.
If an announcement or campaign could cause a short traffic spike, review capacity with the technical team. Can hosting handle the expected load? Are backups current, who can restore the site, and how will broken forms be detected? Base traffic estimates on planned communications and previous campaigns where available, rather than an invented growth figure.
Publish in stages, then test how the site works
Expansion details need not go live together. Have service leads, delivery teams and legal or compliance advisers where needed review draft pages. Set an approval date for factual claims, particularly office openings, staff appointments, permits and project status. If a statement depends on a lease, license or contract, leave it unpublished until that condition is confirmed.
- Approve one source of truth for services, locations, dates and contact owners.
- Update essential pages and inquiry routing before announcing the expansion.
- Test links, forms, mobile layouts and accessibility on the published site.
- Review incoming inquiries and questions after launch for gaps or confusing information.
Ask someone outside the project team to find the new service, check its geographic coverage and send a test inquiry from a phone. Confirm where the message arrives and who takes it forward. If a second office is due to open on 1 September, schedule a check that morning: the homepage, location page and form confirmation should all agree on its address, opening status and contact route.