Skip to main content
gold leaf
Procedure for Fulfilling Enterprise-Level Standards for Web Properties (3.3)

Procedure for Fulfilling Enterprise-Level Standards for Web Properties (3.3)

Print | PDF

This online version is for convenience; the official version of this policy is housed in the University Secretariat. In case of discrepancy between the online version and the official version held by the Secretariat, the official version shall prevail.

Approving Authority: Provost and Vice-President: Academic and Vice-President: Advancement and External Relations

Original Approval Date: February 19, 2020

Date of Most Recent Review/Revision: June 24, 2024

Administrative Responsibility: Information and Communication Technologies (ICT) and External Relations (ER)

Parent Policy: 3.3 Web Governance Policy

1.0. Meeting Enterprise-Level Standards

1.1. The enterprise-level standards, outlined in policy 3.3 Web Governance Policy, set high-level standards related to all web properties conducting university business. Compliance with the enterprise-level standards can be achieved by planned integration into the core web properties through one of Laurier's enterprise content management systems (CMSs), through another approved application (app), or through ongoing demonstration of compliance with Laurier’s enterprise-level standards.

1.1. Integrating into the Core Web Properties

1.1.1. Web properties that align with the audience, functionality and goals of the core web properties should be integrated directly into the core web properties.

1.1.2. The core web properties are centrally funded with operational support provided by Digital Experience (External Relations) and Enterprise Solutions (ICT). Details on authority, responsibility, quality assurance and compliance can be found in policy 3.3 Web Governance Policy.

1.1.3. Digital Experience and Enterprise Solutions, with support from all authorized web editors, are responsible for the compliance of the core web properties with the enterprise-level standards.

1.1.4. To initiate a content integration project related to the core web properties, contact Digital Experience in External Relations.

1.2. Integration into an Enterprise CMS or an Approved App

1.2.1. Web properties that do not clearly align with the functionality or goals of the core web properties may warrant independent build-out within an enterprise CMS or an approved app.

1.2.2. The enterprise CMSs are centrally funded with some operational support provided by Digital Experience (External Relations) and Enterprise Solutions (ICT).

1.2.3. Based on individual service-level agreements, Digital Experience, Enterprise Solutions, and a property’s web manager are responsible for compliance with enterprise-level standards.

1.2.4. To initiate a content integration project related to a new subdomain within an enterprise CMS or another approved application, contact Enterprise Solutions.

1.3. Ongoing Demonstration of Compliance

1.3.1. Web properties that remain outside of the core web properties, enterprise CMSs or approved apps must submit an annual statement of compliance with the enterprise-level standards.

1.3.2. Web managers are responsible for compliance with enterprise-level standards.

1.3.3. A template will be circulated annually to support web managers in providing a statement of compliance, including known issues and action plans, to the Executive Sponsors.

1.3.4. Compliance outreach and support for research and academic-related web properties will be facilitated by The Office of Research Services and/or Teaching and Learning as appropriate.

2.0. Creating or Renewing Web Properties

2.1. Those looking to create or refresh web properties are strongly encouraged to contact Digital Experience and Enterprise Solutions while still in project conception to understand related options and obligations, including:

  • Functional overlap with existing web properties;
  • Consideration of enterprise solutions and approved apps;
  • Resource planning;
  • Awareness of legal and contractual obligations for university web properties;
  • Guidance on the Privacy and Security Impact Assessment (PSIA) process; and
  • Guidance on branding and style guidelines.

2.2. Research web properties can be initiated through the Office of Research Services.

2.3. Teaching web properties can be initiated through Educational Technologies within Teaching Excellence and Innovation.

3.0. Support and Contact Information

×