Data and integrations

Visible data exchange, without pretending every connector is live

Use built-in ILR, calendar and versioned imports now, with tenant-scoped health and supported recovery; add external OAuth only after real approval.

Journey / Director Dashboard
JS
Dashboard
Learners
Funding
Compliance
Quality
Gateway
Director Overview

Provider performance and risks at a glance.

Active Learners

1,248

At Risk

34

Reviews Overdue

12

Achievement Rate

68.2%

At-Risk Learners
Learners requiring immediate intervention.

Alex Carter

Software Developer L4

OTJ behind target
Urgent

Priya Shah

Business Administrator L3

Missed review
Warning

Sam Jenkins

Data Analyst L4

Safeguarding concern
Urgent
Funding at Risk (Current Period)
ESFA completion payments at risk due to missing evidence.
Missing ILR signatures£12,450
Late gateway evidence£8,200
BIL 60+ days£3,100

Illustrative integration-health register with sample data.

Definition

What integrations does Journey support?

Journey currently supports built-in ILR export, an internal delivery calendar, versioned applicant CSV import and audited transactional email. Google Calendar and Microsoft 365/Teams connectors require customer OAuth and licence approval before they can be connected.

Are Google Calendar and Microsoft Teams connected in Journey today?

Not by default. Journey shows those connectors as approval required until a provider completes the correct Google Workspace or Microsoft Entra consent. Where a viable API is unavailable, Journey uses a versioned, validated file-exchange path rather than claiming a fake integration.

Brings together what used to be separate tools

Untracked CSV overwritesHidden sync failuresUnverified connector claims

Versioned Import Centre

Preview, map, validate and apply applicant CSV data while preserving provenance and guarded rollback.

Built-in ILR and calendar

Core ILR export and delivery scheduling work without an external calendar dependency.

Integration health

Directors can see status, last success, errors, recovery guidance and approval dependencies for their tenant.

Honest connector states

External OAuth, licences and customer-specific APIs stay unavailable until they are genuinely configured and tested.

Last reviewed: July 2026

A connector register that tells the truth

Journey separates working built-in services, recoverable errors, supported file exchange and connectors that still need external approval. Administrators can see the real state without assuming that a logo means a live sync.

Frequently asked questions

Evidence-linked and accountable by design

Built so your team can trace evidence, decisions and actions

Hard tenant isolation

Every record is scoped to your organisation on each read and write — one provider can never see another's data.

Append-only audit log

Every state change is recorded against the real person who made it, so the history stands up at audit.

Versioned DfE rule packs

Funding-sensitive figures use centrally managed packs selected by start date: 2024/25, 2025/26 and published 2026/27 version 3 coverage.

Governed AI

After provider, DPIA and release approval, Advance AI is metered per tenant and prepares authorised drafts and K/S suggestions for human review. It does not make regulated decisions or change the source record.

Evidence-led security controls

Tenant isolation, access controls, audit records and governed operations are designed into the platform.

Your data and employers stay yours

No lock-in: export your data whenever you like, and your employer relationships always remain yours.

Journey is independent software and is not DfE or Ofsted approved. It does not guarantee funding or inspection outcomes.

See Journey on your own provision

Book a walkthrough and confirm the right operating scope.

Compare Journey