Choosing the Right IDD Software Shouldn't Feel Like Guesswork

IDD Software Evaluation Rubric: 14 Criteria to Score Any Platform

Most agencies don’t set out to end up with disconnected IDD software systems. It happens gradually, one workaround at a time, until manual fixes start to feel normal instead of signs the software isn’t doing its job. Sales demos often don’t help either: they’re typically built around clean sample data, which rarely resembles the real documentation your team works with day to day.

This rubric is designed to close that gap. It breaks platform evaluation into 14 criteria — from service line depth and state compliance fluency to billing/RCM capability, AI maturity, and security and data ownership — each scored on a 1–5 scale, with a clear definition of what separates a 5 from a 1. Use it to score any platform you’re evaluating, including the one you’re on today.

Few platforms will score a 5 across all 14 criteria, and that’s the point: this isn’t about finding a perfect platform, it’s about seeing clearly where a platform is genuinely strong and where the tradeoffs are, so you can weigh what matters most for your organization.

1. IDD Service Line Depth

5 (Exceptional) — Built exclusively for IDD/disability services, with proven, audit-tested workflow coverage across multiple major service lines (residential, employment, day habilitation, community services, case management). Documentation, streamlined billing, and compliance logic built specifically for each service line's requirements, not adapted from a general framework or a broader-market platform. Reporting specific to your needs: authorization utilization reports, goal progress reports, monthly forms, service note reports. Incident reporting. Customer references available across service lines.
4 (Strong) — Primarily focused on IDD with solid coverage across most major service lines. Any secondary focus areas overlap closely with IDD workflows. Some of the above core features available, though not all. References available for most, though not all, service lines. May also serve adjacent verticals that dilute IDD-expertise depth.
3 (Moderate) — IDD is a core focus, but depth is concentrated in one or two service lines; adequate but less proven coverage elsewhere. May also serve adjacent verticals in a way that can dilute IDD-specific development priority.
2 (Limited) — Coverage extends beyond a single service line but remains shallow outside the primary focus area. IDD is a secondary or recently added focus for a platform built primarily for other industries.
1 (Minimal) — A general-purpose platform with IDD support added as a feature layer, or purpose-built for one narrow service line (e.g. day programs only) rather than IDD service delivery broadly. Few or no references outside primary focus area.

2. State-Specific Compliance Fluency

5 (Exceptional) — Active, maintained compliance support across most states with distinct requirements coded into the platform. State-specific forms, billing formats, reports, incident typologies, and ISP structures built into the platform, not reliant on a fixed or flexible forms engine, or custom development to handle updated formats. Proactively updates when state requirements change.
4 (Strong) — Solid, purpose-built compliance logic in most active states, with proactive updates in core markets. Has some of the state-specific requirements, but may be spotty across service lines or funders. Support team knows some of your important needs. References available in more than one state.
3 (Moderate) — Strong compliance depth in a defined geographic region or a small number of states. Handles state-specific requirements in its core markets but less proven outside them. May rely more on configuration than purpose-built state logic in secondary markets.
2 (Limited) — Compliance support exists in name across states but depends heavily on a generic forms rather than built-in state logic. Vendor engineering team is needed to make form and reporting updates (which may take a while). Track record is thin outside one or two markets.
1 (Minimal) — Limited state-specific depth; broad claims of multi-state support are backed by engineering effort to build forms and reports rather than built-in capabilities. Few or no references in most states. Little track record through state-specific audit cycles.

3. Documentation Quality and Workflow

5 (Exceptional) — Documentation workflows designed for IDD service delivery across roles (DSPs, supervisors, QA, billing). Platform flags missing required elements, compares notes against service authorizations and plan goals, and supports audit-ready documentation as a default rather than an afterthought. Staff learn workflows quickly; low error rates reported by customers.
4 (Strong) — Well-structured documentation workflows with meaningful validation built in across most roles. Audit-readiness is a design goal, if not fully default.
3 (Moderate) — Functional documentation workflows that cover most common requirements. Some validation and quality checks in place, but less proactive in catching gaps before they become compliance findings.
2 (Limited) — Documentation workflows cover basic requirements but validation is inconsistent. Compliance gaps are often caught after the fact rather than prevented.
1 (Minimal) — Documentation is primarily a data entry function with limited built-in validation or quality assurance. High reliance on staff discipline to ensure documentation quality.

4. AI Maturity

5 (Exceptional) — AI runs in production at meaningful scale across real customer operations, across the entire platform, with verifiable volume metrics. AI automatically drives activity across the platform. PHI handling and model usage are transparent. AI meaningfully changes customer operations, delivering significant efficiency and quality improvements across the board.
4 (Strong) — AI is in real production use across core functions at impressive scale, though not embedded across the entire platform. Agentic workflows may exist but are not omniprescent.
3 (Moderate) — AI features exist and are in use by some customers, but production scale or impact is limited. Use cases are narrower rather than spanning the whole platform.
2 (Limited) — AI features are announced or in early rollout with minimal verifiable customer use.
1 (Minimal) — AI is primarily a marketing claim or demo feature, with no verifiable production volume.

