What happens when your best property manager quits?
Whatever she knew that wasn’t written down leaves with her—which properties take Section 8, what the pet policy actually is at the building with the owner who hates dogs, how the last exception was handled. Opsurant turns that knowledge into a living, cited library everyone can search while she’s still there, so her leaving is an HR event, not an operational one.
The pain
Your operation runs on what your best people happen to remember.
Every PMC has a person like this. Ten, fifteen years in, and they carry an entire operating manual in their head that nobody else has: which properties are Section 8 versus conventional, what the actual pet policy is at the building whose owner hates dogs, how the county wants a three-day notice posted versus the one two towns over, what the last regional decided about that one recurring owner complaint. None of it is written down anywhere, because it never had to be—she was always there to ask.
Until she isn’t. She gives two weeks’ notice, or she’s out sick for a month, or she just goes to lunch at the wrong time, and suddenly the answer to a routine question isn’t routine anymore. Someone has to guess, or wait, or call around. Multiply that by every tenured employee at every property, and what you actually have is an operation running on a set of oral traditions that happen to still be employed.
The failure mode isn’t dramatic—it’s quiet. A new site manager makes a reasonable-sounding call that turns out to be wrong for that property’s program. Two leasing agents give two different answers to the same prospective resident because they learned the policy from two different people. A regional spends the first week after a departure just trying to figure out what the departed person actually knew, because nobody wrote a job description for “the person who remembers everything.”
This isn’t a hiring problem or a loyalty problem. Your people are carrying institutional memory that was never designed to be portable, and every departure is a small, avoidable data loss.
What changes
The knowledge becomes a library, not a memory.
Opsurant’s Knowledge module turns your policies, procedures, and the things your tenured staff know into a searchable library that answers instantly and cites its source. A question about pet fees, notice periods, or an owner’s standing preference gets the same correct answer whether the person asking has been there six years or six days—and the answer already accounts for which property and which program it’s being asked about.
Just as important: it notices what it doesn’t know. When staff ask something the library has no good source for, that gap gets flagged instead of silently guessed at—so it gets a real answer added while the person who knows it is still around, instead of becoming next year’s departure crisis.
How you start
A paid engagement whose deliverable is yours either way.
Building the library isn’t automatic, and Opsurant doesn’t pretend it is. The Knowledge Foundation is a structured, paid consulting engagement: a real process that works through your existing policies, your programs, your property mix, and interviews your longest-tenured staff to capture what they know but never wrote down. It’s onboarding labor, priced as labor—not bundled into a subscription as an afterthought.
The reason this is a safe bet even in the worst case: the deliverable belongs to you. The structured operations library the engagement produces is fully exportable in standard formats, whether or not you continue with Opsurant afterward. Worst case, you walk away owning the cleanest, most complete documentation of your operations your company has ever had—built while the people who know it were still there to say it out loud.
Questions PMCs ask about knowledge loss
What happens when a property manager quits and takes their knowledge with them?
Whatever they knew that wasn’t written down anywhere goes with them—policy exceptions, owner preferences, which properties take which programs, the reasoning behind past decisions. The remaining team is left reconstructing it by asking around and guessing, often for months. Opsurant addresses this by turning what staff already know into a searchable, cited library while they’re still there to answer questions, so the knowledge outlives any one person’s tenure.
How does Opsurant capture institutional knowledge before someone leaves?
Through the Knowledge Foundation engagement: a structured, paid onboarding process that turns your existing policies, procedures, and the things your longest-tenured staff know but never wrote down into a cited, searchable library, organized by property and program. It also surfaces gaps—questions staff ask that no current document answers—so those get documented while the person who knows the answer is still around to give it.
Is the knowledge library something we own, or does it disappear if we stop paying?
You own it. The Knowledge Foundation engagement is a one-time paid deliverable, and the structured library it produces is yours—fully exportable in standard formats whether you continue with Opsurant or not. Worst case, you walk away owning the cleanest documentation of your operations you’ve ever had.
How is this different from a shared drive full of policy documents?
A shared drive holds documents; it doesn’t answer questions. Staff still have to know which folder, which file, and which version is current—and a generic policy document doesn’t say whether it applies to a LIHTC property or a conventional one. Opsurant’s Knowledge library is searchable in plain language, every answer is cited to its source, and answers are property-aware—the same question can correctly return a different answer depending on the property asking.
Kick the tires. Then bring us your portfolio.
We’re onboarding early-access partners now—PMCs who want a real say in what gets built next. Bring your unit count and your worst operational headache.