Compare the evidence, product by product
Echidna Online — published capabilities
- Plan budgets and funding periods
- Appointments, billable notes and claim items
- Client goals and progress reporting
- Forms with electronic client sign-off
Source check: 2026-09-24. Published vendor statements, not independent feature testing.
Questions for Echidna Online
- How does the FTE calculation handle casual and variable-hour staff?
- What happens to records after cancellation or read-only access ends?
- Can claim and note histories be exported with attachments?
FlowLogic — published capabilities
- Participant case records
- Rostering and workforce app
- NDIS claim generation and PRODA connection
- Incident and compliance reporting
Source check: 2026-09-24. Published vendor statements, not independent feature testing.
Questions for FlowLogic
- Which PRODA and PACE functions are active in our edition?
- How are incident records permissioned across sites?
- What is required to migrate historical case notes?
Run the same scenario in both
Use a fictional recurring community-access service. Change the worker, record the delivered support, correct a note and reconcile the invoice.
- Trace service agreement and budget to the roster and delivered record.
- Check what the worker can see, what they must record and how corrections are retained.
- Change or cancel a service and inspect the effect on timesheets, billing and reporting.
- Export the participant history with attachments and demonstrate the exit process.
Put the quotes on the same basis
Model active clients, staff logins, sites, service lines, setup and required accounting/payroll connections.
Use the same volumes, currency, GST basis and billing period for both quotes. Include migration, staff training time, required companion subscriptions and the cost of retrieving records at exit. If a charge is unverified, keep it as an open question rather than treating it as free.
How to reach a decision
- Choose the tasks your service cannot operate without before either demonstration.
- Record demonstrated, partial, not demonstrated or not applicable for each task. Keep the evidence and edition name.
- Ask the vendor to resolve every failed essential task in writing; a high average score cannot erase it.
- Test a correction, permission change and export. These are part of everyday operations, not just implementation.
- Decide using workflow fit, full cost and your team’s capacity to change systems. Retain the written assumptions for review.
What this comparison does not establish
Service-delivery software varies by provider size, module and funding workflow. Scheduling alone does not establish complete NDIS claiming or clinical-record coverage. A capability not mentioned in the reviewed source remains unverified, not absent. This comparison does not certify compliance, integrations, accessibility, security or migration outcomes.