What a completion record looks like
Every learner gets one when they finish. This is a sample.
Completion record
- Name
- Sample learner
- Course
- SQL Foundations — answer a manager's questions from a database you did not build
- Completed
- 8 November 2026
- Project
- View the dashboard →
- Skills demonstrated
- Opening a database file in a browser and establishing what it holds before trusting it · Retrieving rows that meet several conditions at once, sorted and limited deliberately · Establishing what values really are — numbers stored as text, absences, and one category spelt several ways — before computing with them · Counting and totalling, and knowing which count ignores absent values · Answering a question per group, filtering groups, and finding duplicates nobody mentioned · Joining two tables and checking what the join lost · Verifying your own answer against the row count before reporting it
What was built
An answers file you keep: the statements you wrote, still runnable, that answer one question per session about a wholesale supplier's two years of orders — what was sold, to whom, when, where, and how much of what the file says can be trusted.
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.