Student data platform readiness

Why run this

What this checklist is for

Institutions know a great deal about their students and can rarely assemble it into a picture of where any individual is. The data exists; the profile does not.

Most early alert and analytics projects fail on routing and ownership rather than on signal quality, so this checklist weights those heavily.

Run it with

Registrar or Director of Planning

And with

Data platform team

And with

Student services and academic representatives

The checklist

20 checks, in the order we would run them

Tick only what you can genuinely evidence today. An item you intend to do is not an item you have done, and scoring yourself generously here only produces a comfortable number and an uncomfortable project.

Section 1

Governance

Decisions that must precede engineering.

A data governance group exists with academic and professional service representationA platform governed only by IT will produce definitions the academic side disputes.
Legitimate educational interest is defined and enforceable by roleThis is the access model. Asserting it in policy without enforcing it in the system is not sufficient.
Student consent and privacy positions are documentedIncluding what students are told about analytics performed on their data.
Definitions for retention, progression and attainment are agreed institutionallyFaculties measuring these differently produce an institutional number that means nothing.
An ethical position exists on predictive analytics about studentsPredicting who will fail carries real risk of becoming self-fulfilling. Decide the position deliberately.

Section 2

Data foundation

Whether the sources can be joined.

Every source system is identified with an owner and a refresh cadenceStudent records, learning platform, finance, engagement and library systems.
A stable student identifier exists across systemsWithout one, joining is probabilistic and the errors are invisible.
Historic data is available for a meaningful baselineAt least three cycles, because education outcomes are seasonal and noisy.
Data quality on critical fields is measured before buildingEnrolment status, module registration and attendance are the fields most likely to be inconsistent.
Bronze layer retains source data untransformedSo a disputed figure can be traced to what the source actually said.

Section 3

Access and protection

The obligations that make student data different.

Row-level security restricts staff to students they have a reason to seeTested with real role accounts, including one that should see nothing.
Special category data is identified and handled with heightened controlsDisability, health and similar data commonly present in support records.
Analytics copies are covered by the same retention as source recordsAnalytical copies of student data carry the same obligations and are routinely overlooked.
Access is reviewed periodically with recorded outcomesStaff move roles frequently in institutions and access follows slowly.
Export and download capability is controlled deliberatelyRow-level security governs what a report shows, not what somebody does with it afterwards.

Section 4

Acting on it

The half that determines whether any of this matters.

Every alert or insight routes to a named person, not to a dashboardThis is the most common failure in early alert programmes and the most avoidable.
Those people have the capacity to actAn alert to an advisor with no time produces a record of a missed intervention.
Interventions and their outcomes are recordedOtherwise the institution never learns which interventions work.
Effectiveness is measured across a full academic cycleA result after one semester is noise, and any partner claiming otherwise is selling.
Students are not disadvantaged by being flaggedCheck how the flag is used in practice, not only how it was intended.

What your score means

Read this against the number above

These bands are deliberately blunt. The middle band is where most organizations honestly sit, and it is a perfectly reasonable place to proceed from — provided the gaps are written down with owners rather than carried as optimism.

0–59%Significant gaps

Do not proceed yet. More than four in ten items are unaddressed, and the ones that fail here are usually the foundational ones that make everything after them harder.

60–84%Mostly ready, with known gaps

Proceed on a defined scope, with the outstanding items written into the plan as risks with owners and dates. This is the most common honest position.

85–100%Ready

The remaining gaps are small enough to handle during delivery rather than before it. Confirm the unticked items are genuinely minor rather than simply unexamined.

Your score highlights automatically as you tick items above. Nothing is saved, sent or tracked — refreshing the page clears it.

Closing the gaps

If you could not tick these, start here

The four items below are the ones whose absence causes the most trouble downstream. If your unticked items include any of these, they are worth addressing before the rest.

No agreed institutional definitions

Settle these first. A platform built on contested definitions produces reports that get disputed rather than used.

No named alert owner

Assign one per alert type. A dashboard is not an owner, and this is where these programmes most reliably fail.

Analytics copies outside retention

Bring them into scope. They carry the same obligations and are the copies most likely to be forgotten.

Measuring within one semester

Extend to a full cycle. Education data is seasonal and a partial-cycle conclusion is usually wrong.

Want a second opinion on your score?

We will map your current sources and show what a joined student view would look like, including how the access model would satisfy your registrar.

Talk through your result Read the related guides We reply to every message within one business day.

Keep going

Related checklists

intune

educationReadiness

Device refresh readiness checklist

Twenty checks before a large device refresh in an institution, covering procurement, provisioning and the academic calendar.

June 6, 2026 · 20 checksOpen

d365-sales

educationReadiness

Enrolment cycle readiness checklist

Twenty checks before a recruitment cycle opens, covering data, communication and the melt window most institutions leave unmanaged.

January 31, 2026 · 20 checksOpen

sharepoint

educationReadiness

Student records and information architecture audit

Twenty checks on whether student information is organised, protected and findable across a federated institution.

January 17, 2026 · 20 checksOpen

What this checklist is for

Run it with

And with

And with

20 checks, in the order we would run them

Governance

Data foundation

Access and protection

Acting on it

Read this against the number above

If you could not tick these, start here

No agreed institutional definitions

No named alert owner

Analytics copies outside retention

Measuring within one semester

Want a second opinion on your score?

Related checklists

Device refresh readiness checklist

Enrolment cycle readiness checklist

Student records and information architecture audit

Tell us what you're trying to fix

Let’s get started on something great

Phone

Email