What a completion record looks like

Completion record

Name

Sample learner

Course

Python Foundations — answer a manager's questions from a file you did not make

Completed

8 November 2026

Project

View the dashboard →

Skills demonstrated

Reading a file somebody else exported into Python and establishing its size and shape before claiming anything about it · Selecting columns and filtering rows on several conditions at once, in an order chosen on purpose · Establishing what values really are — money read as text, two kinds of absence, one category written many ways, and dates the reader refuses — before computing with them · Counting and totalling, and knowing which count skips the rows with nothing in them · Answering a question per group, and finding repeated records that were inside an earlier total · Joining two tables and stating what the join lost · Checking an answer against the row count before reporting it

What was built

An analysis notebook you keep: the cells you wrote, still runnable from the first to the last, answering 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 export 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.