Every policy, one cited answer away.
Knowledge turns your procedures, program rules, and house policies into a living library that answers as staff type—and every answer names the document and section it came from. The same question answers differently at a LIHTC property than a conventional one, because it should, and if nobody’s written the answer down yet, Knowledge says so instead of guessing.
Your policies, actually findable.
Most PMCs already have the policies written down—somewhere. A pet policy PDF from three reorganizations ago. A compliance binder in a regional’s office. A procedure that only exists as what the last person who did the job remembered. None of that is findable at the moment someone actually needs it, which is why the same question gets asked five different ways to five different people and answered five slightly different ways.
Knowledge takes what you already have—policy documents, program guides, house rules, procedures—and turns it into one searchable library that everyone on staff can reach from the hub. It doesn’t replace your source documents; it makes them usable at the desk, in the moment, instead of buried in a folder nobody opens until there’s a problem.
Matches surface before you finish asking.
Staff don’t need to know the exact policy title or which document it lives in. They start typing the question the way they’d ask a coworker, and the matching sections surface as they type—the same instant, forgiving search the rest of the internet trained everyone to expect, pointed at your own procedures instead of the open web.
Click a match and Knowledge composes a direct answer from it, not a link to go read the whole document. The composed answer still shows exactly where it came from—the policy title and the section—so nobody has to take the assistant’s word for it. Anyone can check the source in one click.
The same question, the right answer for that property.
A pet policy question at a conventional property and the same question at a property carrying a housing-authority contract don’t have the same answer—and Knowledge knows which property is asking. It cross-references the property’s program and jurisdiction automatically, so the answer is specific instead of generic and technically wrong for that building.
Cedar Court (CC-1104) participates in Section 8—copy the housing authority on the deduction notice within the same window. HAP Program Guide §5.1
An unanswered question becomes a content request, not a dead end.
Every library has gaps, and pretending otherwise is worse than having them. When Knowledge can’t find a confident answer, it says so honestly—no fabricated policy, no guess dressed up as a citation—and logs the question as a gap. Whoever owns your policy library sees a running list of what staff are actually asking that nobody’s written down yet, which turns real usage into the roadmap for what to document next.
The Knowledge Foundation—a paid engagement, a deliverable you keep.
Turning years of scattered policy documents, program guides, and tribal knowledge into a structured library isn’t a settings toggle—it’s real work, and we don’t pretend otherwise or hand it to you as a free add-on. The Knowledge Foundation is a one-time paid consulting engagement where we work with your team to gather, structure, and cite what your company actually knows.
The deliverable is yours either way. If Opsurant isn’t the right fit after the engagement, you walk away owning the cleanest, most structured documentation of your operations you’ve ever had—a full export in standard formats, not locked behind a login. The Foundation is the guarantee’s teeth: worst case, you still got something worth the cost.
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.