How It Works

The Course Factory

A production system for course catalogs. Built for speed, quality, and cost-control — without a small army.

What you get

  • Course inventory + complexity scoring (Light / Standard / Heavy)
  • 1–2 templates + standards rules (navigation, naming, module structure)
  • Batch delivery (25–50 courses at a time)
  • QA checklist + exception log per batch
  • QA Evidence Pack for sign-off
  • Delivery inside your LMS (Canvas, Blackboard, Moodle, and others — confirm your platform on the fit call)
  • 30-day warranty window for defects within acceptance criteria after each batch is accepted

Best fit

  • 20+ courses
  • Hard deadline / launch window
  • Small internal team
  • Inconsistent standards, messy source content, or SME availability constraints

Not a fit

  • Open-ended redesign with no scope boundaries
  • Projects where subject matter experts are entirely unavailable for review
  • Heavy net-new media production (video) unless separately scoped
Process

Batch delivery, verified every step

We deliver in batches so you see progress every week, and quality is verified — not assumed.

01

Inventory + Complexity Scoring

We map the catalog and rate each course by complexity so scope and pricing are based on your actual catalog, not estimates.

  • Inventory courses + assets
  • Identify integrations and risk areas
  • Define batch size and delivery schedule
02

Lock Standards

When every course is built differently, quality drifts. We lock templates and rules so production is consistent across your entire catalog.

  • 1–2 templates
  • Naming + navigation rules
  • Written acceptance criteria (Definition of Done)
03

Pilot: Prove the Process

We prove the process on a small batch first, then scale. You see the quality, the timeline, and the verification artifacts before committing to the full run.

  • 3–5 course pilot batch
  • Process validated before full production
  • Automation and QA checks calibrated
04

Batch Delivery + QA Evidence

Each batch is delivered with verification, exceptions documented, and sign-off artifacts ready. You don't just receive a finished product — you receive evidence it was built to spec.

  • Batch delivery + weekly review cadence
  • QA checklist + exception log
  • Evidence Pack + warranty
Sample Timeline

What 100 courses actually looks like

Every engagement is scoped to reality, but here is a representative timeline for a mid-size catalog build.

Weeks 1–2

Inventory, complexity scoring, and standards lock. You know the scope, price, and timeline before production starts.

Week 3

Pilot batch (3–5 courses). Proves the process works and calibrates expectations before full production begins.

Weeks 4–10

Production batches of 25–50 courses. QA evidence + exception log with each batch. Weekly review cadence.

Week 11+

Final sign-off, 30-day warranty window for defects within acceptance criteria, and clean handoff documentation.

Actual timelines depend on catalog size, complexity mix, and SME availability.

What Your Team Provides

What smooth delivery depends on

Three things that keep the project moving. The more clearly these are in place before we start, the faster the catalog gets done.

Source content

  • Existing course files, slide decks, PDFs, or documents
  • Raw drafts are fine — we work with what you have
  • Clear indication of which content is current vs. outdated

LMS access

  • A sub-account with course editor or designer-level permissions
  • No admin access required unless the scope demands it
  • Access is revoked at project close

Review availability

  • A designated point of contact who can review and approve each batch
  • Subject matter expert time for content accuracy checks (typically 1–2 hours per batch)
  • Timely sign-off at each wave — delays on approval delay the next batch
Acceptance

Definition of Done (examples)

Written acceptance criteria keep scope clean and sign-off straightforward. These are set before production starts.

Core

  • 0 critical broken links in student-facing areas (or documented exceptions)
  • Templates + standards applied consistently
  • Publish states correct
  • Files organized (no obvious duplicates or stray content)

Accessibility (baseline)

  • Heading structure is properly sequenced
  • Key images have alt text
  • Template elements pass contrast
  • Anything out of scope is documented in the exception log

Evidence

  • QA checklist completed
  • Exception log delivered (owner + next step for each item)
  • QA Evidence Pack generated per batch
  • Sign-off captured from client contact
Book a 30‑Min Fit Call