[cntainer]

I've been doing something similar when coding.

On one long-term project we even had special comments with an expiry date attached. Every time the build was running a script would scan all comments and print to output those comments that were expired to make sure someone revists them. And you could either remove, keep and extend expiry or modify that code, depending on context.

I guess it never crossed my mind I could do the same when creating company policies and processes.

[jdsleppy]

I've even written a unit test that fails after a certain date with a descriptive message for this purpose. It's maybe more familiar to developers and already has tooling around it.