Skip to content

How THREVO works

From Personal Wellbeing to Organisational Resilience. One Connected Journey.

THREVO brings people, intelligent support, professional care and organisational intelligence together through one unified operating system.

Employees receive a private and connected wellbeing experience. Practitioners provide appropriate professional support. Managers and organisational leaders receive approved insights that help them understand and improve organisational resilience.

Every experience works together while maintaining clearly defined privacy and access boundaries.

Private journey

  1. 01Employee app
  2. 02Signals
  3. 03Intelligence
  4. 04Care

Employer-facing journey

  1. Privacy gate
  2. Organisational insights

The employee path stays personal until an approved aggregate passes the privacy gate.

One connected experience

Six Steps. One Continuous Wellbeing and Resilience Journey.

THREVO connects daily employee experiences with personal insights, guided support, professional care and organisational intelligence.

Step 01

Join and get started

The organisation establishes its THREVO environment and enrols eligible employees.

  • Organisation setup.
  • Employee roster onboarding.
  • Secure identity creation.
  • Role assignment.
  • Authentication.
  • Consent and privacy preferences.
  • Access to the employee application.

The employee receives secure access to their personal THREVO experience.

Understanding the system

Information Flows Through Controlled Layers.

THREVO is built around four functional layers, supported by shared platform services and a mandatory privacy gate for employer-facing organisational reporting.

The employee journey

A Private Space for Everyday Wellbeing and Support.

Employees interact with THREVO through a dedicated mobile application, with a PWA fallback.

THREVOPrivate

01

Today

A personal daily dashboard for the employee’s own wellbeing experience.

These are the named employee surfaces. The phone is an experience map, not a published production screenshot. Later-release items, including production video and the full programme library, are not shown as available.

Connected care

From Finding Support to Professional Care.

  1. 01

    Employee need

  2. 02

    Guided support

  3. 03

    Practitioner discovery

  4. 04

    Matching suggestions

  5. 05

    Employee choice

  6. 06

    Appointment booking

  7. 07

    Care session

  8. 08

    Outcome measures

  9. 09

    Follow-up

How a session is reached

  • Practitioner profiles are verified before they are offered.
  • Availability comes from the practitioner’s own calendar.
  • The employee selects the practitioner.
  • Booking creates the session. Video, audio and chat are the session modes in the R1 care scope. Production video is an R3 item.
  • Clinical notes stay confidential. Outcome measures are structured records inside the authorised case.

Practitioner portal

  • Practitioner profile
  • Availability calendar
  • Assigned caseload
  • Booking list
  • Session workspace
  • Notes and outcomes

A practitioner sees an authorised case and the information the employee has chosen to share. Other practitioners’ notes, and employer analytics, stay outside that boundary.

Intelligence with human oversight

AI-Assisted Support. Human-Led Care.

THREVO uses its AI Wellness Companion to provide guided self-help and safety-aware triage while preserving a clear pathway to human support.

Normal support path

  1. Employee
  2. AI Wellness Companion
  3. Guided self-help
  4. Relevant resources
  5. Personal support

Safety escalation path

  1. Employee input
  2. Deterministic crisis rules
  3. Safety event
  4. Authorised navigator or clinical staff
  5. Human handoff
  6. Follow-up
  • Deterministic rules run before model processing.
  • R1 crisis support is in English and Hindi.
  • Human handoff follows the applicable tiered SLA.
  • Clinical access stays with authorised staff.
  • The safety event is written to an audit trail.
  • Clinical governance remains with people, not with the model.

A generative model does not make a clinical diagnosis and does not replace emergency services. Additional companion languages are R2. A production LLM is R3.

Measuring organisational resilience

Understand Resilience Through Structured Assessment.

THREVO uses its Organisational Resilience Quotient and Employee Care Score framework to support structured organisational measurement.

  1. 01

    Survey and eligible inputs

  2. 02

    Assessment processing

  3. 03

    Dimension calculations

  4. 04

    Coverage and confidence

  5. 05

    ORQ and ECS outputs

  6. 06

    Approved organisational reporting

ORQ

The organisational resilience assessment calculated using THREVO’s approved methodology. The headline score stays based on signals shared by the workforce.

