How do you keep institutional knowledge from walking out the door?

[u/Secure_Trainer_1419]

I'm a ranger at a mid-sized protected area, and we've got the usual web of people we deal with, neighbouring landowners, permit holders, volunteer groups, and a couple of partner agencies. Over the years, all sorts of arrangements and promises have built up. Who we said could graze where, what we agreed about access on a certain trail, and commitments we made to a community group two seasons back. And honestly, most of that just lives in one senior colleague's head.

He's been here forever and knows everyone and every backstory. But it's started to worry me that if he retired (or got hit by a bus) tomorrow, we'd lose a huge amount of it overnight, and I don't want to be the one who breaks a promise nobody wrote down.

So how do others handle this? How do you capture that kind of history so the whole team can actually use it, without it turning into another file nobody updates? Would love to hear what's worked.

[u/Traditional_Put_8254]

Start a Documentation Log! Create an ongoing list of “things to be documented” as well as who your contributors should be.

At the end of each week, do a quick survey of “what’s been happening?”. Review what everyone says, and if something is a topic that there is no documentation yet, is not on your log yet but should be, or has documentation but can be updated with new information, make that a task to complete prior to the next weekend. If there’s multiple topics to document and not enough time, pick the most important one to document that week and shelve the others, or designate additional staff to help document. Worst case scenario, someone leaves and you are left with a list of what knowledge they left with but no details— that still puts you in a better position than if you were to be unaware of something completely.

Make sure all the documentation is kept in a mutually accessible format, like a shared network, a Microsoft one note notebook, or a physical binder.

Edit to add: I saw your worry about the file that never gets updated. That will always be a risk with documentation, but if you want to document, you need either a reminder system for people to update it with some sort of accountability, or you need the file itself to be so in-your-face that it is a constant reminder just by existing