Concepts

A certification profile is the record Rhythm keeps for each person in Certifications, carrying a copy of their contact details, their last application's answers, and a link to the one training provider that looks after them.

What Certifications's four statuses mean, why any status can change to any other, how a status reason explains a status, and what each of a certification's seven dates governs.

How Certifications decides which application, course, and exam fee lines a coupon code discounts at checkout, and why a coupon might not discount a fee you expected it to.

What appears on each line of a printed credit transcript, how health-safety-welfare and landscape-architecture credit are flagged and totaled, and why a transcript's total can be less than the sum of its lines.

Why a custom field you define on certification applications automatically appears on certifications too, how Rhythm keeps that copy current, and why deleting the application field leaves the certification's copy behind.

What actually changes when a scheduled billing run executes its plan — reminders go out, lapsed certifications drop, approved applications activate, and stalled applications expire — and why a run's work never crosses into a different account.

The eight kinds of requirement a certification application can carry, how Rhythm decides whether each one is met, and how the results roll up into an application's percentage complete and its approval status.

How Rhythm decides which application processes a person or organization can start right now, based on whether they already hold a certification, how close it is to expiring, and whether an application is already open.

What a billing run reads and considers when it plans each kind of work it can do, how its program, provider, status-reason, and application-type filters narrow that down, and what changes when a plan is refreshed.

What Rhythm does automatically once a course seat is paid for — registering the student, awarding credits, booking chosen exams, and confirming attendance — and what a cancelled seat undoes.

What happens automatically once a candidate pays for an exam booking, why they might be charged the retest fee instead of the regular fee, and what happens to a registration when the order behind it is cancelled.

How Rhythm keeps a credit's used and available quantities current as applications draw on it, and why a contact, source record, or application a credit points at can't be deleted while the credit still exists.

What happens to the referees an applicant names on a certification application once it's paid for, how each one becomes a contact and a reference record, and how a completed reference updates the application automatically.

How you learn what a billing run is doing, from the email that says its plan is ready to review, through the action counts on the run itself, to the email that tells you it finished or failed.

How Rhythm counts the certifications a person holds this year once the multiple-certification discount is turned on, charges full price for a set number, and discounts the application fees beyond that.

Which courses, course offerings, exams, and exam sittings appear in an online store and at what prices, based on whether they're published, active, and inside their sale window, and why the store always returns every fee price in your account.

What the training-provider billing status on an application or a course or exam registration means, when Rhythm sets it automatically, where you see it, and how to set or correct it by hand.

The two checks Rhythm runs before a training provider's staff member can act for someone in the Portal, and the three ways a person counts as served by a provider.