The lecturer opens the roll call
One tap creates the QR and a unique code. Duration and rules come from your institution.
From the QR opened in class to the record sent to the SIS at night, requests, appeals and exemptions run in the same system and leave a trail.
A paper list passed around the room lets anyone sign. DAS verifies every signature with a code, a device and a location, and records who signed and when.
Students scan the QR in class and the signature reaches the lecturer’s screen within seconds.

The server regenerates the code at the interval the lecturer picks. A shared screenshot expires almost at once.
Each student’s device is registered. Several signatures from one phone are flagged.

Your institution picks the rule: off, advisory or required. Signatures far from the class are reported separately.
The lecturer opens the roll call, students sign on their phones, and the record goes to the SIS every night.
One tap creates the QR and a unique code. Duration and rules come from your institution.
They scan the QR or type the code. The device, and the location when your rules turn it on, are checked at the same time.
Signatures are written to the attendance record and sent to the student information system every night.
Every signature stores the phone, and the location too when your rules turn it on. Suspicious signatures stand apart on the live screen; DAS flags them, the lecturer decides.
Device binding
The first QR signature registers the phone to the student’s account. A QR scanned from another phone is not accepted; the student sees which device is registered and how many changes are left.
Shared device
If several students sign the same roll call from one phone, every signature from that phone is marked “Shared device” and grouped apart, with its students, on the live screen’s Device tab.
No false alarms
Everyone in the room connects through the same network. That is why DAS never flags anyone by IP address; it flags only when the phone’s own hardware identity matches.
Your institution picks the location check: off, advisory or required. DAS measures and reports; where it is not sure, it flags no one.
Required location
If your institution requires the location check, a signature from outside the allowed radius is refused on the spot and the student sees how far from the classroom they are.
Location cluster
After the roll call DAS takes the class location from the cluster where most located signatures of that session gather, so no classroom coordinates are needed. A signature outside the radius shows up as “Off-site” with its distance.
Campus report
System administrators see off-site signatures by course, student and session. Distance bands and repeating patterns are flagged as well: a second room nearby, signatures always from the same spot, or repeats across courses.
An off-site signature or a shared device is not proof of cheating on its own. DAS flags it; the lecturer decides.
Every role sees only its own scope: a faculty sees its faculty, a department its department.
Follows how attendance runs across campus, unit by unit, without changing any record.
The most common questions about setup and daily use.
A digital attendance system takes class attendance with the student’s phone instead of a paper sign-in sheet. In DAS the lecturer opens attendance with a dynamic QR and a unique code, each signature is bound to the student’s registered device, location is checked when the institution’s rule requires it, and records are written to the SIS every night.
Talk to our team about setup, the SIS connection and settings for your institution.