Standard change tasks created prior to "implement" or "schedule"

[Quinten]

Good morning ServiceNow enthusiasts

Could somebody explain to me the actual reason why the tasks defined within a standard change template are created and assigned PRIOR to the implementation phase? I do understand they are pre-approved changes, but even if it's a standard change, I would expect the tasks to be created only when it reaches the implement phase to avoid executing the change outside of the agreed change window.

If somebody could explain this to me potentially with some sources, I would appreciate that.

Thanks and best regards

Quinten

[Dr Atul G- LNG]

Hi @Quinten 

I’ve worked on Change Management and would be happy to share my thoughts. I completely agree that tasks must be created during the Implementation phase, but let's talk about the Operations or Deployment team specifically.

Let’s say there is a well-defined deployment team with 5 members. If the implementation task is created only during the execution phase, and the team already has several tasks assigned, it becomes difficult to accommodate new tasks at the last minute.

The purpose of creating implementation tasks in advance is to give the deployment team enough time to allocate resources effectively. This ensures that tasks are assigned without conflicts or overlaps with other deployments. Planning ahead avoids last-minute confusion and ensures a smoother deployment process.

It’s similar to going on a vacation—you don’t book your tickets on the day of travel. Booking early allows you to plan your trip more effectively, and the same applies to implementation planning.

[Quinten]

Hello  Atul

That's a great explanation and a good example I understand. But what in ServiceNow prevents the users from executing the change before the agreed change window?

I would have understood if the tasks were getting accessible for completion only once the start date is in the past, but I doubt this is the case. 

[Uncle Rob]

My guess is they don't want Change Tasks to be "just in time". 
By getting them in early (past the approval phase that Standard changes skip), the teams involved are aware of the upcoming work.

We're already at the point where we KNOW this change is going to happen, so lets get it assigned ASAP.

[Quinten]

Fair point, but how can the fulfiller know that he or she is not yet supposed to take action upon that task? If there would have been no scheduling phase I would have understood, but that isn't the case.