BL TECHNO Global School Management Platform • Local-currency pricing Explore the platform
← Feature LibraryACADEMIC FEATURE
AT
BL TECHNO FEATUREAttendance

Make attendance visible from classroom to gate.

Support manual registers, sign-in/sign-out records, attendance events and device-assisted identity workflows while keeping school, centre and class context together.

Built for Administrators • Teachers • Gate/Attendance Teams
Manual RegisterDrop-off / PickupQR / CardBiometric ReferencesEventsParent Alerts
FeatureAttendance
Operating areaAcademic
Product familyBL TECHNO School
Access modelRole + scope aware
ExperienceResponsive
WHY THIS FEATURE MATTERS

Connect the learner journey from first capture to everyday academic action.

Support 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 →
01Learner context
02Centre & class scope
03Role-aware access
04School-time context
HOW ATTENDANCE WORKS

Follow the workflow from first action to review.

Tap a step to change the visual. Each stage comes directly from the feature workflow defined for BL TECHNO.

BL TECHNO Attendance Control illustrative mockupSTEP 01
ACADEMIC WORKFLOW

Scope

Country, centre & class

Attendance Control
BL TECHNO Student Management illustrative mockupSTEP 02
ACADEMIC WORKFLOW

Identify

Learner / approved device

Student Management
BL TECHNO Teacher Platform illustrative mockupSTEP 03
ACADEMIC WORKFLOW

Record

Present, sign-in or sign-out

Teacher Platform
BL TECHNO School Command Centre illustrative mockupSTEP 04
ACADEMIC WORKFLOW

Review

Events & exceptions

School Command Centre
BL TECHNO School Command Dashboard illustrative mockupSTEP 05
ACADEMIC WORKFLOW

Act

Alerts and follow-up

School Command Dashboard
OPERATIONAL OUTCOMES

What Attendance is designed to improve.

These outcomes describe the operating purpose of the feature without inventing customer statistics.

01

One attendance picture

Bring class, gate and event attendance information into the same school context.

02

Flexible capture

Support manual and approved device-assisted workflows instead of forcing one capture method.

03

Faster follow-up

Surface attendance events and parent-alert workflows for authorised teams.

CAPABILITY MAP

Go inside Attendance.

Six capability areas show what the feature organises and how the workflow becomes operational.

MR

Manual Register

Run a conventional class attendance workflow digitally.

Class registerAttendance statusDaily captureTeacher/admin use
GP

Gate Sign-In / Out

Track drop-off and pickup sign activity.

Drop-offPickupGate recordsToday at gate
ID

Identity Methods

Support approved card, QR, face-reference or fingerprint-reference registration.

ID cardQRFace referenceFingerprint reference
DV

Devices & Rules

Register attendance devices and connect rules to capture workflows.

Device registrationAttendance ruleSaved devicesScanner/API logs
EV

Attendance Events

Review captured attendance events across the configured scope.

Event historyClass scopeGate eventsStatus summary
AL

Parent Alert Queue

Prepare appropriate follow-up for attendance exceptions.

Alert queueAttendance exceptionFamily follow-upAuthorised action
OPERATIONAL SIGNALS

Bring the information that matters closer to action.

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.

PresentDaily attendance
GateSign-in / sign-out
EventsCapture history
DevicesScanner readiness
AlertsFollow-up queue
ScopeCentre & class
BL TECHNO Attendance Control mockupAttendance Control
WHO USES IT

One feature. Different responsibilities.

Switch roles to see how the same feature serves different authorised users without giving everyone the same view.

CONNECTED WORK

Attendance does not have to become another isolated tool.

Move into the neighbouring workflows that share relevant school context.

CONNECTED PLATFORM STORY

See Attendance as part of the wider BL TECHNO environment.

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.

IMPLEMENTATION PATH

Introduce Attendance as an operating process, not just another screen.

The exact implementation depends on school size, plan and scope. This path shows the practical sequence for introducing the feature responsibly.

01

Discover

Identify where Attendance fits into the school’s current operating process and what should improve.

02

Configure

Confirm centres, classes, learner context and the people who will use the workflow.

03

Prepare

Check the records, settings and authorised users needed for Attendance to work cleanly from day one.

04

Train

Walk the responsible teams through the Attendance workflow using their real roles and school scope.

05

Launch

Introduce Attendance into the agreed school process with controlled access and clear ownership.

06

Review

Review usage, exceptions and operating quality, then refine the school process where needed.

SECURITY & GOVERNANCE

Access follows responsibility.

Attendance inherits BL TECHNO’s role, scope and permission principles. Public marketing shows the controls; authenticated product access remains authoritative.

Attendance scope by school/centre/class
Controlled identity-device registration
Sensitive biometric reference handling
Role-based event access
Explore Security →
IDENTITYWho is signed in?
ROLEWhat is their responsibility?
SCOPEWhich school / centre / class?
FEATUREAttendance
RESPONSIVE EXPERIENCE

Fit the feature to where the role works.

Tablet-friendly academic workflowsPhone-ready review and follow-upTouch-friendly controlsReadable learner context
Explore Mobile Experience →
GLOBAL CONTEXT

Keep local school context configurable.

School timezone contextLocale-aware dates and timeCountry-aware school configurationTranslation-ready interface structure
Explore Global Platform →
FEATURE FAQ

Questions about Attendance.

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.

SEE ATTENDANCE IN CONTEXT

Bring this workflow into your tailored BL TECHNO demo.

Inspect the feature in detail, then see how it connects to the product family and wider school operation.