New Management-of-Change Coordinator in 60 Days: Turn Approval Into Field Verification

A management-of-change coordinator can inherit a full register, a formal approval route, and a serious control problem. The change may be approved on paper while the people, equipment, procedures, and emergency assumptions around it have already moved. The first sixty days should therefore establish a reliable connection between the approval decision and what workers can actually verify in the field.

The central question is not whether a change form was signed. It is whether the organization can show what changed, who owns the new exposure, which controls were tested, and what evidence permits the operation to return to normal. This role profile gives a new coordinator a practical sequence for building that chain without becoming the owner of every technical decision.

What a new management-of-change coordinator needs to understand before starting

Management of change is a governance activity for altered risk. It applies when a modification can affect equipment, process conditions, materials, software, staffing, procedures, organization, or the assumptions behind a critical control. ISO 45001:2018 places change management within the planning and operational control logic of an occupational health and safety management system, while ISO 31000:2018 frames risk ownership as part of accountable decision-making.

The coordinator does not approve every change and should not become a routing clerk. The role makes the process legible. It clarifies what requires review, which subject-matter experts must participate, when a temporary exception becomes an operating condition, and what evidence closes the loop. OSHA’s Process Safety Management standard, 29 CFR 1910.119, is a useful reference for this discipline because it connects management of change with technical basis, safety impact, procedure updates, training, and authorization before affected work begins.

Andreza Araújo’s Safety Culture: From Theory to Practice offers a practical test for the role. A value becomes credible when it survives an inconvenient decision. In change management, that means delaying startup when a control is not ready, asking for a clearer technical basis when the proposal is vague, and refusing to treat a signature as proof that the field is prepared.

Across 25+ years of executive EHS work, Andreza Araújo has connected safety leadership with operating discipline rather than with isolated campaigns. The coordinator should apply the same logic. The process is credible when it changes how work is authorized, briefed, verified, and reviewed.

Days 1 to 10: define the mandate and decision boundaries

Start by writing a one-page mandate that names the sites, business units, change classes, decision owners, and escalation points within scope. A coordinator who is responsible for “all changes” without authority to stop an unsafe transition will become the visible owner of a system that still belongs to nobody.

Map the current workflow from proposal to closeout. Record where a change is first identified, who classifies it, how the technical basis is documented, where risk assessment occurs, who confirms affected workers were informed, and what evidence is required before the change is closed. Include engineering projects, maintenance substitutions, software changes, staffing changes, and temporary arrangements rather than limiting the map to capital projects.

Use the risk owner’s responsibilities between acceptance and action as a boundary test. The person who coordinates the record may not be the person who accepts residual risk, funds a control, or confirms that operations can restart. Those distinctions should appear in the workflow, not only in a procedure.

By day ten, publish a decision-rights table with four answers for each change class. Who proposes it? Who assesses it? Who authorizes the risk? Who verifies that the new condition is controlled? If one name appears in every column, the process is probably under-designed.

Days 11 to 20: classify changes by altered exposure

Classification should ask what can become different in the work, not only what department submitted the request. A new pump, a revised alarm setpoint, an outsourced maintenance task, and a reduced night-shift crew may arrive through different systems, yet each can alter energy, exposure, competence, supervision, or response time.

Create a short screening route that looks for changes in process parameters, hazardous materials, isolation points, human-machine interaction, staffing, competence, workload, emergency response, and critical-control availability. The form should also ask whether the change is temporary, repeated, or already present in the field. That last question catches changes that bypassed the system before anyone gave them a name.

Do not confuse a low administrative burden with low risk. A small software revision can disable an alarm response, while a minor equipment substitution can create a different isolation method. HSE guidance on managing health and safety provides a useful reminder that arrangements must remain suitable as work changes. The coordinator’s screening logic should expose altered assumptions before a reviewer reaches for a familiar risk score.

At the end of this phase, test ten recent changes from different departments. Compare the classification chosen at intake with the evidence that reviewers later requested. If reviewers repeatedly ask for the same missing information, add that question to the screening route instead of relying on individual memory.

Days 21 to 35: connect the technical basis to the control plan

Every significant change needs a visible technical basis. The record should explain what is being modified, why the change is necessary, which hazards or exposures may move, what assumptions remain valid, and what assumptions must be rechecked. A sentence such as “no additional risk identified” is not a technical basis because it hides the reasoning that another reviewer needs to challenge.

Link each changed exposure to a control and to a verification method. If a new operating temperature is accepted because a relief device remains available, the record should identify how that availability will be confirmed. If a staffing change is accepted because a supervisor will provide additional oversight, the record should define when that oversight occurs and what the supervisor must observe.

The coordinator should make evidence visible before the approval meeting. The risk scenario, control test, and decision record serve different purposes. A scenario explains the exposure, a control test examines whether protection is dependable, and a decision record shows who accepted the remaining uncertainty. Combining them into one vague attachment makes each weaker.

