Talk to us about your tutoring attendance management project.
Tell us how your centre tracks attendance and manages cancellations today. We'll tell you what we'd build and how.
Finding out a tutor did not show up for a session only when the parent messages to complain, rather than the moment the session was supposed to start?
Cancellation charges being applied to some students but waived for others because there is no system enforcing the rule consistently?
Tutoring centres that track attendance manually discover tutor no-shows late, apply cancellation rules inconsistently, and have no clear picture of how many booked sessions are actually being delivered versus how many are falling away to cancellations.
We build custom attendance and session management software for tutoring centres -- tutor check-in with session time recording, automated no-show alerts, student attendance logging, cancellation rule enforcement, and utilisation reporting that shows what is actually happening across the centre.
Tutor check-in with session start and end time recording
Automated no-show alerts when a session starts without a tutor check-in
Student attendance logging linked to each student record
Cancellation rule enforcement with late charge triggers and make-up scheduling
Tutoring centre attendance management software records session start and end times via tutor check-in, logs student attendance per session, fires automated alerts when a tutor has not checked in at session start time, and applies configurable cancellation rules including late cancellation charge triggers and make-up session scheduling. RaftLabs builds custom attendance and session management systems for tutoring centres that need accurate records tied to each student, tutor, and session -- not a manual spreadsheet that gets corrected after parents complain.
Without structured attendance tracking, tutor no-shows are caught late. The session starts, the student sits waiting, and nobody at the centre knows until the parent calls or messages. By then the student has already had a wasted session and the parent's confidence in the centre has taken a hit. A manual check-in sheet or a spreadsheet updated after the fact does not give the centre the immediate signal it needs to act.
Cancellation management has the same problem. Most tutoring centres have a notice period policy -- cancel within 24 hours and a charge applies, or a make-up session is owed. Without a system enforcing that rule, application depends on which admin team member handles the cancellation and whether they remember to apply the charge. Some students pay it, some don't. The inconsistency creates disputes that could have been avoided.
Utilisation is the third gap. A centre can have a full booking schedule on paper while a significant portion of those sessions are being cancelled by students or absorbed as tutor absences. Without session completion data broken down by cancellation type, the centre director cannot see the revenue gap or identify which tutors or which subject areas have the highest cancellation rates. Custom attendance and session management software closes all three of these gaps in a single connected system.
The session clock starts when the tutor checks in at or before the scheduled session start time, giving the centre a precise record of when each session began. Check-in is done by the tutor via a mobile-friendly interface, removing any reliance on an admin team member to log the start time manually. Session end time is recorded in the same way when the tutor marks the session complete, producing an accurate duration for every lesson delivered. The check-in record is linked to the session booking, the tutor's profile, and the student's attendance record so all three update from the same action. Duration data feeds into utilisation reporting so the centre can see whether sessions are running to their scheduled length or being cut short consistently.
When a session start time passes without a corresponding tutor check-in, the system generates an alert to the centre's admin team immediately -- not when the parent complains twenty minutes later. The alert includes the session details, the assigned tutor, and the student affected, so the admin team has everything they need to respond without looking it up. The alert timestamp is stored against the session record so there is a clear log of when the centre was notified and what action was taken. No-show events are recorded separately from student cancellations in the utilisation data, making it possible to see tutor reliability by individual and by subject area. The alert threshold is configurable so the centre can decide whether to trigger at one minute past the start time or allow a short grace period.
Every session generates an attendance record for the student linked to their profile -- present, absent, or late -- updated by the tutor at the time of the session rather than reconstructed afterwards. The attendance record is visible to the admin team and to parents through the parent portal so the attendance history is transparent and does not need to be compiled manually when a parent asks. Cumulative attendance data per student feeds into progress records and retention reporting, giving the centre a signal when a student's attendance frequency is declining before they cancel their enrolment. The distinction between student-initiated absences and tutor-initiated cancellations is maintained in the record so utilisation reporting can attribute each missed session to the right cause. Absence notifications are sent to parents automatically when a session is marked absent without a prior cancellation.
Notice period rules are configured once by the centre and applied consistently to every cancellation from that point forward -- no manual discretion required. When a student cancels within the configured notice window, the system flags the late cancellation automatically and triggers the configured response, whether that is a charge to the student's account, a deduction from their session package, or a make-up session workflow. Make-up session scheduling is built into the cancellation flow so the admin team can offer an alternative slot immediately rather than handling it in a separate message thread. The full cancellation history -- notice given, rule applied, charge outcome, and make-up status -- is stored against the student record. Parents receive a cancellation confirmation that states the notice period outcome clearly, removing ambiguity about whether a charge applies.
When a tutor updates their availability, the change is reflected in the scheduling system immediately rather than sitting in an email that gets actioned the following morning. Tutors update their own availability via a mobile-accessible interface, removing the admin overhead of relaying availability changes between the tutor and the booking system. Availability changes that affect already-booked sessions surface a list of affected students so the admin team can initiate rescheduling before the student is left waiting for a session that no longer has a tutor. Temporary blocks -- a week's holiday, a university exam period, a training day -- are handled separately from permanent availability changes so the tutor's default schedule is not disrupted. The availability record feeds directly into the tutor matching and scheduling system so new bookings only ever show times the tutor has confirmed as available.
Utilisation reporting shows the centre exactly how many booked sessions are being completed versus how many are being cancelled, and breaks cancellations down by type -- cancelled by the student, cancelled by the tutor, and cancelled by the centre. Each cancellation type carries a different revenue implication: a late student cancellation where a charge applies has a different financial outcome from a tutor no-show where the centre owes the student a make-up. The revenue impact of each cancellation type is calculated and displayed alongside the session count so the centre director can see the cost of each category. Tutor-level utilisation shows completion rate and cancellation rate by individual so quality management decisions are based on data rather than impression. The report covers any date range and can be filtered by subject, tutor, or student group, giving the centre the view it needs for weekly review or monthly planning.
Frequently asked questions
The system compares the scheduled session start time against the tutor's check-in timestamp. If the session start time passes and no check-in has been recorded for that session, an alert is generated and sent to the configured admin contacts immediately. The alert includes the session time, the tutor's name, and the student affected so the admin team can contact the tutor and the parent without looking up the details. The no-show event is logged against the session record with a timestamp showing when the alert was triggered. The grace period before the alert fires is configurable -- some centres prefer an immediate alert at the session start minute; others allow a short window before the alert goes out.
Yes. The centre configures the notice period -- for example, cancellations with less than 24 hours notice trigger a late cancellation charge -- and the system applies that rule to every qualifying cancellation without manual intervention. The charge action is also configurable: the system can post a charge to the student's account, deduct a session from their package balance, or initiate a make-up session workflow, depending on the centre's policy. The rule applies consistently to every student regardless of which admin team member processes the cancellation. The cancellation record stores the notice period given, the rule that was applied, and the outcome so there is a clear audit trail if a parent disputes the charge.
Tutors update their availability directly in the system via a mobile-friendly interface. The change takes effect immediately and the scheduling system reflects it in real time -- there is no delay waiting for an admin team member to relay the update. When an availability change affects sessions that are already booked, the system identifies those sessions and surfaces them in the admin team's dashboard so rescheduling can be initiated before the student arrives for a session that no longer has a tutor. Temporary blocks for holidays or specific periods are handled without changing the tutor's default weekly availability, so the regular schedule restores automatically when the block period ends.
A focused attendance and session management module -- tutor check-in, no-show alerts, student attendance logging, cancellation rule enforcement, and utilisation reporting -- typically runs $15,000--$30,000 depending on the number of tutors, the complexity of the cancellation rules, and whether the module is being integrated into an existing scheduling system or built as part of a new platform. When attendance management is built as part of a full tutoring centre platform alongside scheduling, parent portal, and payment processing, the combined cost typically runs $65,000--$110,000. We scope every project before pricing -- fixed cost, agreed before development starts.
What clients say
Three-year average engagement. Founders and operators describing the work in their own words. No marketing varnish.

RaftLabs has been an exceptional partner. From the start, they became more than just a service provider, they embraced our vision with their expertise and dedication.
01 / 02
Tell us how your centre tracks attendance and manages cancellations today. We'll tell you what we'd build and how.