How does a BPO or shared-services team keep job aids current across 300+ processes without a full-time docs team?

If you run ops or enablement at real scale a BPO or shared-services group running hundreds of distinct processes across clients job aids tend to break the same way: someone documents a process once, it's great for a month, the client's system changes, and now you've got 300 documents and no realistic way to know which ones are still right.

Here's the approach that's actually helped us:
1/ Instead of writing job aids by hand, someone records the process on screen once and Trupeer.ai turns it into a step-by-step written guide (with screenshots) plus a short video from the same pass.
2/ When a client's system changes, you re-record just that one workflow and regenerate so updating is minutes, not a rewrite, which is what makes staying current realistic at 300+ processes.
3/ Everything sits in a searchable knowledge base with AI search, so agents find the right job aid instead of pinging a lead.
4/ For multi-client, multi-region teams, the same recording can be translated into 65+ languages instead of re-documenting per site.

Honest limit: this fixes the cost of creating and updating job aids, it doesn't automatically tell you which of your 300 have gone stale. That governance/tracking piece still needs an owner, and it's the part I'm most curious how others handle.

So, do you centralize authoring with a small team or push it to process owners? And how do you track which job aids are actually current? What's working at your scale?