When the record is the product
accountable
A transcript, a licence, a custody chain, a reconciliation. These are systems whose output has to stand up years later, in front of someone who was not there and is not inclined to believe you.
The audit trail is the system, not a report
In a system of record, the history is not a feature added for compliance — it is the same data the workflow runs on. Every state change is attributable, timestamped and immutable after the fact, because a trail assembled afterwards from logs is exactly the artefact an auditor cannot accept. Build it the other way around and the audit question answers itself.
Roles are the hard part
Real institutions have five or six roles with genuinely different jobs, overlapping authority and a sequence everyone already knows. The failure is building one interface with things hidden from some people. We model the authority — who may act, on what, at which stage, and who may override whom — and give each role tooling shaped to its own work, from one data model.
Designed to be disputed
Assume the entry will be challenged: by a counterparty, an auditor, a court, or a successor who inherits the system. That assumption drives the decisions — immutable events rather than editable rows, signed documents generated on demand, exports that reconcile, and a record of every correction rather than a quiet overwrite.
- Consignment and chain-of-custody tracking
- Registries, licensing and institutional records
- Revenue tracking and reconciliation
- Role, permission and audit architecture
- 01A data model built on events, not editable state
- 02Role, permission and delegation architecture, documented
- 03Signed documents generated on demand, with a verification route
- 04Exports and reconciliation reports a finance team can defend
Two departments hold different versions of the same record
A dispute is settled by whoever still has their copy
Reporting is reconstructed at month end rather than read off the system
- 08
Institutional Records Platform
A public platform and a full records system behind it, covering five distinct staff and student roles on one data model.
- 01
Operations Command Center
A live executive command centre joining five production databases into a single operational picture.
- 11
Incentive Administration
Staff incentive calculation and approval with authenticated roles and exportable finance reporting.
Can this replace a system we already depend on?
Sometimes it should not. Where a live system is relied on by hundreds of staff or sits under another vendor's contract, we have had better results reading from it and owning the record above it. Replacement is a decision with a migration plan attached, not a default.
How do you handle corrections?
As entries, never as overwrites. A correction records what changed, who changed it and why, and the original remains readable. Anything else means the system cannot answer what it said last March, which is the question that eventually gets asked.
Who owns the data?
You do, in a database you can point at, with documented schemas and exports that work without us. That is in the engineering charter on /company#principles and in the handover terms on /procurement.
Do you work with regulated records?
Yes — the pattern is the same whether the auditor is internal, a regulator or a counterparty's lawyer. What differs is the retention policy and who may read what, and both belong in the design rather than in a policy document nobody implements.
Start here
Bring us the problem nobody has solved.
A 30-minute technical briefing. We will tell you what we would build, roughly what it costs, and honestly whether we are the right people for it.
- ask@madsoftech.com
- Telephone
- +220 872841578
- Office
- Brusubi, The Gambia