What does Raiseaticket Change Management do?
Raiseaticket Change Management provides a structured process for planning, reviewing, approving and implementing operational or IT changes - so that work which could affect a live service is agreed and recorded before it happens rather than explained afterwards.
What is recorded on a change?
- Reason - why the change is being made.
- Impact - what it affects.
- Risk - what could go wrong.
- Implementation plan - how it will be carried out.
- Approvals - who agreed to it.
- Schedule - when it happens.
- Related assets - what equipment is involved.
- Rollback plan - how to undo it if it does not go to plan.
How do changes connect to other work?
Changes can be linked to incidents, service requests and affected configuration items. That traceability is the part that pays off later: when something breaks, the question is almost always "what changed?", and the link between the incident and the change that preceded it is what answers it.
Why teams use a formal change process
Because unplanned change is a common cause of incidents, and because approval that happens in conversation cannot be reviewed afterwards. Recording reason, risk and rollback in advance forces the thinking to happen before the work, and leaves a record that stands up when someone asks who agreed to what.
Is it part of the free plan?
No. Change management is a premium add-on. The free plan covers the helpdesk itself; change management sits alongside asset management as capability for internal IT teams running services rather than answering customer questions.
