Oil and gas compliance registers: record applicability before reminders

Topics: oil and gas compliance registers; regulatory applicability; source amendments; obligation evidence.

A company uses one compliance spreadsheet for an upstream asset and a petroleum terminal. The rows look comprehensive, dates are colour-coded and every reminder has an owner. What is missing is the basis for applying each row to each asset.

An oil and gas compliance register should begin with applicability. It needs to explain the source, its current operative status, the relevant entity and activity, the qualified interpretation and the evidence required. Reminders become useful after those relationships are established.

Give every row a legal or policy basis

Use separate fields for source type and obligation. A statute, rule, regulatory direction, licence condition, contract requirement, adopted standard, guidance document and internal policy can all matter, but they do not acquire the same status merely by appearing in one register.

For a standard, record how it became applicable: for example, incorporation through an applicable instrument, licence, contract or company adoption, as confirmed by the qualified reviewer. For guidance, identify the decision to use it and its limits. Avoid labelling every official-looking document “law”.

The register should retain the exact title, issuing body, identifier, clause or condition, version, publication date, commencement or effective provisions, amendments considered, source link and retrieval date. A qualified legal or regulatory owner determines applicability, with technical input where needed. Software can organise that decision but cannot supply it by matching keywords.

A real index example: consolidation and amendment differ

At the research check on 15 October 2026, PNGRB's T4S index listed the Petroleum Installations regulations with a consolidation through 23 July 2025, alongside an amendment dated 17 August 2026. That is a reason to retrieve and review the later instrument, not to assume the older consolidated file contains it. The index date alone does not establish commencement. PNGRB T4S index

This is a source-control observation, not an interpretation of the amendment. The reviewer needs the notification, its operative wording and any transitional provisions before deciding what changes in the register.

PESO's website also distinguishes draft notifications from gazette notifications. A proposed amendment belongs in a monitored-change queue until its status and effect have been established; it should not silently replace an operative obligation. PESO circular and notification index

Two assets under one company still need separate decisions

Illustrative example. A fictional company maintains records for an upstream location U-1 and a terminal T-1. The following table demonstrates the register structure. It makes no legal applicability determination for either asset.

Using the same company name does not resolve any of these rows. The applicable entity, activity, location, asset characteristics and licence conditions may differ. Once a reviewer reaches a decision, retain its reasoning, scope and date. “Not applicable” needs a basis too; it should not be a convenient way to clear a reminder.

Unknown applicability is a visible work item. It is not the same as non-compliance, compliance or non-applicability. Report it separately so management can see the unfinished assessment.

Convert a reviewed obligation into an evidence task

After applicability is confirmed, define what action or evidence is required, who owns it, how the due date is calculated and who verifies completion. Preserve the source clause or licence condition beside that task.

A requirement may be event-driven rather than annual. The trigger could depend on an approved change, renewal or another event defined in the operative source. Do not assign a recurring date simply because the calendar tool requires one. If the due-date basis is unresolved, keep the task in review.

Separate completion evidence from verification. Uploading a document shows that a file was submitted. An authorised reviewer must decide whether it addresses the requirement. A rejection should retain the reason and next action rather than restart an indistinguishable reminder cycle.

To see an activated row, consider a fictional internal policy, Records Policy RP-04 revision 2. It requires both U-1 and T-1 to review their named obligation owners after a change of asset manager. Its adoption record expressly covers both sites; this is a company requirement, not a statement of law.

The row retains the trigger, calculation, submission and verification as separate evidence, so a later reviewer can reconstruct why the task arose and how it was completed.

If the same task were only submitted on 9 October, it would still await verification. If applicability had not been reviewed, it would belong in a different queue altogether. These distinctions let managers act on a report without interpreting every green or amber cell themselves.

Review changes without erasing the old basis

When a new source is identified, record its status, affected candidate obligations and review owner. The reviewer determines whether it changes applicability, wording, evidence, deadlines or nothing for the selected asset. Preserve the prior obligation version for historical reporting.

India's Labour Code implementation announcement is another reason to examine the current source set rather than reuse legacy employment rows without review. It does not, by itself, resolve establishment-specific rules or transition questions. PIB implementation announcement

Similarly, the OISD catalogue identifies standards and editions. Full text, incorporation and applicability need separate review. OISD catalogue

A useful change log records the old basis, new basis, reviewer, decision, affected tasks and treatment of existing evidence. If the new interpretation changes an already completed task, retain the original completion and open the required follow-up. Rewriting history makes prior management reports impossible to explain.

Use automation after the interpretation is controlled

A workflow tool can maintain ownership, reminders, evidence links and review history. Integration can notify it of relevant approved asset or contract changes. Automated source monitoring can place a newly found instrument in the review queue, preserving its URL and retrieved version. Activation should follow the recorded applicability decision, so a search result or generated summary cannot silently create a new obligation.

Measure applicable obligations with reviewed current sources, unknown applicability cases, overdue source reviews and evidence tasks awaiting verification. Keep those populations separate. A single “compliance percentage” can conceal both missing requirements and unchecked evidence.

The register also needs access and retention appropriate to licences, assessments and supporting records. Preserve enough history to reconstruct a past report, while limiting access to sensitive attachments. The responsible legal, regulatory and information owners determine those requirements.

A controlled register can support a small, stable obligation set if versions, reviewers and evidence links are protected. A workflow application becomes more useful when several assets share sources, amendments affect many tasks or handoffs are repeatedly missed. Compare the options using one actual change and its historical report. Neither option compensates for an unfinished applicability decision.

Summary and next actions

A useful register lets the owner trace a reminder back to an applicable source, a defined trigger and the evidence needed to close the task. Unknown applicability, submitted evidence and verified completion remain separate, so each reaches the person who can resolve it.

1. Select one asset and inventory its actual entity, activities, licences and approved source set.
2. Have qualified owners review applicability, operative versions and due-date bases.
3. Separate unknown cases and proposed changes from active obligations.
4. Test one amendment through impact review, task updates and historical reporting before scaling reminders.

A register-design assessment can map one asset’s reviewed source set into records, owners and evidence tasks. Start with the qualified applicability decisions and a blank task layout; the assessment organises those decisions rather than supplying a legal opinion.