Framework

Module template

The 12-section structure every module follows.

Module Template

Phase 2 deliverable · v0.1 · 2026-05-19

Every module in modules/M[NN]-*.md ships against this structure. Section order is fixed. Section content is module-specific. The template is the contract — facilitator and learner can move between modules without re-learning the layout.

Frontmatter

YAML frontmatter at the top of every module file:

---
module: M[NN]
phase: [A · Foundations | B · Site Acquisition & Contracting | C · Build, Commission, Launch | D · Operate | E · Lifecycle]
title: [module title in sentence case]
duration_classroom_minutes: [integer]
duration_prework_minutes: [integer]
duration_ojt_minutes: [integer or null]
audience: [Owner + DBM | Owner-led | DBM-led]
prerequisites: [list of module IDs that must be completed first, or "none"]
source_documents:
  - [Ops Manual section, FDD item, MSA clause — each tagged primary or [CONFIRM]]
version: v0.1
last_reviewed: YYYY-MM-DD
---

Section 1 · Pre-work

What the trainee must complete before the classroom session. Cap at 60 minutes for any single module’s pre-work.

Format inside the section:

Required readings. Specific documents or Partner Portal sections with named locations, not vague “review the Manual.”
Required viewing. Video assets where applicable (likely added in v2 — not a v1 dependency).
Pre-session knowledge check. 5–10 closed-form questions the trainee submits before the session. Failing pre-work gates classroom attendance — same competency-assessment language as in the FDD.
Bring to session. Any artifact (lease draft, vendor list, pipeline snapshot) the trainee should bring for in-session work.

Section 2 · Learning objectives

3–5 objectives, written as observable behaviors. Verbs are operational: open, escalate, submit, reject, route, document, reconcile, de-identify. No “understand,” no “appreciate,” no “be aware of.”

Each objective is one sentence and maps to at least one assessment item in Section 7.

Example shape:

By the end of M02, the DBM can correctly classify any inbound site event into SEV 1–5 within 60 seconds using the published criteria, and can open a complete ticket including site ID, observation times, and driver impact in under 4 minutes.

Section 3 · Why this matters

One to two paragraphs. The operator-grade case for why this module is non-optional. Anchored to specific risks: financial exposure, default conditions in the Franchise Agreement, brand-promise events, regulatory consequences.

This section is where the Voice Playbook’s Acknowledged Elephant move runs — name the obvious objection (“isn’t this overkill for a charging station?”) and dispatch it with a fact.

This section is not a motivational paragraph. No “we’re excited,” no “imagine,” no “in today’s environment.”

Section 4 · Core content

The teaching material. Organized into 3–6 numbered sub-sections, each with a one-line subhead in sentence case.

Each sub-section delivers:

The rule, mechanism, or framework
The numbers behind it (response times, deadlines, dollar thresholds, percentages — sourced)
The specific document or system where the operator finds it day-to-day (Partner Portal location, Manual section, FDD item)
The most common operator error and its consequence

Density target: dense enough that a sophisticated multi-unit operator finds new substance on a re-read, loose enough that nothing reads as procedural cut-and-paste from the Manual.

Citation discipline: every claim that involves a specific number, deadline, or procedure gets a parenthetical source tag — (Ops Manual §X.X) or (FDD Item N) or [CONFIRM] for anything paraphrased from the NotebookLM draft without primary-source verification.

Section 5 · Decision drills

3–5 scenarios. Each drill:

Describes a realistic operating moment in 3–6 sentences. Specifics (time, weather, who’s involved, what’s been said) — not abstractions.
States the operator’s available actions
Asks the trainee for a specific decision and the reasoning behind it
Includes a model answer (in facilitator notes only, not in the learner-facing version) with the cited Manual/FDD/MSA basis

Drill format examples (all hypothetical — to be made concrete in each module):

It’s 11:14 pm. A driver calls the number listed on the pylon. Two posts are dark. There’s a smell of burning insulation near the cabinet base. The DBM is 40 minutes away. What does the on-site operations lead do, in order, in the next 10 minutes?
A Site Host emails: “We need a clause letting us offer free charging to our hotel guests after 10 pm. Otherwise we won’t sign.” How does the franchisee respond, and what gets escalated to whom?
The Q3 Sinking Fund balance is $14,000 below the running-balance target because of a transformer-replacement utility cost overrun. The franchisee is considering deferring this month’s deposit to cover it. What’s the correct path?

Decision drills are where competency gets built. Treat them as the heart of the module.

Section 6 · Common operator errors

