Home / Core / MCDS
MyRISK Core · higher education
Turn MCDS from a data standard into assurance operations.
MyRISK Core uses the MCDS data dictionary as the shared language for controls, evidence, reporting and accountability — so one definition can answer many assurance questions.
The problem
MCDS gives us the data language. We still assemble everything by hand.
MCDS gives the sector its data language. But controls, evidence and decisions are still assembled by hand, one request at a time — for reporting, research, credentialing, accreditation, shared services and supplier assurance.
Core maps controls, evidence, owners and reporting onto MCDS-aligned entities, so a definition agreed once can serve many requests.
A data standard describes the sector. An assurance operating model runs it.
Define once, report many
- Controls and evidence attached to the entities the sector already uses
- Owners and review cadence on each definition
- One definition serving reporting, research, credentials and supplier assurance
- Trace attaches where a sign-off must be defended
- Essentials attaches where owners and actions must keep moving
The first step
One use case, not a sector-wide programme
Core is sold as a bounded alignment sprint against one named use case — the MCDS-aligned assurance question that is painful now. The Opportunity Scan comes first: it tests whether one use case is ready and backed, and what the sprint would work from.
MyRISK is an MCDS Implementation Partner in the MortarCAPS ecosystem. That is an ecosystem role, not an accreditation or an endorsement — and we will always describe it exactly that way.
If your institution works with MortarCAPS, we are already part of that conversation.
Use cases the Scan can start from
- Sector and regulatory reporting cycles
- Research governance and data-sharing assurance
- Credentialing and accreditation evidence
- Shared services assurance
- Supplier and third-party assurance
The Scan needs one named use case, someone senior to back it, and someone who lives with the problem. If those are not in place yet, we will tell you what would need to exist first.
For your reviewers
The boundaries, in writing
Where Core stops
- Not a sector-wide integration programme. One named use case, bounded, first.
- Not MCDS accreditation, certification or endorsement — the implementation-partner classification is an ecosystem role and nothing more.
- Not binding on any institution that has not agreed to a definition.
- Not a substitute for your own risk decisions about your own suppliers.
Which MCDS-aligned use case is painful now?
Reporting, research, credentials, accreditation, shared services or supplier assurance. The Opportunity Scan starts with the one that keeps being assembled by hand.