STEP 01Scope
Country, centre & class
Attendance ControlSupport manual registers, sign-in/sign-out records, attendance events and device-assisted identity workflows while keeping school, centre and class context together.
ILLUSTRATIVE • DEMO DATASupport manual registers, sign-in/sign-out records, attendance events and device-assisted identity workflows while keeping school, centre and class context together.
See BL TECHNO School →Tap a step to change the visual. Each stage comes directly from the feature workflow defined for BL TECHNO.
STEP 01Country, centre & class
Attendance Control
STEP 02Learner / approved device
Student Management
STEP 03Present, sign-in or sign-out
Teacher Platform
STEP 04Events & exceptions
School Command Centre
STEP 05Alerts and follow-up
School Command DashboardThese outcomes describe the operating purpose of the feature without inventing customer statistics.
Bring class, gate and event attendance information into the same school context.
Support manual and approved device-assisted workflows instead of forcing one capture method.
Surface attendance events and parent-alert workflows for authorised teams.
Six capability areas show what the feature organises and how the workflow becomes operational.
Run a conventional class attendance workflow digitally.
Track drop-off and pickup sign activity.
Support approved card, QR, face-reference or fingerprint-reference registration.
Register attendance devices and connect rules to capture workflows.
Review captured attendance events across the configured scope.
Prepare appropriate follow-up for attendance exceptions.
The exact records shown depend on the signed-in user, school configuration and current school data. These labels show the kinds of context this feature organises.
Attendance ControlSwitch roles to see how the same feature serves different authorised users without giving everyone the same view.
Capture and review class attendance.
TeacherAttendance ControlManage approved sign-in and identity workflows.
Attendance / Gate TeamTeacher PlatformReview attendance performance and exceptions.
ManagementAttendance ControlMove into the neighbouring workflows that share relevant school context.
This public-safe motion teaser uses illustrative marketing visuals and demo interface language. It is designed to communicate the connected platform story without exposing production school data.
The exact implementation depends on school size, plan and scope. This path shows the practical sequence for introducing the feature responsibly.
Identify where Attendance fits into the school’s current operating process and what should improve.
Confirm centres, classes, learner context and the people who will use the workflow.
Check the records, settings and authorised users needed for Attendance to work cleanly from day one.
Walk the responsible teams through the Attendance workflow using their real roles and school scope.
Introduce Attendance into the agreed school process with controlled access and clear ownership.
Review usage, exceptions and operating quality, then refine the school process where needed.
Attendance inherits BL TECHNO’s role, scope and permission principles. Public marketing shows the controls; authenticated product access remains authoritative.
No. The current attendance module supports manual registers and other capture methods alongside card, QR, face-reference and fingerprint-reference workflows.
The current experience explicitly uses country, centre and class attendance scope.
Yes. The current interface includes drop-off/pickup digital sign records as well as class attendance workflows.
Inspect the feature in detail, then see how it connects to the product family and wider school operation.
BL TECHNO is one global website. We suggest your country automatically so pricing can be shown in the local currency, and you can override the suggestion at any time.