# Run a cohort from enrolment to the last lesson without a spreadsheet *Live teaching* For institutes and teachers running a batch between two dates. Seats, waitlists, attendance, homework and marks are handled as one system, so the cohort is a thing you teach rather than a thing you administer. Try it on Jversity: https://jversity.com/services/live-classes ## Who it is for - A coaching institute running batches with a fixed start and end - A teacher selling a term of live classes as one purchase - A training company running scheduled cohorts for companies or individuals ## What it does ### A cohort with real dates A batch runs between a start and an end. Every lesson has to fall inside that window, so a timetable can never drift outside the term a student paid for. - A required start and end date for the batch - Every lesson checked against the window - Widening the window is free; narrowing it is refused while a lesson would be left outside - The batch closes itself when the term ends, without cutting off access to what was taught ### Seats, and what happens when they run out Cap the batch if you want one. Every route into enrolment checks the cap inside a transaction, so two people paying at the same moment cannot both take the last seat. - An optional seat cap, or no cap at all - Seats checked transactionally at every enrolment route - A waitlist instead of a dead end when the batch is full - Your own words on the public page when enrolment closes ### An enrolment window you control Open and close enrolment by hand, or schedule it. The rule governs self-serve signups only, so you can still add someone yourself whenever you decide to. - A manual open and close switch - Optional open and close dates - Seats-left messaging on the public page - Admins can always enrol someone directly ### The class, live Everyone in the batch can be seen and heard. Screen share, the whiteboard and the rest of the authoring tools are one click away. - Everyone on camera and microphone - Screen share and recording - Live quizzes that grade themselves - Recordings transcoded and published to the class history ### Homework that is actually submitted Students upload their work, or write their answer, or both. One submission per student per assignment, replaced if they redo it. - File uploads, a written note, or both - One submission per student per assignment, replaceable - Notes, classwork and homework kept against the lesson - Marks flowing into one gradebook with quiz scores ### Who is falling behind Attendance is a real record and the platform reads it. A student whose attendance and marks are sliding is flagged before the term ends. - Present, late, excused or absent, recorded per lesson - Automatic at-risk flags from attendance and scores - Reminders 24 hours and 1 hour before each class - Announcements to the whole batch, with read state ## How it is used 1. **Open the batch** — Set the start and end dates, the price, and a seat cap if you want one. Turn the waitlist on if a full batch should still collect interest. 2. **Fill it** — Students enrol and pay once, through your own payment account. When the seats are gone they join the waitlist instead of hitting a wall. 3. **Teach the term** — Run the timetable, take attendance, set homework, and let the quizzes grade themselves. 4. **Close it out** — The term ends, the gradebook is complete, the recordings are published, and the students keep what they paid for. ## How it is built - **The last seat cannot be sold twice** — The seat check runs inside the enrolment transaction with the row locked, so two simultaneous payments cannot both succeed against one remaining seat. It is enforced at every route into the batch, not only the obvious one. - **Cohort dates are dates, not moments** — A batch that ends on the 30th ends at the end of the 30th wherever the student is, because the window is treated as calendar dates rather than an instant on a clock. - **Homework counts only what was handed in** — The gradebook's homework column reads real submissions. It used to count boxes students ticked themselves, which is a different number and a worse one. - **Ending the term does not remove access** — When the cohort ends, going live is disabled but everything already taught stays available to the people who paid for it. ## Questions we get asked ### Do I have to cap the batch? No. Leave it uncapped and anyone can enrol. A cap only exists if you set one, and a waitlist only appears if you turn it on. ### What happens when the batch is full? Students join a waitlist rather than being turned away, and you can see how many are waiting when deciding whether to open another batch. ### Can I add a student after enrolment closes? Yes. The enrolment window governs self-serve signups. An admin adding someone by hand is always allowed. ### What happens when the term ends? You can no longer start new live sessions in that batch, but students keep access to the recordings, notes and marks they paid for.