What a completion record looks like
Every learner gets one when they finish. This is a sample.
Completion record
- Name
- Sample learner
- Course
- Data Studio Foundations — build a report anyone can open at a link
- Completed
- 8 November 2026
- Project
- View the dashboard →
- Skills demonstrated
- Getting an exported file into a place a reporting tool can read · Reading what a connector decided about every field, and telling a decision from a defect · Repairing a field by its type, and repairing one by writing a new field alongside it · Writing text, date, counting and ratio formulas, and guarding a division · Counting things rather than rows · Filtering rows out of an answer, and knowing what a filter does and does not reach · Choosing the chart that answers the question asked · Building an interactive page a reader can drive · Stating a finding in words · Sharing on the web, and being able to say who can see what
What was built
A two-page report — where the money is, and why things come back — reading three connected spreadsheets, with eight fields you wrote and can each explain, a table a reader can sort, a control that narrows the page to one branch, a period a reader chooses, a written finding, and a link whose access you chose deliberately and can describe.
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.