By: Enzo Pennacchioli
When I arrived at the AOSTRA Underground Test Facility (UTF) as a new Chemical Engineering graduate, Steam Assisted Gravity Drainage (SAGD) was still an experiment. Industry professionals were working together to prove that a concept developed by Dr. Roger Butler could unlock Alberta’s vast bitumen resources that were too deep to surface mine.
Looking back, it’s remarkable how the technology and the regulatory framework advanced together. Every breakthrough in SAGD recovery was accompanied by new approvals, requirements, and expectations that would eventually shape today’s in situ industry.
What was very different then was how information was managed. Much of the project’s knowledge lived in paper files, technical reports, meeting notes, and the memories of the people involved. Today’s digital systems make records easier to store and search, but the challenge of preserving context remains remarkably similar.
Over the next three decades, I watched that evolution from several different roles: operations engineer, project developer, regulatory manager, compliance leader, and now regulatory advisor.
One lesson has remained constant throughout that journey:
Projects have long memories, even when organizations don’t.
Then: The UTF and the Early Days of SAGD
The UTF was more than a technology demonstration. It was also the beginning of a regulatory learning process that continues today. Early projects generated technical studies, operating procedures, environmental commitments, and reporting requirements that became part of the foundation for future developments.
At the time, few people imagined that some of those decisions and commitments would still matter decades later.
Yet they do.
What Piles Up Over a Project’s Life
A typical in situ project accumulates an enormous regulatory footprint over its lifetime.
Environmental Impact Assessments. EPEA approvals. Directive 054 annual submissions. SIR responses. Groundwater monitoring reports. GHG compliance filings. Renewal applications. Amendment applications. Internal compliance records.
The list never really ends.
For a mature asset, the complete approval history can easily exceed 50,000 pages of records, and a long-standing EPEA approval may contain dozens of conditions and hundreds commitments in the background layered through amendments, renewals, and regulatory correspondence over many years.
The challenge isn’t creating the record. It’s remembering it.
How Institutional Memory Gets Lost
One situation from my career illustrates the problem.
For example, during the preparation of an annual Directive 054 submission, a regulator asked for some details about a commitment for a heave-monitoring program that had been made approximately ten years earlier. As steam heats the reservoir hundreds of metres below the surface, the ground above can slowly lift (heave) by a small amount, due to thermal expansion. Heave monitoring tracks this movement to make sure it is not causing adverse effects on nearby facilities or infrastructure.
The original project team was gone. Several key individuals had moved on and the asset had changed hands.
What initially appeared to be a simple question turned into a multi-day investigation.
The details of the commitment were eventually found in an SIR response attached to application files that had been submitted years earlier, not in the approval itself. This commonly occurs in OSCA scheme approvals.
Had those records not been located, the company would have struggled to demonstrate the objectives behind the commitment or verify how compliance had been maintained. At best, it would have resulted in significant additional regulatory effort. At worst, it could have created uncertainty about whether the commitment had been properly addressed.
That is the real risk of losing institutional knowledge.
What Good Operators Do
The best operators recognize that compliance isn’t just about maintaining approvals. It’s about maintaining understanding.
Some practical habits that I’ve seen work well over the years include:
Document the reason behind each commitment.
It’s not enough to record what was agreed to. Capture why the commitment was made, what concern it addressed, and what regulatory context existed at the time.
Maintain living compliance trackers.
Compliance systems should connect commitments to source documents, approval conditions, responsible teams, and historical decisions rather than functioning as static checklists.
Conduct knowledge-transfer reviews before people retire or change roles.
Some of the most valuable regulatory information exists only in the experience of long-serving personnel. Structured handovers can preserve insights that would otherwise be lost.
Review historical records during acquisitions and ownership transfers.
When projects change hands, due diligence should include a review of key approvals, commitments, amendments, and regulatory correspondence. Understanding inherited obligations is just as important as understanding the asset itself.
Maintain a defensible legal register.
A strong legal register should serve as more than a list of requirements. It should help explain how obligations evolved and where supporting evidence can be found.
These practices help preserve the “why” behind decisions, not just the paperwork itself.
Where AI Helps and Where It Doesn’t
Today, AI is beginning to change how regulatory professionals interact with historical information.
Tasks that once required days of manual searching through regulatory databases, approval files, amendment applications, and archived correspondence can often be completed in hours. AI-assisted tools can identify historical commitments, connect related filings, summarize large document collections, and surface information that might otherwise be overlooked.
For organizations managing decades of project history, that capability is significant.
But technology still has limits.
AI can help find a commitment. It cannot always explain why a particular decision was made fifteen or twenty years ago. When a regulator asks, “Why was this condition included?” or “What was the original intent behind this commitment?” the answer often requires professional judgment, organizational context, and an understanding of how the industry and regulatory system evolved over time.
In that sense, AI is a powerful research assistant, not a replacement for institutional experience.
The Value of Remembering
After more than 35 years in Alberta’s oil sands sector, that’s perhaps the most important lesson I’ve learned.
Institutional memory remains one of the industry’s most valuable regulatory assets. Preserving it is just as important as preserving the approvals themselves.
The technology has changed dramatically since the days of the UTF. The records are now digital rather than stored in filing cabinets and archives. Yet the fundamental challenge remains the same:
The organizations that perform best over the long term are the ones that not only keep the records, but also preserve the knowledge behind them.
