ServiceNow instances are separate environments: development, test, and production. Work moves between them in update sets, which capture configuration changes. When work goes missing, the cause is almost always process, not the platform. Someone edited outside the active update set, or the set was moved in the wrong order, or a change was never captured at all.
Avoiding the common losses
- Check that the right update set is current before making any change, every single time.
- Move sets in order through each instance, and preview before committing, so conflicts show up early.
- Keep data changes, such as reference records, separate from configuration, since they travel differently.
- After moving a set, verify the change in the target instance instead of assuming the move worked.
Teams that treat update sets as a checklist, not an afterthought, lose far less work. Write the steps down once, and follow them the same way every time.