Replacement in kind exists for a reason. Sites need a way to replace worn or failed components without treating every normal maintenance activity as a formal change project.

The problem starts when replacement in kind becomes a shortcut label instead of a real decision.

What replacement in kind actually means

Replacement in kind means the organization is restoring an approved state, not creating a new one. The replacement should preserve the intended design, function, performance boundary, and operating assumptions.

If the like-for-like logic is real, full Management of Change may be unnecessary. The work still needs control, but not the same assessment burden as a true change.

When it stops being replacement in kind

The line is crossed when the replacement alters something that matters operationally. A new material behaves differently. A modified setting changes process behavior. A substitute component affects inspection, cleaning, maintenance, isolation, competence, or validation. A workaround becomes permanent. A temporary setup stays in place too long.

At that point the question is no longer whether the team replaced something. The question is whether the site changed its operating reality.

The practical test

The practical test is simple: does the replacement preserve the same approved context, or does it create new implications the organization now needs to understand and accept?

If new documents are needed, new risks appear, new checks are required, or new operational assumptions are introduced, the case is probably Management of Change, and likely needs change impact assessment.

The Vinkey view

Vinkey's view is that replacement in kind and Management of Change should not compete. They should be separated clearly enough that teams can move quickly when true like-for-like replacement applies and escalate cleanly when the operating context has changed.

That separation reduces both bureaucracy and hidden risk.