Whenever a sandbox is created or refreshed, there may be additional steps to perform.
This is because the information from the source environment (either Production or another sandbox) is copied to the destination environment (the new or refreshed sandbox).
Some information should remain the same in the destination as in the source. This can be references to certain internal Ids. Or settings to a commonly shared external system (imagine the source and destination need to point to the same 3rd party emailing system).
However, sometimes there is some information that needs to change between environments. The most common example is when the settings for an external system need to be changed.
Imagine a System Integration Testing (SIT) sandbox and production environment. Most likely, you’ll want the SIT to connect to a testing instance for the 3rd party system. And production to connect to a production instance.
A good starting point for building this list is to review the project migration notes. Then store the list in a centralized location, and make sure your client knows where to find it.
The takeaway
Keeping a checklist of which settings within a sandbox need to change after a refresh is an important step in sandbox management.