What a completion record looks like

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

Sample

Completion record

Name
Sample learner
Course
HubSpot CRM Foundations — turn two raw exports into a CRM anybody can trust
Completed
8 November 2026
Project
View the dashboard →
Skills demonstrated
Making a free CRM account and finding the three kinds of record it keeps · Importing a file into a CRM: choosing the object, mapping every column to a property deliberately, and naming the import so the records can be found again · Reading what an import actually did — what it created, what it updated, what it linked and what failed — from the import's own record rather than from memory · Knowing which field a CRM deduplicates each kind of record on, and why the records created can be fewer than the rows supplied · Linking people to the firms they work for, and explaining the ones nothing could link · Repairing values a CRM will not repair for you, by filtering and sorting to find them first · Defining a property for a reason, choosing its field type, and working inside a ceiling on how many you may have · Filling a property for every record by an import that updates rather than creates · Reading an import's error file, and putting the rows that never arrived in by hand · Working a pipeline: finding the records whose stage contradicts what is known about them, moving them, and reading what the totals do · Building saved views and a segment that each answer one named question, and handing one to somebody else · Saying, of any figure on a CRM screen, exactly which records it counted

What was built

A free HubSpot account holding a few hundred contacts, several dozen customer companies and a hundred-odd deals sitting in the pipeline's own stages, with the people linked to their firms, the company names written one way instead of four, a property you defined yourself and filled by an import that updated rather than created, the deals that never arrived found in the import's error file and put in by hand, the stages corrected where the record said one thing and the outcome said another, every deal owned, a segment a colleague can be sent, and a shared view that answers a named question. Four hundred and seventy guided minutes on the first company, then two hundred independent minutes rebuilding it from a brief on the second — just over eleven hours.

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

Session 1Get in, and get the first records in4 October 2026
Session 2The firms, and the records that point at each other11 October 2026
Session 3A field you made, and why18 October 2026
Session 4Deals that arrive, and deals that don't25 October 2026
Session 5Making the pipeline tell the truth1 November 2026
Session 6Something a colleague can open8 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.