COMPASS / v1.0 · PRIVATE BETA

Give your trainers their time back.

Every hour an instructor spends re-formatting a Word template is an hour they don't spend with students. COMPASS replaces the patchwork of templates, shared drives, and tribal knowledge with one structured system — so the people trained to deliver can actually be in the room, delivering.

One system — from course design through to institutional memory.

Training organisations don't need another document tool. They need a system where every course compounds into the next — where institutional knowledge stays, even when trainers rotate out. COMPASS replaces the template patchwork with structured outputs, tracked delivery, and a library that builds itself as your organisation trains.

F·01Live
Course design & document generation
TNA · Lesson Plan · SoW · Handout · Instructor notes
F·02Live
Training management & control
Approval workflows · Every document carries its history
F·03Live
Lessons learned system
Timeline capture · Observations · Lesson statements
F·04Live
Student register & tracking
Students · Cohorts · Course assignment
F·05Soon
Adaptable scheduling
Calendars · Lesson blocks · Change cascade
F·06Live
Institutional knowledge library
Unified library · Course · Lesson · Exercise linked
F·07Live
AI-powered insights
Natural language · Org-scoped · Institutional context
F·08Live
Doctrine-grounded generation
Your frameworks · Your levels · Not the model's defaults
What COMPASS replacesBEFORE
  • Word templates reformatted every course
  • Shared drives with no version control
  • Approval by email chain
  • Tribal knowledge that leaves with the trainer
  • Post-exercise debrief lost in a memo
What you get insteadWITH COMPASS
  • Documents drafted in minutes, not hours — the same work, a fraction of the time.
  • One versioned library, organisation-wide
  • Structured approval with full change history
  • Institutional memory that compounds with every course
  • Exercise outcomes feed back into the next course design

A three-stage system that compounds with every course.

Training organisations don't just need a tool that saves time on the next course — they need a system where each course makes the next one better. COMPASS is built as a loop, not a funnel.

01
Build
Design the course. Generate the documents.
Define the course once. COMPASS generates every required document — TNA, Course Design, Scheme of Work, Lesson Plans, Handouts — mapped to your own frameworks and levels.
Your frameworksYour levelsYour templates
02
Deliver
Run the course. Capture what happens.
Track exercises, capture observations, maintain the student register, and manage approvals — all in the same system the documents came from.
ExercisesRegisterApprovals
03
Compound
Every output becomes institutional knowledge.
Every document, lesson, and exercise outcome feeds your organisation's knowledge base. The next course starts with what the last one learned — not a blank page.
LibraryAI ChatOrg-scoped
↻   Knowledge feeds back into the next course design   ↻

Every document you need, drafted in three minutes.

Instructors describe the training need in their own words. COMPASS structures it into your organisation's format — reference frameworks pre-linked, performance levels mapped, and output structured for editing, not rewriting.

14
Document types
~3 min
Typical draft time
0
Data egress
COMPASS / 03
DRAFTING
Session · Active
Synced
Now drafting
  • Training Needs Analysis
  • Course Design Document
  • Scheme of Work
  • Course Training Plan
  • Training Performance Statement
  • Instructional Scalar
  • Course Evaluation Form
  • Lesson Plan
  • Student Handout
  • Instructor Notes
  • Course Presentation
  • Student Evaluation Form
  • Training Scenario
  • Class Marking Sheet
Time to draft3min

Exercise outcomes become doctrine, not memos.

Structured capture of what actually happened — timeline events, observer notes, reusable lesson statements — linked back to the courses and lessons they affect. When experienced trainers move on, their judgement stays. Every rotation leaves something behind. The next course starts stronger than the last.

Every
Event · captured
Linked
To course · lesson
Preserved
Institutional memory
COMPASS / 04
CAPTURING
Exercise · Live
Recording
Live from the field
  • T+00:27:08 · EX. SENTINEL: Comms failure · relay point 3
  • T+00:14:22 · EX. SENTINEL: Platoon crossing established
  • T+00:42:31 · EX. SENTINEL: Objective secured · assessment complete
  • T+01:08:15 · EX. AURORA: Contact sequence re-drilled at observer request
  • T+00:36:44 · EX. AURORA: Rules of engagement clarified · SO 3.2
  • T+00:19:33 · EX. NIGHTFALL: Night extraction · 2 min within tolerance
Captured asDoctrine

Data. Access. Audit. Grounding.

01
Data architecture
Structured, org-scoped, auditable
Every document, student record, and lesson lives in a structured schema scoped to your organisation. No shared indexes, no cross-tenant retrieval.
02
Audit & evidence
Every change is traceable
Structured approval workflows and version history on every generated document. When a lesson plan is challenged, the audit trail shows who changed what, when, and with whose approval.
03
Access control
Role-based, fully audited
Role-based access with full audit of who read, edited, or approved what — scoped to your organisation by default.
04
Reference doctrine
Curated and controlled by your organisation
Reference doctrine is curated and controlled by your organisation — grounded in your institutional content, not external sources.
We built COMPASS with training commanders, not around them. Every workflow in the system exists because an instructor, a head of training, or a former operator told us what they wasted their Thursday evening on — and what they were afraid would be lost when the next rotation came through.
Jo · Founder, Wisdom LabBuilt from inside the problem — for the people who spend more time formatting training than running it.

See COMPASS in action.

A 30-minute walk-through with the founder — scoped to your organisation's training profile. No slide deck. Your documents, your frameworks, your questions.

Typical response · within one working day · or email jolehndorf@gmail.com directly