01
"What's our attendance this cohort?"
If the answer takes a CSV download per session plus a pivot table, the awarding body is already irritated. Per-cohort attendance has to roll up automatically across every session.
Named cohorts · Recurring calendar · Per-cohort attendance roll-up · Single evidence pack
Stop stitching a Zoom link, a Google Sheet roster and a Slack channel together every Monday. LiveLoop runs the live sessions, holds the cohort as one named object, and rolls up attendance across every session into one evidence pack you can hand to the awarding body.
This page owns the multi-session cohort story. For single live classes see live interactive classes; for breakout pedagogy see breakout collaboration; for credentials see certification & completion; for the recording library see on-demand recordings. Anchored to NSDC NSQF, NCVET, UGC Online 2018 and DPDP §9.
An online workshop and bootcamp platform is the live-session backbone for a multi-day or multi-week cohort programme — recurring sessions on a fixed calendar, a named cohort with a locked roster, per-cohort attendance roll-up across every session, and a single evidence pack at programme end. LiveLoop runs the live sessions in the browser using WebRTC; mechanism for breakouts, recordings, certificates and integrations sits on dedicated owner pages and is referenced from this page by link.
A real cohort calendar from a skill-development bootcamp — 48 learners, 24 sessions across 8 weeks, three sessions per week. Here's what weeks 1–3 look like in the LiveLoop cohort view.
One named cohort. One calendar. One attendance roll-up. The session-by-session pedagogy patterns shown above — case-method, peer review, breakout pods — are documented at /liveloop/solutions/breakout-collaboration/.
These are the four reasons programme owners tell us they replaced a "Zoom + Slack + Sheets" patchwork with a single cohort container.
If the answer takes a CSV download per session plus a pivot table, the awarding body is already irritated. Per-cohort attendance has to roll up automatically across every session.
Three Mondays in, the timetable shifts because Independence Day falls on a session day. Manually rescheduling on Zoom, Slack and Calendar separately is how cohorts lose learners.
If a learner misses session 9 of 24, they shouldn't have to ask which Drive folder this week's recording lives in. Each session's recording belongs to the cohort, scoped to the cohort.
NSDC, NCVET or UGC continuing-ed audits want the per-cohort evidence file — attendance, recordings, transcripts, calendar. The programme owner shouldn't lose a week to manual collation.
The cohort-programme buyer is governed by a different framework stack than a K-12 live class. These are the six anchors that govern this decision.
NCVET-defined skill levels 1 to 10 with QP/NOS codes assigned by sector skill councils. Per-cohort attendance plus recording forms the auditable evidence file for NSQF-aligned programmes.
The qualifying authority for vocational education in India. LiveLoop carries the programme delivery metadata; NCVET retains awarding authority. The two are deliberately separate by design.
UGC permits short-term certificate courses and continuing-education programmes in online mode for a defined component of regular programmes. Per-session record + cohort attendance trail forms the audit evidence.
CBSE-affiliated schools running Vocational Education subjects (AI, Banking, Tourism, Retail) deliver project and lab sessions in cohort format. The per-cohort attendance and recording file forms the inspection evidence.
For programmes that include learners under 18, the institution as Data Fiduciary collects verifiable parental consent. LiveLoop is the Data Processor; consent capture happens at cohort enrolment, before the first session.
The open standard for ICS calendar feeds. Each cohort's calendar is a spec-compliant feed; subscribing learners get every session in their calendar app of choice — Google, Outlook, Apple — without any LiveLoop-specific app.
For the first six months we ran a Zoom link, a Telegram group and a Google Sheet for attendance. Every audit cycle, our co-ordinator lost a week reconciling them by hand. The NCVET QP/NOS evidence file took longer to prepare than the actual cohort took to teach. With LiveLoop, the cohort is one object — when I open the August cohort I see the calendar, the roster, every session's attendance, every recording, every transcript, in one place. The Q3 audit took an afternoon.
Most cohort programmes run their first LiveLoop cohort as the rollout itself. Here's the three-stage shape.
The cohort mechanism is the same; the duration, the awarding body and the evidence anchor change with the programme.
State and central skill-development missions running NSQF Level 4–6 cohorts for 8–12 weeks. Anchor: NSDC NSQF + NCVET. Evidence pack feeds the assessment-body audit.
College continuing-ed cells running 6–10 week certificate programmes — data analytics, finance, soft skills. Anchor: UGC Online Regulations 2018. Cross-link: learning analytics for IQAC reports.
Schools running CBSE Vocational subjects (AI, Banking, Tourism) with project and lab cohorts. Anchor: CBSE Vocational Education curriculum. Cross-link: SchoolDeck Virtual Classroom handles K-12 scheduling.
Year-long foundation and 6-month booster cohorts for entrance-exam coaching. Recurring sessions, cohort-scoped recordings library, separate batches per centre.
Edtech founders running 8–12 week cohorts in coding, design, product management. Anchor: certification-completion for credential issuance + LinkedIn deep-link.
Educational trusts running internal teacher-training or NGO programmes for community workers. 4–6 week duration. Anchor: corporate-training-webinars for one-off PoSH/SEBI sessions.
Boundary discipline, the honest non-features, the comparison to a stitched-tool setup, and the cluster cross-links.
This is the buyer-story page for running a multi-day or multi-week cohort programme — workshops, bootcamps, skill-development courses, college add-on certificates, capacity-building programmes for trust or NGO staff. The page's specific ownership: how a recurring series of live sessions is held together as one named cohort, with consolidated attendance, scoped recordings, and a single end-of-programme evidence pack. That is genuinely new ground in the cluster — every other shipped sibling owns a different slice.
What the page does not own, and explicitly defers: the breakout-room mechanism (feature page), breakout pedagogy (its own solution page), the MP4 recording mechanism, the recording library workflow, certificate issuance, calendar mechanism detail, API integration, and learning analytics. Each has a dedicated owner. The discipline keeps every page sharp.
Six LiveLoop solution pages live in adjacent territory. Knowing which one owns which decision saves the evaluator's time.
The premise of this page is simple: the cohort is the unit of organisation, not the session. When the programme owner opens "Data Foundations — August 2025", they don't see a list of Zoom links and a separate spreadsheet. They see one object that holds the roster, the recurring calendar, every session's attendance, every recording with its transcript, and the end-of-programme evidence pack. The "Zoom + Slack + Sheets" patchwork is replaced by one container that holds all of it.
The cohort is what the awarding body asks about. NCVET doesn't ask "show me session 14's attendance" — it asks "show me the August cohort's evidence file." Building the platform around the cohort, not the session, is the entire point.
Multi-week programmes hit calendar drift constantly. Independence Day falls on a session day. Monsoons close the institute for a week. A guest speaker is available only on a different weekday. In a stitched setup, the programme owner reschedules manually in three places and praying everyone notices.
LiveLoop's cohort calendar is an RFC 5545 iCalendar feed. Learners subscribe once at enrolment; every session and every reschedule propagates through the feed automatically to Google Calendar, Outlook, Apple Calendar or any spec-compliant client. The OAuth scope LiveLoop requests is calendar events only — never inbox, never Drive, never contacts. Calendar mechanism detail lives at /liveloop/features/calendar/.
At the close of the cohort, the programme owner exports a single PDF + ICS pack. It contains: the cohort metadata, the roster, every session's session-duration attendance roll, every recording link scoped to the audit, every transcript, the calendar feed. For NSDC and NCVET-aligned programmes, this is the file the assessment body needs. For UGC continuing-ed, this is the file the IQAC uses for the AQAR submission. For an internal trust audit, this is the file the trustees review at the quarterly meeting.
Credential issuance from the evidence pack is the next link in the chain, and it is owned by the certification-completion solution page. The two pages handshake by design — the evidence pack is the input, the certificate is the output.
We deliberately do not publish a "maximum cohort size" claim. The practical limit on cohort size is not a LiveLoop technical limit; it is the bandwidth of facilitators and the size of effective breakout pods. Adult-learning research consistently favours intimate groups for high-touch facilitation — 15 to 40 learners is the most common range we see. Larger cohorts of 60 to 120 work when the programme is broken into smaller breakout pods within each live session, but the facilitator-to-learner ratio is what determines outcomes, not the platform's capacity number.
If a vendor quotes you a specific maximum-cohort number on their landing page, ask them what the facilitator-to-learner ratio is in that maximum. The number alone is a marketing artefact.
We don't ship a community-chat product. No "persistent cohort chat", no "topic threads", no Slack-replacement claim. Most cohorts already have a communication tool of choice — WhatsApp group, Slack workspace, Discord server, or the institution's own intranet. LiveLoop owns the live session and the cohort container; cross-session conversation lives where the cohort wants it to live.
We don't ship a built-in whiteboard. The cluster decision was made on the screen-sharing page — for drawing-heavy work (diagrams, design sprints, code architecture), cohorts use Excalidraw, Microsoft Whiteboard or Jamboard in a browser tab and share that tab into the session. We don't pretend the in-call doodle tool replaces a real whiteboard.
We don't ship a payment gateway or course-marketplace product. No Stripe / PayPal / Razorpay registration page claim, no subscription billing for course enrolment. For Indian programmes that take payment, the institution uses its existing fee infrastructure — SchoolDeck UPI fees, the college fee portal, NSDC's e-skill platform, or an external course marketplace. LiveLoop hands off cleanly; it doesn't own the enrolment-payment surface.
We don't ship LMS-style content drip. If a programme needs week-by-week content release of slides, quizzes and reading PDFs, that is an LMS function. LiveLoop runs the live cohort session; the LMS content can be linked into the calendar entry but is not stored or scheduled by LiveLoop. For LMS integration via 1EdTech LTI 1.3, see integrations-api.
We don't publish fabricated completion-rate statistics. Marketing claims like "self-paced courses have 5% completion and cohort courses have 85%" are widely repeated but unverifiable in any specific institutional context. We won't put one on this page just because competitors do.
| What programme owners need | Zoom + Slack + Google Sheets stitched setup | LiveLoop cohort container |
|---|---|---|
| Roster source of truth | Google Sheet, manually kept | One cohort object, locked at enrolment |
| Recurring session calendar | Calendar invites copy-pasted per session | RFC 5545 ICS feed, subscribe once |
| Per-session attendance | Zoom lobby ping CSV, downloaded weekly | Session-duration timestamps, auto-rolled |
| Cohort attendance roll-up | Manual pivot table from CSVs | One number, every cohort, always current |
| Recording delivery | Drive folder link in Slack channel | Cohort-scoped library, in-app per learner |
| Reschedule when Aug 15 falls on a session | Three tools, three updates, partial coverage | One calendar edit, propagates through ICS |
| Awarding-body evidence file | Co-ordinator loses a week before audit | One-click cohort evidence-pack export |
| Under-18 consent capture | Ad-hoc, not §9-valid | DPDP §9 verifiable parental consent at enrolment |
| Cross-cohort programme template | Copy-paste from last cohort's Sheets | Clone last cohort, change name and dates |
| Co-ordinator time per cohort | ~2 hr/week stitching + audit week | Setup hours; ongoing zero |
The cohort programme sits across multiple Databus surfaces. SchoolDeck Virtual Classroom covers CBSE Vocational and school-side cohort scheduling. CampusAlly covers college continuing-ed cohorts and the IQAC reporting flow. TutorDesk covers coaching-institute foundation and booster cohorts. LiveLoop is the live-session backbone across all three — the cohort calendar reads roster from the relevant Databus product, the recording and attendance writes back, and the certificate metadata flows to certification-completion. The boundary discipline is the same as every other cluster surface: one product owns one thing well, and links cleanly to the next.
Ten questions that come up in almost every demo, answered the way we'd answer them in the demo itself.
Four distinct cluster siblings — no overlap with this page's territory.
Book a 30-minute demo. We'll set up a real cohort, schedule a recurring session, and walk you to the one-click evidence-pack export.
From ₹499/host/month · Browser only — no installs · NSDC / NCVET / UGC / CBSE Vocational-ready