Capability 13 · Data & registers
The register started in Excel.
Now it carries too much risk.
A register workflow for teams managing sensitive, regulated, or operationally important data through spreadsheets — landowners, contracts, permits, cases, and assets that outgrew the sheet they live in.
The situation
The spreadsheet became a system — without system controls.
A team keeps a register in Excel. It may hold landowners, contracts, customers, assets, permits, cases, or other sensitive records.
At first, Excel was enough. Then more people needed access. More fields were added. More versions appeared.
Each update came to depend on someone remembering the right process — and the spreadsheet quietly became a system without any of the controls a system should have.
The challenge
Excel is flexible. That is the problem.
Anyone can change the wrong field. Versions can drift. Sensitive data can be shared too widely. Status can become unclear.
And when something goes wrong, it is hard to know who changed what, and why.
The business does not need a bigger spreadsheet. It needs a controlled register.
The capability
A controlled register, with the flexibility you actually use.
We build a register workflow that moves sensitive or important records out of Excel and into a structured tool. Users get the fields they need; roles control what each person can see and edit.
Status is visible. Changes are logged. Documents and notes can be connected to the record.
It keeps the flexibility of a working register — with the control a spreadsheet cannot provide.
How the flow works
Before / after
The register lives in Excel. People copy, filter, edit, share, and save versions by hand.
Sensitive updates depend on discipline.
The register becomes a controlled workflow. Users work in the right fields, and status is visible.
Access, changes, and ownership are clear.
Controls
- Role-based access decides who sees each record
- Field-level validation keeps entries clean
- Change history records every edit
- Status control governs how records move
- Sensitive fields are protected from wide access
- Documents are linked per record
- Export rules limit what leaves the register
- An audit trail captures important changes
Where this applies
What changes
Questions about registers
Is it safe to put sensitive records into an AI system?
It depends entirely on where the data sits and who can reach it. Handled properly the records stay in a governed store with access set per person, and the assistant only ever sees what that person is already allowed to see.