What a completion record looks like
Every learner gets one when they finish. This is a sample.
Completion record
- Name
- Sample learner
- Course
- Word Foundations — turn a draft nobody can navigate into a report you can hand over
- Completed
- 8 November 2026
- Project
- View the dashboard →
- Skills demonstrated
- Getting an existing document into the web version of Word and knowing where it then lives and what is keeping it · Telling a heading from a line that merely looks like one, and reading the style a line is carrying before trusting anything built on it · Applying heading styles from an agreed plan rather than by eye, and matching a document's wording to the plan it was written against · Building a contents list the software maintains, and knowing why the word Contents is deliberately not a heading · Starting a section on a page of its own with a page break instead of a run of empty lines · Using find and replace to make one name one name, and knowing the difference between replacing one and replacing every one · Turning typed characters into a real list, and saying why that matters · Repairing a table against the export it was built from: removing what should not be there, ordering it, and giving it a style · Making a document agree with its own appendix, and checking that it still does · Putting a header and page numbering on a document, and handing it over with the permission you meant
What was built
A report of several pages in Word for the web: every agreed section carrying a real heading style, a contents list the software builds from those headings and rebuilds when they change, one name written the same way everywhere, the sampling points as a real bulleted list, an appendix table with nothing in it the client should not see and the rows in date order, a header carrying the firm and the report, page numbering in the footer that says which page of how many, a copy downloaded to your own machine, and a link you chose the permission for.
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.