Prepare by practising decisions, not definitions: classify petroleum volumes with the evidence actually given, choose production forecasting methods that match the reservoir data available, reason about well barriers and professional obligations from paper scenarios, and rehearse writing concise evidence-based statements of your own engineering judgement.
Classifying petroleum volumes when commerciality is unclear
Reserves are quantities expected to be commercially recovered from a development that is sanctioned or clearly commercial; everything else is resources, however large the volume. Anchor your study on the evidence gate, not the geology.
Compare proved, probable, and possible reserves with contingent resources by asking one question: is there a committed development with a reasonable expectation of commerciality? Contingent resources can sit in the ground with mapped structures, drilled appraisal wells, and encouraging test results, yet remain resources because no development decision exists. Trace this distinction through a hypothetical: a discovery with 200 MMbbl in place, two flow tests, but no development plan — the volume is contingent, not reserves.
Apply the same reasoning to maturity steps. A project moves toward reserves when appraisal reduces uncertainty, economics are assessed, and a sanction decision is taken; it can also move backwards if costs rise or markets shift. Build flashcards around trigger events — sanction, farm-out, licence expiry, failed appraisal — rather than around definitions. This trains the most useful habit when classifying volumes: identifying which classification the stated facts actually support, rather than the one that sounds optimistic.
- Reserves classification hinges on commerciality and commitment, not on volume size.
- Contingent resources can have wells, tests, and maps and still not be reserves.
- Study trigger events (sanction, appraisal results, cost changes) that move volumes between categories.
| Evidence given in a scenario | Defensible classification | Why it matters |
|---|---|---|
| Sanctioned development, first production achieved | Proved reserves (1P) | Recovery is committed and commercial; uncertainty is limited |
| Sanctioned development with identified upside infill targets | Proved plus probable (2P) | Upside is technically supported but less certain |
| Discovery appraised, economics drafted, no sanction | Contingent resources | No development commitment exists |
| Lead or prospect from seismic only | Prospective resources | Risk of discovery is still entirely untested |
| Development previously sanctioned, now uneconomic at current prices | Classification requires review | Commerciality is a live condition, not a one-time label |
Choosing between decline curve analysis and material balance
Decline curve analysis extrapolates rate behaviour; material balance uses pressure and production data to estimate volumes and drive mechanisms. The defensible method depends on data quality, drive mechanism, and what changed operationally.
Trace the classic error with a scenario: a well has shown a smooth exponential decline for three years, so an engineer extends the curve another ten years to estimate recovery. Last year, though, the operator installed artificial lift, and the water cut has begun rising steeply. Extrapolating the pre-lift decline through an operational and mechanistic change is the mistake; the better decision is to treat the decline parameters as unreliable, check what the water cut trend implies about the drive mechanism, and cross-check with any pressure data before quoting a forecast.
Compare the two methods on their assumptions. Decline analysis needs a stable, established trend and a drive mechanism that will not change; it says nothing about reservoir pressure or ultimate recovery directly. Material balance needs reliable pressure measurements and accurate production and fluid data; it constrains volumes in place and reveals the drive mechanism but rarely gives short-term rates. A second worked scenario: two wells show identical rate declines, but one sits in a strong aquifer drive and one in depletion drive — identical declines, very different futures. The lesson to rehearse is that a forecast is only as good as the mechanism assumption beneath it.
| Method | Data required | Answers best | Fails when |
|---|---|---|---|
| Decline curve analysis | Extended stable rate history | Short-term rate forecast for a well with unchanged conditions | Operational changes, new drive mechanism, or a short history |
| Material balance | Static pressure, production, PVT data | Volumes in place and drive mechanism identification | Pressure data are sparse or unreliable |
| Reservoir simulation | Geological model, full dataset | Development options and longer-term recovery | Model lacks history-match quality or data support |
Technical limit versus economic limit in field life decisions
The technical limit is when the reservoir can no longer deliver hydrocarbons; the economic limit is when revenue no longer covers operating costs. Field abandonment timing follows the economic limit, and separating the two is a skill worth drilling deliberately.
Distinguish the concepts explicitly in your notes. A field can reach its technical limit — water cut approaching totality, reservoir pressure depleted, no remaining workover targets — years after it has passed its economic limit of marginal cash flow, or the reverse can occur if prices rise. In practice scenarios, the instructive trap is recommending continued production because hydrocarbons technically remain, without testing whether the operating cost per barrel is defensible, or conversely recommending abandonment while a low-cost intervention could extend profitable life.
Apply this with a mini-example. Suppose a marginal field produces 800 bopd at an operating cost that leaves a thin margin; a proposed compression project could add 150 bopd for a capital outlay. The judgement needed is not whether the extra barrels are technically recoverable — they are — but whether the project clears an economic hurdle within remaining field life. Practise writing one-sentence recommendations that state the limit being applied, the threshold used, and the sensitivity (price, cost, and rate assumptions) that would change the decision.
Reasoning about well barriers from paper scenarios
Well integrity rests on two independent barrier envelopes — primary and secondary — each with identified elements. Paper scenarios are the safe way to practise identifying which envelope an anomaly threatens and what observation would confirm or refute the concern.
Study barrier thinking as a two-envelope concept. The primary barrier contains reservoir fluids in the normal flow path; the secondary barrier — cement, casing, wellhead, and the BOP or tree in drilling and intervention contexts — provides containment if the primary barrier fails. Independence is the key property: a single failure should not remove both envelopes. In a paper scenario where sustained casing pressure appears on the annulus, the reasoning task is to identify which barrier is leaking, what the monitoring data show, and what further observation — pressure testing, temperature or noise logging — would discriminate between causes, all analysed on paper rather than performed as unsupervised fieldwork.
Train yourself to separate diagnosis from response. A scenario might report an annulus pressure that bleeds down and builds back: the observation pattern suggests a source, but the safe response is containment and assessment within the operator's integrity management process, not an improvised fix. Rehearse writing answers in three moves: state which barrier element is suspect, state the observation that supports the suspicion, and state the escalation route. This structure keeps your analysis anchored to evidence rather than assumption, and it transfers directly to how integrity anomalies are discussed in real operating organisations.
- Primary and secondary barriers must be independent; a single failure should not defeat both.
- Match each anomaly (annulus pressure, tubing leak, cement channel) to the envelope it threatens.
- Frame responses as observations and escalation, not unsupervised intervention steps.
Writing competence evidence that shows judgement, not task lists
Professional review for chartered registration is built around evidence that you can take responsibility for engineering decisions. Evidence statements should each name a decision you made, the options you weighed, and the outcome or justification — not list activities you attended.
Compare two evidence statements. Weak version: 'I was involved in the drilling of twelve wells and attended daily morning meetings.' Stronger version: 'I recommended skipping a planned coring run when drilling parameters indicated a shifting pressure regime, documented the risk trade-off, and the well was safely circulated to the next section.' The second shows a decision, alternatives considered, and ownership of consequences. Audit your own experience inventory against this standard: every claim should survive the question 'what did you decide, and what would have happened if you had decided differently?'
Structure preparation around extracting decisions from your history. For each major project, write one paragraph covering the technical problem, the uncertainty you faced, the options available, the choice you made, and how you know whether it worked. Professional-commitment evidence — ethics, safety culture, sustainability awareness — deserves the same treatment: cite a moment when you raised a concern or applied a standard, not a general assertion that you value safety. This converts years of work into the currency that competence statements are written in.
- Each evidence statement: decision, options weighed, justification, outcome.
- Replace participation language ('involved in', 'attended') with ownership language ('recommended', 'decided', 'accountable for').
- Back professional-commitment claims with a specific incident, not a general value statement.
Handling a professional ethics scenario under commercial pressure
Ethics scenarios worth practising present a conflict between commercial direction and professional obligation. A defensible response pattern is: verify the facts, escalate through the proper channel, and document — never simply comply, and never leak externally first.
Work a practice scenario. Your manager asks you to report a reserve estimate using an aggressive decline assumption that you believe is unsupported by the production data, and the figure feeds an investor update. The poor decision is silently complying, because it misrepresents technical work under your name; the equally poor decision is an immediate external disclosure, which bypasses internal governance. The better path is to document your technical objection in writing, present the data supporting a range of decline assumptions, and escalate through your company's technical assurance or ethics channel if overruled in a way you believe misleads stakeholders.
Note the reasoning pattern, because it generalises. First, separate fact from inference: is the decline assumption genuinely unsupported, or is it a defensible optimistic case within an accepted range? Second, use the hierarchy of response: raise, document, escalate internally. Third, protect the record: dated written objections are what professional codes and subsequent reviews assess. Practise this pattern on variations — a safety-critical pressure test result under schedule pressure, an environmental monitoring figure, a contractor's certification — so the sequence becomes automatic rather than improvised.
A six-week preparation sequence with a self-check rubric
Build readiness in three passes: concept precision, scenario practice, then evidence writing. Use the rubric below weekly; treat scores as learning milestones to guide review, not as predictions of any assessment outcome.
Weeks one and two: concept precision. Build classification flashcards (reserves, contingent and prospective resources, and the trigger events between them) and one-page comparisons of decline analysis, material balance, and simulation, each with its data requirements and failure modes. Weeks three and four: scenario practice. Work two or three paper scenarios per session — a volumes classification case, a forecast-method choice, an integrity anomaly, an ethics conflict — writing your decision, the evidence, and the alternative rejected. Check against the rubric and rewrite anything that scored below standard.
Weeks five and six: evidence and integration. Draft your competence statements using the decision-options-outcome structure, then cross-read them against your scenario notes so the same judgement vocabulary appears in both. Finish with a self-set mock: one classification case, one forecasting case, one ethics case, written in thirty minutes each. Adapt the sequence to your schedule by compressing weeks one and two if your technical grounding is current, and expanding weeks five and six if the review you are preparing for is primarily evidence-based rather than question-based.
- Scenario answer rubric (score each 0–2, target 5+/6 per case):
- Decision stated explicitly and unambiguously (0–2)
- Evidence from the scenario cited, not assumed facts imported (0–2)
- Alternative considered and reason for rejection given (0–2)
- Readiness checks before you stop: you can classify a volume from its evidence alone; you can name the failure mode of each forecasting method in one sentence; you can separate technical and economic limits in a case; every competence claim you have drafted names a decision you owned.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.