Skip to content
All applications
Fictional application concept02 / 05

Community referral coordination

Follow every referral without losing the person.

Kinship

Kinship keeps responsibility, partner requirements, communication preferences, and the next accountable step together.

Interactive no-backend prototype
Modeled customer
Harborline Community Health · Community navigation team
The fictional brief
Create one calm place to see who needs follow-up, what each partner is waiting for, and who owns the next step.

Working prototype

Try the operating idea, not just the screens.

Every control below changes local browser state. Use the navigation inside the product, complete the sample workflow, and reset it whenever you want to replay the story.

Use the reset control inside the application to return to the seed scenario.
KinshipLocal demo stateEN / ES

Loading prototype… / Cargando prototipo…

01

Starting point

The spreadsheet counted referrals. It could not hold the promise behind them.

This fictional team received referrals from forms, outreach events, calls, and partner email. Intake lived in a shared inbox, statuses in a spreadsheet, and important context in individual notes.

A row could be marked in progress without showing who promised the next action, what the partner needed, or how the participant preferred to be contacted.

02

Customer ask

Make handoffs clearer without turning people into ticket numbers.

The fictional brief prioritizes a calm daily view, shared status definitions, named ownership, dated follow-up, and visible language and contact preferences.

It also asks the resource directory to show when partner information was last reviewed, so a complete handoff can begin from current context.

03

What we designed

A community thread connecting person, partner, owner, and next step.

The referral workspace keeps the journey, activity, communication preference, partner requirement, and next best action in one readable context.

The prototype demonstrates ownership changes and follow-up completion without presenting itself as an electronic medical record or making health-outcome claims.

Scene by scene

Every screen earns its place in the workflow.

  1. 01

    Today

    What you are seeing

    The day begins with owned promises rather than a count of aging rows.

    Problem solved

    Priority had to be reconstructed from inbox age and personal memory.

    Try this

    Select a person or attention group to enter the shared referral workspace.

  2. 02

    Referral queue

    What you are seeing

    Owner, partner, status meaning, and follow-up date stay visible in a real work table.

    Problem solved

    Sent, waiting, and in progress meant different things to different coordinators.

    Try this

    Filter the caseload, choose a record, and inspect the next accountable action.

  3. 03

    Referral journey

    What you are seeing

    Each stage remains tied to the person, evidence, owner, and dated follow-up.

    Problem solved

    Context separated from status as work moved between people and partners.

    Try this

    Complete the next step, add a local note, and watch the journey update.

  4. 04

    Resource handoff

    What you are seeing

    Current resource information becomes the beginning of a complete referral.

    Problem solved

    Partner details aged quietly and were recopied into separate trackers.

    Try this

    Search sample resources and begin a prefilled, browser-local handoff.

What the concept connects

Kinship

  • Shared status definitions and named ownership
  • Language and communication preferences in context
  • Journey, activity, and next step in one record
  • Resource-to-referral handoff builder
Prototype boundary

This is not an electronic medical record and makes no compliance or health-outcome claim. It does not transmit referrals, messages, or personal records.

Next application

Construction project control

Fieldstone

Explore case study

Have a workflow that deserves its own system?

Bring the people, records, exceptions, existing tools, and decisions. We will help define the smallest complete application worth building.

Discuss your application