Core casework
Follow the person’s journey without losing context.
- Referral, triage, intake and eligibility decisions
- Relationships, consent, assessments and care plans
- Goals, reviews, referrals, closure and aftercare
Haven Suite
Explore connected workflows for cases, daily services, supporters and organisational accountability.
A human-services product blueprint for care homes, shelters, charities and child or family services. Begin with your programme and the information each role should be allowed to use.
Product scope and implementation assessment · Deployment readiness requires confirmation
A PERSON-CENTRED WORKFLOW
Private case context stays protected
No real beneficiary, child, family or case data is shown.
Four connected domains
Follow the person’s journey without losing context.
Connect the plan to the service delivered.
Build relationships without exposing private cases.
Make responsibilities and follow-through visible.
Trace what was received and how it was used.
Make information boundaries part of the workflow.
A referral becomes a plan
A referral needs a proportionate first record, a responsible worker and a clear next step. Assess eligibility, consent, needs, strengths and available capacity before admitting or referring onward.
For an accepted case, connect the plan with delivered services and review dates. A transition or closure should preserve the reasons, responsibilities and aftercare arrangements.
REFERRAL → SUPPORT → FOLLOW-UP
Capture minimal necessary details and immediate concerns.
Review eligibility, consent, capacity and the responsible worker.
Record the agreed services, goals, changes and the person’s preferences.
Review closure, onward referrals, property and follow-up responsibilities.
Illustrative workflow. Roles, configuration and acceptance are agreed for your deployment.
The publication boundary
Fundraising and casework have different purposes. Sharing a story should be a separate, reviewed action with a defined audience.
Case notes, health detail, family identity, legal status and safeguarding information belong to restricted workflows. A donor or sponsor relationship does not grant access.
Prepare a separate update with only permitted content. Check consent, purpose, confidentiality and safeguarding implications before approval.
A supporter sees the approved publication within its agreed scope. Do not publish a direct view of protected case notes or expose identifying details by default.
Make the next step specific
No. Haven’s scope concerns human-services coordination and accountability. Clinical, safeguarding and statutory decisions remain with qualified people and the responsible organisation.
Request a demonstration of the modules and workflows you need. We will confirm their availability, supported environment and delivery scope in your proposal before you commit.
Use synthetic examples or appropriately redacted material. Agree a suitable private handling route before sharing beneficiary, child, family or safeguarding information.
Bring a fictional referral, role map and an example of the update supporters should receive.
All Industry Apps · Implementation services · Corvus Cloud for Odoo