5. Implementation Methodology

5 (Exceptional) — Structured implementation methodology covering data migration, billing configuration per funder, state-specific compliance validation, role-based training, process improvement, change management, and a go-live plan. Dedicated implementation resources on both sides. Handoff to a named client success contact at go-live. Typical timeline is honest and scales appropriately with agency complexity.
4 (Strong) — Structured implementation process with most of the above in place, though dedicated resources, timeline transparency may vary slightly by agency complexity. Deep implementation expertise may be lacking.
3 (Moderate) — Implementation support exists and covers core setup, but depth varies. May lack dedicated resources for complex migrations, multi-funder billing configuration, or state compliance validation. Promises during sales may drive implementation timelines as the vendor needs to build what was sold.
2 (Limited) — Implementation support is inconsistent or under-resourced for anything beyond basic setup. Timeline and support structure post-go-live are unclear. As Moderate above, promises may drive and lengthen implementation timelines.
1 (Minimal) — Implementation is primarily self-serve or lightly supported. Very short timelines suggest either a narrow product or corners being cut.

6. Vendor Longevity and Track Record

5 (Exceptional) — 15+ years serving IDD specifically. Established multi-state customer base with verifiable multi-year retention. Financially stable with a clear path to profitability or demonstrated profitability - providing peace-of-mind on vendor ability to serve long-term. Has weathered multiple regulatory cycles, audit seasons, and state requirement changes.
4 (Strong) — 10–15 years in IDD with a stable multi-state presence and demonstrated retention, though with a somewhat shorter track record through regulatory cycles than top performers.
3 (Moderate) — 7–12 years in IDD, or shorter with a parent company's longer track record providing stability. Regional or limited national presence. Reasonable customer retention but limited multi-year renewal data available.
2 (Limited) — 3–7 years in IDD, or a longer history in an adjacent category with limited IDD-specific track record. Retention data is sparse.
1 (Minimal) — Under 3 years in IDD, or recently entered the market, perhaps from an adjacent category. VC-backed with investor pressure that may prioritize growth over depth. Limited track record through full audit cycles.

7. Mobile Experience

5 (Exceptional) — Mobile experience purpose-built for DSP workflows in the field (EVV, documentation, AI assistance) with offline capability where needed. Works reliably across device types. Integrated with the main platform so mobile documentation flows directly into billing and reporting without manual handoffs. Updates quickly to keep pace with changing state requirements.
4 (Strong) — Purpose-built mobile experience covering most field workflows, with reliable performance, and offline capability where needed.
3 (Moderate) — Functional mobile experience that covers core tasks but with limitations. May lack offline capability, separate EVV experience, or full documentation workflow support.
2 (Limited) — Mobile experience covers only the most basic field tasks (e.g. EVV clock-in/out) with little else built for mobile use.
1 (Minimal) — Mobile experience is minimal, primarily browser-based without mobile optimization, or limited to EVV only. Documentation workflows are primarily desktop-dependent.

8. Integration Ecosystem

5 (Exceptional) — Live, actively maintained integrations with major billing clearinghouses, HR/payroll systems, medication management, EVV aggregators, state billing systems, and other ecosystem vendors. Integration quality is high and data flows without manual intervention. Customers can verify which integrations are in active production use.
4 (Strong) — Broad set of live integrations across core categories, with generally reliable data flow, though the pace of new integration development may lag top performers.
3 (Moderate) — Core integrations are in place (billing, payroll, EVV) but the ecosystem is narrower, or vendor does not focus on integrations.
2 (Limited) — Only one or two core integrations are truly live; most others require manual workarounds or are roadmap-only, or vendor does not focus on integrations.
1 (Minimal) — Few live integrations. Agencies often need to maintain manual data transfer between systems.

9. Billing / RCM Capability

5 (Exceptional) — Native revenue cycle management purpose-built for Medicaid HCBS complexity — claims submission, denial management, waterfall billing across multiple funders, and AR tracking all built in. Minimizes manual reconciliation and reduces denied claims. Automates more complex billing requirements (e.g. dynamically applying billing codes or modifiers). Offers a complete ledger.
4 (Strong) — Native billing covers most billing functions; minor gaps in advanced billing needs (waterfall biling, AR automation, eligibility checks). May not have a complete ledger.
3 (Moderate) — Core billing (claims submission, basic AR) is built in, but advanced billing functions like waterfall billing or denial management are completed outside the EHR.
2 (Limited) — Billing functionality is basic; most billing/RCM tasks happen outside the platform.
1 (Minimal) — No native billing; agencies rely entirely on separate billing software or manual processes.

10. Total Cost of Ownership (Multi-Year)

