Capture
Receive the agreed group of scan records with the device, campus location and time.
Connected Campus · Attendance & access
A punch is evidence. Attendance needs a trusted decision.
One duplicate or missing attendance scan can become a register dispute, a family call and another task for the teacher. Connect your selected card/tag readers (RFID) or biometric devices to an attendance process staff can check—not a stream of events accepted without question.
Your separately ordered integration combines agreed rules for matching people and repeated scans, staff responsibility for uncertain events and accepted attendance records. It is configured, tested and accepted before your agreed launch.
- Bring
- Your reader models and one disputed or missing scan.
- Check
- Identity matching, repeated scans, late uploads and authorised review.
- Agree
- The supported connection, staff responsibilities and tests before launch.
Your commissioned workflow
From the first scan to a record you can explain.
Each step has a purpose: receive the event, check its context, resolve uncertainty and retain the decision.
Validate
Check that scans match the correct people, times are valid, repeated scans are identified and the device is working.
Review
Route uncertain or conflicting entries to the authorised operator.
Post
Update attendance from accepted events under your institution’s rules.
Reconcile
Keep the reason, reviewer and result so staff can check the record later.
The moments that matter
Design for the exception, not only the perfect scan.
Problem
The learner scans twice.
A second event may be a duplicate, an exit, or a valid correction.
BCO approach
Agree when repeated scans count as duplicates, and send uncertain sequences to an authorised staff member.
Problem
The device goes offline.
Late batches can change a class record after teachers have acted on it.
BCO approach
Record when each scan happened separately from when the device uploaded it. Agree who reviews late uploads before attendance changes.
Problem
An identity does not match.
A card or device identifier may no longer match the correct active student or staff member.
BCO approach
Keep uncertain identities out of the official attendance record until an authorised staff member resolves them.
Acceptance before launch
Test the difficult day as well as the ordinary one.
The checks agreed for acceptance cover the people, devices and failures included in your order—so staff know what to do when a scan cannot be trusted.
- CoverageWhich entry points, campus locations, people and schedules are included?
- AccuracyHow are repeated scans, uncertain identity matches and late uploads checked?
- OwnershipWho reviews an uncertain event, and by when?
- RecoveryWhat happens when hardware, power or connectivity fails?
- PrivacyWhat identifying information is needed, and how long is it kept?
Commissioned for your institution
The right connection, with responsibility built in.
Attendance-device integration is commissioned separately from the base ERP subscription. Your order names the selected models, how they connect, the delivery schedule and the checks required for acceptance. Hardware, installation, network and provider responsibilities are agreed before work begins.
Your attendance rules
- A list of devices, their campus locations and the staff responsible.
- Matching scans to people, identifying repeated scans and handling late uploads.
- Who reviews uncertain scans, makes corrections and retains the history.
- Staff handover and the checks agreed for acceptance.
Your delivery scope
- Named reader models, agreed supplier connections and support contacts.
- Installation, connectivity, warranty and usage costs.
- Approved identifying information, permitted access and storage periods.
- Configuration, testing and acceptance before agreed go-live.
We agree what data is needed for the selected use. Connecting a biometric terminal does not by itself require BCO to store biometric templates—the saved patterns a device uses to recognise a person. Read the Connected Campus buyer questions.
Continue the Smart Campus story