ECS

A complementary employee care measure within the organisational intelligence framework.

Survey-led

Structured survey inputs. This is the R1 assessment path.

Hybrid

Survey information combined with eligible additional signals. This mode is part of the R2 scope.

Biometric-enriched

Eligible biometric enrichment only after written legal approval, appropriate consent and bias correction. It is not a default.

The full-product direction is eight dimensions. R1 supports six, and D7 and D8 need sign-off before they are treated as in scope. Names, weights and formulas stay in the versioned methodology. Coverage and confidence sit beside the headline score. They are not the score itself. Wearable readings do not enter employer-facing ORQ by default.

Privacy by design

Your Personal Experience Is Not Your Employer's Dashboard.

THREVO separates individual wellbeing experiences from organisational reporting through structural privacy controls.

  1. 01

    Employee private data

  2. 02

    Random employee token

  3. 03

    Isolated identity-to-token vault

  4. 04

    Purpose-specific consent check

  5. 05

    Anonymisation gate

  6. 06

    Aggregation and suppression

  7. 07

    Approved organisational insights

  • 1. Personal tables use random employee tokens.
  • 2. Identity-to-token mapping remains isolated in the vault schema.
  • 3. Analytics uses organisation-salted token hashes.
  • 4. Free text is encrypted per person and never leaves the operational store.
  • 5. Consent is checked on every read.
  • 6. Groups smaller than 10 are suppressed.
  • 7. Complementary suppression protects hidden totals.
  • 8. Differencing protection limits repeated-query disclosure.
  • 9. Exports contain only approved aggregates and are watermarked and audit-logged.

What employers never see

  • Individual wellbeing scores.
  • Personal health records.
  • Employee names linked to private wellbeing data.
  • Personal free text.
  • Wearable health readings.
  • Individual practitioner notes.
  • Life Transition case content.
  • Lists of employees based on private wellbeing information.

One Platform. Seven Role-Based Experiences.

Employee

Own personal information, consent, own case files and selected support resources.

One identity may carry more than one role. Switching roles moves the person into a separate application shell, with a separate API access boundary.

Engineered as one system

One Modular Architecture. Multiple Connected Experiences.

THREVO is specified as a modular monolith with 22 canonical NestJS modules, supported by a Python FastAPI service for scoring and machine learning.

User experience

  • React web.
  • React Native.
  • Expo.
  • PWA fallback.

Backend

  • NestJS modular monolith.
  • 22 canonical modules.
  • Controlled module interfaces.
  • API gateway.

Scoring and intelligence

  • Python FastAPI.
  • ORQ and ECS calculations.
  • Scoring services.
  • Machine learning services.

Data and infrastructure

  • PostgreSQL 16.
  • TimescaleDB.
  • pgvector.
  • Valkey.
  • MinIO.
  • Keycloak.

Every module has a defined responsibility and a controlled interface. External infrastructure sits behind ports, so an implementation can be replaced without changing the calling module. R3 is the stage for production substitutions. This diagram is the specified architecture. It is not a statement that every service is already running in production.

From foundation to official launch

A Carefully Governed Path to Full Product.

The same interface contracts and tests are used when Part A adapters are replaced by Part B production services. R2 and R3 items below are planned. They are not deployed capabilities.

R1

Defined scope

Core product and pilot

  • Employee daily experience.
  • Core AI companion and crisis handoff.
  • Practitioner booking and sessions.
  • Life Transition Help starter content.
  • HR console.
  • Executive Centre.
  • Initial ORQ and ECS.
  • Privacy foundation.

R2

Planned

Full product

  • All eight ORQ dimensions.
  • Three assessment modes.
  • All 13 Life Transition modules as content lands.
  • All 18 reports.
  • Survey builder.
  • Trained team-level risk models.
  • Wearable and HRMS adapters against free sandboxes.

R3

Planned

Official launch

  • Production infrastructure substitutions.
  • Production identity and video services.
  • Production integrations.
  • Required security and operational readiness.
  • Production support runbooks.

See How a More Resilient Organisation Works.

THREVO connects personal wellbeing, intelligent support, professional care and privacy-protected organisational intelligence in one unified ecosystem.