An IR website needs ongoing support because the information, software, and connected services continue changing after launch. The operating plan should verify that important investor tasks still work and that the public content remains current under the company's policies.
Distinguish monitoring from maintenance. A monitor may detect a failure; someone still needs authority, access, and a process to resolve it.
Monitor journeys rather than one page
Choose checks tied to the company's communications. Can a visitor open the latest results, reach the official filing, follow an event link, or complete an alert signup? Identify which checks can run automatically and which require a person to confirm meaning and accuracy.
For an automated filing archive, compare the site's output after a known filing with the official record. The SEC's submissions API updates as filings are disseminated, but the website integration has its own retrieval and display process. [1] The EDGAR feed guide explains where delays and mapping errors can occur.
Do not interpret a successful homepage response as proof that a document link, external player, or form submission works.
Use both a calendar and event triggers
Build an operating calendar around results releases, investor events, governance reviews, and platform maintenance. Before a scheduled event, verify the public date, time zone, access instructions, and destination. Afterward, confirm the approved replay and archive treatment.
Add event-triggered reviews for leadership changes, a new presentation, policy revisions, supplier changes, and security or platform updates. The website owner should know which company decisions require a publishing request.
Set review frequency according to the importance and change rate of the content. A fixed monthly review alone may be too late for an event that changes tomorrow; continuous availability monitoring does not replace a human governance-document review.
Give every alert an owner
For each monitored condition, record what counts as failure, who receives the alert, how quickly it must be acknowledged, and when it escalates. Include backup contacts and a route for incidents outside ordinary working hours where the service agreement provides coverage.
Avoid alerting a distribution list with no accountable responder. Test the escalation route during onboarding and after personnel changes. The hosting and reliability guide explains how response and recovery commitments should be specified.
Keep the company involved in decisions about public content. A technical responder can restore a service; the issuer's authorized team decides whether a corrected statement or other communication is needed.
Maintain access and accessibility
Review administrator accounts, supplier access, and recovery contacts. CISA recommends MFA and prioritizing privileged access. [2] Confirm that agreed controls remain enabled when new team members or tools are added.
Include accessibility in the release workflow. A new document, form, or template can require its own evaluation. W3C recommends assessment throughout development and explains that human evaluation is needed alongside tools. [3]
Use the accessibility guide to define the scope and retesting evidence. Do not assume a launch assessment permanently covers every later change.
Report findings in business terms
A useful service review shows failed journeys, stale or incorrect information, completed maintenance, unresolved issues, and response performance against the agreed terms. Include the action taken and the owner of remaining work.
Use repeated incidents to improve the system. If an event link is missed every quarter, revise the publishing checklist. If feed errors recur, investigate the integration and acceptance criteria. If a supplier cannot provide evidence for a promised service, resolve that gap in the agreement.
The essential website checklist can structure a periodic broader review. Keep its findings connected to the same issue log used for everyday support.
Questions companies ask
What is the difference between support and monitoring?
Monitoring detects or checks conditions. Support handles requests and incidents. Define how one leads to the other in the service plan.
Should an automated feed still be checked?
Yes. Verify the public output, especially after known filings and configuration changes. Automation does not remove the need for accountability.
What should a monthly service report show?
Use the reporting period agreed with the provider. Include material incidents, completed work, unresolved actions, and performance against the defined service commitments.
Who should own content freshness?
Assign the business owner for each category and specify the publisher's responsibilities. The provider cannot independently know every internal change that affects public copy.
When discussing ongoing support with VendorGroup, start with the calendar, critical journeys, and escalation responsibilities the company needs covered.
Related VendorGroup resources
- The Essential Investor Relations Website Checklist
- How EDGAR and SEC Filing Feeds Work on an IR Website
- IR Website Hosting, Security and Reliability