5 (Exceptional) — Transparent, predictable pricing across a multi-year period. Implementation costs are disclosed early and honestly. Fees for adding service lines, state compliance updates, and AI features are clearly defined.
4 (Strong) — Pricing is largely transparent with most costs disclosed early, though some add-on fees may not be fully clear until later in the sales process.
3 (Moderate) — Base pricing is reasonably transparent but some costs become clearer later in the sales process. Year-one pricing may understate multi-year costs. Costs add up unexpectedly for many additional modules.
2 (Limited) — Pricing structure is difficult to assess upfront; multiple cost categories are undefined until deep into the sales process.
1 (Minimal) — Pricing is vague until late in the sales process. Low year-one pricing may obscure higher renewal costs once dependency is established.

11. Reporting and Analytics

5 (Exceptional) — Real-time, customizable dashboards across departments. Users can build their own reports without vendor support. Data supports both operational and outcome-based reporting (state, funder, accreditation).
4 (Strong) — Strong built-in reporting with most customization available; advanced custom reports may need vendor help.
3 (Moderate) — A standard report set covers common needs; deeper customization is limited or costs extra. No comprehensive report builder exists.
2 (Limited) — Reporting is basic; agencies often export to spreadsheets to get the insight they actually need.
1 (Minimal) — Minimal reporting capability; most analysis happens outside the platform.

12. Support

5 (Exceptional) — Dedicated, named support contact with documented SLAs. Proactive outreach on regulatory/compliance changes. High customer-reported satisfaction with response time and resolution quality. Deep IDD expertise.
4 (Strong) — Responsive support with clear escalation paths; SLAs may be less formal but response times are consistently good. Has some IDD expertise.
3 (Moderate) — Standard ticket-based support; adequate response times, though resolution may take multiple touches. Support expertise in IDD is limited or spotty.
2 (Limited) — Support is slow, inconsistent, or unfriendly; customers often report needing to escalate repeatedly.
1 (Minimal) — Minimal or self-serve support only; customers report significant frustration getting timely help.

13. Security and Privacy / Data Ownership

5 (Exceptional) — Documented compliance with relevant standards (HIPAA, SOC 2, NIST, etc.), transparent data ownership terms giving agencies full control and export of their data, clear breach-notification policy, and regular third-party security audits. Compliant state-by-state and funder-by-funder. Fully US-based teams prevent accidental data leakage outside the US.
4 (Strong) — Solid security posture and compliance documentation; periodic third-party security audits are performed, and some conformance to relevant standards is present, officially or unofficially.
3 (Moderate) — Basic compliance is claimed but documentation or certification is limited; data ownership terms exist but aren't fully transparent.
2 (Limited) — Security practices are not well documented; data ownership or portability terms are unclear or restrictive.
1 (Minimal) — No verifiable security certifications; data ownership terms are unclear or heavily favor the vendor.

14. Ease of Use and Staff Adoption

5 (Exceptional) — Role-based interfaces designed for how DSPs, supervisors, QA staff, and billing teams actually work, not a single interface adapted for all roles. Staff can complete core tasks in a single workflow without navigating between screens. Training time is low.
4 (Strong) — Meaningful role-based design with efficient core workflows; training time is reasonable and adoption is generally smooth.
3 (Moderate) — Functional interfaces that most staff can learn with reasonable training investment. Some role differentiation in the UI. Navigation between workflows requires more steps than ideal.
2 (Limited) — Interface requires significant workarounds for daily tasks; role differentiation is minimal and training investment is substantial.
1 (Minimal) — Interface is primarily built for one role or adapted from a general platform. Staff adoption challenges are common.

What's next?

Ready to see it all in one place?

SETWorks is built to manage your entire organization, from client records to billing to compliance, without juggling multiple systems.

Connect with our team to learn how our purpose-built software platform created specifically for disability services can empower your agency.

Schedule a Call

Frequently Asked Questions (FAQ)

How do I choose an IDD software?

A demo is a useful first step, but it shouldn't be the only input in your decision. Demos are typically built around clean sample data and best-case scenarios, so they don't always reflect what your team will be working with day to day. Pair demos with a consistent set of evaluation criteria (like the 14 covered in this rubric) and specific, real-world questions about implementation, compliance updates, and ongoing support, so you're comparing platforms on substance, not just first impressions. Check out our list of 8 key questions to ask during a sales demo!

What is the best IDD software?

There isn't one best IDD software platform. The right fit depends on your service lines, state requirements, and where your current operations are breaking down. A platform that's excellent for a residential-focused agency may not be a perfect fit for one running VR or employment services, for example. Use a structured rubric to score any platform you're considering against the criteria that matter most for your organization, rather than relying on rankings or vendor claims alone.

What should I look for in IDD software?

Look for a platform that connects your operations rather than adding another disconnected system to the pile. Documentation, billing, EVV, and reporting should all work together without manual re-entry. Beyond that, look closely at state-specific compliance support, how implementation and ongoing support actually work in practice, and whether the platform was purpose-built for IDD service delivery or adapted from a more general system.