Use a simple control plan with four fields: changed condition, required control, verification source, and accountable owner. If the owner cannot name a source such as a test record, field observation, updated procedure, alarm check, or training confirmation, the control is still an intention.

Days 36 to 45: make affected workers part of verification

Workers who will execute the changed task should see the proposal before the approval is treated as complete. Their contribution is not a ceremonial consultation. They can identify access constraints, sequence conflicts, informal workarounds, recovery problems, and emergency actions that are absent from the design package.

Ask questions that reveal the operating reality. What will be different at the point of work? Which step is most likely to be misunderstood? What would make the new control unavailable during a busy shift? What would a worker do if the approved sequence could not be followed? A useful answer may require a design correction rather than another briefing.

Use the temporary-change review checks when the proposal is time-limited or dependent on a future repair. A temporary state needs an owner, an expiry or review date, a compensating control, and a clear trigger for escalation. Otherwise the exception becomes the normal process while the register continues to describe the old condition.

By day forty-five, run one supervised field verification on a live or recently completed change. Compare the approved sequence with the work as performed, then record every discrepancy without assigning blame to the person who surfaced it. The purpose is to test the change system, not to stage a compliance performance.

Days 46 to 60: establish startup, closeout, and review discipline

A change is not ready because its approval route is complete. Startup readiness should require evidence that affected procedures are current, competence has been addressed, emergency arrangements still work, labels and drawings are accurate, and the controls named in the decision record are available where the work occurs.

Build a closeout review that happens after the new condition has operated long enough to reveal friction. The review should ask whether the technical basis held, whether workers encountered an unplanned exposure, whether a control needed repeated intervention, and whether the change should remain temporary, become permanent, or be reversed. Closure is a decision, not a date entered into a database.

Use a short dashboard for leaders. Show open changes by age and risk, changes awaiting field verification, overdue temporary arrangements, repeated changes involving the same control, and decisions that lack an accountable owner. The leading-indicator interpretations that change a safety decision are more useful than a simple count of forms completed.

Senior leaders should see one additional measure: the proportion of sampled changes for which the approved control was confirmed at the point of work. A high approval rate with weak field evidence means the organization is optimizing paperwork. A lower approval rate with clear escalation may indicate that the process is finally seeing risk early enough to act.

Month 3 onward: turn the process into organizational memory

After the first sixty days, the coordinator should shift from building the route to improving the quality of decisions that pass through it. Review recurring change types, repeated control failures, late involvement of operations, and patterns in temporary extensions. Each pattern points to a design weakness that a procedure revision alone may not solve.

Connect change reviews with incident investigation, maintenance learning, procurement decisions, competence management, and capital planning. When a failed control appears in several changes, the organization may need a design standard, a stronger specification, a different approval threshold, or a leadership decision about acceptable exposure.

The process should also preserve uncertainty. If evidence is incomplete, the record should say what remains unknown, who owns the uncertainty, and when the next review will occur. Visible uncertainty supports better escalation than a confident status label that no one can defend later.

Common mistakes new coordinators make

The first mistake is measuring activity instead of control quality. Completed forms, approval meetings, and training records show movement through a process, but they do not prove that the changed condition is safe to operate.

The second mistake is treating every change as a project. Some changes happen through staffing, scheduling, software, procurement, or work instructions, so a capital-project workflow will miss them. The classification route must follow altered exposure wherever it originates.

The third mistake is accepting unclear ownership because a senior person attended the review. Attendance is not authorization, and authorization is not field verification. The record needs separate names for decision, implementation, and confirmation.

The fourth mistake is allowing a temporary control to survive without a decision date. A temporary arrangement that is extended repeatedly has become a new operating condition and deserves the level of review applied to a permanent change.

Resources to deepen the role

Use ISO 45001:2018 for the management-system structure, ISO 31000:2018 for risk ownership and decision logic, and OSHA 29 CFR 1910.119 for the discipline of technical basis, procedure updates, training, and authorization around process changes. HSE guidance on managing health and safety provides a useful additional lens for keeping arrangements suitable as work evolves.

Andreza Araújo’s Safety Culture: From Theory to Practice helps connect those formal elements to leadership behavior. The book’s central implication for this role is direct: the safety culture is revealed by the decisions leaders make when the approved plan no longer matches the work.

Comparison: approval activity versus field verification

Conclusion

A new management-of-change coordinator creates value by making altered risk visible from proposal through field verification, not by processing more forms. In sixty days, the role should establish decision boundaries, classify changed exposure, connect controls to evidence, involve affected workers, and give leaders a clear view of unresolved conditions.

The strongest change process does not promise that every transition will be frictionless. It makes friction visible early enough for someone with authority to decide. If your organization needs help connecting management of change with operating discipline, explore Andreza Araújo’s safety leadership resources.