Reporting views
Read-only views over the register. Raukawa's own Power BI and Fabric connect to these, so the numbers leadership reads are the register's own rather than a copy of it.
The reporting connection
Demo
Here: The views are listed by name and by the columns they carry, so you can see what a connection would give you. In production: A read-only connection Raukawa controls, refreshed on a schedule you set. It is one of the four connections in scope, and it never sends data anywhere: your tools come and read.
Registrations
How many uri are registered, where they live, and which marae they belong to.
registration number, status, marae, verified date, region, country
Processing times
How long a registration takes at each step, and where it waits.
submitted, checked, verified, days at marae, days paused, channel
Contact updates
Whose details changed, when, and through which way in.
uri, field changed, changed at, changed by, source
Demographics
Age bands, regions and marae, for planning and for funders.
age band, region, country, marae, status
Grants
Applications, decisions and amounts, by programme and by round.
reference, programme, round, status, requested, committed, decided by
Communications
What was sent to whom, and by which channel.
record, template, channel, sent at, sent by
Retention and disposal
What is due for review or disposal under the rules Raukawa sets.
record type, created, retention rule, due, status
Payments
What was paid, when, and against which application.
application, amount, paid at, batch, approved by
What this means for Rakai
No export, no overnight file, and no second copy of the register to keep in step. The dashboards Raukawa already has keep working, and they read a register that is finally worth reading.