A few students being recognised quickly is a promising start to a demonstration. An institution also needs to understand busy arrivals, unsuccessful attempts and staff workload. A pilot should reveal whether everyday operation is manageable under real conditions rather than provide only one impressive demonstration.
1. Define expected scenarios beforehand
Prepare a short list covering entry, exit, late arrival, an unrecognised person and any confirmation screen. Record the number of participants, test times and devices. A group made up only of people who comfortably position themselves in front of the camera may not represent daily operation.
2. Separate wrong matches from no decision
Correct recognition, no decision and selection of the wrong person are different results. Do not hide them inside a single success percentage. A wrong-person attendance record has different implications from an attempt requiring another look. Track each outcome separately with staff verification.
3. Measure the whole transaction
Do not measure only the time until a name appears. Stopping, providing confirmation where required and clearing space for the next person affect total flow. Measure several examples during busy periods. The shortest single attempt should not be interpreted as a guarantee for every student.
4. Count staff interventions
Note cases requiring positioning advice, photo updates or event checks. Where staff struggle can reveal training or placement needs. Record problematic examples and their resolution rather than excluding them. Device operation and the institution’s ability to manage the workflow should be assessed separately.
5. Follow notifications and reports through
Check that each event belongs to the correct student, time and recipient. Record notification timing alongside the channel’s reported status. Use test recipients to avoid unnecessary guardian messages. At the end of the demo, review missing events, corrections and unanswered questions together.
Set demo goals together
Share busy arrival periods and expected scenarios with BE Soft before the demo. Clear measurement goals support a more informed decision afterwards.