is it recommended to create a CTASK Automatically for Reviewing CHG when the CHG is in Review state

[jesseisaac]

The following are the states in Change Management in ServiceNow.
New, Assess, Authorize, Scheduled, Implement, Review, Closed

Is it recommended to create an automated CTASK under the Change Ticket for validating the change that is implemented? Already the lifecycle has "Review" state for the change to be reviewed and validated.

[Dr Atul G- LNG]

No, I’m not in favor of this change. The reason is that if you create a task in the Review state, you have to manually close it every time. The Review task should only be used when a change fails or is unsuccessful, so that you can perform the PIR and take corrective action.
Keeping tasks in Review for every type of change would create unnecessary overhead, so I would avoid that.

[Ankur Bawiskar]

@jesseisaac 

No, it's not recommended.

-> Review state is manual by design for post-implementation validation, stakeholder sign-off, and lessons learned. -> If you have automated CTASKs this might duplicate this purpose and reduce quality control.

-> Use tasks in Implement state only.

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Tanushree Maiti]

Completed changes may be reviewed in CAB meetings. The examination of a completed change is called a post-implementation review (PIR). The purpose of a post-implementation review is to study recently completed changes and apply the experience gained to subsequent changes. Post-implementation reviews allow change management to learn from the past and continually improve the change management process.

This Automated PIR task would be a customization.  

Please refer this links, see if it helps you:

https://community.servicenow.com/community?id=community_question&sys_id=516611bf1b075c50d2ccea89bd4b...

ITIL Change Management - A Comprehensive Guide - ServiceNow Community

[Dr Atul G- LNG]

PIR is not a customization — it’s a configuration and works out of the box. When a change is marked as Emergency, the task is created automatically.