Customizations and relationships
Map the tables, applications, scripts, flows, integrations, and dependencies that shape how the instance actually works.
// INSTANCE DISCOVERYSERVICENOW
Know the instance
before delivery starts.
ServiceNow instance discovery creates a shared picture of what is customized, connected, owned, stale, or risky. It gives a new delivery team, platform lead, or cleanup effort a reviewable starting point instead of months of rediscovery.
01Map
customizations + dependencies
02Review
risk + cleanup candidates
03Handoff
context the team keeps
INSTANCE DISCOVERY MAP REVIEW READY
// WHAT DISCOVERY COVERS01
Technical map.
Operating context.
Discovery is useful when it explains both the configuration and the delivery reality around it.
Ownership and operating context
Identify the teams, owners, conventions, and undocumented decisions that delivery work depends on.
Risk and cleanup candidates
Surface stale configuration, duplication, broken references, and review candidates without automatically deciding what should change.
A usable handoff
Turn discovery into an orientation brief and review queue the platform team can validate, prioritize, and reuse.
// THE OUTPUT02
From unknowns
to a review queue.
The output is not an automatic cleanup. It is a grounded orientation brief, a map of important relationships, and a bounded queue of findings for the platform team to review.
See the workflow evidence$ oz discover --instance inheritedcontext: mapped
customizationsORGANIZED
risk candidatesBOUNDED
platform teamDECIDES
// START WITH THE INSTANCE YOU HAVE03
See what is there.
Then choose what matters.
The free AI assessment identifies whether instance discovery, cleanup, orientation, or a deeper AI-readiness review would create the strongest starting point.
Take the free assessment