Every agency has a system. The question is whether that system is software or the three people who know where everything lives and what the workarounds are.
Here are five signs that the answer is the second one.
1. Your intake process lives in someone's inbox.
Applications come in by email, fax, or a web form that dumps a PDF into a shared drive. Someone reads them, logs them somewhere, and moves them to the right queue. That person is your case management system. When they're out sick, intake slows down. When they leave, it stops.
Real case management routes work automatically. It does not wait for a person to notice something has arrived.
2. You can't answer basic program questions without pulling a report.
How many open cases do you have right now? How many applications came in this week? How many are past their review deadline? If the answer to any of those requires opening a spreadsheet, running a query, or asking someone who maintains a separate tracker, the program does not have operational visibility. It has documentation after the fact.
3. Your eligibility rules exist in a document, not in the system.
The policy says households over 80% AMI don't qualify. The form doesn't check that. Staff checks it manually against the document per application. The document gets updated when policy changes. The staff training gets updated when someone thinks to do it. The form is never updated, or only when there's budget for it.
If eligibility is enforced by people reading a PDF, it will be applied inconsistently. That inconsistency shows up in appeals, audits, and the occasional call from a legislator's office.
4. Reporting season is a fire drill.
The funder requires a quarterly report, and the federal dashboard needs updated numbers. At the same time, the board wants a full summary. Each report is in a different format and pulls data from a different place. Someone spends three days trying to match up numbers that do not quite line up across systems.
Agencies that have real case management pull reports in minutes. Agencies that run on spreadsheets and email spend weeks on them every quarter and every year.
5. Institutional knowledge is your business continuity plan.
You know the staff member who knows everything, where the exceptions are documented (or aren't). Which funders require which forms? Which cases have a complicated history that requires careful handling. That person is not a feature. That person is a single point of failure.
When they leave, and at some point they will, the program does not lose an employee. It loses the system.
The pattern these five share
Each one is a sign that the program is being held together by people rather than tooling. That works until it doesn't. Staff turns over. Auditors ask questions. Programs scale or merge. A policy change in 72 hours, and 400 open cases need to be re-evaluated.
Agencies that have been through one of those moments tend to recognize these signs quickly. Agencies that haven't tend to find out the hard way.
The fix is not always a large technology project. Sometimes it's a targeted change to how a single intake step works. Sometimes it's connecting two systems that should already be talking. The starting point is being honest about which of these five are true, and how many people's working memory is currently standing in for software.
Agencies across the country have closed these exact gaps without adding headcount or requiring multi-year implementation timelines. See how they did it at [PSN landing page link].
Questions about this piece or Kinetech's work with public agencies and nonprofits? Get in touch today.
Craig Smith
Craig.Smith@KinetechCloud.com
(773) 230-5157.
.png?width=246&height=70&name=Kinetech%20PM%20246%20x%2070%20(1).png)