Funded learning operations
Connect the learner record to the funding workflow.
Journey+ is the funded-learning product direction in the TechGeek ecosystem. It is aimed at training providers, colleges and adult-education teams that need learner records, delivery evidence and funding administration to tell the same story. A useful evaluation follows a record from enrolment through delivery and into the organisation’s return-preparation process.
Guided product evaluation
The product information distinguishes current capabilities from planned additions. Confirm supported funding streams, access and the exact workflow you need in a current walkthrough.
Illustrative workflow
Follow the work through Journey+.
Record the learner and learning
Identify the permitted learner information, relevant course or aim, delivery plan and the organisation responsible for maintaining it.
The provider’s job
Make delivery and administration easier to reconcile.
Funded learning crosses several teams. An enrolment record may be maintained by administration, evidence by delivery staff and a return by a specialist data team. The evaluation should establish how those records connect and how the organisation identifies missing or inconsistent information before relying on it.
The Journey+ direction covers learner records, contracts and allocations, qualifications and delivery plans, evidence, progress reviews, learner import and ILR-file preparation. Its product material addresses adult skills, bootcamps, advanced learner loans and 16-to-19 provision. The supported tasks and rule versions for your provision require a current demonstration.
A representative record journey
Follow the information all the way through.
An effective walkthrough should use one sample learner record across the stages. This shows whether information is being carried forward or merely re-entered in disconnected screens.
Record the learner and learning
Identify the permitted learner information, relevant course or aim, delivery plan and the organisation responsible for maintaining it.
Connect delivery evidence
Review how evidence, progress and changes are recorded, and how the right staff identify the next action.
Reconcile the funding context
Check the relevant contract, allocation and supporting records. Separate stored funding information from a confirmed eligibility or claim decision.
Prepare the return
Demonstrate the supported checks and file output, the person responsible for submission and the way the organisation records what was returned.
Current scope
Keep implemented and planned work separate.
The reviewed product information distinguishes its main feature list from planned additions. That distinction matters more than a long capability list. Ask the product team to demonstrate the exact version and environment proposed for your provision.
| Product area | Evaluation boundary |
|---|---|
| Learner records, evidence and reviews | Demonstrate creation, authorised changes, visibility and the resulting history. |
| Contracts and allocations | Confirm the supported funding model and how it relates to delivery records. |
| CSV learner import and ILR preparation | Confirm the actual mappings, validation, exceptions and current schema support. |
| Eligibility, LARS and batch ULN checks | The reviewed product information lists these as planned; do not assume they are available. |
| Learner/employer sign-off, API access and AI document checks | The reviewed product information lists these as planned; establish current status before relying on them. |
A worked evaluation
Use a record with something missing.
A clean demonstration is helpful, but an incomplete record reveals how a system supports a data team. Choose a fictional learner and deliberately omit information that your return-preparation process would need.
How it relates to Journey
Choose the workflow before the product name.
Journey’s published product proposition centres on apprenticeship management. Journey+ centres on broader funded-learning administration. The shared naming does not establish shared accounts, an automatic data transfer or identical editions.
If your organisation runs more than one form of provision, describe the responsibilities and records that need to connect. The team can then confirm which product fits each task and whether a handoff, migration or integration needs separate work.
Before you commit
Bring the contract context and the operational questions.
Prepare a non-sensitive description of the provision, the learner-record systems in use, the funding or return cycle and the people responsible for it. Agree an evaluation against representative sample records before planning a wider move.
- Identify the current rule and specification versions your team works to.
- List the record mappings, exports and reconciliations you require.
- Include an incomplete record and a changed record in the test scenarios.
- Confirm roles, training, support and how an error is recovered.
- Keep responsibility for eligibility, evidence and submission with the appropriately authorised team.
Questions before the next step
A clearer view of Journey+.
Is Journey+ the same product as Journey?
They have different public propositions. Journey focuses on apprenticeship management; Journey+ covers broader funded-learning administration. Confirm product fit, account arrangements and any data handoff separately.
Does Journey+ submit an ILR return for the provider?
The described workflow leaves the provider responsible for downloading the prepared file and uploading it to the government submission service. A generated file is not evidence that a return has been submitted or accepted.
Are funding eligibility and learner-record checks all available?
Do not assume so. The reviewed product information lists eligibility, LARS and batch ULN checks among planned features. Ask the product team to demonstrate the current version and the tasks you need.
What should we use for an initial demonstration?
Fictional or appropriately anonymised learner examples, your required outputs and the questions the data and delivery teams need answered. Do not send learner records through a public website enquiry.
Make the next conversation useful
Start with the work.
Explore the fit.
Bring your workflow, the people involved and the decisions you need to make.