What a completion record looks like
Every learner gets one when they finish. This is a sample.
Completion record
- Name
- Sample learner
- Course
- R Foundations — turn an export you did not make into an answer you can defend
- Completed
- 8 November 2026
- Project
- View the dashboard →
- Skills demonstrated
- Reading a delimited export into R and confirming its size against the file it came from · Reporting what a file actually contains: column types, distinct values, missing values and repeats · Repairing text, numeric and duplicate faults in code rather than by hand, proving each repair · Summarising a table by group and stating what the summary leaves out · Drawing a summary so that somebody who was not there can read it · Writing results out as a file and re-running the whole script to prove it reproduces
What was built
A script you keep: a few dozen lines of R that read one export of a wholesale supplier's orders, say what is wrong with it, fix each fault in code, total the money by region, draw the totals and write the answer out — runnable start to finish, on a file you have never seen.
The 6 sessions, and when each was completed on their own
Each session was completed twice: once with step-by-step guidance on one company’s data, then on a second company’s data from a brief, with guidance only when asked. Every check passed on both. Alongrail records the sessions, the checks and the dates; the dashboard itself is the learner’s own, hosted where they chose.
The record is a description of work you did, not a claim about you. Anyone who opens it can see the work for themselves. It stays private until you publish it, and you can unpublish it at any time.
The name, the course, the date, the skills and the link to the dashboard: that is the whole of it. Nothing on it is about you that you didn’t do.