What a completion record looks like

Every learner gets one when they finish. This is a sample.

Sample

Completion record

Name
Sample learner
Course
Visual Studio Code Foundations — a working environment you set up, and a project you shipped from it
Completed
8 November 2026
Project
View the dashboard →
Skills demonstrated
Installing and opening a code editor on a folder, and trusting a workspace deliberately · Reading and editing files, with the preview alongside · Choosing extensions by publisher and identifier, and recording the choice with the project · Workspace settings against user settings, and a formatter the project owns · Formatting a file, and reading the Problems panel · Initialising a repository, ignoring a file, staging and committing from the editor's own view · Searching a project, fixing a fault, and reading the change as a difference before committing it · Discarding an unwanted change safely · Documenting how to work on a project so the next person gets the same environment

What was built

The society's folder opened as a Visual Studio Code workspace, with the extension recommendations and the workspace settings recorded inside the project, a Prettier configuration the project owns, every source file formatted, the stylesheet's bad property and the script's wrong file name fixed, a readme that says how to work on the site, and a Git repository with three commits and an ignore file, all made from the editor's own views, with five short terminal commands and no other typing beyond lines the course gives exactly.

The 6 sessions, and when each was completed on their own

Session 1Install, open the folder, and change one thing4 October 2026
Session 2Choose your extensions, and keep the choice with the project11 October 2026
Session 3Let the project decide the formatting18 October 2026
Session 4Source control, from nothing25 October 2026
Session 5Find the fault, fix it, prove it, commit it1 November 2026
Session 6Ship it8 November 2026

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.