IT Change Management Workflow

Do I need to install any software or hire a developer to get this running?

No installation or development work is needed. The IT Change Management Workflow runs entirely inside assess.one, and you can publish it and have your team running live change requests within minutes of signing up. All routing logic, notifications, and approval steps are configured directly in the platform — no third-party dev projects required.

Can my team customise the approval steps and risk routing to match how we actually work?

Yes, every step in the workflow is fully customisable inside assess.one. You can adjust risk thresholds, change who sits on the technical review or CAB approval stage, add or remove steps, and update notification logic to match your internal policies — all without writing a single line of code.

How does the AI risk prioritisation step work?

When a change request is submitted, the AI Risk Prioritisation step analyses the details provided and assigns a risk priority level before any human reviewer sees it. The workflow then routes the request automatically — high-risk changes go through an additional review track, while standard changes follow the normal path — so your team's attention is always focused where it matters most.

What happens if a technical reviewer asks for revisions?

If the technical review flags issues, the workflow automatically notifies the requester that a revision is required and moves the record into a Revision Submitted status once they resubmit. The revised request then goes back through a dedicated re-review step, so nothing slips through and the audit trail captures every iteration of the change.

Is this workflow suitable for teams that need to meet ITIL or compliance requirements?

Yes, the workflow is structured around ITIL-aligned change management principles, including formal intake, risk assessment, technical review, CAB approval, and post-change review stages. Every action is timestamped and recorded inside assess.one, giving you the documented evidence trail that auditors and compliance teams typically require.

Who needs access to the workflow, and can I control what each person can see or do?

You control roles and permissions directly inside assess.one. Requesters, technical reviewers, CAB members, and implementers can each be given access only to the steps and information relevant to their role. This means a requester can track their change's status without seeing internal review notes, and CAB members only see requests that have passed technical review.

Can my team receive notifications in Slack or by email when a step needs their attention?

Yes, email and Slack notifications are configured inside assess.one — no external integration setup or third-party tools needed. You can set up automated alerts at any step, such as notifying the CAB when a change is ready for approval or pinging an implementer when a change is scheduled and approved.

What happens at the CAB approval stage if the board rejects a change?

The Route on CAB Approval step handles both outcomes automatically. If the CAB approves, the request moves to the scheduling and implementation track and the requester is notified. If the change is rejected, the workflow routes it accordingly — you can configure this to notify the requester with feedback, archive the record, or send it back for revision, depending on your process.

How long does it take to implement this workflow for our organisation?

Publishing the template takes minutes, and your team can start submitting and processing live change requests immediately after. There is no weeks-long implementation project — you customise the steps, roles, and notifications inside assess.one at your own pace, and changes you make to the workflow take effect straight away.

Is there a post-implementation review built into the workflow?

Yes, post-change review is included as a structured step after implementation and validation, ensuring your team formally closes out every change rather than moving on the moment the work is done. This step captures lessons learned and confirms the change achieved its intended outcome, which feeds directly into your continuous improvement and compliance records.