Skip to Content

Haven Suite

Coordinate the care.
Protect the person.

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

EXPLANATORY MODELCare and accountability

Private case context stays protected

01
The person & their planConsent, needs, goals and accountable worker
02
The service deliveredPlacement, daily support and reviewed outcomes
03
The approved storySeparate, reviewed updates for supporters

No real beneficiary, child, family or case data is shown.

Four connected domains

A shared purpose. Different responsibilities.

01

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
02

Daily operations

Connect the plan to the service delivered.

  • Placement, occupancy, attendance and authorised movement
  • Caregiver assignments, shifts and handovers
  • Meals, supplies, transport and daily service records
03

Supporter engagement

Build relationships without exposing private cases.

  • Donors, sponsorships, volunteers and partners
  • Pledges, in-kind contributions and stewardship
  • Separate approved publications and audience-specific portals
04

Governance & evidence

Make responsibilities and follow-through visible.

  • Obligations, licences, policies and review cycles
  • Risks, inspections, findings and corrective actions
  • Board decisions, outcomes and reporting snapshots
05

Funds & resources

Trace what was received and how it was used.

  • Grant restrictions, budgets and analytic dimensions
  • Procurement, stock, expenses and allocations
  • Frozen donor reports and separation of financial duties
06

Consent & access

Make information boundaries part of the workflow.

  • Programme, site, assignment and role-specific access
  • Restricted safeguarding records and protected documents
  • Publication review, retention and authorised export scope

A referral becomes a plan

Make every handover accountable.

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

  1. 1
    Understand the referral

    Capture minimal necessary details and immediate concerns.

  2. 2
    Agree the response

    Review eligibility, consent, capacity and the responsible worker.

  3. 3
    Deliver and review

    Record the agreed services, goals, changes and the person’s preferences.

  4. 4
    Plan the transition

    Review closure, onward referrals, property and follow-up responsibilities.

Illustrative workflow. Roles, configuration and acceptance are agreed for your deployment.

The publication boundary

A supporter update is not a case file.

Fundraising and casework have different purposes. Sharing a story should be a separate, reviewed action with a defined audience.

Protected working record

Case notes, health detail, family identity, legal status and safeguarding information belong to restricted workflows. A donor or sponsor relationship does not grant access.

Reviewed publication

Prepare a separate update with only permitted content. Check consent, purpose, confidentiality and safeguarding implications before approval.

Permitted audience

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

Begin with one programme and its boundaries.

Is this a hospital EHR or a safeguarding authority?

No. Haven’s scope concerns human-services coordination and accountability. Clinical, safeguarding and statutory decisions remain with qualified people and the responsible organisation.

What is available for deployment today?

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.

Can we use real case records in the initial discussion?

Use synthetic examples or appropriately redacted material. Agree a suitable private handling route before sharing beneficiary, child, family or safeguarding information.

Bring a workflow.
Leave with a clear scope.

Bring a fictional referral, role map and an example of the update supporters should receive.

Discuss Haven Suite ↗

All Industry Apps · Implementation services · Corvus Cloud for Odoo