What you do with Management of Change
Two approval gates
Gate 1 decides whether you may work out a change, gate 2 whether it may actually be carried out. No release means no implementation; the system enforces this.
Configurable approval route
Each gate runs step by step through the route you set up in Workflows, with approve or reject at every step. Who decided and when is shown in the approval timeline.
Actions before and after rollout
For each action you record the owner, deadline and timing. Actions before implementation must be completed before release; actions after implementation are follow-up.
Risks per change
The risks tab shows each risk on one line with its level and a warning if a measure is missing. Expand a line for scores, measure and residual risk.
TRA as a condition
If you use the TRA module and the change involves high-risk work, you mark a TRA as required before implementation and create a pre-filled TRA from the change. No approved TRA means no release.
Processes, objects and RACI
Link the processes and objects affected by the change. Each process shows the accountable person from the RACI matrix.
How it works
- 1
Submit
Create a new change and record its type (permanent or temporary), owner, reason, scope, impact areas and planned implementation date. You already draw up the action plan in the draft.
- 2
Gate 1: elaboration
The change goes through the approval route for elaboration. Once approved, the planned actions become real actions for their owners.
- 3
Work it out
During elaboration you update documents, instructions, communication, the risk assessment or the aspects register, for example. At the top you always see what still needs to be done before the next step.
- 4
Gate 2: release
Once the actions before implementation are complete, you request release. After approval you carry out the change and mark it as implemented.
- 5
Evaluate
In the evaluation you establish whether the change has landed well and close the record.
In the employee app
Until gate 1 is approved, planned actions do not reach their owners anywhere, including the employee app. Once approved, they become real actions and the owners see them.
Where it helps you
BrydgeOne contains no text of the standards. Here you see which topics from standards and legislation this module helps you with.
Works together with
Every module works on its own. Switch on more and they fill each other in automatically.
Read more about Management of Change
Terms related to Management of Change
Questions about Management of Change
When does a change need MoC?
Rule of thumb: any change that can affect risks, permits, documents or competences. Small operational adjustments can go through a regular action.
How does a temporary change work?
You record the end date, but the system does not monitor it. So add an action with a deadline straight away to reverse the change or make it permanent through a new review.
Can a change be rejected?
Yes. When rejecting you can give a reason; the requester adjusts the change and resubmits it.
Can we define the approval route ourselves?
Yes. Both gates run through an approval route you set up in Workflows, with steps assigned to roles. Every step records who approved or rejected it and when.
Start with just Management of Change and expand when you want
You do not have to set up everything at once. Switch this module on, add other modules later and keep using the same data and the same app. BrydgeOne fits every organisation, from a small company to enterprise, and you only pay for what you switch on, from € 49 per month.
See Management of Change in your own situation
You only pay for the modules you switch on, from € 49 per month. In a demo we show how it works with your own processes.