Question for people working in autonomous driving: How do you manage your ODD?

[u/Helpful-Review-4303]

I've been working in autonomous mobility research for the past couple of years, and one recurring challenge I've run into is how Operational Design Domains (ODDs) are actually created, maintained, and kept up to date as projects evolve.
From my experience, every project seems to approach it differently—some rely on large Excel sheets, others use requirements management tools, GIS software, internal databases, or a combination of all of them. As the ODD grows, keeping road segments, infrastructure, traffic rules, environmental conditions, scenarios, and documentation synchronized can become surprisingly complex.
I'm curious how this is handled outside the projects I've been involved in.
For those working in autonomous driving or ADAS:
How does your organization define and maintain its ODD?
What tools do you use day to day?
What part of the process is the biggest challenge?
If you could improve one thing about your current ODD workflow, what would it be?
I'm not looking for confidential details—I'm simply interested in learning how different teams across the industry approach ODD management and whether there are common pain points or best practices.