A record entered once is the same record everywhere it appears.
We put incident, action, change and audit onto one data model inside the Microsoft tenant you already license. An incident raised at a site, the action it generates, the change that action requires and the audit finding that references it are four views of one record rather than four entries that have to be reconciled.



- A spreadsheet per site, each with its own columnsOne data model, so a corporate view needs no reconciliation
- Actions living in the system that produced themOne register, whatever raised the action
- Mail chains carrying approvals nobody can find laterApproval recorded against the record it approved
- A monthly pack assembled by hand from four sourcesReporting that reads the source systems directly
- Field observations written on paper and typed up on MondayCaptured on an approved device in the area, or at the nearest workstation on the same round
It runs inside your own tenant
Nothing here asks your IT function to approve a new vendor, issue a second set of credentials or send plant data somewhere it has not already agreed to.
Your Microsoft tenant
- Identity
- Your existing Entra ID. No second set of credentials to issue, revoke or forget.
- Storage
- Inside your own tenant. Plant data never crosses a boundary your IT function does not already govern.
- Licensing
- The Power Platform and SharePoint entitlements carried by your existing Microsoft 365 subscription.
- Retention
- Your records policy, applied by the platform rather than by habit.
- Ownership
- Documented and handed over, so your administrators can extend it without us.
One record, four audiences
Row level security means a technician and a group director read the same underlying record and never see the same screen. The difference between the two views is a permission rule, not a second application to maintain.

Technician
The task in front of them and the last few records for that equipment, on whatever device is permitted in the area.
Supervisor
Their own crew's open actions and overdue items, nothing else.
Plant manager
The site, with the oldest open action and the change queue on the front page.
Group director
Every site on one definition, and which one is drifting.
What it will not do for you
A platform does not create discipline. It makes the absence of discipline visible, which is uncomfortable in the first quarter and useful in every quarter after that. Sites that were quietly not closing actions will show as sites that are not closing actions.
Put incident, action, change and audit on one record
We will come back with the data model, the order we would build it in and what it would cost. Tell us which systems hold these records today and which tenant you run.