Start with the operating question
Define the problem in terms the operating team recognises. What is changing? When does it occur? Which records or observations could help explain it?
Agree the review boundary and the people who need to contribute before collecting more information.
Bring the records and the people together
An initial review can combine process information, maintenance history, quality records and discussions with the team. Record inconsistencies and missing information so they remain visible in the conclusions.
Distinguish observations from explanations
A review should make clear what was observed, what is a possible explanation and what needs to be checked. This helps the team assess the strength of each recommendation.
Finish with a usable action plan
Group proposed actions by priority and assign an owner to the next investigation or decision. Include dependencies, required information and the intended way to assess progress.
A concise, shared action plan is easier to use than a long list of recommendations with no clear starting point.
A general discussion guide, not a site-specific engineering assessment. The right approach depends on the project and its operating context.
