Website Monitoring Plan

1. Purpose

The Website Monitoring Plan establishes a systematic approach to monitoring the availability, functionality, performance, content integrity and usability of the official AIIMS Bilaspur website. It aims to ensure that citizens, patients, students, faculty, staff and other stakeholders can access reliable institutional information and online services.

2. Scope

This plan covers the public website, principal pages and navigation, content management system, downloadable documents, internal and external links, forms and other published online services, subject to the responsibilities and access arrangements of authorised technical teams.

3. Monitoring Objectives

  • Identify website downtime and service interruptions.
  • Detect broken links, missing pages and inaccessible documents.
  • Identify performance and page-loading issues.
  • Verify that important notices and announcements display correctly.
  • Check usability across common devices and browsers.
  • Identify suspected security incidents or unauthorised changes.
  • Support accessibility, multilingual consistency and applicable Government website guidelines.
  • Maintain records of incidents, corrective actions and follow-up.

4. Monitoring Activities and Frequency

The following schedule is proposed for approval and implementation according to available technical resources.

Monitoring Activity Proposed Frequency
Website availability and major service failures Automated monitoring where available, with alerts to authorised personnel
Homepage, key notices and important public information Daily or whenever significant updates occur
Internal links, external links and page errors At least weekly
Forms, downloads and major public-facing functions At least weekly and after relevant changes
Website performance and page-loading issues Periodically and after significant technical changes
Content integrity and unauthorised changes Through available security controls and routine checks
Accessibility and mobile display Periodically and after significant design or platform changes
CMS, software updates and security advisories Regularly, based on applicable advisories and maintenance requirements
Monitoring records and unresolved issues Monthly, or more frequently for critical incidents

This is a proposed schedule. Actual monitoring arrangements and response targets shall be approved by the Institute and aligned with the responsibilities of designated technical service providers.

5. Monitoring Procedure

  1. The designated technical team checks website availability and operation using approved monitoring tools and manual verification where necessary.
  2. Alerts, complaints and detected issues are logged with the date, time, affected page or service and available diagnostic information.
  3. The issue is classified according to its impact on public access, institutional operations, information accuracy or security.
  4. The responsible technical team investigates the issue and coordinates with the relevant content owner or service provider.
  5. Corrective action is taken through the authorised maintenance process.
  6. The affected page or service is re-tested after correction.
  7. The incident record is updated with the action taken, outcome and preventive measures, where applicable.

6. Content and Link Monitoring

The website management team shall check that important content is current, approved and displayed correctly. Internal links, external links, downloads and navigation items shall be checked periodically. External links should be clearly identifiable where required by applicable Government website guidelines.

Broken links, missing files, expired announcements and references to superseded information shall be reported to the responsible department for correction, replacement or archival.

7. Security and Technical Monitoring

Authorised personnel shall undertake security monitoring in coordination with the designated IT team or service provider. Activities may include reviewing system alerts, access records, software advisories, backup status and indicators of unauthorised changes, subject to approved security arrangements.

Software updates, configuration changes and maintenance activities shall follow authorised change-management procedures. Where practicable, changes should be tested before deployment to the production environment.

8. Incident Reporting and Escalation

Website issues shall be reported through the designated institutional or technical support channel. Incidents affecting major public services, sensitive information, website integrity or widespread availability shall be escalated promptly to the responsible technical authority and institutional administration.

Incident records should include:

  • Date and time of detection.
  • Affected service or page.
  • Nature and impact of the issue.
  • Action taken and responsible team.
  • Restoration or resolution status.
  • Preventive measures, where applicable.

9. Reporting and Accountability

The designated technical team shall maintain appropriate monitoring and incident records. Periodic reports may summarise availability issues, broken links, unresolved incidents, performance concerns, maintenance activities and corrective actions for review by the designated authority.

10. Review and Approval

This plan shall be reviewed periodically and following significant changes to website infrastructure, service arrangements or applicable Government guidelines. It shall be implemented in accordance with the approved responsibilities and arrangements of AIIMS Bilaspur.