Cohort.software · The whole series
Explain the series without exposing the group.
Cohort.software is a static marketing site for a planned series product. This page separates that public reading experience from a future operational roster. An initial evaluation can use invented adult scenarios and counts; it does not need participant names, contact details or enrollment records.
Reading these pages is not joining a series
There is no enrollment form, live checkout or card collection on this site. The renderer does not create a Cohort roster when someone reads a lifecycle explanation, follows a local link or views display-only pricing. The existing help page describes the site as static, without session or authentication state or third-party analytics and advertising scripts. The apex includes non-executable structured metadata derived from its visible FAQ so the public page can be described consistently. That metadata contains product questions and answers, not participant information.
This is a description of the marketing surface, not a complete account of every hosting or email system involved in a visit or message. It is not a retention schedule, deletion guarantee or operational access model for an unbuilt service. If those details matter to a later evaluation, ask about the actual proposed setup before sharing records. The fact that a page accepts no roster upload does not establish how a future enrollment product would manage records. Keep the scope of each statement attached to the surface it describes.
Use the least revealing example that still explains the problem
For a first conversation, a fictional adult workshop with eight meetings and twelve possible places is enough. Describe a holiday skip, a moved evening or a late join using invented dates and labels. The useful information is the relationship between the series, its occurrences and its membership. A real participant list adds exposure without improving that relationship. Do not send a spreadsheet simply because it is convenient to export. Write a short account of what changes and what should remain stable, then inspect whether the planned model can explain it.
Private circumstances are usually unnecessary too. A facilitator can say that someone cannot attend a revised date without explaining their personal reason. The design question is what the program's existing policy does with that objection, not why the individual raised it. Keep any actual conversation with the participant in the process already responsible for it. An evaluation should not create a second informal record of a person's circumstances merely to illustrate a scheduling exception. If the fictional version cannot express the need, first explain what decision is missing.
A planned roster still needs an operational privacy decision
The product plan says that roster membership travels with the series identifier. That describes the intended relationship between enrollment and calendar changes; it does not specify who may inspect a roster, how access is granted, how long records remain or how a request about a record is handled. Those are material questions for any future deployment. This page does not fill the gaps with an invented mechanism or certification. A buyer should ask for evidence tied to the actual surface before putting a real group into it.
The same boundary applies to next-intake continuity. An opt-in step in the planned lifecycle is a product behavior, not a general permission to reuse participant information for unrelated purposes. The completed series and a possible future intake have different commitments. A useful review asks what information would be needed for each decision and why. It should also distinguish keeping an enrollment relationship intelligible from retaining every possible historical detail. The static marketing site cannot choose that operating policy on behalf of a facilitator or participant.
Contact begins a conversation, with clear limits
The contact route links to [email protected]. Opening that link uses your email application; sending a message shares the content you choose to include. Start with the fictional series brief and omit credentials, payment details and participant exports. This page does not promise a response time, a case-management system or automatic deletion of messages. If you need a particular handling arrangement for a later operational discussion, establish it before sending the information that arrangement would govern.
Cohort is explicitly outside K-12 institutional timetabling and does not target minors by design. These companion guides keep their examples adult-oriented and add no minor enrollment or consent workflow. A different audience or a request involving sensitive records is not a small variation on the fictional exercise. It requires a separately reviewed scope rather than an assumption that the series model supplies the necessary protections. Related-product links explain those products' own purposes; following one does not establish a shared account, a data transfer or an available integration.
A useful design can still be an unfinished product
The recurrence rule, series enrollment and roster continuity described here are planned. The shared capacity-N engine is a narrower built component; it does not establish that a facilitator can publish a Cohort series, accept an enrollment or change an occurrence through this website. There is no live checkout and no card is charged here. Examples describe decisions a future product must make legible, not records being created in the background. A polished explanation should make that boundary easier to see, not harder.
For an evaluation, keep your existing calendar and enrollment process in charge. Choose one fictional adult series and work through what a facilitator and participant would need to understand at each step. If the proposed behavior does not fit, that is a useful result. A conversation is not an enrollment, a displayed price is not a bill, and a related product link is not evidence of an integration. Read the help guide for the existing capability ledger and the starting guide for the scope of a conversation today.