Attendance
Mark attendance per batch, per session.
What this covers
- 1Session-level captureAttendance per batch
- 2What to use instead, while totals waitRenewal tracking for who is unlikely to come back
- 3What has to change before totals shipA required session label on every capture
In short
What does attendance do in RaivatEdu?
RaivatEdu records attendance per batch, per session, with a session label, against the student records already in the workspace. It does not publish attendance totals or percentages: the uniqueness constraint on the attendance table allows duplicate rows where the session label is empty, so any total built on it could be wrong, and we would rather say so than print a number you cannot defend.
- per session
- Per batch
- student records
- Shared
- totals published yet
- No
What attendance does today.
Every line here is a feature that exists in the product right now. Anything still being built is listed further down, on the same page.
01
Session-level capture
Pick a batch, pick the session, mark who was there. The record sits against the same student your admissions and fee teams work from, so attendance is not a parallel list in another tool.
- Attendance per batch
- Per session, with a session label
- Against the shared student record
02
What to use instead, while totals wait
The questions institutes usually ask attendance to answer are commercial ones: who has gone quiet, who is not going to renew, who owes money. Those are answered better elsewhere in the workspace, and answered from data that is safe to add up.
- Renewal tracking for who is unlikely to come back
- Dues and ageing for who owes what
- The student record for a learner you are worried about
03
What has to change before totals ship
The fix is small and specific: the uniqueness constraint on the attendance table currently includes a session label that is allowed to be empty, which is what lets two rows describe the same student in the same session. Once that label is required, the existing captures become countable and totals follow. We would rather tell you that than show you an average.
- A required session label on every capture
- Then totals are a calculation over clean rows
- Captures you make today are the rows those totals will use
Where this stops
What attendance does not do.
We would rather you read this before you buy than discover it in week two. If something here is a requirement for you, tell us and we’ll be straight about the timeline.
Ask us about a gap- Attendance totals and percentages are not published. The uniqueness constraint on the attendance table includes a session label that can be empty, which means duplicate rows are possible, so a total built from it is not yet trustworthy.
- Nothing in the product decides exam eligibility from attendance.
- No automatic notification goes to a guardian when a student is absent.
FAQ
Attendance, answered plainly.
Yes, per batch and per session, with a session label, against the same student records the rest of the workspace uses.
Not yet, and we will not show you one. The uniqueness constraint on the attendance table includes a session label that can be empty, so duplicate rows are possible and any percentage calculated from them could be wrong. Capture works; totals wait for that constraint to be fixed.
No. There is no exam or eligibility logic in the product, and no rule that reads attendance to allow or block anything.
No. There is no automatic absence alert. Absence is visible to your team in the workspace.
Because capture is genuinely useful on its own: a faculty member marking a session builds the record that the totals will eventually be calculated from. We would rather ship the honest half than a number nobody can defend.
Yes. The captures are real rows against real students. What is missing is a constraint that guarantees no two rows describe the same student in the same session, and adding it does not throw away what you have already marked.
Use the parts of the workspace that are safe to add up. Renewal tracking tells you who is unlikely to come back, dues and ageing tell you who owes what, and the student record carries the history for a learner you are already worried about.
Attendance sits in the workspace against the student record, alongside the rest of your data. What we do not do is publish a derived figure on top of it while a duplicate row is possible.
Next in the product
- Students & BatchesOne record per learner, documents attached, and batches with real seat limits.
- Enrolment & RenewalsEnrol onto a batch, then price it — plus renewal rules you set once.
- ReportsCollections, dues and education KPIs you can click through to the list.
Your next student is already looking for you.
Give your admissions team one place to capture, connect and convert every opportunity.
Rather talk it through? Request a callback or talk to sales.
- 30-minute walkthrough
- Your workflow, not a script
- No card required