I've certainly dealt with that in the past, but the reports, scripts, and webhooks in Netbox helped us automate our documentation QA. Whenever data is altered,

I've certainly dealt with that in the past, but the reports, scripts, and webhooks in Netbox helped us automate our documentation QA. Whenever data is altered, QA gets an immediate ticket to validate it and the reports give them the ability to quickly check it against our real-time inventory system. To catch the case where data isn't entered, all project tasks and work tickets need to be associated with one or more Netbox updates, and QA confirms that as well. There's no solution to this problem that's purely technical. In my experience you need to make it as easy as possible with your tooling, but you still have to have processes in place to catch mistakes and omissions.