The newly created Change Request was automatically set to "Implement" state instead of access.

[Nishant2007]

The issue is currently observed for only 1 to 2 users. When these users select certain values in the Location field (e.g., Burlington), the Change Request automatically transitions from New to Implement. In some scenarios, the transition occurs immediately after the location is selected, while in others it occurs after the record is saved. This suggests that the behavior may be driven by a Change Model, Flow Designer Flow, Workflow, Any other possibility?

[brianlan25]

Unless someone overrode the out of the box script includes I would think the only way to do this would be thought change model. There is nothing out of the box the affects change based on location. There is also no configuration who change going directly to implement. Even for Standard changes that always goes to scheduled out of the box.

[Tanushree Maiti]

Hi @Nishant2007 

Check all BR  on change request table , If there is a customization in place.

Also check specific customized Flow/Workflow(if you are using legacy workflow) for your specific change type.