ProviderQMS

Allied health

eTrack vs Zanda (formerly Power Diary)

Compare the published scope, cost evidence and buying questions before you commit.

Sources checked 2026-09-24 · Source-based comparison

Vendor-source research, not hands-on tests or a ranked endorsement. ProviderQMS sells document kits and a separate QMS product. No vendor enquiry collection or affiliate source links. How we compare.

The decision to make

eTrack and Zanda (formerly Power Diary) both appear in our allied health research. Connect bookings, clinical documentation, practitioner workflows, funding and invoices. Start with the differences below, then test the same essential workflow. We have not used these products hands-on or established an overall winner.

eTrack vs Zanda (formerly Power Diary): the published starting point
Buying questioneTrackZanda (formerly Power Diary)
What does it do?eTrack is an NDIS CRM and practice platform for coordinators and therapists. It connects case notes, tasks, budgets, compliance registers and invoicing.Zanda provides allied health scheduling, documentation and billing. Its NDIS workflow generates bulk-upload CSV files for the myplace portal, with no direct NDIS integration.
Why consider it here?Vendor explicitly markets its NDIS CRM to coordinators, therapists and providers.Australian allied health practice system with explicit NDIS workflows.
What is the cost basis?Vendor describes usage-based pricing; current amount not verified, so request a written quote.Current price not verified; request a written quote.
What should the demo show?Record a coordinator task from an email, bill time to the right item and inspect remaining plan hours and invoice.Generate a multi-clinician NDIS claim batch and verify the CSV plus plan-manager statement.

Compare the evidence, product by product

eTrack — published capabilities

  • Case notes linked to goals and billable time
  • Participant funding and budget views
  • Compliance registers
  • Mobile tasks, notes and signatures

Source check: 2026-09-24. Published vendor statements, not independent feature testing.

Questions for eTrack

  • Does the myNDIS interface cover our participant consent model?
  • How do OneDrive or SharePoint documents export with metadata?
  • What controls lock or correct case notes?
Read the full eTrack profile ↗

Zanda (formerly Power Diary) — published capabilities

  • NDIS bulk-upload CSV report
  • plan-manager statements
  • session packs and funding tracking
  • digital service agreement template

Source check: 2026-09-24. Published vendor statements, not independent feature testing.

Questions for Zanda (formerly Power Diary)

  • How is the current NDIS price guide applied?
  • What happens after a portal rejection?
  • Which forms and reports are included in the quoted tier?
Read the full Zanda (formerly Power Diary) profile ↗

Run the same scenario in both

Book a fictional NDIS therapy appointment, record the supplied assessment information, prepare the invoice and share a report through an approved channel.

  • Show intake, consent and restrictions on who can see clinical information.
  • Demonstrate practitioner note templates, amendments and supervisor review where needed.
  • Separate appointment duration, delivered quantity, travel and cancellation handling.
  • Export the clinical record and attachments without losing authorship or dates.

Put the quotes on the same basis

Model practitioners, locations, support staff, messages, telehealth, AI features and payments, using the same GST and billing-term assumptions.

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

  1. Choose the tasks your service cannot operate without before either demonstration.
  2. Record demonstrated, partial, not demonstrated or not applicable for each task. Keep the evidence and edition name.
  3. Ask the vendor to resolve every failed essential task in writing; a high average score cannot erase it.
  4. Test a correction, permission change and export. These are part of everyday operations, not just implementation.
  5. 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

Clinical systems serve different professions. NDIS billing support, clinical suitability and record-governance obligations each require separate checks. A capability not mentioned in the reviewed source remains unverified, not absent. This comparison does not certify compliance, integrations, accessibility, security or migration outcomes.