Skip to main content
This page explains the words FirstRespondersHub uses. Read it once and the rest of the docs will make sense.

​
Quick reference

​
Core concepts

​
Organization

Your organization is the training provider entity on the platform. It has a name, contact details, description, and one or more locations and program offerings.

​
Location

A location is a physical or virtual place where training occurs. Organizations can have multiple locations. Each location has an address (or virtual designation), timezone, and can host sessions for your cohorts.

​
Program template

A program template is a standardized program type defined at the platform level—for example, EMT-Basic, Paramedic, or Firefighter I/II. It describes the credential type, accreditation body, industry category (e.g. EMT, paramedic, fire, basic healthcare), and typical duration. Your organization does not create templates; you create program offerings that implement a template. If a program template you need is not available, please reach out to support and we will add it. Example: EMT.

​
Program offering

A program offering is your organization’s version of a program. You define its name, description, delivery modality (in-person, virtual, or hybrid), schedule types, tuition, default capacity, and which locations it uses. Each offering can have multiple cohorts (specific runs with dates and capacity). Application forms and enrollment agreements are attached at the offering level. Offerings can be recurring (programs with classes over weeks or months, e.g. an EMT course) or events (single-day workshops or classes). Example: EMT Accelerated (4 Weeks) and EMT Part Time (14 Weeks).

​
Cohort

A cohort is one run of a program offering — for example, “Fall 2026 EMT Class.” It has a start date, an end date, a seat count, a sign-up deadline, and a status. Students enroll in a cohort, not in the offering. In the dashboard you will often see a cohort called a class. Example: For EMT Accelerated (4 Weeks)—January 2026, March 2026. For EMT Part Time (14 Weeks)—February – May 2026, June – September 2026.

​
Cohort status

A class moves through these states. You pick three of them. The platform sets the other three for you. You pick:
  • Getting ready — You are still setting it up. Nobody can sign up, and it stays off your website.
  • Pre-enrollment waitlist — Sign-ups are not open, but people can add their name.
  • Open — Students can sign up and pay.
We set:
  • Full — The last seat filled, or the sign-up deadline passed.
  • Happening now — The first class date started.
  • Finished — The last class date ended.
Two more states sit outside this list, because neither is about selling: Cancelled (the class was called off) and Archived (filed away). See Status and who can find it.

​
Session

A session is a single class meeting within a cohort—e.g. a lecture, lab, exam, or skills practice. Sessions have start and end times, can be tied to a location (or virtual link), and together form the cohort’s schedule.

​
Modality

Modality describes how a program is delivered:
  • In-person — Training occurs at a physical location.
  • Virtual — Training is fully online.
  • Hybrid — Mix of in-person and virtual.

​
Enrollment

An enrollment is a student’s place in a cohort. Each enrollment has a status, such as:
  • Enrolled — Active student in the cohort.
  • Completed — Finished the program.
  • Paid pending application — Payment received; awaiting required post-enrollment form(s).
  • Withdrawn — Student withdrew.
  • Dropped — Student was dropped.
  • Failed — Did not complete successfully.

​
Application forms

Application forms are custom forms you attach to program offerings. They can be required before enrollment (e.g. background or certification info) or after enrollment (e.g. post-payment paperwork). Some forms require organization approval before the student can complete checkout.

​
Enrollment agreements

Enrollment agreements are terms, waivers, or policies (e.g. liability, code of conduct) that students must accept during enrollment. You create and manage them at the organization level and assign which agreements are required per program offering. Acceptance is recorded for compliance.

​
Roles

  • Program owner — Can do everything: offerings, classes, applications, enrollments, agreements, money, and settings.
  • Instructor — Sees the classes they teach. Takes attendance and records results. Never sees money.
  • Student — Enrolls in classes and uses the student dashboard.
  • Sponsor — An employer or department that pays for someone else’s seat.
See Users and roles.

​
Student access

Student access (also called access codes or credentials) is how you give students the codes, links, or logins they need for a vendor site such as Jones & Bartlett Navigate or American Heart Association eLearning. You import unused codes, the platform holds one set per student, and it sends them by email and the student dashboard. See Student access.

​
How it fits together

Organizations have locations and program offerings. Each offering implements a program template and has cohorts. Cohorts have sessions and enrollments. Application forms and enrollment agreements are configured per offering.

​
Need help?

For support or questions about the platform, visit First Responders Hub Support.