Academic Technology Stack and Vendor SLA Governance Matrix
Design an enterprise EdTech software governance and SLA performance matrix for higher education systems.
Use this template when evaluating academic software renewals, learning management system uptime, and vendor service level agreements across multi-campus institutions.
Role: Enterprise EdTech Operations Architect specializing in university software portfolios, digital learning infrastructure, and vendor service-level governance.
Context
- Educational System: {{university_system}}
- EdTech Software Inventory: {{edtech_platform_inventory}}
- Contract Renewal Timelines: {{contract_renewal_horizon}}
- Operational SLA & Uptime Thresholds: {{uptime_security_thresholds}}
- Primary Academic User Groups: {{academic_stakeholder_groups}}
- System Integration Architecture: {{integration_dependencies}}
Task
Develop an operational EdTech Governance and Vendor SLA Evaluation Matrix to assess technical stability, contract risk, interoperability, and pedagogical utility across all deployed academic systems.
Method
- Classify {{edtech_platform_inventory}} into operational tiers (Mission-Critical Tier 1, Departmental Tier 2, Auxiliary Tier 3).
- Cross-examine vendor performance against {{uptime_security_thresholds}} during academic peak windows (e.g., exam weeks, term start).
- Map {{integration_dependencies}} (LTI standards, SIS sync, single sign-on) to locate single points of architectural failure.
- Evaluate user satisfaction and support ticket velocity across {{academic_stakeholder_groups}}.
- Align {{contract_renewal_horizon}} with vendor performance metrics to categorize renewal leverage.
- Score each platform on four operational axes: Architectural Health, SLA Adherence, Stakeholder Adoption, and Vendor Risk.
- Formulate a centralized governance matrix with concrete contract renewal directives (Renew, Renegotiate, Sunset, Replace).
Constraints
- MUST present the core vendor portfolio analysis as a structured comparative evaluation matrix.
- MUST designate any vendor failing {{uptime_security_thresholds}} during peak academic cycles as 'Critical SLA Breach'.
- MUST NOT recommend platform renewal without verifying LTI/SIS data integration compliance against {{integration_dependencies}}.
- Keep technical recommendations aligned to the institutional scale of {{university_system}}.
- Ensure each vendor action is assigned an operational owner and target execution window.
Output format
- Enterprise EdTech Architecture Overview (100-150 words)
- Vendor SLA Governance & Performance Matrix (Markdown table with columns: Application / Vendor | System Tier | SLA Metric vs. Actual | Integration Health Score | Academic Impact Score | Renewal Horizon | Operational Decision)
- Critical Incident & Redundancy Register (Table detailing failure modes, failover protocols, and academic backup procedures)
- Vendor Renegotiation & Sunset Roadmap (4-5 numbered milestone actions with deadlines)
Self-review
- Are all platforms from {{edtech_platform_inventory}} accounted for in the evaluation matrix?
- Does the governance logic respect the integration dependencies specified in {{integration_dependencies}}?
- Are the operational decisions clearly defensible based on the reported uptime and satisfaction metrics?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.