Onboarding Review: <School Name>

Discovery: Stakeholder Input Framework

<Date>

Version X.X

<Author>

Change Control

Version	Date	Author	Changes

1.	Introduction	4

2.	Current State	6

3.	Vision	7

3.1	Where Do You See The School in 3-5 Years Time	7

3.2	Value Propositions	7

3.2.1	Value Proposition 1 Name	7

3.3	Events	8

3.3.1	Internal	8

3.3.2	External	8

Introduction

This document is designed to act as a framework for the stakeholder input of the <Review Name> Review Discovery Phase. It is intended that the document be used to record input points rather than delivered as a completed/finished product. It will form part of the Stakeholder Feedback sessions scheduled for <Date>.

The document is structured in exactly the same way as the Stakeholder Briefing pack and is designed to capture;

Current State: What’s working, Issues and Projects

Vision Requirements

New Capabilities and associated Value Propositions

Events: Internal and External to the school

Input Type	Definition
Current State	What is in place now?
Issues	What issues is your stakeholder group currently facing. Please express in terms of Issue, related System or Technology, and Impact. It was also be good to understanding the severity of the issue and the frequency of occurrence.
Projects	An overview of which IT related projects are planned or being executed in your area. Minimum details should be; Project Name Project Objectives Project Status (Planned, Approved, In Progress, Completed) Project Start & End Dates
Vision and Enabling Capabilities	A description of how you see your stakeholder group using educational technology over the coming years. This could either be in the form of improvements to existing capabilities or introduction of new capabilities. A capability should be expressed in the form; If we had / could do (text description) Then the benefits to the school / my stakeholder group would be (text description) It would need to be in place by (year/month) And the costs would be approximately $ (if known)
Events	Which future events will have an impact on the school’s IT and Data strategy; Internal: something happening at the school that needs to be supported by IT. For example, the opening of a new campus External: something that will happen outside, but will have an impact on the school. For example, new data protection regulations coming into force

If additional stakeholder input is being provided in other document forms (eg lists in Excel) then these should be referenced in this document and submitted along with it.

Please contact <Review Manager Name> (Review Project Manager) if there are any questions at <Review Manager Email / Phone Number>.

Current State

How do you view the current state of information technology in the school?

Area	Detail	Notes
What’s Working Well
Issue Areas
Projects

Vision

Where Do You See The School in 3-5 Years Time

Where do you see the school in 3-5 years time in relation to educational technology and how you use it? Consider changes to existing capabilities and completely new ones that may need to be implemented.

Area	Detail	Notes
Enhancements to existing capabilities
New capabilities

Value Propositions

For each new or enhanced capability that you envision, please create a high level value proposition by filling in the tables below and modifying the section title. If you have several capabilities in mind please just copy and paste the template table

Value Proposition 1 Name

Element	Detail	Notes
Type	Enhancement / New	Delete as appropriate
Capability	If we had / could do (text description)
Benefits Statement	Then the benefits to the school / my stakeholder group would be (text description)
Timing	It would need to be in place by (year/month)
Costs	And the costs would be approximately $ (if known)

Events

Internal

Name	Description	Date (MM YY)	Technology Implications

External

Name	Description	Date (MM YY)	Technology Implications