A short numbered list (3–6 items) of the most predictable mistakes operators make in this module’s domain, drawn from:

Explicit “you must never” prohibitions in the Operations Manual
Material-breach triggers in the Franchise Agreement
Patterns that show up in field audits

Format per item:

The error, named in one sentence
The consequence (financial, contractual, brand)
The discipline that prevents it

This section overlaps slightly with Section 4 but earns its keep — it’s the operator’s pre-flight checklist for the topic, separable from the teaching flow.

Section 7 · Competency assessment

Two components per module:

Knowledge check (FDD-aligned “competency assessment”). 8–12 questions, closed-form or short-answer, drawn from Sections 4 and 6. Pass threshold: 80%. Trainee may retake once; second failure triggers FBC review.

Application demonstration (one per module). A scenario derived from the decision drills, scored against a rubric. Pass criteria: trainee correctly identifies the action, the responsible role, and the cited basis.

For modules with OJT (M04, M10): the application demonstration is performed at the HiON EV Facility — a Site Walk capture for M04, an inspection-log walkthrough for M10 — and scored by the facilitator on-site.

The full assessment package per module is named and cross-referenced in FDD Item 11. “Successfully complete the Franchisee Training Program” = pass every module’s knowledge check and application demonstration.

Section 8 · Job aids

The artifacts the operator takes back to the field. One section per module produces:

Checklists (e.g., Site Walk checklist; Commissioning Readiness checklist; Daily Inspection log template)
Decision trees (e.g., severity classifier; exception-request decision flow)
Templates (e.g., Site Host outreach email; FBC monthly performance commentary)
Reference cards (e.g., the SEV 1–5 response-time matrix as a single page)

Job aids live in modules/M[NN]-jobaids/ as separate files when they exceed one page. The module file lists them with paths.

Every job aid is itself voice-compliant — no exclamation points, no clichés, no filler.

Section 9 · Facilitator notes

For the trainer running the live session. Not exposed to the trainee. Includes:

Pacing. Suggested time per Section 4 sub-section; where to leave room for questions.
SME deep-dives. Which moments are best handed off to the named SME on the Training Matrix (e.g., Jim on lease economics; Joe Lewis on staffing structure; Joe Frank on operations cadence; Tony Cuomo on commissioning).
Common misunderstandings. What trainees consistently get wrong, with the corrective framing.
Discussion prompts. Questions the facilitator uses to surface assumptions before delivering the rule.
Decision drill model answers. Full reasoning with cited basis.
Recommended visual aids. Diagrams, screenshots, or live Partner Portal walkthroughs to incorporate.

Section 10 · Cross-references

Two lists:

Modules: Which other modules this one connects to, with one-line context on why. (Example for M02: M01 — role split frames who handles which severity tier; M04 — pipeline tickets are opened under the M02 system; M10 — fault escalation is the operate-phase use of the M02 severity model.)

External documents: Operations Manual sections, FDD items, MSA clauses, Lease Addendum sections — full citation list for the module.

Section 11 · Source verification log

A table tracking every [CONFIRM] tag in the module:

Claim	Current source	Primary source needed	Status
180-day Site Authorization deadline	NotebookLM §M05	FDD Item 11 + Franchise Agreement	unverified
…	…	…	…

Updated as primary sources are obtained. The full set across all modules consolidates into reference/Source-Gaps-Log.md.

Section 12 · Change log

Version	Date	Author	Changes
v0.1	YYYY-MM-DD	Claude	Initial draft

What the template prohibits

Some patterns are excluded by template, not just by voice:

No “Introduction” section beyond what Section 3 (Why this matters) already does. Introductions are filler.
No “Conclusion” or “Summary” section. The Knowledge Check is the summary that matters.
No motivational framing. “Imagine you’re a successful HiON franchisee…” is not an instructional opening.
No restatement of the Voice Playbook inside modules. The playbook is the rubric; modules execute against it without reciting it.
No promise-language about outcomes the franchisee cannot control. “After this module you will be successful…” is not a learning objective. “After this module you can open a SEV-2 ticket inside the required window” is.

What the template requires

Every module ends with Section 12 (Change Log) — even if the only entry is v0.1.
Every claim with a number is sourced or [CONFIRM]-tagged.
Every objective in Section 2 maps to at least one item in Section 7.
Every drill in Section 5 has a model answer in Section 9.
The 8-point Training Diagnostic (see 03_Training-Register.md) is run against the module and logged in reference/Voice-Diagnostic-Log.md before the module is committed to the repo.