Deepdive

Deepdive · modules

The operating layer behind accountable programme delivery.

DARE Nexus brings the programme workflow together — from participant management and supervised activities to evidence review, reporting and next-step coordination. Modules are configured for each institution’s roles and information requirements.

Modules

Ten configurable modules, one six-stage journey

Filter by stage to see which modules support it.

Programme & workspace management

ConfigureRoute / Close
Problem it solves
Programmes start without agreed rules, roles or indicators.
Who uses it
Programme owner, programme manager
Typical record / output
Versioned programme configuration and decision-ownership map
Required owner approvals
Programme owner; product owner

Participants & case records

OnboardAssess
Problem it solves
Duplicate identities, missing consent and lost case history.
Who uses it
Intake workers, data steward, participants
Typical record / output
One reconciled record per person, with consent and status
Required owner approvals
Data steward; DPO / privacy owner

Learning, assignments & assessment

AssessActivate
Problem it solves
Attendance is mistaken for learning; assessment is inconsistent.
Who uses it
Facilitators, assessors, participants
Typical record / output
Assignment submissions and assessments against a rubric (optional AdaptSprint or LMS link)
Required owner approvals
Assessment owner; issuing body for any credential

Field tasks & work orders

Activate
Problem it solves
Field activity is hard to supervise and evidence is scattered.
Who uses it
Field teams, supervisors
Typical record / output
Work orders and supervised task logs (location only where justified and approved)
Required owner approvals
Programme owner; safety and privacy owners

Evidence capture & review

Evidence
Problem it solves
Work is collected but never reviewed, corrected or accepted.
Who uses it
Reviewers, facilitators, evaluators
Typical record / output
Evidence with submitted / reviewed / accepted / rejected status and reviewer
Required owner approvals
Authorised reviewer; programme owner

Monitoring, evaluation & reporting (MEAL)

EvidenceRoute / Close
Problem it solves
Reports mix registrations, outputs and outcomes.
Who uses it
M&E officers, funders, programme owners
Typical record / output
Indicator definitions, denominators and cohort reports with limits stated
Required owner approvals
Evidence lead; independent evaluator where needed

Referrals, services & partners

Route / Close
Problem it solves
Next steps have no owner, so follow-up fades.
Who uses it
Programme owner, service partners
Typical record / output
Referral or next action with owner, reason and follow-up date
Required owner approvals
Programme owner; receiving partner

Funding & resource activation

Route / Close
Problem it solves
Funding status and evidence are tracked in disconnected spreadsheets.
Who uses it
Programme owner, funders, finance partners
Typical record / output
Status coordination and reconciliation — financial decisions stay with the authorised institution
Required owner approvals
Financial institution / funder; legal owner

Governance, access & integrations

Configure
Problem it solves
Unclear data control, access and system boundaries block procurement.
Who uses it
CIO, procurement, data protection
Typical record / output
Role-based access, tenancy and approved integrations
Required owner approvals
CIO / technical owner; DPO

Built on CoreXOS

Evidence
Problem it solves
A record must show its source and that it has not been changed.
Who uses it
Technical owners, reviewers
Typical record / output
Evidence provenance and status checks, where scoped and accepted
Required owner approvals
CoreXOS release owner; programme owner
Architecture

Programme owners decide. DARE Nexus coordinates. CoreXOS supplies the trust layer underneath.

  • Institution / programme owner — eligibility, approvals, referrals, funding and outcome decisions.
  • DARE Nexus programme layer — workflow, participants and cases, activities, reviews, routing, reporting.
  • CoreXOS (always underneath) — governed identity, policy, evidence provenance and status checks. Capabilities such as record anchoring are activated per programme.
  • External authorities and specialists — legally or scientifically authoritative findings.

A tamper-evident record shows a file is unchanged. It does not prove the training, identity, payment or outcome behind it is true.

Trust & architecture
3D illustration of the DARE Nexus architecture: the six programme stages across the top, the closed-loop engine in the middle, and a base of trust, data and integration services underneath.
TopThe six stages every participant moves through.MiddleDARE Nexus runs the loop: cases, reviews and routing.BaseCoreXOS trust infrastructure, live underneath; capabilities activated per programme.

Scope the modules your programme needs.

We start bounded: one programme, the modules it needs, and acceptance criteria agreed up front.