How are you managing/validating the Ownership information of CIs?

[Suggy]

Today we are using OWNED BY, MANAGED BY fields for Server and other CIs. 

But the problem we are seeing is, how to maintain it as users would leave the org, users might change the role, change the department etc and those fields would be outdated.

So looking for a process to 'Validate that data regularly' and 'How to update' when there is a change in the value.

[Brian Bouchard]

I completely agree, Mark. I should have specified our flow is largely centered around references to the user table

There is a MANAGED BY GROUP field, I believe, OOB for CMDB tables, but I don't believe there is an OWNED BY GROUP.  Probably because "Owned By" indicates some level of accountability, which ultimately should be done at the individual level.  In our case, we specifically created an OWNER GROUP field for the reasons Mark mentioned and made the business decision the ultimate owner is the manager of that group.   If that manager separated, that's when our flow would kick in to automatically update the field and tell the new group manager how to reassign if they weren't the right person.

I also like the point on different roles. It's not always an easy thing to determine systematically, but you can definitely look at things like department, title, or manager changes to try to deal with some of the low hanging fruit there, and/or you can periodically certify group managers similarly to how you would do CMDB data.