A multi-division academy consolidates access
A training organization runs four schoolhouses, each with several groups and dozens of
courses. Today a new deputy chief needs access granted course by course, which takes a
week and is never quite complete — the gaps surface months later when someone cannot
open a report they were supposed to own.
In Guidepost that person is placed once, at their schoolhouse. Everything beneath the
placement becomes visible and manageable in the same act, and nothing beneath a
different schoolhouse does.
Result: access provisioning stops being a checklist and
starts being a consequence of the org chart, which is the only version anyone actually
keeps current.
A course director prepares next fiscal year
Planning a year of course runs means knowing what is already booked, which weeks
collide, and where instructors are committed twice. That picture normally lives in a
spreadsheet that is out of date the moment a session moves.
The Guidepost calendar shows course run windows as bars and class sessions as markers on
the day, at day, week and month views, paging through a two-year window — six months
back and seventeen forward — so next year is reachable without leaving the page. A new
course or session can be started from the day itself, with the date pre-filled.
Result: next year's schedule is planned in the same
place it will be delivered from, so there is no second copy to keep honest.
An instructor gates a course on readiness
A technical course keeps starting with a cohort of wildly mixed background, so the first
two days are spent leveling rather than teaching. Asking by email produces a handful of
replies and no usable picture.
The instructor builds a short survey and marks it as the course's pre-course
questionnaire. A student completing enrollment is taken straight to it, and enrollment
proceeds once it is done. Responses come back as charts, exportable to PDF, with staff
notified as they arrive.
Result: the cohort's actual baseline is known before
day one, from every student rather than the ones who replied.
A schoolhouse publishes for its graduates
Alumni of a certification course need updated procedures after they finish — material
that is genuinely for them, must not appear inside the course, and must never become one
more thing a current student has to complete.
An author marks a module "alumni only" on the same Build page, using the same tools and
block types. It disappears from the course entirely and appears on the site-wide Alumni
page for anyone holding that course's certificate, grouped alongside everything else
they have earned.
Result: a continuing relationship with graduates,
without touching the course anyone is currently trying to finish.
An audit asks who approved what
A review asks how a particular cohort was enrolled, who approved each person, when
certificates were issued and on what basis. Reconstructing this from mail threads and
exported spreadsheets takes days and satisfies nobody.
The roster already carries approval tracking — who approved an enrollment and when — as
live fields shown identically on the roster and the course detail page. Certificates are
issued on completion and independently verifiable by code, and every administrative
action is attributable and timestamped.
Result: the answer is a page, not a project.
An organization trains on a closed network
The training environment has no route to the public internet, and will not be granted
one. Most platforms treat that as a deployment edge case, and it surfaces as fonts that
never load, embeds that hang, and features that quietly do nothing.
Guidepost is built for closed and air-gapped environments from the ground up: no public
internet dependency at runtime, no external data store, and nothing that attempts a
connection out of the boundary on its own.
Result: the closed network is the design target, not a
configuration that has to be discovered to be broken.
A new customer onboards a thousand people
An organization arrives with a thousand employees who all need accounts before anybody
can be enrolled in anything. There is no public self-registration — deliberately — so
every one of those accounts has to be created by an administrator.
Their existing list of people goes in as a spreadsheet. The whole file is validated
before a single account is created, so a role that is not a real role, or the same
username twice, stops the import with the row named rather than leaving half an
organization in place. What comes out is one single-use sign-in link per person, which
their own administrators distribute through the channel they already use. The platform
emails nobody.
Result: the first day is an upload rather than a
fortnight, and re-running the same file next month is safe rather than destructive.
A briefing that should not be a course
A policy changes on Monday and everybody has to know by Friday. Building a course for it
means a course shell, an enrollment for every person and a completion figure nobody will
look at — three days of work for four minutes of content, which is why this material
usually goes out as an email instead and is usually not read.
An ISD publishes it as a micro-lesson: a summary, the video, a short body and two
knowledge checks on one screen, live to every signed-in account the moment it is
published. Where it is only the video that matters, it goes up as an informational video
with its captions and nothing else around it.
Result: short material stops being either a course it
does not warrant or an attachment nobody opened. What it deliberately does not become is
a compliance record — that is still what a course and a certificate are for.
A procurement review asks about accessibility
A review asks whether the platform meets WCAG 2.1 AA and whether there is a VPAT. The
convenient answer is yes to both. It is also the answer that gets found out.
What we send is the internal assessment itself: which pages have been scanned, under
which rule set, and what was found and fixed — alongside the parts nobody has looked at,
including that no screen-reader pass has been run and that three hundred and seven
elements have no measured contrast ratio at all. There is no VPAT today, and you hear that
from us before a decision rather than after one.
Result: a reviewer gets something they can check instead
of a claim they have to take on trust, and the work a real conformance report would need
is named rather than implied.
