THE INTELLIGENT PIA LEADERSHIP PROGRAMME
The Petroleum Industry Act belongs in the operating model.
15-Session Programme · 25 Minutes Per Day · Free · For leaders in Nigeria’s petroleum industry
WEEK 2 OF 3 · EXECUTING THE OBLIGATIONS · SESSIONS 6–10 · WORK AT YOUR OWN PACE
Evidence Foundation · Chapter 4SESSION 6
The Regulatory Intelligence Engine
Why This Matters
Week 1 gave you an obligation with an owner, decision rights and an evidence index. This week we execute it, and the first question is where AI belongs in that work. Most of the proposals reaching your desk will describe a chatbot that “knows the PIA”. That is the wrong product. What your company needs is narrower and more demanding: an engine that answers a defined question from approved evidence, within permissions, and shows how it got there. Today you learn how to specify it, where rules beat models, and the line the service must never cross. A well-drawn boundary is cheaper than any incident it prevents.
25-Minute Module
0:00 – 5:00
A chatbot is not an engine
- A generic chatbot answers from whatever it finds: a fluent paragraph built from the internet, an old circular and your shared drive, without saying which.
- A regulatory intelligence engine answers a narrower question from an approved body of evidence, within the permissions of the person asking, and shows how the answer was obtained.
- Its purpose is defined work: retrieve conditions, compare instruments, check a pack, draft a response. Each needs its own tests and permissions.
- THE DOCTRINE
A regulatory intelligence engine answers a narrow question from an approved body of evidence, within permissions, and shows how the answer was obtained.
When a vendor says the system knows the Act, ask which version, which passages, and who approved them.
5:00 – 11:00
Four layers, and who owns each
- Design the engine around the decision, in four logical layers. In a Lagos depot the tanks, the release procedure and the gatekeeper are different jobs; so are these.
Layer What it holds or does What it may not do Source Controlled instruments and evidence, each with version and status Hold uncontrolled copies or superseded text as current Interpretation Approved applicability and process rules Accept a model's reading as approved Workflow Tasks, reviews and authorised changes; records who accepted what Move a status without an authorised person Intelligence Retrieves, compares and drafts within the other three Redraw the boundaries it works inside - A model output stays a proposed interpretation until the owner accepts it; the workflow, not the model, records that acceptance.
- THE DOCTRINE
Every answer that matters shows source version, passage and scope. A broad disclaimer beneath a confident answer is a weak substitute for specific uncertainty.
- Missing evidence should be named, with an owner and a resolution task.
Ask to see the passage, not the paragraph. The paragraph is the model's; the passage is the law's.
11:00 – 17:00
Conditions, rules and models
- Retrieval must preserve conditions. Short fragments can separate a duty from its exception; headings, subsections, cross-references and definitions must travel with the text.
- Test it on an existing licence, a new licence, a transferred asset and an activity outside scope. The same answer to all four means keyword matching, not retrieval.
- A displaced column in a scanned table can attach a fee to the wrong activity: use approved structured tables for calculations. The corpus needs a release record — files indexed, integrity identifiers, source status, exclusions.
Work Where it belongs Approved dates, calculations, tolerances, document requirements Rules Comparing wording, retrieving related evidence, drafting readable explanations Language model Forecasting and anomaly detection in operational data Their own models, with their own tests A renewal reminder A rule. A reminder does not need a large language model. - For a material calculation, show inputs, formula, source, period and result. The language layer may explain it, never invent its parameters.
Ask why each task needs AI. Simpler work is cheaper and fails in ways you can diagnose.
17:00 – 21:00
The approval boundary
- Give the service identity — the account the engine runs under — narrow permissions. Retrieval reads an approved corpus. Drafting writes to staging. An agent may create a task.
- THE DOCTRINE
Approval, certification, submission and money movement require separate controls and authorised people. No prompt widens that boundary.
- Retrieved material may contain hostile instructions: treat it as evidence, never as authority. An internal email saying “approved” needs its sender's identity, scope and version verified.
- UPSTREAM · THE WORKED CASE
- Upstream. An assistant drafts a renewal response for a recently transferred asset. The source layer must say which entity now holds the permission; a fluent draft in the former holder's name is a defect.
ACROSS THE CHAIN · THE PARALLEL- Midstream and downstream. A terminal's assistant prepares a pack that includes a fee. The figure comes from an approved structured table; an authorised person in finance releases payment; the assistant only flags it.
- Plan for failure: a manual process when retrieval is down, a rollback for a bad release, and a check whether a transaction occurred before retrying.
Write down what the engine may never do before you write down what it should do.
21:00 – 25:00
Value, measures and your wrap
- Price the whole service, including evaluation, maintenance, incidents and reviewer correction time. Require exportable records, so changing technology never costs you the obligation model or decision history.
- Keep a release record linking model, prompts, tools, index and tests, and a source owner who retires superseded material while preserving its history.
- Ask the board for supported-answer rate, wrong-version retrieval, permission-test results, correction effort, availability and incidents. Usage indicates adoption; it does not establish dependable execution.
- Before you close: for your Session 1 obligation, write one task for each layer, one thing that must stay a rule, and one thing the service identity may never do. That is Section 6 of your game plan.
The narrowest useful role is usually the one that survives its first audit.
Key Terms
Regulatory intelligence engine
A service that answers defined regulatory questions from an approved body of evidence, within the user's permissions, showing source version, passage and scope.
Service identity
The account under which an AI service acts. Its permissions set what it can read, write or trigger, and should be the narrowest that supports the defined work.
Corpus release record
The record of which files were indexed, their integrity identifiers, source status and exclusions. Without it, a test result cannot show what later users receive.
Proposed interpretation
The status of any model output on applicability or meaning until the accountable owner accepts it through a recorded workflow step.
Self-Check — Before You Submit
1. You test a vendor's engine with four questions: an existing licence, a new licence, a transferred asset and an activity outside scope. It gives substantially the same answer to all four. What does that tell you?
- A. The engine is consistent, which is what a regulator wants
- B. It is probably matching keywords rather than retrieving the conditions that distinguish the cases
- C. The corpus is complete, because every question found an answer
- D. The model needs a larger context window
B. It is probably matching keywords rather than retrieving the conditions that distinguish the cases — The four cases differ in their conditions, so identical answers mean the conditions were lost. Consistency sounds reassuring, but here it is the symptom, not the virtue.
2. Which task belongs in a rule rather than a language model?
- A. Comparing the wording of two versions of an instrument
- B. Drafting a readable explanation of an approved calculation
- C. Retrieving correspondence related to a condition
- D. Calculating the internal preparation date for a renewal from an approved legal date
D. Calculating the internal preparation date for a renewal from an approved legal date — Approved dates, calculations and tolerances belong in rules that give the same answer every time. The other three are comparison, drafting and retrieval, which suit language models under review.
3. Your regulatory manager receives an internal email reading simply “Approved” in reply to a draft submission, and the engine's agent is configured to submit on approval. What is the right control?
- A. Let the agent submit, because the approval is in writing
- B. Have the agent reply asking the sender to confirm
- C. Verify the sender's authority, the scope and the version approved, and keep submission with an authorised person outside the agent's permissions
- D. Submit, then seek ratification at the next executive meeting
C. Verify the sender's authority, the scope and the version approved, and keep submission with an authorised person outside the agent's permissions — Submission is beyond the approval boundary, and one word can come from someone without authority or refer to an earlier draft. A confirmation reply still leaves the agent holding a power it should not have.
Today’s Assignment
Specify the narrowest useful AI role for your Session 1 obligation in your company, across the four layers, with the approval boundary stated plainly.
- Restate your obligation with its identifier from Section 3. If AI has no plausible role in it, use the nearest obligation in your business where it does.
- Source layer: list the controlled instruments and evidence the engine may read, the source owner by role, and what must be excluded or retired from current retrieval.
- Interpretation and workflow layers: name who accepts a proposed interpretation, and the workflow step that records it.
- Rules versus model: list at least three tasks that must be rules (dates, calculations, tolerances, document requirements) and at least two that suit a language model, with a sentence each on why.
- The boundary: what the service identity may read, write and trigger, and what it may never do.
- The honest part: describe one place where your company today lets a tool, a template or an email stand in for an authorised decision.
- Aim for 400 to 900 words. This becomes Section 6 of your 90-Day PIA Game Plan.
YOUR GAME PLAN
Section 6 — The AI role: layers, rules versus model, and the approval boundary.
How this is marked — the rubric
| Assigns specific work to each of the four layers for a named obligation, with a source owner by role | 30 |
| Separates rules from model tasks correctly, with at least three rules and two model tasks justified | 25 |
| States the service identity's read, write and trigger permissions and excludes approval, certification, submission and money movement | 25 |
| Names one real place where the company lets a tool or an email stand in for an authorised decision | 20 |
| Total · pass mark 70 | 100 |
Submitting session 6
Write your answer in Word or Google Docs. The first line must read
Write your answer in Word or Google Docs. The first line must read
Session: 6, or the submission is refused. Upload the Word file (.docx), or switch to the Google Doc tab and paste your document’s share link.Marked against the rubric above and returned as a written letter, saved to your progress page. Do not submit until you have passed the self-check above.Capabilities Covered
Engine specificationRules versus modelsApproval boundaryRetrieval testingRelease control
Operating Obligations · Chapter 5SESSION 7
Licensing and the Asset Lifecycle
Why This Matters
Every executive in this industry has signed off a change believing the permission covered it. Sometimes it did. A valid permission is not unrestricted authority to keep changing an asset, and the expiry calendar most companies rely on cannot see a change of entity, product, capacity or configuration. This session moves your obligation model out of the legal folder and onto the asset, from concept to retirement. You will learn the internal states that stop an acknowledgement letter being read as approval, and build a permission dependency schedule that tells your executive committee which commercial promise rests on a regulator's decision not yet made.
25-Minute Module
0:00 – 5:00
A permission has a scope
- Construction approval, operating permission and modification consent serve different purposes. Holding one does not imply the others.
- Replacement equipment with different characteristics, a revised process, a new operating envelope or a changed entity can each affect the evidence a permission rests on. An expiry calendar sees none of them.
- THE DOCTRINE
A valid permission is not unrestricted authority to keep changing an asset. The obligation model moves with the asset, from concept to retirement.
- The lifecycle view runs from concept through development, operation, change and retirement. Your obligation record from Section 3 should be attached to the asset at each of those stages, not to a folder.
Ask of every material change: which permission covers this configuration, and who confirmed it?
5:00 – 11:00
Map permissions to the actual activity
- Record the activities each asset actually carries out and the permissions governing them. Attach conditions to the configuration and entity covered. Keep the signed instrument, application basis, drawings and correspondence in one evidence chain.
- Then separate the states. These are recommended internal states, not regulatory categories.
Internal state What it establishes What it does not establish Prepared The pack exists internally That anything has been sent Submitted The pack was sent That it was received or complete Acknowledged Receipt Permission Under review The matter is open with the regulator Any outcome or timetable Approved The permission, within its stated scope and conditions Cover for later changes Rejected, expired or superseded The permission no longer supports the activity as recorded That history may be deleted - Payment proves payment, not satisfaction of every condition. I have seen a renewal reported green because the fee receipt was on file and two conditions were not.
- Use current instruments for the asset concerned — for midstream and downstream, these include the Midstream and Downstream Petroleum Operations Regulations 2025, S.I. 79 of 2025. A historical checklist does not become the current rule set without a supersession review.
If your tracker has one column called status, it is hiding at least three of these.
11:00 – 17:00
The permission dependency schedule
- Connect physical project milestones to approvals. Identify evidence that depends on engineering, testing, land, environmental work, corporate information or funding.
- Set internal preparation dates ahead of the external requirement — the separation of management time from legal time you made in Session 3.
- Find the critical dependencies early. If an application needs inspection evidence, fund the inspection early enough to resolve findings. If configuration affects permission, the gate must say so before procurement commits to a design.
- THE DOCTRINE
Do not assume regulatory silence is consent. Any default-approval provision requires a documented assessment of its conditions and exceptions.
- Escalate when approval threatens a commercial milestone, while the executive committee still has options.
The schedule earns its keep the first time it moves an inspection forward by a quarter.
17:00 – 21:00
Where AI helps, and change control
- An assistant can read conditions, extract dates, compare a proposed change with approved evidence, assemble a renewal pack and find missing attachments.
- Distinguish factual completeness from legal sufficiency. The assistant may establish that a certificate is present; a specialist decides whether it covers the required equipment and period. A processing-time forecast is not a regulator's commitment.
- UPSTREAM · THE WORKED CASE
- Upstream. A flow station replaces compression equipment with units of different characteristics. Under management of change, the change record lists the previous basis, the proposal, affected permissions, reviewers, approvals and completion evidence. The assistant may identify interfaces; it never approves engineering change or bypasses safety controls.
ACROSS THE CHAIN · THE PARALLEL- Midstream and downstream. A fictional terminal proposes another loading bay. The assistant compares the controlled facility record with the proposal; the engineer and regulatory owner confirm dependencies; the executive committee decides on detailed design and studies.
- Forecast dispatch capacity stays conditional until the required operating evidence exists, so a planning assumption never becomes an unqualified revenue promise.
- Obligation review belongs inside management of change, not in an optional consultation afterwards.
Commercial will want the new capacity in the budget. Let it in, labelled conditional.
21:00 – 25:00
Pilot, board measures and your wrap
- First pilot: an upcoming renewal or modification. Build the accepted pack manually, then test the assistant with a document from another facility, an obsolete drawing and an acknowledgement letter that grants nothing. Measure missing conditions and false completeness separately.
- If source records turn out to be uncontrolled, that is the finding: it tells you which workflow needs repair.
- Ask the board pack to show unresolved permission conditions, milestones dependent on external decisions, changes awaiting applicability review and commitments made against unconfirmed capacity.
- Before you close: name one asset or planned change in your business, the permission it rests on, and the one milestone that depends on a decision you do not control. That is Section 7.
Board measures are useful only while the company still has options. Show them early.
Key Terms
Permission scope
The activity, configuration, entity and conditions a permission covers. Anything outside it needs its own review, whatever the expiry date says.
Permission dependency schedule
A plan linking physical and commercial milestones to the approvals and evidence they depend on, with internal dates set ahead of external requirements.
Factual completeness
Every required document is present. Distinct from legal sufficiency, which a specialist decides: whether the documents cover the right equipment, entity and period.
Supersession review
A check, before reuse, that a checklist or instrument is still current, recording what replaced it while preserving the historical basis for earlier submissions.
Self-Check — Before You Submit
1. A renewal tracker shows a facility as green. The file holds the submitted application, the regulator's acknowledgement letter and the fee receipt. What has actually been established?
- A. That the application was received and the fee paid; not that permission was granted or every condition satisfied
- B. That the permission is renewed, since the regulator has acknowledged it
- C. That the permission is renewed unless the regulator objects within a reasonable time
- D. Nothing, because acknowledgement letters have no evidential value
A. That the application was received and the fee paid; not that permission was granted or every condition satisfied — Acknowledgement proves receipt and payment proves payment. Treating silence after acknowledgement as consent is the trap, and dismissing the letter entirely discards real evidence of receipt.
2. Commercial wants to sell the capacity of a planned loading bay in next year's contracts. Engineering has preliminary design; the permission review has not started. What do you approve?
- A. The contracts, since the bay will clearly be built
- B. Nothing until every permission is in hand
- C. Detailed design and studies, with forecast capacity carried as conditional and no unqualified commitment until operating evidence exists
- D. The contracts, with a clause blaming any delay on the regulator
C. Detailed design and studies, with forecast capacity carried as conditional and no unqualified commitment until operating evidence exists — This keeps the project moving while preventing a planning assumption becoming a revenue promise. Freezing everything wastes the option, and selling unconfirmed capacity creates exposure the company cannot control.
3. An assistant reports that a renewal pack is complete: every listed certificate is present. What does a specialist still need to determine?
- A. Whether the assistant's software version is current
- B. Whether each certificate covers the required equipment and period, which is legal sufficiency rather than factual completeness
- C. Whether the pack is long enough to satisfy the regulator
- D. Nothing, if the assistant passed its pilot
B. Whether each certificate covers the required equipment and period, which is legal sufficiency rather than factual completeness — Presence is not coverage. A certificate for the wrong equipment or period makes an unsuitable application look complete, and passing a pilot does not transfer that judgement to the tool.
Today’s Assignment
Build the permission dependency schedule for one asset or one planned change in your business.
- Choose the asset or change connected to your Session 1 obligation. If none is, use the nearest asset in your business with a permission due or a change planned in the next twelve months.
- List the permissions it rests on, the activity and configuration each covers, and its current internal state using the states from this session.
- Map at least four milestones (physical, commercial or financial) to the approvals and evidence they depend on, with the external requirement and your internal preparation date for each.
- Identify the critical dependency: the inspection, study, land, environmental or corporate item that must be funded or finished first, and who decides it.
- State what an assistant could do here and what a specialist must decide, separating completeness from sufficiency.
- The honest part: name any commitment your company has made, or is about to make, against capacity or an approval not yet confirmed.
- Aim for 400 to 900 words. This becomes Section 7 of your 90-Day PIA Game Plan.
YOUR GAME PLAN
Section 7 — The permission dependency schedule.
How this is marked — the rubric
| Names the asset or change, each permission's scope, and its internal state without conflating acknowledgement or payment with approval | 30 |
| Maps at least four milestones to approvals and evidence, with external and internal dates kept separate | 30 |
| Identifies the critical dependency and the role that decides its funding or timing | 20 |
| States honestly any commitment made against unconfirmed capacity or approval | 20 |
| Total · pass mark 70 | 100 |
Submitting session 7
Write your answer in Word or Google Docs. The first line must read
Write your answer in Word or Google Docs. The first line must read
Session: 7, or the submission is refused. Upload the Word file (.docx), or switch to the Google Doc tab and paste your document’s share link.Marked against the rubric above and returned as a written letter, saved to your progress page. Do not submit until you have passed the self-check above.Capabilities Covered
Permission scopingLifecycle obligation mappingDependency schedulingChange controlCompleteness versus sufficiency
Operating Obligations · Chapter 6SESSION 8
Measurement and Custody Transfer
Why This Matters
Barrels are where the PIA meets your revenue. Production, transfer, receipt, inventory and sale are different events, and a business can report a consistent total in each function while the totals fail to reconcile across the chain. When they fail, the word that reaches the executive committee is usually theft. Sometimes it is. More often it is timing, conversion, calibration, allocation or data handling, and calling everything theft prevents the investigation that would find out. Today you learn to read a quantity as an evidence chain, to walk a difference down a reconciliation hierarchy, and to refuse a saving that is only arithmetic.
25-Minute Module
0:00 – 5:00
Different events, different totals
- Think of a crude transfer from a Niger Delta flow station to a terminal. The station, the pipeline operator, the terminal and finance each hold a number. Each can be internally consistent; together they may disagree.
- A discrepancy may come from timing, conversion to standard conditions, calibration, allocation, data handling or physical loss. Labelling every difference theft prevents an accurate investigation.
- Engineers need to know whether a meter is dependable. Finance needs an approved volume basis. Commercial needs defensible transfer records. The regulatory owner needs evidence behind the submitted quantity.
- THE DOCTRINE
Measurement has an evidence chain. Intelligence should support it, not substitute estimates for required measurements.
When someone says the barrels were stolen, ask which of the six causes has been ruled out, and on what evidence.
5:00 – 10:00
The regulatory anchor and the data
- The Nigerian Upstream Petroleum Measurement Regulations 2023 address approved metering arrangements, measurement systems, logs and production reporting. They apply to upstream measurement. They are not a universal downstream checklist; assets in the Authority's remit use its current instruments.
- Start from approved measurement points and equipment identities. Keep raw readings, timestamps, operating conditions, calibration history, maintenance events and conversion methods, linked to tickets, counterparties and periods.
- Label every value: measured, allocated, calculated or estimated. Make units explicit: gross observed volume is not automatically standard volume, and gas volume, energy and mass have their own bases.
- Keep event time, posting time and reporting cut-off separate. A loading that crosses midnight can land in different periods at dispatch and receipt.
An unlabelled estimate is the most expensive number in your company. Nobody knows to question it.
10:00 – 17:00
Walking a difference down the hierarchy
- A reconciliation hierarchy compares like with like at each interface, accounts for timing, and identifies the residual, with the explanation and approval for every adjustment preserved. Here is the book's worked example. The inputs are illustrative teaching assumptions for a fictional system.
Step Barrels Share of dispatch What it is Dispatched (standard) 100,000 — Starting quantity for the defined period Received (standard) 99,400 — Counterpart quantity Initial difference 600 0.6% Before any explanation Agreed cut-off 200 — Reconciled reporting difference Documented conversion correction 150 — Reconciled reporting difference Residual 250 0.25% Unexplained; goes to investigation - THE DOCTRINE
The 350 reconciled barrels are reporting differences, not recovered product. The $5,000 sensitivity on the residual is exposure, not a saving, and never an AI benefit.
- At an assumed contribution margin of $20 per barrel, the 250-barrel residual is $5,000 of potential contribution exposure, for sensitivity analysis only. The residual investigation examines meter performance, inventory, operating events and loss evidence.
- If the issue stays unresolved, the executive needs that status, not a manufactured explanation.
Count the same financial outcome once. Investigation effort saved, product recovered and billing corrected are three different things.
17:00 – 21:00
AI as an investigative lead
- Anomaly detection can compare a meter with its history; retrieval can find the relevant calibration certificate or maintenance event; models can prioritise exceptions across points.
- Treat every output as an investigative lead. A model can see that two totals which usually track together have diverged. It cannot establish a cause. The engineer decides which test, inspection or reconciliation follows.
- UPSTREAM · THE WORKED CASE
- Upstream. At a flow station, allocated well volumes are reconciled to an approved measurement point; the 2023 Measurement Regulations address the upstream metering arrangements and production reporting behind it. A model may reconstruct a missing day for analysis, but whether a substitute quantity is permitted in actual reporting is a decision for the company, not the model.
ACROSS THE CHAIN · THE PARALLEL- Midstream and downstream. At a depot, a tank receipt in gross observed volume is compared with a dispatch ticket at standard volume. The conversion basis and reference conditions are checked first, under the Authority's current instruments, before anyone treats the gap as loss.
- First pilot: one transfer interface, detection run in parallel, the measurement team classifying alerts, and the model never changing the official quantity. It fails if it creates a queue larger than the team can examine or encourages unsupported allegations.
An alert is a question addressed to an engineer. It is never an accusation addressed to a counterparty.
21:00 – 25:00
Review, board measures and your wrap
- Review material unexplained differences with measurement, operations, finance and commercial owners present. Separate age from magnitude: a small recurring difference can signal a persistent weakness; a large one explained by documented timing may be simple.
- Ask the board for residual differences after approved reconciliation, exception age, calibration evidence gaps and retrospective changes.
- Before you close: draw one quantity handoff in your business, label each value, and write the reconciliation rule you will apply. That is Section 8.
- Pop Quiz 2 opens now — five questions on Sessions 6 to 8, closed book. Sit it before you start Session 9.
The residual that nobody owns is the one that grows.
Key Terms
Reconciliation hierarchy
An ordered method comparing like with like at each interface, accounting for timing and conversion, and isolating an unexplained residual with every adjustment approved and recorded.
Residual difference
What remains unexplained after approved reconciliation. It is the subject of investigation, and the figure the board should see.
Standard volume
Volume converted to agreed reference conditions. Gross observed volume is not automatically standard volume; comparing the two misleads.
Value classification
Labelling each quantity as measured, allocated, calculated or estimated, so its basis travels with it into every report and invoice.
Self-Check — Before You Submit
1. In the worked example, 100,000 barrels are dispatched and 99,400 received. Agreed cut-off explains 200 and a documented conversion correction 150. What is the residual, and how should the 350 be treated?
- A. 600 barrels; the 350 are recovered product
- B. 350 barrels; the 250 are a timing effect
- C. 250 barrels, 0.6% of dispatch; the 350 are recovered product
- D. 250 barrels, 0.25% of dispatch; the 350 are reconciled reporting differences, not recovered product
D. 250 barrels, 0.25% of dispatch; the 350 are reconciled reporting differences, not recovered product — 600 less 350 leaves 250, which is 0.25% of dispatch. The trap is booking the reconciled 350 as product recovered, when nothing physical was found.
2. Your operations head proposes reporting the $5,000 contribution figure on the residual as the first-year saving from a new anomaly-detection tool. What do you say?
- A. No: it is a sensitivity on potential exposure, not evidence of a saving, and must not be booked as an AI benefit
- B. Yes, provided finance signs it off
- C. Yes, but only half of it, as a prudent estimate
- D. Yes, because the tool found the residual
A. No: it is a sensitivity on potential exposure, not evidence of a saving, and must not be booked as an AI benefit — The figure is an illustrative exposure at an assumed margin. Finding a difference recovers nothing, and finance signing an unsupported claim only makes it more expensive later.
3. A model flags that two meters which usually track together have diverged. What is its output?
- A. Proof of meter failure
- B. An investigative lead; the engineer decides which test, inspection or reconciliation follows
- C. Grounds to adjust the official quantity
- D. Evidence of theft to be reported to security
B. An investigative lead; the engineer decides which test, inspection or reconciliation follows — A model can detect divergence but cannot establish a cause without evidence. Adjusting quantities or alleging theft on an alert alone is exactly what a pilot must prevent.
Today’s Assignment
Map one measurement or quantity handoff in your business and write its reconciliation rule.
- Choose the handoff closest to your Session 1 obligation. If your obligation does not touch quantities, use the nearest handoff in your business where a number changes hands: production, transfer, receipt, inventory, sale or a regulatory return.
- Draw the chain from the first measurement to the reported figure, naming each system, owner by role, unit and time basis.
- Classify every value in the chain as measured, allocated, calculated or estimated, and say where an estimate loses its label today.
- Walk one real difference, or an illustrative one clearly labelled, down the reconciliation hierarchy to its residual, stating who approved each adjustment.
- Write the reconciliation rule you will apply, including how you separate age from magnitude.
- The honest part: name the explanation for differences your company reaches for first, and whether the evidence supports it.
- Aim for 400 to 900 words. This becomes Section 8 of your 90-Day PIA Game Plan.
YOUR GAME PLAN
Section 8 — The quantity evidence chain and reconciliation rule.
How this is marked — the rubric
| Maps one real handoff with systems, owners by role, units and time basis stated | 25 |
| Classifies every value as measured, allocated, calculated or estimated and identifies where a label is lost | 25 |
| Walks a difference to a residual with each adjustment and its approver, without treating reconciled differences as recovered product | 30 |
| States the company's default explanation for differences and tests it honestly against the evidence | 20 |
| Total · pass mark 70 | 100 |
Submitting session 8
Write your answer in Word or Google Docs. The first line must read
Write your answer in Word or Google Docs. The first line must read
Session: 8, or the submission is refused. Upload the Word file (.docx), or switch to the Google Doc tab and paste your document’s share link.Marked against the rubric above and returned as a written letter, saved to your progress page. Do not submit until you have passed the self-check above.ASSESSMENT NOW OPEN
Pop Quiz 2 — Engines, Permissions and Barrels opens now. Sit it before you start the next session — it is how you find out whether the doctrine landed, and the practice papers may be resat as often as you like.
Sit Pop Quiz 2 →Closed book, no notes, and Coach Ritchie switches himself off while you sit it.Capabilities Covered
Quantity evidence chainsReconciliation disciplineValue classificationExposure versus savingInvestigative use of AI
Operating Obligations · Chapters 7 and 8SESSION 9
Host Communities, Environmental Evidence and Methane
Why This Matters
Two obligations today, and they share a weakness. A host community trust and an emissions return can both look complete while resting on a basis nobody can reconstruct. In community relations it shows up as promises, meetings, projects and payments the company cannot reconcile. In environmental reporting it shows up as a total that fell because records went missing. Both reach the board as good news until someone asks how the number was produced. I will be direct: AI can make these records usable, but it cannot supply legitimacy that consultation has not established, or create evidence that physical work has not produced.
25-Minute Module
0:00 – 7:00
Host community funding: the anchor and the arithmetic
- For the upstream contribution basis, PIA section 240(2) specifies 3% of the settlor's preceding-year actual operating expenditure in the relevant operations. Section 244 allocates 75% to the capital fund, 20% to the reserve fund and 5% for administration. Regulation 24 of the 2022 upstream host communities regulations addresses operating-expenditure treatment.
- The percentage is not a flat levy on revenue, nor a rule for every industry participant. Establish applicability and the audited eligible basis first. The inputs below are the book's illustrative assumptions, not a real trust's accounts.
Line Basis Illustrative amount Approved eligible preceding-year opex Audited, reconciled, exclusions documented ₦10 billion Contribution 3% (section 240(2)) ₦300 million Capital fund 75% (section 244) ₦225 million Reserve fund 20% (section 244) ₦60 million Administration 5% (section 244) ₦15 million - THE DOCTRINE
The important work happens before multiplication. A language model should explain the approved calculation, not invent its base or redirect money.
When the contribution figure arrives, ask to see the expenditure reconciliation before the percentage.
7:00 – 13:00
Three events, and the evidence of each
- Separate contribution liability, transfer evidence and project expenditure. An internal allocation does not prove transfer. Transfer does not prove delivery of a project.
- Record commitments when made, with the speaker and their authority. A promise at a town hall creates expectations before internal approval; the record should expose that gap to leadership, not quietly treat it as authorised or erase it.
- Do not make community decisions through opaque scoring. Ranking communities by predicted cooperation can entrench bias and damage trust. A translation material to consent needs validation of meaning: faster translation does not show that people understood or agreed.
- UPSTREAM · THE WORKED CASE
- Upstream. A fictional trust approves a water project. The register shows most of the contract paid; the assistant finds a different pump specification on the final invoice and no location record for completion photographs.
- It creates a review task. The project owner checks whether the change was approved; the authorised governance body decides payment and acceptance. The assistant neither accuses the supplier nor certifies delivery.
ACROSS THE CHAIN · THE PARALLEL- Midstream and downstream. Section 240(2) sets the upstream basis. A midstream or downstream company must obtain the current host-community instruments for its own activity and approve applicability before calculating anything; copying the upstream percentage is not a method.
- Treat a false allegation as a material defect in any pilot. Precise language — “possible duplicate requiring examination” — and an explained matching basis protect both the company and the trust.
Installing a water asset does not establish that it reliably supplies water. Ask the board for both.
13:00 – 20:00
Environmental evidence and methane
- The upstream environmental remediation regulations (2024) provide a specific framework for remediation. Keep remediation funding distinct from retirement funding and host-community funding: their purposes and evidence differ.
- NUPRC's April 2026 methane and greenhouse gas directive moves reporting from at least IPCC Tier 2 in the third quarter of 2026 to Tier 3 or equivalent high-level measurement-based methods by January 2027. These are reporting milestones, not proof that any asset has achieved them.
- Define the reporting boundary: asset, period, equipment and activities, and the treatment of flaring, venting, combustion and fugitive sources, with method, factor, uncertainty and methodology version preserved for each period. Separate measured, estimated and calculated values.
- THE DOCTRINE
Boundary changes can look like performance changes. Explain the effect of added sources or revised factors before claiming any reduction.
- A suspected methane leak belongs in established inspection and safety procedures. A model should not infer safety because an abnormal pattern is familiar. Avoided emissions are not recovered sales revenue unless gas is actually captured and sold on a defensible basis.
Track methodology readiness and evidence gaps, not the attractiveness of the dashboard.
20:00 – 25:00
The inventory correction, and your wrap
- A fictional gas facility reports lower quarterly emissions. The assistant finds equipment records excluded during a database migration. They are restored, and the total rises.
- The proper account is a corrected inventory and a resolved control defect, not a setback caused by AI. The tool prevented an unsupported performance claim. Next: test the other migrated periods, correct affected submissions through the approved route, and reconcile the source list to the physical asset inventory.
- Ask the board for contribution reconciliation, transfer confirmation, acceptance evidence and unresolved grievances (with confidentiality), and for inventory completeness, measurement gaps, retrospective corrections and demonstrated physical changes.
- Before you close: write the one claim your company makes about its communities or its emissions that its evidence would not yet support. That sentence anchors Section 9.
A number that rises because it became complete is good news. Say so to the board in those words.
Key Terms
Eligible operating expenditure basis
The audited, reconciled preceding-year operating expenditure in the relevant operations to which the section 240(2) percentage is applied, with exclusions and allocations documented.
Contribution, transfer and delivery
Three separate events: the liability calculated, the money actually transferred, and the project delivered and accepted. Each needs its own evidence.
Reporting boundary
The assets, period, equipment, activities and source types an emissions inventory covers. Changing it changes totals without changing physical emissions.
Measurement-based method
An emissions method resting on measurement rather than factors alone; the NUPRC directive sets Tier 3 or equivalent as the January 2027 milestone.
Self-Check — Before You Submit
1. Approved eligible preceding-year operating expenditure is an illustrative ₦10 billion. What are the contribution and the capital, reserve and administration amounts?
- A. ₦300 million; ₦225m, ₦60m, ₦15m
- B. ₦300 million; ₦240m, ₦45m, ₦15m
- C. ₦3 billion; ₦2.25bn, ₦600m, ₦150m
- D. Three per cent of revenue, split equally three ways
A. ₦300 million; ₦225m, ₦60m, ₦15m — 3% of ₦10 billion is ₦300 million, split 75/20/5 under section 244. Applying the percentage to revenue is the trap the book warns against: the basis is eligible operating expenditure.
2. After a data migration is corrected, your gas facility's quarterly emissions total rises. The communications team calls it a setback caused by the new AI tool. How do you describe it to the board?
- A. As a setback, and pause the tool
- B. As a corrected inventory and a resolved control defect; the earlier lower figure was unsupported
- C. As a model error to be reversed so the trend is preserved
- D. As an emissions increase requiring an immediate operational response
B. As a corrected inventory and a resolved control defect; the earlier lower figure was unsupported — Restored records made the inventory complete; physical emissions did not change. Pausing the tool or restoring the lower figure would reinstate the unsupported claim it caught.
3. An assistant finds a different pump specification on a trust project's final invoice. What should happen next?
- A. The supplier is notified of suspected fraud
- B. Payment is withheld automatically
- C. A review task: the project owner checks whether the change was approved, and the authorised governance body decides payment and acceptance
- D. The assistant updates the register to the invoiced specification
C. A review task: the project owner checks whether the change was approved, and the authorised governance body decides payment and acceptance — The assistant surfaces a discrepancy; people with authority resolve it. Accusing or withholding on a match alone treats suspicion as evidence, which the book counts as a material defect.
Today’s Assignment
Write the evidence chain, from basis to delivered outcome, for the host community or environmental obligation that applies to your business, and name the claim its evidence would not support.
- Choose host community funding or environmental and methane reporting, whichever applies to your company. If neither does, use the nearest stakeholder or environmental obligation in your business, or link it to your Session 1 obligation if it fits.
- State the source instrument and whether it is upstream-specific. Do not apply an upstream percentage or milestone to an activity it does not cover.
- Write the chain step by step: basis (eligible expenditure or reporting boundary), calculation or method, approval, transfer or submission, and delivered outcome, with an owner by role and the evidence at each step.
- Mark each figure as measured, estimated or calculated, and each commitment with who made it and on what authority.
- The honest part: quote, as closely as you can, one claim your company currently makes — in a report, a meeting or a press line — that this chain would not support, and say what evidence would.
- Aim for 400 to 900 words. This becomes Section 9 of your 90-Day PIA Game Plan.
YOUR GAME PLAN
Section 9 — The stakeholder or environmental evidence chain, and the unsupported claim.
How this is marked — the rubric
| Names the obligation, its source instrument and its scope correctly, without extending upstream rules to other activities | 25 |
| Writes the full chain from basis to delivered outcome with an owner by role and evidence at each step | 35 |
| Separates liability, transfer and delivery (or boundary, method and physical change) and labels value types | 20 |
| States one real unsupported claim and the evidence that would support it | 20 |
| Total · pass mark 70 | 100 |
Submitting session 9
Write your answer in Word or Google Docs. The first line must read
Write your answer in Word or Google Docs. The first line must read
Session: 9, or the submission is refused. Upload the Word file (.docx), or switch to the Google Doc tab and paste your document’s share link.Marked against the rubric above and returned as a written letter, saved to your progress page. Do not submit until you have passed the self-check above.Capabilities Covered
Trust funding arithmeticCommitment recordingReporting boundariesMethane readinessUnsupported-claim detection
Operating Obligations · Chapters 9, 10 and 11SESSION 10
Safety, Supply and the Midstream–Downstream Chain
Why This Matters
This session closes Week 2, and it covers the three places where I have seen value leak most quietly: a defect that is closed on paper and open on the pipe, a volume that is promised twice, and a handoff between depot and customer that nobody owns. Safety, supply and the midstream–downstream chain are different disciplines with different regulators and different consequences. What they share is a gap between a record that says done and a condition that is actually done. Twenty-five minutes cannot cover three chapters in full, so we take the decisions that matter most to an executive and leave the detail to the book.
25-Minute Module
0:00 – 7:00
Safety: document closure is not physical closure
- Safety evidence sits across inspections, work orders, competence files and engineering documents. Planned tasks can look complete while a critical defect stays open under a different equipment name.
- The Nigerian Upstream Petroleum Safety Regulations 2024 address upstream arrangements. Midstream and downstream controls need their own applicable framework and facility conditions. Nothing here replaces permit-to-work, management of change, independent protection or competent-person requirements.
- A closed work order may prove labour charged, not repair. Training attendance is not authorisation. A temporary arrangement needs basis, limits, monitoring, expiry and an approving person. Preserve original observations: a summary that turns “intermittent vibration” into “healthy” removes what the engineer needs.
- THE DOCTRINE
Document closure is not physical-condition closure. An AI risk score must never become an informal waiver.
- Do not claim a prevented-accident benefit without a defensible method. And fund the work: an application that creates an unfunded defect queue has exposed a problem, not resolved it.
Ask for findings awaiting authority and corrective work awaiting funding. Those two lines are yours.
7:00 – 14:00
Supply: one volume, several commitments
- Obligation quantity, contract, nomination, delivery, accepted billing and collected cash are different commitments, even when they share a number. Regulatory constraints belong in the approved planning basis, never as optional instructions a conversational model can revise.
- Forecast ownership is split: engineering owns physical capacity, commercial owns contract positions and nominations, finance owns collection, legal and regulatory owners approve obligation treatment. The worked scenario below uses the book's illustrative teaching inputs for a fictional system, not a statutory allocation.
Line MMscf/d Note Available 30 Before outage Obligation (approved planning basis) 18 Fixed in the basis Firm commitment 8 Existing contract Total committed 26 18 + 8 Optional business 4 30 − 26 Available after outage 24 Shortfall of 2 against the 26 committed - The model cannot remove the 2 MMscf/d shortfall by producing a more confident allocation table. It should show feasible responses within the authorised framework; commercial and regulatory owners examine notifications, alternatives and customer effects; leadership decides resources and communication.
- THE DOCTRINE
A plan to secure replacement supply is not secured supply. A customer conversation is not a revised contract. The forecast changes only when the condition is established.
Back-testing must use only what was known at the time. A model given final production cannot claim it predicted it.
14:00 – 20:00
Midstream and downstream: value lost at handoffs
- Map activities, not one corporate label: refining, processing, storage, transport, wholesale supply and retail may need different permissions and conditions.
- The Midstream and Downstream Petroleum Operations Regulations 2025, S.I. 79 of 2025, commenced on 7 July 2025. Regulation 156 revokes specified older 2023 instruments, with savings for prior matters. Reusing an older checklist requires a supersession review; keep the history behind earlier submissions.
- Batch and tank identities must survive transfers. Nameplate capacity is not proof of available capacity. Copying another batch's certificate creates no evidence for the current product, and product release stays with authorised people.
- UPSTREAM · THE WORKED CASE
- Upstream. Repeated corrosion observations on a transfer line sit under different names. The assistant links them and finds a repair recommendation still open while later reports use softer language. The engineer checks; the executive decides resources and timing. History has been reconstructed; fitness for service has not been established.
ACROSS THE CHAIN · THE PARALLEL- Midstream and downstream. A fictional distributor's dashboard shows strong dispatch while complaints rise. The assistant finds inconsistent measurement bases and missing batch links. Operations, quality, finance and the regulatory owner each check their part; leadership prioritises record repair.
- Loss reduction is claimed only when later comparable records establish it.
Ask where the batch identity changes. That is usually where the evidence breaks.
20:00 – 25:00
The critical handoff, and your wrap
- Three handoffs to choose from: integrity finding to closure, obligation to cash, or receipt to inventory to dispatch. Each has a point where the record says done and the condition may not be.
- Ask the board for corrective work awaiting funding, obligations at risk under realistic scenarios with progression from delivery to cash, and unreconciled inventory, quality gaps and capital tied to disputed stock.
- Before you close: name your critical handoff, the point where its evidence breaks, and who decides there. That is Section 10, and it completes the operating half of your game plan.
- Practice Exam 2 opens now — fifteen questions covering Sessions 1 to 10. Sit it before Week 3; you may resit it as often as you like.
A week of obligations ends here. Next week we govern them.
Key Terms
Physical-condition closure
Evidence that a defect has actually been repaired and verified, accepted by an authorised person. Distinct from a closed work order, which may prove only labour charged.
Approved planning basis
The set of obligations, allocations and constraints a supply plan must respect. A forecast or optimiser works inside it and cannot revise it.
Supersession review
A check that a checklist or instrument is still current before reuse, such as after S.I. 79 of 2025 revoked specified 2023 instruments, preserving the basis for earlier submissions.
Available capacity
What an asset can actually handle given berth, storage, loading, maintenance and permission constraints. Nameplate capacity does not prove it.
Self-Check — Before You Submit
1. Using the illustrative supply scenario: 30 MMscf/d available, 18 for an obligation, 8 for a firm commitment. An outage cuts availability to 24. What is the position?
- A. No shortfall, because the 4 MMscf/d of optional business absorbs it
- B. A 6 MMscf/d shortfall against total availability
- C. A 2 MMscf/d shortfall against the 26 MMscf/d of existing commitments
- D. A 2 MMscf/d shortfall that the model can resolve by reallocating the obligation quantity
C. A 2 MMscf/d shortfall against the 26 MMscf/d of existing commitments — Commitments total 26 against 24 available, leaving 2 short. The optional 4 has already gone with the outage, and the obligation quantity sits in the approved basis, not in the model's gift.
2. A maintenance dashboard shows a critical corrosion finding as closed because its work order is closed. What do you ask for?
- A. Proof of repair and the required verification, accepted by an authorised person
- B. The work order number, for the audit file
- C. A model risk score confirming the line is now low risk
- D. Nothing further; a closed work order is closure
A. Proof of repair and the required verification, accepted by an authorised person — A closed work order may prove only labour charged. A risk score is not evidence of repair and must not act as an informal waiver of the finding.
3. Your depot team wants to reuse a 2023 compliance checklist for a midstream activity. What is the right step?
- A. Reuse it, since it was approved at the time
- B. Discard it and all records made under it
- C. Ask an assistant whether it is still valid and accept the answer
- D. Run a supersession review against S.I. 79 of 2025, which revokes specified older instruments with savings, and preserve the history behind earlier submissions
D. Run a supersession review against S.I. 79 of 2025, which revokes specified older instruments with savings, and preserve the history behind earlier submissions — The instrument base changed on 7 July 2025, so the checklist needs review, not reuse. Discarding it destroys the legal basis for historical submissions, and an assistant's answer is only a proposed interpretation.
Today’s Assignment
Map one critical handoff in your business and identify where its evidence breaks and who decides.
- Choose the handoff that touches your Session 1 obligation: integrity finding to closure, obligation to cash, or receipt to inventory to dispatch. If none fits, use the nearest handoff in your business where a record passes between functions.
- Map it step by step, naming the record at each point, its identifier (asset, batch, tank, contract or work order), its owner by role and what it actually proves.
- Mark the point where the record says done and the condition may not be, and the evidence that would close the gap.
- Name who decides at that point, and whether they have the authority and the funding from your Section 4 design.
- State what an assistant could usefully do here and what it must never do.
- The honest part: describe one occasion when your company reported something as closed, secured or available that later proved not to be.
- Aim for 400 to 900 words. This becomes Section 10 of your 90-Day PIA Game Plan.
YOUR GAME PLAN
Section 10 — The critical handoff and where its evidence breaks.
How this is marked — the rubric
| Maps one real handoff with records, identifiers, owners by role and what each record proves | 30 |
| Locates precisely where the evidence breaks and states the evidence that would close it | 30 |
| Names the decision-maker at the break and tests their authority and funding honestly | 20 |
| Describes a real occasion when something was reported done that was not | 20 |
| Total · pass mark 70 | 100 |
Submitting session 10
Write your answer in Word or Google Docs. The first line must read
Write your answer in Word or Google Docs. The first line must read
Session: 10, or the submission is refused. Upload the Word file (.docx), or switch to the Google Doc tab and paste your document’s share link.Marked against the rubric above and returned as a written letter, saved to your progress page. Do not submit until you have passed the self-check above.ASSESSMENT NOW OPEN
Practice Exam 2 — Executing the Obligations opens now. Sit it before you start the next session — it is how you find out whether the doctrine landed, and the practice papers may be resat as often as you like.
Sit Practice Exam 2 →Closed book, no notes, and Coach Ritchie switches himself off while you sit it.Capabilities Covered
Integrity evidenceSupply commitment disciplineHandoff mappingSupersession controlCapacity realism