▶
58:14
Period 2 · 09:50–10:48
Auto-record · Auto-share with absentees · Section-scoped · Inspection-ready
LiveLoop turns the live classes you already run into a year-long, access-controlled on-demand library. The session records itself, attaches to the right period on the SchoolDeck timetable, and lands in the parent app of every absentee — same day, in-app, no email-the-link routine.
This is the buyer-story page for building an on-demand recorded-class library. The MP4 file and absentee auto-share mechanism live on /liveloop/features/recording/; searchable transcripts and click-to-jump live on /liveloop/features/transcription/. Anchored to CBSE Bye-Laws Ch. 9, UGC Online Regulations 2018, NAAC AQAR 2.3.1 and DPDP §9.
An on-demand class recording library is a cloud-stored archive of recorded live teaching sessions, scoped to a school or institution, that students can watch asynchronously after the class. LiveLoop builds it automatically — every live session is recorded, attached to its timetable period, pushed in-app to absentees, and retained per the institution's policy. It is built for Indian K-12, higher-education and coaching contexts under CBSE Affiliation Bye-Laws Chapter 9, UGC (Online Courses) Regulations 2018 and the DPDP Act 2023 §9 consent boundary.
Aarush was absent Tuesday morning. Here's what he sees in the parent app at 6 pm — three recordings auto-attached to his timetable periods, scoped to his section only.
Mock-up of the parent-app view. Each tile opens in-app — there are no public URLs to share, copy or scrape.
These are the four reasons schools tell us they replaced a Google Drive folder of recordings with a structured on-demand library.
A flat list of files sorted by date is hostile to revision. Students need to see the recording next to its timetable period — not hunt by filename.
A teacher emails the recording link to the absentee at 5 pm. The parent doesn't see it till next morning. The child has lost a day. It has to land in the parent app — in-app, same day.
If a CBSE inspector asks for "the Class 9-B Science records for the last term," the answer can't be "let me dig through Drive." The library has to be scoped, indexed and exportable as evidence.
A public Drive link circulates. A teacher's lecture becomes a coaching-rival's marketing asset. The library has to be in-app, scoped, and watermarked — not just "we set the link to view-only".
Recording is not just a convenience feature — for Indian schools and colleges, the recording plus the attendance log is academic evidence. These are the six anchors that govern the decision.
Requires retention of teaching and attendance records as part of the academic record retrievable during inspection. LiveLoop's per-session recording bundled with the attendance log satisfies the evidence requirement.
UGC permits blended-mode delivery for a defined component of regular HE programmes. Per-session recordings and attendance trails form the audit evidence for the blended component during the affiliation cycle.
NAAC Annual Quality Assurance Report metric covering student-centric pedagogical methods including blended and online delivery. LiveLoop per-course session data — recording + attendance + transcript — evidences this metric directly.
National Education Policy 2020 (Ministry of Education, 29 July 2020) on online and digital learning. Recognises asynchronous access to recorded sessions as essential for educational continuity and learner-paced revision.
Digital Personal Data Protection Act 2023, §9 — verifiable parental consent for processing personal data of children under 18. Recording of minors falls inside the consent boundary; the school is the Data Fiduciary, LiveLoop the Data Processor.
Rights of Persons with Disabilities Act 2016 — equal access to education for children with disabilities. Recordings carry the live-caption transcript bundled with them, so an absent or hearing-impaired student gets the lesson with captions.
The thing I needed evidence of, every quarter, was that the blended portion of our B.Com programme was actually being delivered. Earlier I was collating Zoom links, Drive folders and an Excel attendance sheet by hand the week before the IQAC review. Now I open one panel, pick the course, and export the recording + transcript + attendance log as a single PDF. The Cycle-3 AQAR submission for Metric 2.3.1 took an afternoon, not a week.
A realistic rollout journey — what gets done each week and what gets signed off before go-live.
No "unlimited storage" marketing. The retention you get is the retention you can plan around — by tier.
| Tier | Default retention | Extendable to | Best for |
|---|---|---|---|
| Free | 14 days from session date | Not extendable | Pilots, evaluations, one-off events |
| Paid · default | 90 days from session date | Up to 12 months on request | Routine K-12 and college academic year delivery |
| Archive | 12 months by default | Multi-year on per-institution basis | Boards, NAAC accreditation cycles, board-archive needs |
Retention configuration lives on the recording feature page; confirm the active tier with Databus before publishing student-facing policy.
The library mechanism is the same; the retention need and the inspection anchor change with the buyer.
Class-section-scoped recordings land in the parent app of the absent child the same evening. Anchor: CBSE Bye-Laws Ch. 9 academic record retention.
Live-caption transcript travels with the recording — usable by hearing-impaired and low-literacy English students. Anchor: RPwD §16.
Per-course session data — recording + transcript + attendance — exported as a single PDF for IQAC. Anchor: NAAC AQAR 2.3.1 + UGC 2018.
Batch-scoped library — Foundation, Booster, Final. Watermarked playback prevents the "Telegram leak" failure mode. Cross-link: learning analytics for cohort viewing.
Multi-month retention for NSDC-aligned upskilling programmes. Cross-link: certification-completion defers here for class-recording evidence.
A single-teacher library scoped to their batch, with watermarked playback. The teacher's IP stays the teacher's IP. Cross-link: TutorDesk integration on roadmap.
The full picture — boundary discipline, the honest IP-protection posture, comparison to Drive folders, and the cluster cross-links.
This is the buyer-story page for building a year-long, access-controlled, inspection-ready on-demand library out of the live classes you already run. It owns: retention policy, access scope, parent-app delivery for absentees, the IQAC and CBSE evidence-pack export, and the honest IP-protection posture. It does not own — and explicitly defers — the MP4 file itself, the absentee auto-share mechanism, searchable transcripts, click-to-jump, post-session digests, and per-session viewing data. Each of those has a dedicated owner page that does the deep mechanism work.
The reason this discipline matters: if this page tried to re-document the MP4 mechanism or the transcript search interaction, it would cannibalise the feature pages that already rank for those terms. The cluster's defer-by-link rule keeps each surface clean.
Five LiveLoop surfaces touch the word "recording" — knowing which one owns which decision saves the evaluator's time.
The live class ends. LiveLoop stops the recording, finalises the MP4 and the bundled live-caption transcript, and writes both to storage. The recording is attached to the SchoolDeck timetable period it belongs to — so it shows up in the right place in the timetable, not in a flat date-list. Session-duration attendance identifies which rostered students were absent. LiveLoop pushes the recording link to those students' parent and student apps. The link opens inside the app — no public URL. The teacher's evening is unchanged; no email composing, no Drive folder uploading, no permission-fiddling.
For the depth on how the MP4 itself is captured, encoded and stored, see the recording feature page. For how the transcript that ships alongside is generated, see the transcription feature page.
Access defaults to the class section that attended. A Class 9-B Science recording is visible only to students rostered in Class 9-B, their parents and their teachers. Multi-section content — a JEE Foundation batch that spans Class 11-A and 11-B, say — is scoped to a named cohort, not the whole school. Single-teacher batches in a TutorDesk-style setup get a private library scoped to the tutor's roster. The admin and the IQAC see an audit log of who watched what, which is the foundation of inspection evidence.
This is where most vendor pages mislead. We won't.
What we do: playback is gated by the user's app login; playback URLs are unique per user and expire on a short window (so a copied URL stops working); a visible dynamic watermark with student identity floats over the player as a deterrent; MP4 download permission is off by default and gated by school admin.
What we don't claim: we do not claim to prevent a determined user from running a screen-recording tool against the playback. No platform can solve that completely — it is a problem of the operating system, not the player. Anyone who tells you otherwise is selling you a misleading guarantee. The honest posture is: access-scope discipline plus visible deterrence, with audit logs that surface anomalies.
For a CBSE inspection or a NAAC AQAR submission, the principal or IQAC coordinator can export a per-course or per-section evidence pack as a single PDF: the recording links (scoped to the inspector's access for the duration of the audit), the bundled transcripts, and the session-duration attendance log. The pack maps directly to CBSE Bye-Laws Ch. 9 academic record retention, UGC (Online Courses) Regulations 2018 blended-mode evidence, and NAAC AQAR Metric 2.3.1 student-centric methods. No collation week required.
We don't claim to prevent screen recording. No platform can. Saying so would mislead a buyer who is genuinely worried about IP leak. The right defence is access scope, watermarking and audit — not a fake guarantee.
We don't build engagement heatmaps for recorded playback. No "which 30 seconds did students rewind the most", no behavioural inference, no attention scoring. The cluster bans this pattern on minors under POCSO duty-of-care and DPDP §9. Live-session participation signals (polls, hand-raise, Q&A) are owned by /liveloop/solutions/student-engagement-tools/.
We don't own subject taxonomy. "Subject > Chapter > Topic" hierarchy belongs to the SchoolDeck academics module. LiveLoop reads the SchoolDeck timetable period metadata and attaches the recording to it; it does not maintain a parallel taxonomy.
We don't host public-link Vimeo/YouTube uploads. Recordings live in the in-app library scoped to the section. If a school wants to publish a session publicly (say, a Founder's Day address) that is a deliberate publishing action through the SchoolDeck communications module, not a default of the recording library.
| What you actually need | Drive folder of Zoom/Meet recordings | LiveLoop on-demand library |
|---|---|---|
| Organisation | Flat list by date — file names | Attached to the timetable period — same place each day |
| Absentee delivery | Teacher emails the link manually | In-app push to absentee parent/student app, auto |
| Access control | Whoever has the link can watch | Scoped to class section / named cohort |
| Identity binding | Same link for everyone | Per-user expiring playback URL |
| Deterrence to leak | No watermark; downloadable by default | Visible dynamic watermark with student identity |
| Captions / transcript | Separate file, separate folder | Bundled with the recording, every time |
| Retention policy | Whatever Drive quota allows, manually managed | Locked tiers: 14 / 90 / 365 days, extendable |
| Inspection evidence | Manual collation the week before | One-click evidence-pack PDF for CBSE Ch. 9 / NAAC |
| Under-18 consent posture | Drive ToS — not a §9-valid consent record | School-collected DPDP §9 verifiable parental consent |
| Cost of teacher time | ~10–15 min per class on upload + share | Zero — recording attaches itself |
The on-demand library sits at the intersection of three product surfaces. SchoolDeck Virtual Classroom schedules the period and provides the timetable hook the recording attaches to. LiveLoop runs the live session and produces the recording artefact. After the class, the recording link appears in SchoolDeck Communication for the absentee push and in the SchoolDeck academic vault for archive. The IQAC pulls the evidence pack from the LiveLoop side; the day-to-day class-teacher and parent flows pull from the SchoolDeck side. The boundary holds: each product owns one thing well, and links 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 run a live class, end it, and show you the recording landing in an absentee's parent app — same screen, same minute.
From ₹499/host/month · Browser only — no installs · Retention 14 / 90 / 365 days