Skip to content

In use at: Manisa Celal Bayar University
One system, every step

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.

Dynamic QRUnique code sign-inLocation checkOff-site signature reportDevice bindingManual signatureHeadcount declarationMerged lecturesLate-open requestMake-up classCorrection request
Student appealBulk exemptionExcluded coursesSignature correction ledgerSIS transferInstitutional sign-in (SSO)LDAP / Active DirectoryPDF, Excel, CSVEvent attendanceAudit logPush notifications
Why DAS

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.

Goodbye to the paper list

Students scan the QR in class and the signature reaches the lecturer’s screen within seconds.

The QR is dynamic, a copy is useless

The server regenerates the code at the interval the lecturer picks. A shared screenshot expires almost at once.

Every signature tied to a device

Each student’s device is registered. Several signatures from one phone are flagged.

Location checked by your rules

Your institution picks the rule: off, advisory or required. Signatures far from the class are reported separately.

How it works

The lecturer opens the roll call, students sign on their phones, and the record goes to the SIS every night.

  1. The lecturer opens the roll call

    One tap creates the QR and a unique code. Duration and rules come from your institution.

  2. Students sign on their phones

    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.

  3. The record goes to the SIS

    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

Each student, one phone

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.

  • Two device changes per term, renewed every term
  • When changes run out, the student asks the lecturer from the app
  • The lecturer grants an extra change with a written reason; it goes into the audit log

Shared device

Two signatures from one phone show up at once

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.

  • One match is enough, signing is not blocked
  • Also visible in roll-call history and on the student’s detail page
  • Feeds the campus-wide anomaly report

No false alarms

Same Wi-Fi is not a reason for suspicion

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.

  • An IP address alone never raises a flag
  • Randomised or fake identifiers are ignored
  • Phones whose identity cannot be read are listed separately

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

When location is required, far signatures are refused

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.

  • The radius is set in the panel, from 10 m to 50 km
  • If the institution chooses, a lecturer cannot open a roll call without location
  • A distance that cannot be measured never drops a signature

Location cluster

The class finds its own location

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.

  • At least 5 located signatures and a majority cluster are needed
  • If signatures are few or scattered, no one is flagged
  • Any measurement margin counts in the student’s favour; the lecturer can accept the signature

Campus report

Campus-wide, in one list

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.

  • The report opens only for administrators with two-step sign-in
  • Filtered by distance band, exported to Excel
  • Decision support, not proof of cheating on its own

An off-site signature or a shared device is not proof of cheating on its own. DAS flags it; the lecturer decides.

Security and data protection in detail

Who it’s for

Every role sees only its own scope: a faculty sees its faculty, a department its department.

Rectorate and leadership

University-wide · view only

Follows how attendance runs across campus, unit by unit, without changing any record.

What they see and learn

  • Class hours opened and courses with a roll call
  • Breakdown by faculty, department and programme
  • Which unit opened its expected classes in which week
  • Roll calls open right now and pending work

Their screens

  • Home
  • Live Monitoring
  • Compliance Analysis
  • Weekly Compliance Matrix
  • Lecturer Reports
FAQ

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.