How attendance is verified, explained, reviewed, and recorded
A transparent path from a geo-fenced check-in to a final, auditable record — with a clear role for the student, faculty, and administration at every stage.
Presence is checked against a defined boundary
Each class, lab, or departmental session is assigned a geo-fence — a defined location boundary. When a student marks attendance from the app, the device location is checked against that boundary. Marks made from within the boundary are accepted automatically; marks made outside it are flagged for review.
- Boundaries are configured per room, lab, or campus area by administrators.
- Device location is used only at the point of marking, for verification.
- Out-of-boundary marks route automatically to the reason workflow.
A structured path for missed or late attendance
When a mark is missed, late, or made outside the geo-fence, the student can submit a reason directly from the app. The request then moves through a defined review path rather than an informal email or in-person conversation.
1. Reason submitted
The student selects the affected session and submits a reason, with optional supporting notes.
2. Term conditions applied
The system checks the request against the active term's attendance rules before it reaches faculty.
3. Faculty review
The faculty member responsible for the session approves, returns, or requests more information.
4. Status recorded
The final decision updates the student's attendance record and is visible in their history.
Term A — Lecture-heavy
Standard reason categories, single-level faculty approval.
Rules that follow the academic calendar, not a fixed default
Attendance requirements can differ meaningfully between a lecture-focused term and a practical- or posting-heavy term. AAS's rule engine lets administrators define attendance thresholds, accepted reason categories, and approval steps per term, semester, or department — so a pathology practical term can carry different conditions than a standard lecture term.
Review and escalation, with a clear owner at each step
Session-owning faculty
First review sits with the faculty member who ran the affected session or posting.
Department escalation
Unresolved or disputed requests can be escalated to the department coordinator.
Administrative override
Administrators can override a status when required, with the reason and actor logged.
Every override leaves a trace, every status stays visible
Faculty and administrative actions — approvals, returns, and overrides — are logged with the acting user and timestamp, so the history of a decision is always reconstructable. Students see a clear, current status for every session rather than an ambiguous or delayed update.
- Full audit trace on every override or manual edit
- Transparent, always-current status for students
- Exportable records for institutional review
Frequently asked questions
Each session is assigned a defined location boundary. When a student marks attendance, their device location is checked against that boundary before the mark is accepted. Try the live demo above to see how the boundary check works.
Yes. Students can submit a reason directly from the mobile app for a missed, late, or out-of-boundary mark, which then enters the faculty review workflow.
Yes. Attendance thresholds, accepted reason categories, and approval steps are configurable per term, semester, or department.
Yes. The student app is intended for distribution on both Google Play Store and Apple App Store. See the Mobile Apps page for details.
Yes. Department-wise visibility means pathology faculty and coordinators review and manage attendance for their own postings, labs, and seminars independently of other departments.
Yes. Attendance logs can be filtered and exported by student, batch, department, or date range for institutional recordkeeping.
Walk through the policy engine with your own rules
We can map your existing attendance policy into the term rule engine when you reach out.