Management of change records: connect the decision to the affected documents

Topics: oil and gas management of change; MOC document control; affected records; change approval evidence.

A change has been approved and the work record is marked complete. The drawing reference has been updated, but the linked maintenance document still points to the earlier equipment configuration. The change register shows closure while the people using the documents see two different versions of the asset.

Management of change records should connect the authorised decision to its required evidence and follow-up actions. Approval of a proposal, completion of an action and authorised closure are different events. The record system should preserve the relationship between them.

Let the approved MOC process define the decisions

The qualified MOC authority determines technical and safety review, applicable approval stages and closure requirements. The software's role is to represent those decisions faithfully, including who made them, under what authority and against which scope revision.

OISD's catalogue lists OISD-STD-178, Management of Change, with an August 2023 edition. That catalogue entry identifies source material; this article does not interpret its clauses or provide an engineering change procedure. OISD standards catalogue

Start with a change identifier, proposed scope, affected asset references, initiating reason, responsible owner and review status. Then record the affected-document assessment and required actions. A field marked “documents updated” is too broad to explain which documents were considered and which changes were accepted.

Record the initial screening decision too. If the process distinguishes replacement in kind from a change requiring MOC, retain who made that classification and on what basis. Similar equipment descriptions are not enough for software to decide the classification. An unclear proposal belongs with the designated authority before the workflow assigns it a route.

Follow the dependency that prevents premature closure

Illustrative example. Change C-117 concerns an approved equipment change. The technical design and execution details are outside this example. The record set identifies three documentation actions and one verification action.

The drawing and asset-master actions are complete, but closure still lacks the approved maintenance document. The system should show the missing document review and its owner. It should not convert the draft's existence into an approved revision or permit administrative closure because a percentage threshold has been reached.

Each action also needs the milestone by which it must be satisfied under the site's process. A prerequisite for implementation and an action required for final administrative closure serve different purposes. Have the MOC authority define those dependencies explicitly; the fictional closure example above does not establish whether implementation is permitted.

Now suppose the scope changes after the drawing is approved. The MOC authority determines which earlier decisions and actions need reconsideration. The system retains the previous scope and approval, links the new revision and marks affected evidence for review. An approval attached only to the change number, without a scope version, would be difficult to interpret.

Model documents as dependencies, not attachments

For each affected document, record its identifier, current approved revision, proposed revision, relationship to the change, document owner and required disposition. Some documents may be reviewed and found unaffected; retain that decision where the approved process requires it.

A repository link that always opens “latest” is useful for everyday access but insufficient for historical evidence. The change record needs the exact revision that supported a decision. Keep a separate link to the current approved revision if users need both views.

This is a provenance problem: the record should explain how one decision or document version led to another and who was responsible. W3C's PROV overview offers general concepts for those relationships; the MOC process supplies their business meaning. W3C provenance overview

Avoid copying the same document into several change records. Controlled references reduce the chance that one copy is updated while another remains in circulation. Where a snapshot is retained for evidence, label its revision and status explicitly.

Check for concurrent changes to the same document. If C-117 and C-118 both start from drawing revision 6, the second review must account for the revision accepted through the first change. Otherwise one approved update can overwrite another. Show the shared dependency to the document owner and retain the decision on how both changes are incorporated.

Temporary changes need a review outcome

A temporary-change record should expose the approved duration or review trigger and the authority responsible for the next decision, as defined by the site's process. A reminder is useful only if it leads to a documented outcome.

The software should not automatically extend the change when the owner misses the date. It should identify the overdue review and route it through the approved escalation process. Any authorised extension, restoration or other disposition needs its own decision and supporting evidence.

Similarly, a reopened action should remain linked to the original closure history. Deleting the previous closure or silently changing its date prevents the team from understanding what was known at each stage. The appropriate operational response remains with the qualified authorities, not the workflow engine.

Choose integration points that preserve authority

A dedicated MOC module may manage the decision workflow, while the document repository owns revisions and the EAM owns asset records. Define which system owns each state. A document update can notify the MOC register that evidence is available; it should not automatically represent MOC closure unless that action is explicitly supported by the approved process and authority.

If a document feed is unavailable, show the last confirmed revision and the unresolved verification. Do not assume no change occurred. Test links to superseded documents, changed access permissions and an action reopened after apparent completion.

A relationship table may be enough to connect the change, documents and actions. If search software suggests additional affected documents, record those suggestions separately until the document owner reviews them. The useful result is an explainable list of assessed dependencies, not a longer list of unexamined attachments.

Review the evidence trail, not just overdue totals

Useful measures include changes with complete required document relationships, actions awaiting approval, stale references and overdue temporary-change reviews. Select a closed change and reconstruct the authorisation, affected records and closure evidence. A low overdue count does not compensate for missing closure support.

Record the scope and cutoff of the report. Separate open proposals from authorised changes and from changes awaiting closure verification. Those populations have different decisions pending and should not be collapsed into one completion rate.

Summary and next actions

A reviewer should be able to follow a closed change from its scope and authorisation to the exact document revisions and completed actions. Open dependencies, concurrent changes and temporary-change reviews need named decisions before the record can accurately show their outcome.

1. Select one recent change and map its exact scope revision to all required document and record actions.
2. Identify the owner and acceptance evidence for each action.
3. Test a revised scope, an overdue temporary-change review and a reopened action.
4. Use the knowledge-assistant pilot only after document versions and permissions can be trusted.

For a change-record assessment, use one closed change and its document-version list to test the evidence trail. The review can define the missing system relationships and notifications; the qualified MOC authority retains the process and acceptance decisions.