Skip to main content

Template

Course management software specification: the filled-in template

Students, enrolments, attendance, hour cards, payments: the one page that fully describes a class-school application. Copy it, put in your actual disciplines, and it becomes your specification — or directly your Blueprint Maker description.

This template applies the four-block method — THE THINGS, THE LINKS, THE STATES, THE NUMBERS — to a class school: music, dance, tutoring, yoga, sport. It's filled in for a community music school: the example shows how to describe enrolment season, the typical week and payments, without ever describing a screen.

The trade has two clocks: the year (enrolments, terms, payments) and the week (recurring classes, attendance). The template separates them: the enrolment carries the year, the class carries the week — and attendance links the two.

Filled with your vocabulary, this text briefs a developer — or is submitted as-is to Blueprint Maker, which turns it into an application plan you validate, then a generated application: database, screens, dashboard and demo data.

The template to copy

My business: community music school, 120 students,
six teachers, individual lessons and group workshops.

THINGS tracked:
- Students (name, date of birth, parent contact if minor)
- Teachers (name, disciplines)
- Classes (discipline, teacher, day, time, individual or group,
  capacity)
- Enrolments (student, class, school year, fee, payment status —
  paid, 3 instalments, pending)
- Attendance (class, date, student, present or absent)

LINKS:
- An enrolment links a student to a class for the year.
- Attendance is recorded per student at each class session.
- A teacher runs one or more classes.

STATES of an enrolment: trial, enrolled, suspended, ended.

NUMBERS to see every week:
- Today's classes with headcounts
- Remaining seats per group class
- Payments pending or late
- Students absent two sessions in a row

Adapting this template to your school

  • Your disciplines and formats: 30-minute individual lesson, one-hour group workshop, holiday intensive — describe your real formats, they carry different capacities and fees.
  • The trial class: the "trial" state avoids the classic ghost — the student who came once, never enrolled, never followed up. The list of trials without follow-through is a ready-made win-back.
  • Repeated absences: "absent two sessions in a row" is the drop-out signal — for a minor, a call to the parent; for an adult, a message. Simple retention.
  • Punch cards: if you sell 10-session cards rather than school years, replace the yearly enrolment with a card and a draw-down — same mechanics as driving-school packages.
  • Payments are tracked (paid, instalments, pending) but compliant invoicing and collection stay on your usual tools — the code being exportable, a developer can connect online payment if needed.

The matching use case

Run a teaching school without notebooks or fragile spreadsheets

School described? See the application it produces