Ascend
Ascend turns documents you already have into a course people can take: modules, lessons and a test, written solely from the files you assign to it. Publish it to your profile and anyone with the link can sit it — contractors, new starters, franchisees, resellers, customers — with an email address and no account to create. You see who passed, and which questions people keep getting wrong.
The handbook exists. The standard operating procedure exists. The safety brief, the data-retention policy, the onboarding pack — they all exist, as a PDF somebody emails and everybody files.
What is missing is the twenty minutes it would take to turn that PDF into something a person actually works through, and the test at the end that tells you whether any of it landed. So it never gets made. The document goes out, an acknowledgement comes back, and the acknowledgement is the only evidence anyone has — which is evidence that a file was opened, not that a person understood it.
Ascend closes that gap in the place the documents already live. Open a project, choose the files, and it writes the outline, the lessons and the questions from them. What comes out is a course, on your public profile, that anyone can take from a link.
This is the whole feature, and it is the reason to use it rather than a chatbot. A compliance course written half from your retention policy and half from what a model believes about retention policies is worse than no course at all — because it is confidently wrong in exactly the places nobody would think to check.
Every lesson and question traces back to one of your assigned documents, checked before it is saved. This is a rule applied to what comes back, not an instruction the model is trusted to follow; it is a check applied to what comes back.
Generation with no documents is turned down before a single model call is made — rather than quietly falling back on general knowledge. It is why every Generate button stays greyed out until you have assigned something, and why it tells you so.
It draws on exactly what you switched on — your documents, in your project, and those alone. The list of what a course was written from is on the course.
The reason internal training does not reach contractors, franchisees or customers is almost never the training. It is the account.
Somebody has to be provisioned, licensed, invited, chased, reset and eventually removed — and for a forty-minute course taken once, that work costs more than the course is worth. So the course goes out as a PDF instead, and nobody finds out what happened to it.
A published Ascend course lives on your public profile. You send a link. The person reads the lessons one at a time, gives a name and an email, sits the test, and gets their result on the screen and in their inbox. There is no password, no invitation, no seat to buy back, and nothing for you to clean up afterwards.
Who has actually taken it — and which parts of your own document nobody understood.
A list of everyone who has sat it, their score, their best attempt and the date. Exportable, and yours to remove a person from.
Per-question difficulty across everyone who has taken it. A question two thirds of people fail is usually not a hard question — it is a paragraph in the source document that does not say what you thought it said.
If you turn cohort results on, each person is shown the average, the spread and their standing in plain words — “above two thirds of the people who have taken this” — rather than a bare percentile.
Worth being exact about, because the gap between “we can show people took this” and “we can show people are certified” is the kind of gap that only becomes visible in an audit.
Ascend records that a person entering a particular name and email address answered these questions, this way, on this date. That is a real and useful record, and for a great many things — an internal policy, a contractor briefing, a product refresher, a franchise standard — it is exactly the record you want. It is not an accredited qualification, and it does not verify that the person at the keyboard is who they say they are. If your obligation is a regulated certification with proctoring and an accrediting body behind it, this is not that, and we would rather say so here than have you find out later.
We build alongside a small, deliberately chosen group of researchers and teams — close enough that what you ask for tends to ship. Tell us what you research, and we'll open the door.
Request your invitation