Strong fit
This page is most useful when...
- In-home and hybrid providers
- Organizations with caregiver makeup coordination
- RBT teams affected by unpredictable hours
- Clinics seeking role-specific communication boundaries
Two role-specific edges of the same workflow
Caregivers and RBTs should not have to repair the clinic's coordination system from their phones.
Care Pocket and FieldPocket are designed to give each person the information and action appropriate to their role without exposing one portal to the other or transferring clinical authority.
Built for: ABA owners, operations leaders, clinical leaders, caregivers and field-team leaders evaluating family and RBT workflows.
Important limits
This is not a promise to...
- Putting caregiver and staff data in the same unrestricted view
- Turning RBTs into schedulers
- Using notifications to pressure families or staff
- Sending PHI through public marketing analytics
How the workflow should operate
Every handoff needs an owner, a reason and a measurable outcome.
- 1
Caregiver records the event
The family can report a cancellation and the windows they are genuinely open to considering.
- 2
The organization evaluates options
Operations and clinical rules determine which paths can be proposed.
- 3
Eligible staff see appropriate context
A voluntary opportunity includes enough information to evaluate feasibility without exposing unnecessary family data.
- 4
Both sides confirm the final plan
The family sees the proposed staff/time and the organization tracks whether the session actually occurs.
What becomes visible
The outcome should answer a decision, not decorate a dashboard.
Less phone tag
Collect structured availability and decisions instead of repeating the same coordination across calls and messages.
Role boundaries
Give each user the minimum information and actions their role requires.
Staff predictability
Make appropriate voluntary opportunities visible when cancellations affect hours.
Family transparency
Show what was proposed, confirmed and completed without implying the family must accept recovery.
Product proof with boundaries
The sample clinic shows separate caregiver, field and leadership perspectives.
Explore the fictional workflow and evaluate whether each role receives enough context without crossing privacy or authority boundaries.
Buyer questions
Answers should reduce uncertainty, not hide it behind a demo form.
Can RBTs see the caregiver portal?
No. Role-specific experiences should enforce separate access. A production implementation requires tenant-aware RBAC, authentication, audit logging and minimum-necessary data controls.
Does the caregiver have to accept a makeup?
No. Family choice remains explicit. The workflow records availability and confirmation without treating refusal as a failure by the family.
Can an RBT claim any open session?
No. Opportunities should be limited by configured role, credential, capacity, timing, geography, continuity and review rules.
Are these production mobile apps today?
The public experience demonstrates the workflow direction using fictional data. Production identity, notification, consent, offline, device and security requirements must be completed before real use.
Continue the buyer journey