Activity log brings learning activity into one clear, consistent place. It makes it easier for learners to record off-the-job learning, and easier for your team to review, report on, and evidence progress with confidence.
This article sets out what to expect and what you can do now to prepare, so adoption is smoother, your data is cleaner, and you get value from day one.
Why it's worth preparing
Clarity for learners. A simple way to record what they have done, when, and how long it took.
Confidence for delivery teams. Cleaner verification with feedback, supporting better coaching conversations.
Better reporting from day one. Consistent entries improve totals, trends, and exceptions, such as over or under planned hours.
Audit-ready record keeping. A more structured trail, reducing reliance on parallel spreadsheets.
Three things you can do now
1. Make your curriculum structure activity log friendly
Standardise module and component names so they are clear, consistent, and recognisable.
Complete any planned remapping so components reflect how you actually deliver.
Refresh short component descriptions so learners can choose confidently.
2. Set expectations for great logging and great reviews
Agree what "good" looks like: timely entries, meaningful notes, and the right component.
Confirm who reviews and approves entries, and your typical turnaround times.
Keep one source of truth. Avoid logging the same hours in more than one place.
3. Sense check planned hours and your compliance approach
Check planned hours per component are realistic, so any variances are meaningful.
Confirm your tripartite review and sign-off expectations across learner, employer, and tutor.
How rollout works
Programme by programme enablement. You can adopt activity log in phases: pilot, learn, then scale.
A clear switch for users. Once a programme is opted in, activity recording for that programme happens in activity log.
Continuity of history. Relevant existing information carries across, so you keep context.
You stay in control. You decide timing and readiness, supported by programme settings.
If you use reporting feeds or integrations
If you currently use the API or OData for off-the-job or evidence reporting, plan a small change window to move to activity log data when you opt programmes in.
Book time to test and validate downstream reports, including MIS or BI exports, compliance packs, and internal dashboards, ahead of go-live.
What to expect at go-live
Simple logging and verification. Learners record activity, and tutors review and provide feedback through a consistent workflow.
Totals plus detail. Dashboards and totals give you the headline view, with activity log holding the supporting detail.
Clearer review conversations. Reviews can be backed by current progress and recorded activity.
Export options. Improved exports support audit and record keeping.
Quick checklist
Use this list to check you're ready:
Curriculum tidy-up complete (names, remaps, concise descriptions)
Planned hours reviewed and updated where needed
Agreed guidance for what to log (examples, minimum note quality, turnaround times)
Single source of truth agreed, with no duplicate hours across tools
Programme opt-in plan confirmed, pilot first, then scale
If you use integrations: changes identified and a short test window booked
Adopting activity log across your programmes is also an important step towards eligibility for the learner app early access programme.
Next steps
Talk through any questions and your rollout plan with your Implementation Consultant or Customer Success Manager. They can walk you through configuration choices, share examples of strong entries, and help you understand what success looks like in the first few weeks.