Institute of Learning · MBRU · Reference architecture, 2 September 2026
Capture to Score
The concept in one sentence: a learner's placement becomes a Ministry data point because the form that approved it would not save without the fields the KPI needs. Nothing is reported afterwards. The work leaves evidence as it happens, one data model holds it, flows route and remind, and the score is a query.
1. The mechanism, traced through one placement
Figure 1 follows a single event, a learner starting a clinical placement under WF-13, from the moment it happens to the moment it appears on the Ministry's OBEF dashboard. Every other workflow uses the same five layers.
Figure 1. One placement, five layers. The blue box is the only place the concept lives: a form that refuses to save without the KPI fields turns capture into a gate instead of a request. Everything below it is plumbing that follows from the row existing.
Dataverse and the app that writes to itOutside MBRU: Forms for people who cannot log inScore outputsFile, not data
2. Which door the data comes through
The mistake to avoid is a Microsoft Form for everything. The route is decided by who is typing and what they are referring to, not by convenience.
Figure 2. Four doors. Forms is the door for people who cannot log in, which is why it sits on one branch and not four.
3. What makes a workflow start
Fifty-one documented triggers fall into four classes. Only one class is cheap to automate fully, and it is not the class where points are lost.
Figure 3. Classes A to C are engineering. Class D is design: the only defence is a form faster than not filling it in, and a number on the operational dashboard that makes non-capture visible and owned.
4. Where it lives, and who can see what
Figure 4. One solution moves Dev to Test to Prod; nothing is built in the tenant default environment. Forms is drawn outside the boundary on purpose.
5. Three pictures of the same data
Figure 5. Three audiences, three cadences. A dashboard that shows IoL a better number than the Ministry shows MBRU is a disagreement to resolve, not a picture to display.
6. What the design refuses to do
Store data in files, or files in tables.
Use Forms where a lookup is needed.
Build in the default environment or outside a solution.
Let a flow decide anything a workflow gives to a human.
Let a survey platform hold the only copy of raw responses.
Assume MBRU's licence, environment policy or data residency.
Sources: Architecture/00_Visualisation_and_Data_Architecture.md, 01_M365_Solution_Design.md, 02_Dataverse_Schema.xlsx. OBEF anchors from the University Guide v11.5, Appendix A; the band-to-score mapping is an assumption until MoHESR publishes it.