Operating record

What it is

An operating record is a single, signed, attributed record of an enterprise's operational and governance work. In contrast to point-tools that maintain their own data silos, an operating record is the substrate underneath them — a unified ledger of what the company does, who decided it, when, and why. Each module that runs on the operating record reads and writes to the same data; there are no exports, no re-keying, no reconciliation step. The architectural pattern is the foundation of what is sometimes called 'service-as-a-software' (the inverse of SaaS): the relationship and the record are the product, software is the delivery mechanism.

Why it matters

Setting up enterprise systems is the expensive part. Mapping the org structure, clearing security review, defining roles, proving integration patterns, getting the audit trail right — every procurement repeats it. Each new tool absorbs months of internal work before it produces value. An operating record collapses this. The foundation is loaded once: identity, security posture, integration patterns, audit trail. Every additional capability deploys on top of the foundation as a thin layer — the integration is already proven, the security is already cleared, the audit trail is already running. The marginal cost of a new capability collapses from a six-month project to a one- or two-week deployment.

How Norrsent handles it

Norrsent operates this way. Risk, compliance, sustainability, audit, and Copilot all run on the same operating record. Capital decisions, planning, contract management, and other capabilities deploy on the same record on demand — typically within fourteen days from configuration to production. The shared infrastructure (identity, encryption, residency, audit trail) is loaded at onboarding and used by every module that runs on top of it.

Common questions

How is this different from a 'platform' in the standard sense?

A platform is software that hosts other software. An operating record is the data substrate underneath all of it — the canonical record of what the enterprise does. Most 'platforms' offer integration; an operating record offers a shared write model, where every module changes the same record and the audit trail is unified.

What's 'service-as-a-software'?

The thesis that software value is shifting from 'access to a tool' to 'a long-term operating relationship delivered via software'. The customer pays for outcomes — a working risk programme, a compliant disclosure, a clean audit — not for feature lists. The software is how those outcomes are produced. Norrsent operates on this model.

Is an operating record the same as a data warehouse or data lake?

No. A data warehouse stores data for analysis; it doesn't enforce shared write semantics, signed audit trails, or human-in-the-loop approvals. An operating record is the system of record itself — every write goes through it, every read sees the same authoritative version, every change is signed.