Skip to Content

Haven Suite

Care and community, connected.

Coordinate protected cases, daily services, placements, supporters and organisational accountability.

Request a demonstration Explore the workflow
Haven Suite

Illustrative workflow · tailored to your agreed scope

  1. 01Receive and assess the referral
  2. 02Agree the service plan
  3. 03Coordinate services and placements
  4. 04Review outcomes and next actions

Follow the work from start to finish.

Give each role the context it needs, with the next hand-off visible.

Referrals & cases

Connect intake, assessment, care or service plans and the next action.

Services & placements

Organise daily work, capacity, placements and the handovers that support continuity.

Safeguarding & consent

Keep restricted information, consent and responsibility boundaries explicit.

Supporters & volunteers

Coordinate approved communication, volunteer assignments and supporter engagement.

Resources & funding

Connect grants, costs, in-kind resources and operational accountability.

Governance & outcomes

Organise actions, reviewed outcomes and controlled supporting evidence.

Product scope

Start with the right profile.

Four connected domains: Core, Operations, Engagement and Governance. This is human-services software; supporter access never implies access to confidential cases.

From referral to service delivery.

Record the referral and relevant case context. Review the proposed service or placement. Coordinate daily tasks and resources. Keep consent, safeguarding and follow-up work visible to authorised staff.

Keep sensitive work within its proper boundary.

Case work, supporter activity and volunteer coordination can belong to the same organisation without sharing the same access. A supporter or donor role must not expose confidential case information. Define those boundaries before importing data or inviting users.

Review the service as well as the record.

Explore resource coordination, governance and outcome reporting alongside operational work. Agree which information is collected, who can act on it and how exceptions reach the responsible person. The system does not replace safeguarding judgement or an organisation's policies.

Useful questions, answered.

The proposed deployment should map access and responsibilities to the relevant service teams and confidential records.

A fictional referral and service pathway, plus the roles that should and should not see each stage.

See your team’s workflow.

Bring one representative example, including the exceptions that make the work difficult.