A public company should consider redesigning its investor relations website when the existing structure repeatedly prevents accurate publishing, useful navigation, or reliable operation. A redesign needs a business reason: a documented problem the current platform or information architecture cannot reasonably resolve.
Begin with an evidence-based review. Separate individual defects from recurring limitations, then decide whether targeted improvements or a broader rebuild will address them.
Distinguish a repair from a structural problem
A missing document, incorrect link, or outdated contact usually calls for an immediate correction. Do not wait for a new website to resolve those issues. If similar failures recur because the system cannot support the required workflow, investigate the underlying constraint.
For example, a results archive that cannot group materials by reporting period may require repeated manual workarounds. A navigation component that cannot be operated with a keyboard may require replacement across many pages. Document the constraint and the work needed to change it before deciding that the entire site must be rebuilt.
Use the common mistakes guide to assemble a specific issue register. The register should identify affected tasks, frequency, ownership, and the limits of a smaller repair.
Review the way the team publishes
Ask the people maintaining the site to demonstrate a routine update and an urgent correction. Identify approval gaps, unnecessary handoffs, missing version history, and tasks dependent on one person.
Then separate platform limits from process choices. A different CMS will not automatically resolve unclear approvals. Conversely, a well-written process may still fail if the system cannot enforce the required permissions or preview the final page accurately.
Describe the desired future workflow in the brief. A provider should be able to explain how it will support that workflow and what remains the company's responsibility.
Test accessibility and technical maintainability
Assess accessibility before committing to a cosmetic refresh. W3C recommends early and ongoing evaluation, including knowledgeable human review. [1] Use the findings to determine whether components can be repaired or require a more substantial change.
Ask the technical operator to explain the site's dependencies, supported software, update process, backup recovery, and ownership arrangements. A redesign brief should identify which of these conditions must improve and what evidence will demonstrate acceptance.
Avoid using a single automated score as the whole business case. Review actual pages, documents, forms, and investor journeys against the agreed requirements.
Account for changes in the company
A new corporate identity, expanded reporting archive, merger, or change of provider may justify revisiting the site's structure. Define what has changed before expanding the project. A new logo might need a controlled design update; combining two issuers' histories raises different information and approval questions.
If URLs will change, include migration work in the decision. Google recommends planning URL mappings and redirects and monitoring the move. [2] Treat those as project responsibilities rather than something to arrange after the design is approved.
Write a measurable redesign brief
Specify the tasks that must work, the content to retain, the publishing process, and the acceptance evidence. Include constraints such as a results announcement, contract end date, or internal review capacity.
Compare the proposed redesign with a targeted improvement option. Estimate both using the same scope assumptions and ownership model. The cost guide explains the categories to compare; the timeline guide shows how to turn dependencies into a realistic schedule.
A useful approval decision states why the current site cannot meet the agreed needs, what will change, and who will verify the result. “It needs to look more modern” is a preference; connect that preference to the investor experience it should improve.
Questions companies ask
Is there a fixed redesign cycle?
Review the site when requirements change or repeated problems suggest that targeted repairs are no longer sufficient. Use its condition and the company's needs to make the decision.
Can we improve the site in phases?
Yes. Identify a coherent first release and preserve necessary access during the transition. Include unfinished work in a dated plan with accountable owners.
Should we change providers at the same time?
Evaluate that separately. Compare the current provider's ability to deliver the required changes with the cost and continuity work of switching.
What makes a redesign successful?
Completion of the agreed tasks and operating improvements, supported by acceptance evidence. Appearance is one part of that result.
Share the findings and desired outcomes with VendorGroup to frame a redesign around the work the website needs to perform.
Related VendorGroup resources
- Common Investor Relations Website Mistakes
- How Much Does an Investor Relations Website Cost?
- How Long Does an Investor Relations Website Redesign Take?
