How management of change (MOC) works: machine changes, risks, approval
In brief
A change to a machine, a process or a material should not be applied before its impact is seen. OSHA's five questions, HSE's change procedure, the step-by-step path of a machine change and the temporary change trap.
8 November 2026 · 5 min read
Sample company · demo dataChange history
Management of change (MOC) is the routine of assessing and approving a change before it is applied and updating everything it affects. The process safety standard of the US Occupational Safety and Health Administration (OSHA) requires written procedures to address, before a change, its technical basis, its impact on health and safety, the changes needed in operating procedures, the time period and the authorisation; affected employees are informed and trained before start-up. The UK Health and Safety Executive (HSE) also counts a written change procedure, authorised approval and post-change checks among the basic measures for plant modifications. Both sources say the same thing: a change may look small, but its impact cannot be known until it is examined.
Why a separate routine is needed
Most accidents happen after a change: a different raw material, a new sensor, a removed guard, a conveyor run faster. The person making the change sees the impact in their own area; they do not see the impact in maintenance, quality, safety and training. MOC brings those views to the same table before the change is made. Without the routine the change is still made; only nobody is informed, and the instruction, the risk assessment, the FMEA and the training stay as they were.
The path of a machine change
Request: what will change, why, which machine or process, permanent or temporary, planned date. For a temporary change an end date is mandatory.
Classification: the type of change (machine, process, material, software, organisation) and its risk level. The type determines the impact list.
Impact assessment: what does the change affect? Risk assessment, FMEA, work instruction, maintenance standard, training, safety data sheet, environmental aspect, supplier contract, audit plan.
Approval: an approval chain by risk level; a low-risk change is approved by the unit manager, a high-risk one by several areas together.
Implementation and check: the change is made, every affected document and training is updated, and a check is done before start-up.
Closure: the change does not close until every item on the impact list is completed at its source.
Assessing the risks
The weakest point of an impact assessment is items being waved through as “not applicable”. A good routine asks for a reason for every “not applicable” and keeps it; when an incident happens a year later, those reasons are the first thing read. Existing risk assessment and FMEA rows are rescored with the change; if a new hazard arises, a new row is opened. If a machine change touches a guard, speed, power or the control system, machine safety is assessed separately.
In Türkiye this topic now has a legal dimension: under the Machinery Safety Regulation of 16 October 2026, a person who makes a substantial modification to a machine is treated as the manufacturer; the provision applies from 20 January 2027. The company's expert decides which change counts as substantial; this article is not legal advice.
The temporary change trap
The most dangerous change is the one made temporarily and left permanent: a guard removed “for a week”, a speed raised “until the order is done”. The end date of a temporary change matters as much as its start date; when the date passes, either the old condition returns or the change is reassessed as permanent. A temporary change without an end date is an unapproved permanent change.
A fictional example
On a press line the position of a safety light curtain was to be changed to shorten die changeover. The request was opened as low risk; the impact assessment produced a risk assessment row, an FMEA row, a work instruction and operator training. The machine safety screening answered yes to “does it touch the protective system” and the request went to expert review. The expert wrote that what was needed was not a new curtain position but a new safety distance calculation. The change was still made; but with a calculated distance and an updated instruction.
Sample company · demo dataChange history
How it is done in Gemy
A change is opened as a request: title, reason, type, unit, owner, risk level and planned date; an end date for a temporary change. Change types are the company's data; a starter list can be added in one click.
The impact list is generated from the type's template; items can be an FMEA review, risk assessment, document revision, training, device check, autonomous maintenance standard, safety data sheet, environmental aspect, external party review, audit, action or manual task. An item marked “not applicable” requires a reason of at least 10 characters, which is written to the history.
Approval runs by risk level according to the company's approval settings; the impact list is locked while in approval.
Closure gate: the change does not close until mandatory items are completed at their source; for example the document item does not count as done until the document's new revision is in force.
The company can add screening questions to a change type; a single yes makes the request a candidate, and it does not go to approval until the person the company has given expert permission writes the result with a reason. The system does not decide.
The product does not decide which change counts as legally substantial and does not replace legal advice. Management of change is a module the company switches on if it wishes.
In short
Management of change means assessing and approving a change before it is applied and updating everything it affects. The path has six steps: request, classification, impact assessment, approval, implementation and check, closure. Every “not applicable” needs a reason; a change touching machine safety goes to expert review; the end date of a temporary change matters as much as its start. This article is general information, not legal advice.
You may copy and share this article with attribution (Gemy, https://www.gemydigital.com/en/blog/degisiklik-yonetimi-moc-nasil-isler-makinede-degisiklik-riskler-onay).
Every solved problem is a piece of knowledge; in most companies it leaves with the person who solved it. The four places where knowledge is lost, the view of ISO 30401 and ISO 9001, and five habits that make knowledge independent of people.
A supplier audit is a process, not a visit: which supplier, which question, which finding, which evidence. The audit principles of ISO 19011, the structure of the question list, finding classes and how the reply returns to the same record.
Document control ensures the right version of the right document is with the right person. What ISO 9001 asks for, document types and numbering, the approval chain, distribution and reading, withdrawing the old version and the five most common gaps.
9 November 2026 · 6 min
Cookies
Essential cookies are needed for the site to work. Analytics cookies load only if you allow them; declining is as easy as accepting. You can change your choice at any time via the footer link.