What a completion record looks like

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

Sample

Completion record

Name
Sample learner
Course
Notion Foundations — turn a raw export into a service desk anyone can read
Completed
8 November 2026
Project
View the dashboard →
Skills demonstrated
Bringing an exported file into Notion as a database, and reading what the software decided about every column before trusting any of it · Choosing a property type for a reason, and knowing what a wrong type stops you doing · Repairing the defects an export arrives with — a note row, a name written several ways, a stray space, a word where a number belongs, a code no reader knows, an empty cell a count depends on · Building views that each answer one named question, and knowing that a view's settings are its own · Reading a count and a total off a database, and checking either against something derived another way · Writing a formula property that repairs a column, and explaining it a piece at a time · Relating two databases so that one can count the other, without duplicating either · Collecting new records through a form, and knowing where the answers land · Publishing a page to the web, saying exactly who can then see it, and taking it down again

What was built

A Notion page holding a service-job database of a few hundred jobs, every property the type it should be, four formula properties — two repairing defects you found yourself and two banding a number into labels you can group by — a table view and a board view that answer named questions, a chart, a second database of technicians related to the first with a rollup that counts their work, a form that adds a new job, a reusable job template, and the whole thing published at a web address you can hand to a stranger.

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

Session 1Get in, and get the data in4 October 2026
Session 2A database you can trust11 October 2026
Session 3Views that answer a question18 October 2026
Session 4Formulas that repair what remains25 October 2026
Session 5Two databases that know about each other1 November 2026
Session 6Collect it, publish it, defend 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.