There is no sign-up form on this page. That is deliberate.

What actually happens

Three steps, and you can stop after any of them.

Three conversations, depending on who you are

Facilitator-led, corporate L&D, or enterprise.

Facilitator-led programs. Bootcamp section leads, tutoring pods, coaches and therapists running an 8-week group, wellness studios selling a term or session block. We walk the series lifecycle and what continuity through a moved week will look like.

Corporate L&D and training. We discuss multi-cohort programs, 0% commission on tuition or dues at any tier, and the self-serve-entry plan — no quote-only gate.

Enterprise and white-label. Per-tenant licensing, the module-toggle layer shared with the rest of the platform, and what a self-hosted or managed deployment looks like in your context.

Write the whole commitment before choosing the first date

Use an invented adult botanical-illustration program with five Saturday meetings and a maximum group of six. The facilitator intends the meetings to build on one another: observing a specimen, making an initial study, developing the drawing, reviewing it and completing the final work. Start by writing what one enrollment means across those five meetings. That account is the input to a series evaluation. A calendar full of similar titles is not enough to establish the commitment. The output should let a colleague explain what someone would be joining without needing to infer the relationship between separate entries.

Compare that arc with five unrelated drop-in workshops. In the second version, a person might reasonably choose only the last date, and the group could change entirely between meetings. The recurrence looks similar, but the membership rule is different. Decide which version represents the program before discussing a roster-continuity feature. If the facilitator actually wants independent purchases, acknowledge that early. Cohort's series layer remains planned, so the exercise cannot enroll anyone in either version. Its value is a clear fit decision about the unit of participation, with no customer records required to make the distinction.

Make the holiday rule visible in the planned dates

Now put a fictional holiday between the second and third meetings. The facilitator must decide whether the program still contains five meetings and ends later, or whether the original span includes a skipped meeting. Those are different promises. On paper, list the intended occurrences before and after the exception and mark the finish. This manual preparation does not expand a recurrence rule in software. It gives an evaluator a concrete result to inspect and prevents the phrase five-week program from hiding a disagreement about how many meetings an adult is actually expected to attend.

Then ask what should remain unchanged. For a whole-series program, the intended answer is the continuing enrollment relationship, not necessarily every date or every person's ability to attend it. Write those separately. An adult may object to the revised finish even if their place in the arc remains represented. The facilitator's existing policy and communication process must handle that practical issue. Do not claim that the planned continuity layer resolves it automatically. A useful preparation sheet includes the proposed calendar, the membership expectation and the unresolved human decision, so a later conversation can address each on its own terms.

Decide what a late arrival would be offered

In the illustration example, a fictional adult asks to join after the observation and initial-study meetings have happened. The facilitator needs to decide whether joining now makes sense for the learning arc. Possible answers include the remaining meetings, a separate catch-up arrangement or an invitation to consider a future intake. This page chooses none of those policies for the program. The product plan mentions late joins and proration, but it provides no live enrollment or charge calculation here. Preparing a clear intended treatment is more useful than assuming a software control would settle the teaching decision.

Write the proposed offer to the late arrival beside the original commitment of the existing group. If the two differ, state the difference explicitly. The existing enrollments should not need to be reconstructed merely to describe what remains for the new person, but the new person still needs an understandable account of what they would receive. The output of this exercise is a pair of commitments the facilitator can explain consistently. Use invented labels, not an actual roster or a personal account of why someone missed the beginning. A scheduling evaluation does not need those circumstances to identify the policy question.

Choose the evidence that would make a future walkthrough useful

The preparation can end with three short comparisons: the initial five-meeting arc, the revised dates after the holiday, and the proposed treatment of a late join. For each, name what the facilitator and participant should be able to understand. The central continuity question is whether the same existing group remains associated with the series while an occurrence changes. A visually convincing calendar is not enough if that relationship is unexplained. Conversely, a roster picture does not answer whether the revised dates accurately describe the offer. A future walkthrough would need to make both parts legible.

Keep the current enrollment process in charge while this is a fictional evaluation. No account is provisioned, no place is held and no participant is invited by completing the preparation. The next decision may be to refine the program policy, identify a missing capability or wait until the Cohort-specific surface can be evaluated operationally. Record which question remains and why it matters. That gives a conversation a useful boundary without making the preparatory exercise look like onboarding. The repeated series reference below is background; the five-meeting illustration and its concrete decisions are the specific work to bring to the review.

Start with one adult series you can describe without a roster

Use a fictional professional workshop: eight weekly meetings, twelve possible participants and one facilitator. Give it a start, an end and a time zone. Those details are enough to discuss the scheduling shape; names, email addresses and an exported enrollment list do not help at this stage. Write down whether a person is joining the whole arc or buying individual meetings. If every week can be purchased independently, say so early. That changes the central unit and may put the need closer to single-session booking than Cohort's planned whole-series enrollment.

Then describe one exception in ordinary language. Perhaps the fourth meeting moves to a different evening, or a holiday means the group skips a week and finishes later. State what you expect to stay the same: the group, each existing enrollment and the agreed size of the series. State what may change: one occurrence, the final date, or the message the facilitator needs to send. The output of this exercise is a short, reviewable account of continuity. It is not a recurrence configuration that this site will execute.

Name the decision you cannot settle today

A good brief admits the awkward case. What should a late joiner receive: the remaining meetings, the entire learning arc with a separate catch-up arrangement, or a place in the next intake? Who decides whether the program still makes sense for them? A calendar cannot answer that teaching question. The product plan mentions mid-series joins and proration, but this website does not calculate a charge or accept a join. Put the intended rule beside the scenario so an evaluation can distinguish a scheduling requirement from a program policy.

Do the same for a participant who cannot make the moved meeting. Preserving their enrollment should not be confused with promising they can attend every new date. Describe how the facilitator handles that conversation through the process already in use. A useful design discussion can expose the difference between a seat continuing to exist and a person agreeing to a changed commitment. Keep those decisions explicit. Do not turn an unanswered policy question into a default simply because a proposed screen would be easier to draw that way.

Finish with a decision, including a decision to wait

Write a simple acceptance sentence: after a holiday exception, the existing group should still belong to the same series, and both sides should be able to understand the revised dates. Add a refusal sentence: the conversation must not be presented as a working enrollment or as a reservation of a seat. Those two sentences give a walkthrough something concrete to answer. They also prevent an attractive calendar picture from standing in for the harder question of what actually survives a change.

The immediate outcome may be a narrower requirement, a mismatch with the planned series model, or a decision to revisit the idea when an operational surface exists. None of those outcomes requires moving a roster or retiring a tool. Pricing on the apex remains display-only, and sending a message does not commit you to a subscription. If a conversation reaches a point where real records, an integration or a deployment would be needed, stop the fictional exercise and establish that separate scope before treating anything as a pilot.

What starting does not involve

No card, no charge, no contract signed on a web page.

There is no live checkout on this site. Reserving early access does not create a payment, does not store a card, and does not commit you to anything — the pricing on the home page is the plan, not a price you can be billed at today. The 0% commission commitment is a product commitment, not a live billing state: there is nothing to skim from because nothing is charged here yet.