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 integrations that stay inert
until they are pointed at real infrastructure inside the boundary.
Result: the closed network is the design target, not a
configuration that has to be discovered to be broken.
