Technology decisions at IDD agencies are made under difficult conditions. Leadership is busy, budgets are tight, the compliance environment is always changing, and the stakes of getting it wrong are high. In that context, it is not surprising that many agencies end up with technology that does not serve them well. What is surprising is how consistent the mistakes are. The same errors show up across organizations of every size, in every state, with every service mix.
Here are the most common technology mistakes IDD agencies make, and what to do instead.
Mistake 1: Buying for the Lowest Line-Item Cost
The most common technology mistake in the IDD sector is selecting software based on the subscription price without accounting for the full cost of operating it. A billing platform that costs less per month but requires a billing coordinator to spend 20 additional hours per billing cycle on manual reconciliation is not less expensive. It is more expensive in a way that never appears on the invoice.
The real cost of IDD software includes the staff time consumed by workarounds, the revenue lost to denied claims that better pre-submission error detection would have caught, the compliance risk that comes from documentation gaps that organized case management would have prevented, and the turnover that happens when staff are frustrated by tools that make their jobs harder rather than easier.
What to do instead: calculate total cost of ownership before making a technology decision. Ask your billing coordinator how many hours per week go to manual reconciliation. Ask your case managers how much time they spend on documentation tasks that feel redundant or disconnected from the work. The gap between what you are currently spending in staff time and what an integrated platform would cost often tells a different story than the subscription price comparison does.
Mistake 2: Treating Billing and Case Management as Separate Problems
The second most consistent mistake is selecting a billing platform and a case management platform independently, from different vendors, and assuming they will work well enough together. They will not. The gap between billing and case management is where most IDD billing errors originate, where most documentation gaps develop, and where most of the manual reconciliation time goes.
When billing and case management are connected in one system, the documentation a case manager creates is immediately available to billing. Authorization tracking reflects real-time service delivery. The pre-submission error rate drops because the data billing needs is already there, verified, and linked. When they are in separate systems, the connection between them requires human effort at every billing cycle, and human effort introduces errors.
What to do instead: evaluate billing and case management as a connected function rather than two separate line items in a software budget. Ask any vendor you are considering how their billing module and case management module share data. Ask to see the data flow from a service note to a submitted claim. If the answer involves an export, an import, or a manual step, you are looking at a system that will cost you reconciliation time.
Mistake 3: Assuming General Healthcare Software Works for IDD
Many IDD agencies adopt general healthcare billing platforms or EHR systems because they are familiar, widely used, and have strong marketing. The problem is that general healthcare software was not built for IDD-specific billing complexity. It does not handle commensurate wage calculations for 14(c) vocational programs. It does not understand the difference between an Individual Options waiver claim and a Level One waiver claim in Ohio. It does not have EVV integration designed for community-based IDD services at non-fixed locations.
When IDD agencies force general healthcare tools into their environment, they end up building workarounds that consume the efficiency gains the software was supposed to provide. The workarounds become institutional knowledge that lives in the heads of specific staff members. When those staff leave, the workarounds leave with them.
What to do instead: ask any software vendor you evaluate to demonstrate, in a live system, how they handle the specific billing requirements of your state and your waiver programs. A vendor who can show you Ohio DODD billing codes in a live demo is in a different category than one who says their system is configurable to meet your needs. Purpose-built IDD software that has already solved these problems is more valuable than general software that requires your team to solve them.
Mistake 4: Going Live Before the Team Is Ready
Implementation failures at IDD agencies are rarely caused by bad software. They are caused by rushing a go-live before the staff who will use the system are genuinely prepared. Training that happens once in a group webinar is not sufficient preparation for a billing coordinator who needs to submit claims correctly from day one. Documentation templates configured without input from case managers produce workflows that staff immediately work around.
What to do instead: protect your team’s time for implementation. Designate an internal implementation lead who has authority to make configuration decisions and accountability for keeping the project moving. Require role-specific training, not just a general platform overview. Build a test period into the timeline where staff use the system in real conditions before go-live. Ask your vendor what go-live support looks like in the first 30 days and what the response time is when something goes wrong during that period.
Mistake 5: Expecting Technology to Solve Culture Problems
The last mistake is expecting software to fix problems that are actually about management practices, staff culture, or organizational accountability. A documentation compliance tool does not make case managers who do not value documentation suddenly value it. A scheduling platform does not make supervisors who cannot manage coverage gaps suddenly able to do so.
Technology creates the conditions for good practices to work more efficiently. It does not create the practices themselves. Agencies that implement new software without addressing the underlying management issues that created their documentation gaps, their billing problems, or their scheduling chaos will find that the problems persist in the new system.
What to do instead: before evaluating new software, spend time understanding what is actually causing your operational problems. If billing errors are being caused by documentation gaps, the solution involves both a connected case management system and a management conversation about documentation standards. If scheduling chaos is being caused by unclear accountability, the solution involves both better scheduling tools and clearer expectations for supervisors. Technology is most powerful when it is supporting good practices, not compensating for the absence of them.
Connect with the Vertex Systems team to talk through what your agency’s technology situation actually looks like and what a different approach would make possible.
