Modify access in Complete status of Change
Wondering why you would want to do this? There are serious implications involved in this type of activity. In the event there are events that push xml data downstream this could easily lead to a data imbalance that could be catastrophic. What I am trying to say unless that business has a really good reason this is never recommended.
You may want to create a workflow that allows for this on a limited ability where you have more than one release state. I am hoping we can say here that this would only happen once per change…..
If this is true you could do something like this
PENDING > SUBMIT > REVIEW > RELEASE1 > SCOPE CHANGE > RELEASE2
This could help you out but I would limit the ability to move to SCOPE CHANGE and RELEASE2 so this does not become an abusive process. Many times best practices makes processes difficult so that we can become better at our jobs as we hope that a) creators did due diligence to get everything right and b) reviewers did their job correctly.
Best of luck