What MapAble is
MapAble is not being built as a simple marketplace. It is being shaped as a disability support operating system with marketplace features, provider operations, participant controls and quality and safeguarding workflows.
About MapAble
An accessibility-first operating system for disability support.
MapAble is being developed to connect public discovery, participant choice, provider operations, consent, audit and safeguarding into one coherent platform.
Explore modulesDetails
Clear information, without overstated claims.
Current status
Public module pages and provider discovery are available for exploration and pilot feedback. Operational claims such as NDIS registration, WCAG conformance and Australian data sovereignty require evidence before being stated as confirmed.
Design principles
- Consent before sensitive sharing.
- Deny access by default and audit sensitive access.
- Human confirmation for high-risk actions.
- Accessibility-first design with formal testing before compliance claims.
Strategic contrast
Care-only platform vs MapAble Complete Support
Comparison is by capability, not colour. Both columns list what each model includes.
Care-only platform
Typical worker marketplace scope
- Worker search
- Basic profile matching
- Shift booking
- Platform messaging
- Payment admin
- Limited visibility into transport and access barriers
MapAble Complete Support
Operating system for accessible support delivery
- Access-fit matching
- Care + accessible transport bundles
- Worker capability passport
- Participant-controlled Access Pass
- First shift trial
- Live shift companion
- Care team builder
- NDIS-aware budget guardrails
- Service confirmation and attestations
- Support coordinator command centre
- Digital twin access data
- Rights and complaints pathway
Measurable outcomes
KPIs that reflect whole-journey support
Targets for product and pilot evaluation — not live dashboards on this page.
Participant metrics
- Time to first suitable match
- Care + transport completion rate
- First shift continuation rate
- Participant confidence score
- Complaint resolution time
Worker metrics
- Completed shifts
- Response time
- Training completion
- Reliability score
- Payout processing time
Provider and coordinator metrics
- Request-to-first-appointment conversion
- Invoice accuracy
- Transport failure reduction
- Service gap visibility
- Plan utilisation visibility
Ecosystem metrics
- Verified access profiles
- Completed attestations
- Community access updates
- Thin-market requests resolved
- Repeat bookings
Build roadmap
Three phases to beat the category
Phase 1
Beat search and booking
- Access-Fit Matching
- Care + Transport Bundle
- Worker Capability Passport
- First Shift Trial
- Budget Guardrails
Phase 2
Beat trust and reliability
- Reliability Engine
- Care Team Builder
- Live Shift Companion
- Attestation Layer
- Rights Navigator
Phase 3
Beat the category
- Support Coordinator Command Centre
- Accessibility Digital Twin
- Thin-Market Support Missions
- Academy
- Hybrid Workforce Model
Trust layer
Trust is the product
Consent first
Sensitive information is shared only with explicit participant control.
Role-based access
Workers, providers, and coordinators see only what their role requires.
Worker verification
Screening and credentials are tracked with clear status — not implied.
Pricing transparency
Line items, transport, and platform fees visible before payment.
Complaint pathway
Rights Navigator and support tickets with neutral, procedural language.
Human review for high-risk workflows
Safeguarding, disputes, and high-value payouts require human decisions.
Audit trail
Material actions on bookings, consent, and payments are logged.
Privacy by design
Need-to-know defaults; no silent broad sharing of access data.
Accessibility by default
WCAG-oriented patterns; formal conformance claims require evidence.
MapAble should never silently automate high-impact decisions about safety, eligibility, payments, complaints, or sensitive disclosures.