Why operational memory matters: helping teams reuse expert judgement across sites
Many organisations have experienced people who spot things others miss.
They may work in safety, security, compliance or operations. Over time, they build up practical judgement that is hard to replace. They know what good looks like, what weak looks like, what tends to be missed, and what usually causes trouble later on.
That knowledge is valuable. It is also often fragile.
In many businesses, important know-how lives in the heads of a few experienced people. The wider organisation depends on them to review the same things, answer the same questions and spot the same gaps again and again.
That is where operational memory matters.
Operational memory is not just about storing documents in an AI system. It is about helping the organisation keep and reuse practical judgement, so that useful expertise does not stay with one person, one team or one site.
The everyday problem
Think about a head of safety or security reviewing RAMS. A contractor sends in a document for planned work on site. On first look, it may seem fine. The formatting is tidy. The headings are there. It appears complete. But an experienced reviewer often sees more than the page in front of them.
They may notice that:
- Responsibilities are vague
- Site-specific risks are too generic
- Emergency arrangements have been copied from another job
- Access controls are light
- Handover arrangements are unclear
- The document looks polished, but would be difficult to work from in practice
That judgement is built over time.
It comes from previous reviews, past incidents, lessons learned, and repeated exposure to what works and what does not. The problem is that this knowledge often stays informal.
So the organisation falls into a familiar pattern:
- A junior person does the first review
- They are unsure what really matters
- They send it to the experienced manager
- The experienced manager spots the same issues again
- Everyone waits for that person’s judgement
- Standards vary when they are busy, away or move on
This is common and it’s also avoidable.
What operational memory means in practice
Operational memory gives an organisation a way to capture and reuse the practical checks that experienced people make every day. In the RAMS example, that might include:
- The common reasons a document is sent back
- The follow-up questions that need asking
- Examples of what good looks like
- Recurring weak points in contractor submissions
- Differences that matter between sites
- Lessons from previous reviews or incidents
- The checks a strong reviewer usually makes before approval
This does not mean replacing expert judgement. It means making that judgement easier for the wider team to use.
So when the next RAMS document arrives, the reviewer is not starting from scratch. They can be guided by the same practical checks, patterns and lessons that an experienced head of safety or security would usually apply.
Why that matters
This matters because most organisations do not struggle only with access to information. They struggle with reusing good judgement consistently. A document may exist. A procedure may exist. A previous lesson may exist.
But if the right person still has to remember the same things every time, the organisation has not really solved the problem.
Operational memory helps change that. It can help teams:
- Carry out better first-pass reviews
- Reduce dependence on one or two experienced people
- Work more consistently across sites and shifts
- Bring newer staff up the curve more quickly
- Preserve lessons in a form the wider business can use
- Improve the quality of routine operational decisions
A simple example
Imagine a business with several sites.
At Site A, the head of safety has spent years reviewing contractor documents. They know the weak points that tend to appear in RAMS for electrical work, access control, out-of-hours maintenance and temporary closures. They also know which contractors tend to submit generic plans that need further scrutiny.
At Site B, the local team may not have that same depth of experience.
Without operational memory, Site B may repeat the same mistakes Site A has already learned from. The organisation has expertise, but it has not really spread it.
With operational memory, the lessons from Site A can be made more usable across the wider team. The same practical checks, patterns and examples can support reviews elsewhere.
That does not make every site identical. It does make the organisation better at reusing what it already knows.
This is not just about RAMS
The same issue appears in many everyday workflows. A security manager may know which incident reports look minor but often need escalation.
A compliance lead may know which wording in a supplier document usually hides weak ownership or missing controls.
An operations manager may know which plans tend to work on paper but fail in practice.
In each case, the challenge is the same. How do you stop useful judgement from staying with one person? How do you help the wider organisation benefit from what experienced people already know? That is the role of operational memory.
The real value
The real value is not just storing information. It is making experienced judgement easier to reuse.
That is especially important in organisations with multiple sites, rotating teams, contractor activity, growing operations or pressure on experienced managers’ time.
When good judgement stays local, scale is fragile.
When it becomes operational memory, teams can work more consistently, learn faster and make better use of the expertise they already have.
For organisations thinking about AI, that is an important distinction.
The point is not simply to upload documents into a system.
The point is to make useful knowledge and practical judgement more reusable in the moments where work gets done.
Conclusions
If your organisation depends on a small number of experienced people to review the same issues repeatedly, operational memory may be worth a closer look. It can help teams reuse hard-won judgement more consistently across sites, shifts and workflows.
FAQ 1
What is operational memory?
Operational memory is a way of keeping and reusing practical knowledge and judgement so teams can apply lessons, checks and good practice more consistently in everyday work.
FAQ 2
How is operational memory different from storing documents in AI?
Storing documents makes information available. Operational memory is about making useful judgement easier to reuse in real workflows, such as document review, triage and decision support.
FAQ 3
Why does this matter for RAMS reviews?
Experienced reviewers often know the weak points that appear again and again. Operational memory helps capture and reuse those checks and lessons so more of the team can benefit.
FAQ 4
Does this replace expert judgement?
No. It helps spread expert judgement further, so the wider team can work from stronger guidance and practical lessons.
Author bio: Andrew Tollinton
Andrew Tollinton is Co-Founder of SIRV, the UK’s enterprise resilience platform. A leader in risk management technology, he chairs the Institute of Strategic Risk Management’s AI in Risk Management group and regularly speaks on AI and resilience at global conferences. A London Business School alumnus, Andrew brings 20+ years’ experience at the intersection of technology, compliance and security.
"SIRV helped us move beyond basic reporting into a system that actively supports decision-making". Les O'Gorman, Director of Facilities, UCB - Pharma and Life Sciences
