The SETWorks alternative that runs the whole agency.
Enmantle is one platform built inside a working Ohio IDD agency: scheduling, native Sandata EVV, ISP goals, incidents, billing and payroll under one login, with native mobile apps for the field. SETWorks is a browser-based, mobile-first platform with deep per-county Ohio flexibility — here is how the two compare.
Last reviewed · Enmantle team
Enmantle is one Ohio-built platform for scheduling, native Sandata EVV, ISP goals, incidents, eMBS billing, and payroll. Where SETWorks runs as a browser-only, mobile-first experience with no native app, Enmantle adds native iOS and Android apps built for the field. SETWorks serves I/DD employment, day, residential, community, and personal-care providers nationally, with a separate Ohio DODD/OOD-specific offering of its own.
SETWorks markets itself to I/DD employment, day, residential, community, and personal-care service providers, positioning itself nationally while separately maintaining an Ohio DODD/OOD-specific offering. Its founding year is not published on its site, so we do not state one here.
In Ohio, SETWorks appears on the state's certified alternate EVV vendor list and describes, in its own case study, a customer that serves 66 of Ohio's 88 counties — each with its own funding sources and requirements. SETWorks says it solves that scale problem by importing information in whatever format it arrives and exporting results in the right format for each county.
Enmantle vs SETWorks, side by side
The table below compares Enmantle with SETWorks module by module, using only what each vendor documents about itself. A filled dot (●) means the capability is documented as built into the platform; a half-filled dot (◐) means it is partial, browser-only, or billed separately from the base subscription; "Not publicly documented" means we found no public source for that row as of the retrieval date shown. Every SETWorks cell is footnoted to the SETWorks page it came from, retrieved September 20, 2026.
| Capability | Enmantle — one platform — | SETWorks |
|---|---|---|
| ISP goals and documentation | ● ISP goals scored inside every shift note how it works | ● Built-in goal & outcome tracking (no 'ISP' term)1 |
| Incident reporting (UI / MUI / Internal) | ● UI / MUI / Internal wizard with deadlines from the discovery date how it works | ● Incident/event forms, state-specific (no UI/MUI term)2 |
| Staff scheduling and coverage | ● Time grid, open-shift claiming, on-call splits how it works | ● Scheduling w/ open-shift claiming, recurring appts3 |
| Ohio EVV (Sandata) | ● DODD-approved alternate EVV vendor; submits directly to Sandata how it works | ● ODM-certified alternate EVV vendor4 |
| DODD billing (eMBS) | ● eMBS file generation, preflight, remittance import how it works | ● Medicaid/DODD billing incl. Ohio flat-file eBilling5 |
| Payroll and expenses | ● Payroll calendar, pay stubs, expense accounts, mileage how it works | ◐ Mileage log + payroll timesheet/earning codes6 |
| Mobile app for DSPs | ● Native iOS and Android app; GPS EVV; offline clock-ins and incidents how it works | ◐ Browser-based mobile; offline EVV mode; no app7 |
| Learning and certifications | ● Courses, in-person sign-off, certification expiry alerts how it works | ◐ Tracks certs/training; LMS via partner (GoodLife U)8 |
| County-board rates and service codes | ● Cost centers, rate tables, service crosswalk how it works | ◐ Per-county authorization/export formats (OH case study)9 |
| Pricing model | ◐ Quoted per agency; one tier that scales with clients, staff and locations how it works | ◐ Tiered by avg. individuals served/yr, not per-seat10 |
| Contract and export terms | ● CSV export any time; no export fees; no lock-in how it works | Not publicly documented11 |
| Support | ● Email and in-app; Mon–Fri 8 a.m.–6 p.m. ET; reply within one business day how it works | ◐ Client success + US-based support team; email listed12 |
| Implementation | ● Two to four weeks with a parallel run; migration included how it works | ● Go-live: ~1 mo (small) to 6+ mo (large multi-state)13 |
Comparison reflects SETWorks's own public documentation (footnoted below, retrieved ) and Enmantle's own Help Center. ● documented as built-in · ◐ partial, or via a partner or add-on · "Not publicly documented" means we found no public source; it is not a claim that the capability is absent. SETWorks is a trademark of its respective owner. This page is an independent comparison, not affiliated with or endorsed by SETWorks. Corrections: hello@enmantle.com.
Sources and notes for every cell (13)
- set-works.com/explore-the-platform/the-client-record — The Client Record page states SETWorks lets staff 'track outcomes, goals and related information by individual per service,' link goals to authorizations, and 'show an individual's progress over time with goal reporting,' though it does not use the specific term 'ISP.' (retrieved 2026-09-20) ↩
- set-works.com/explore-the-platform/the-client-record — The Client Record page states users can 'create generic and state-specific incident/event forms, then export, print, or email them,' and lists incident, accident and seizure reporting under health records, without using the terms 'UI' or 'MUI.' (retrieved 2026-09-20) ↩
- set-works.com/communities-we-serve/community-services — The Community Services page lists scheduling capabilities including 'assign staff to individuals or groups,' 'identify and claim open shifts,' 'create recurring appointments,' 'share calendars,' and 'print schedules.' (retrieved 2026-09-20) ↩
- dam.assets.ohio.gov/image/upload/medicaid.ohio.gov/Providers/EVV/AltSy — SETWorks (listed as "SetWorks") appears on the Ohio Department of Medicaid's certified alternate EVV vendor list, updated June 12, 2026; SETWorks's own page describes its mobile check-in as 'browser-based but purpose-built for mobile devices' with 'an offline mode [that] keeps EVV running when signal drops,' and its EVV feature page adds that EVV is 'built directly into your staff's daily documentation workflow — no duplicate entry, no separate app.' (retrieved 2026-09-20) ↩
- set-works.com/setworks-in-ohio — SETWorks's Ohio page states it provides 'support for documentation and billing needs for OOD, DODD and other Ohio funders' and offers 'DODD ebilling via flat-file upload,' while its general Billing page separately describes HIPAA EDI 837/835 claims and integration with funder eBilling systems. (retrieved 2026-09-20) ↩
- support.set-works.com/portal/en/kb/articles/mileage-billable-group-act — SETWorks's support knowledge base describes mileage documented directly within a Billable Individual/Group Activity Record with odometer start/end and commute fields, and its Residential Programs page separately states the activity record 'serves as the staff time sheet, making payroll simple' with 'payroll earning codes' and shift-differential rates. (retrieved 2026-09-20) ↩
- set-works.com/setworks-explained-straight-answers-on-mobile-implementa — This page states 'SETWorks is mobile-first, offering a mobile experience that's browser-based but purpose-built for mobile devices' with 'an offline mode [that] keeps EVV running when signal drops'; no SETWorks app was listed on Apple's 'Setworks, LLC' App Store developer page, and no SETWorks app was found on Google Play. (retrieved 2026-09-20) ↩
- set-works.com/explore-the-platform/powerful-integrations — SETWorks's Integrations page lists 'LMS' among its integration categories and names 'GoodLife U' as one of its specialty integration partners, while its platform overview separately states SETWorks tracks employee 'training, certifications, and onboarding.' (retrieved 2026-09-20) ↩
- set-works.com/capabilities-case-study — In this case study a customer serving 66 of Ohio's 88 counties says SETWorks let them 'import information however it was to us and then export the results in the right format for each county,' noting 'each of the 88 counties in Ohio has its own funding sources and requirements'; no explicit 'rate table' feature is named. (retrieved 2026-09-20) ↩
- set-works.com/faq — The FAQ states SETWorks pricing is 'tiered pricing based on average individuals served annually (not user count)' with the subscription including all features, unlimited storage, and support, while items like EVV, system integrations, and authorization imports are billed separately — no dollar figures are given. (retrieved 2026-09-20) ↩
- No public source found. — Not stated on vendor's site as of this check. (retrieved 2026-09-20) ↩
- set-works.com/faq — The FAQ states clients get a 'client success team' for strategy/integration support and a 'US-based support team' for technical issues and functionality questions, reachable via hello@SETWorks.com; no specific support hours or phone number are published on the site. (retrieved 2026-09-20) ↩
- set-works.com/setworks-explained-straight-answers-on-mobile-implementa — This page states a 'small, single-service agency' can 'go live in a month,' a mid-sized agency takes 'about 2-4 months,' and a 'large, multi-program/multi-state' organization 'can take 6 months or more,' covering data migration, configuration, billing setup, compliance validation, and training. (retrieved 2026-09-20) ↩
SETWorks's clearest strength in this comparison is exactly that multi-county flexibility: a platform built to import and export in dozens of different county-specific formats is solving a real Ohio problem. Its go-live estimates are also the most detailed and specific of any vendor covered on this site — about a month for a small, single-service agency, two to four months for a mid-sized one, and six months or more for a large, multi-program, multi-state organization, per its own materials.
What SETWorks does well
SETWorks's per-county flexibility is a genuine, documented strength. Its capabilities case study describes a customer serving 66 of Ohio's 88 counties that can "import information however it was to us and then export the results in the right format for each county," because, as the case study puts it, each of Ohio's 88 counties has its own funding sources and requirements. That is a harder problem than a single-county agency ever has to solve, and SETWorks has clearly built for it.
Its day-to-day documentation is thorough without leaning on Ohio-specific labels. The Client Record page lets staff "track outcomes, goals and related information by individual per service," link goals to authorizations, and show progress over time with goal reporting — without using the specific term "ISP." The same page supports generic and state-specific incident and event forms that can be exported, printed, or emailed, covering incident, accident, and seizure reporting, without using the terms "UI" or "MUI." Scheduling covers assigning staff to individuals or groups, claiming open shifts, creating recurring appointments, sharing calendars, and printing schedules.
SETWorks's EVV design philosophy is worth crediting on its own terms. Its materials describe EVV "built directly into your staff's daily documentation workflow — no duplicate entry, no separate app," with an offline mode that keeps EVV running when a signal drops, delivered through a mobile experience that is "browser-based but purpose-built for mobile devices" rather than a downloadable app. Its billable activity record does double duty as the staff timesheet, with payroll earning codes and shift-differential rates built in, per its support documentation and its Residential Programs page.
Where Enmantle differs
One login instead of a stack
SETWorks already puts a lot behind one subscription, and its own FAQ says the base plan "includes all features," with unlimited storage and support. But that same FAQ lists EVV, system integrations, and authorization imports as billed separately from the subscription, with pricing tiered by average individuals served per year rather than a flat number. Enmantle prices per agency with EVV, billing, payroll, scheduling, and every core module inside the same tier, and migration is included rather than a separate line item — so the number you hear in the demo is the number you pay.
Built for the direct support professional in the field
Enmantle ships native iOS and Android apps built for direct support professionals (DSPs) working a shift from a phone, not a browser tab. A DSP clocks in with a single GPS point, dictates the daily note by voice and polishes it with AI that only cleans up phrasing and never invents content, and scores each ISP goal inline in that same note. SETWorks describes itself as "mobile-first" but browser-based, with no SETWorks app found on Apple's or Google's app stores under its developer name; its own materials frame this as a deliberate choice, and its offline mode is built specifically to keep EVV running when a signal drops. Enmantle's app is native to the device and adds voice dictation and inline goal scoring on top of a similar tolerance for a dropped connection.
EVV that is native, not bolted on
Enmantle is a DODD-approved alternate EVV vendor and submits directly to Sandata. GPS is captured at exactly two moments per shift — clock-in and clock-out — and that same clock event derives the billing row and feeds the EVV Status dashboard, which catches denials before DODD does. SETWorks is also an ODM-certified alternate EVV vendor, and its own materials describe EVV built directly into the daily documentation workflow with "no duplicate entry, no separate app," plus an offline mode that keeps EVV running when signal drops — a philosophy genuinely close to Enmantle's own. The difference is what happens after the visit is verified: Enmantle's dashboard reconciles verified visits against billed units, post-lock de-verifications, and eMBS denial codes in one place — we found no public documentation of a comparable dashboard on SETWorks's site.
What migrates from SETWorks
Agencies moving off SETWorks carry over the same core records Enmantle's import tools are built for. The table below lists what typically moves and how.
| What | How it comes across |
|---|---|
| Locations (homes, sites, day programs) | Import wizard step 1, from Excel or CSV guide |
| Users (staff and roles) | Import wizard step 2, tied to their locations guide |
| Clients | Import wizard step 3; Ohio clients can also be drafted from the ISP PDF guide |
| Certifications | Import wizard step 4, attached to the imported users guide |
| Active ISP goals | Read from each client's ISP PDF into the goal list guide |
| Open billing cycles | Carried across with the Enmantle team during onboarding guide |
| Larger or recurring loads | Write-only API tokens scoped to each import step guide |
The import wizard brings locations, users, clients, and certifications in from Excel or CSV files, in that order, because later records point back at earlier ones — see the full sequence in Importing your agency's data. Ohio clients can also come in one at a time through the ISP PDF import, which reads a standard DODD Individual Service Plan PDF and drafts the person's identity, service authorizations, ISP goals, and contacts, highlighting anything it is unsure about for review before anything saves. Agencies with a larger or ongoing feed, including one already used to exporting per-county formats out of SETWorks, can use scoped, write-only API tokens instead of the wizard. Onboarding runs two to four weeks end-to-end, covering migration, staff onboarding, and EVV configuration, with a parallel-run period so your SETWorks data keeps working until Enmantle is verified against it.
When to stay on SETWorks
SETWorks is worth keeping if your agency already spans dozens of counties or several states with funding formats SETWorks has already been configured to export, or if your team has built its process around SETWorks's per-county import and export flexibility and a browser-only workflow suits how your staff already work. Enmantle is live in Ohio only today, so a multi-state agency outside Ohio's DODD system, or one with a long history of custom county-format exports already tuned in SETWorks, may have less to gain from switching this year.
Frequently asked questions.
Is Enmantle a good SETWorks alternative for Ohio DODD providers?
How does Enmantle pricing compare with SETWorks?
Does Enmantle handle Ohio EVV like SETWorks?
What migrates from SETWorks, and how long does it take?
Does Enmantle have a native mobile app like SETWorks?
How does Enmantle support compare with SETWorks?
Sources and how this page is kept current.
Reviewed . Every regulatory statement links to its primary source; corrections to hello@enmantle.com.
- SETWorks — The Client Record
- SETWorks — Community Services
- Ohio Department of Medicaid — ODM-Certified Alternate EVV Vendor List
- SETWorks — SETWorks in Ohio
- SETWorks — Mileage & Billable Group Activity Records (support KB)
- SETWorks — Straight Answers on Mobile, Implementation, Scale and AI
- SETWorks — Powerful Integrations
- SETWorks — Capabilities Case Study
- SETWorks — FAQ
- Importing your agency's dataBring your locations, users, clients, and certifications into Enmantle in the right order with the import wizard — or via write-only API tokens.
- Build a weekly schedule with the Time GridThe Time Grid is where you build the week: place shifts, see who's available, catch double-bookings, and publish so staff get notified.
- Clocking in and out with GPS: what's captured, and whenClock in and out from your phone. Enmantle reads GPS at those two moments only — never in between — and that clock data is what feeds DODD EVV.
- From clock-ins to a clean eMBS invoiceFollow the billing flow end to end: clock data becomes billing rows, preflight flags problems, and you generate an eMBS invoice you can trust.
- FAQ: data export, migration from Brittco, support, and pricingStraight answers on exporting your data, migrating from Brittco, getting support, pricing, Ohio EVV approval, and the mobile apps.
— See it on your workflow —
Bring your SETWorks data. We'll map the rest.
Thirty minutes in the live product, mapped to your agency — bring your SETWorks setup and we'll show the same workflow inside Enmantle.