Design Reviews and Change Control

A mine design review is a structured engineering judgement about whether a proposal is sufficiently supported for a particular decision. Change control preserves that judgement as assumptions, equipment, layouts and operating conditions evolve. Together they connect the reasons for a design with the authority to alter it and the evidence that the resulting configuration performs its intended function. Their value lies in exposing technical consequences before commitments become difficult to reverse.

Define the decision and the design maturity

A review needs a stated purpose, a defined package and evidence appropriate to the decision. Crossrail's Systemwide Design Gate Review Procedure, Revision 6.0, provides an infrastructure precedent: a gate assesses evidence of completed checks and reviews against specified criteria. Applied to a mine, this means defining the next authorised commitment; a percentage-complete label cannot establish engineering maturity.^[1]

The following examples illustrate how the decision changes the required evidence; they are not universal project gates.

A mature package can contain uncertainty. Identify the design basis, its revision and the assumptions that would invalidate the decision. A finished drawing does not establish that the underlying uncertainty has been resolved.

Combine discipline checks with independent challenge

Review competence and independence serve different purposes. A specialist understands a calculation or failure mechanism; a sufficiently detached reviewer can question its premise. The historical NSW MDG 1014, issued in July 1997 and now retained for historical reference, identifies persistent weaknesses in mining risk assessments: omitted credible events, optimistic safeguards, unsupported assumptions, predetermined conclusions and common causes that defeat several apparent barriers. It also recognises that an external consultant can lose detachment through close identification with the project. These are useful review questions, without treating that document as current legislation.^[2]

A review therefore needs people who can challenge both the proposed technical solution and the evidence used to justify it. Before accepting several protective measures as independent, ask whether the same power loss, ground movement or maintenance omission could compromise them together. A report can be internally consistent while its assumptions are poorly matched to the mine. Record the relevant expertise and the scope of each review so that a signature cannot be mistaken for scrutiny of every discipline.^[2]

For a shaft station, for example, structural and geotechnical checks do not answer ventilation, emergency access, materials handling and maintenance questions. Operators and maintainers can reveal access or recovery problems that are absent from normal-duty calculations. The design authority must integrate these contributions; inviting many disciplines to a meeting alone does not demonstrate that their interfaces agree.

Scope verification and validation precisely

ISO 9000:2026 distinguishes verification of specified requirements from validation for a particular intended use or application. Both depend on objective evidence, and validation may use actual or simulated conditions. For mine engineering, define the object and scope of the claim. Verification of a ventilation design can check its calculation and conformity with specified airflow requirements; validation addresses its suitability for the intended operating application. State the conditions, limitations and unresolved assumptions whenever describing a design as verified or validated.^[3]

The 2019 Western Australian ground-control guideline describes verification by comparing design inputs with outputs, followed by practical validation of the geotechnical structure's performance over the relevant mine life and, where applicable, after closure. Monitoring, inspections, audits and lessons from successful and unsuccessful performance contribute to that review. Its examples cover the geotechnical model, mine planning and design, and operational matters such as excavation geometry and ground-support performance.^[4]

This means the review programme can extend beyond initial design release. A slope design supported by an accepted geological model remains conditional on the ground and groundwater assumptions. New mapping or an unexpected response can require reconsideration of that basis. Review conclusions should identify the observations that would test the assumptions and the engineering responsibility for interpreting them; a future monitoring programme needs a defined purpose before it can provide useful validation evidence.^[4]

Turn review findings into bounded decisions

A review outcome distinguishes acceptance, conditional acceptance and further work. Crossrail's gate procedure records conditions, proposed closure timescales and closure evidence. For a mine, state what may proceed, which dependency remains unresolved and who can accept the evidence. Identify the disputed assumption or interface and the decision that depends on its resolution.^[1]

Conditions should be connected to the work they constrain. If foundation loading is unresolved, permission to order unrelated equipment does not imply permission to construct that foundation. A response stating that a comment was considered is different from an engineering disposition explaining how the concern was resolved. Preserve the original concern alongside the accepted response so later changes can be tested against the actual reasoning.^[1]

Control changes against an identifiable baseline

ISO 9000:2026 defines a configuration baseline as approved configuration information representing an item at a particular time and providing a reference through its life cycle. In a mine project, identify the relevant package and revisions before evaluating a proposed change.^[3]

DOE-STD-1073-2016, for U.S. Department of Energy facilities and activities, describes change control as maintaining agreement among requirements, physical configuration and documentation. It covers assessment of consequences, the decision, implementation, assessment of results and updating information. Changes may originate in procurement, maintenance, operations or software as well as design. Mining projects can adapt this logic; the standard's institutional requirements apply within its own scope.^[5]

Three different states therefore need evidence. Approval establishes permission for a defined change. Implementation establishes what was actually altered, including any partial completion. Assessment establishes whether the altered result meets the agreed criteria. A signed change request alone cannot demonstrate all three. Define the necessary post-change checks while evaluating the proposal, when the intended outcome and its assumptions are still explicit.^[5]

An interface review traces the consequences beyond the originating discipline. Crossrail's interface procedure, Revision 5.0 of 2017, identifies agreed boundaries, requirements, constraints and responsibilities; it tracks unresolved interface actions and requires changes after Gate III to be checked against the original interface configuration. For a mine, the useful application is to identify the parties on both sides of each affected boundary and obtain their engineering agreement to the revised conditions. A change in one package can invalidate information already accepted by another.^[6]

Consider an illustrative increase in underground pumping duty. Connect the changed flow and head to the pump, pipe pressure envelope, motor supply, control logic, discharge capacity and maintenance access. Consider the assumed availability of dewatering during a power interruption. These questions establish the change's boundary; pump procurement cost is a poor proxy for the alteration's engineering extent.

The same logic applies to a small drawing revision or a substitute component. NSW's Mechanical Engineering Control Plan code, Version 4.0 of May 2025, states that alteration outside original design parameters is a design change and should be directed by a person with appropriate mechanical engineering competence. It also illustrates how apparently minor alterations can have significant safety consequences and encourages consultation with the original designer, manufacturer or supplier where possible. The code addresses NSW mines; its examples show why classification by drawing count or purchase value alone can miss the consequence of a change.^[7]

Manage temporary configurations and preserve the evidence

A temporary modification creates a real configuration for its period of use. The Mining Association of Canada's 2011 guide to audit and assessment of tailings facility management examines authority for extending temporary changes and making emergency changes. It also addresses time limits and follow-up of risk-mitigation actions. These are management principles from tailings guidance that can inform the design of a project's change-control process.^[8]

At project level, a useful temporary-change record states the purpose, affected boundary, authorised duration or termination condition, operating constraints, and the evidence needed for removal or permanent adoption. Several individually small temporary changes should also be considered together. For an emergency change, define an expedited authority and review route within existing emergency arrangements. Preserve the chronology of the decision, the condition created and the engineering disposition. These are design-management principles, not instructions for responding to an incident.^[8]

Retain a traceable chain from baseline through proposal, review, authorised revisions, implementation evidence and closure. A later engineer should be able to distinguish an intentional choice from a discrepancy and identify accepted assumptions. The practical test is whether someone can reconstruct why the configuration is considered appropriate and what evidence would require that judgement to change.^[5]