01
Configure your tenant.
Import student records via CSV. Define check-in windows (morning, lunch, afternoon). Assign schedule groups. Set the detention threshold. Apply your branding, colors, and timezone.
How it works
From check-in to year-end reporting.
A four-step deployment process. Attendy integrates with your existing workflow and automates the administrative work behind every check-in.
02
Capture attendance.
Use any combination of QR kiosks, scantron uploads, manual entry, or self-service tablets. All channels write to the same unified attendance record.
03
Automate workflows.
Late passes convert absences to late records. Excused-absence windows suppress detentions. Beyond the configured threshold, detentions are auto-generated with full audit trail back to the originating absences.
04
Run reports.
Reports refresh nightly and are ready before the next school day. Filter by group, tag, schedule, or registration. Save filter sets. Export to CSV, XLSX, or PDF on demand.
Operational timeline
A typical day, end to end.
- 7:42 AM
First scan
A student scans their QR at the entrance kiosk. The dashboard increments. Schedule group and registration type are matched automatically.
- 8:05 AM
Late pass issued
A teacher issues a 15-minute late pass. The system converts what would have been an absence into a late record without manual reentry.
- 9:18 AM
Scantron upload
An off-site classroom uploads a photograph of the printed Attendy bubble sheet. OMR processing converts the image into structured attendance records.
- 12:30 PM
Lunch window opens
Afternoon-schedule students begin checking in. Morning-only students are not marked absent during the lunch window.
- 3:25 PM
Detention queue updated
Three new detentions are auto-generated for students who crossed the threshold, with full audit trail back to the originating absences.
- Overnight
End-of-day processing
Unscanned records are converted to absent status, expired coupons are cleared, and the next day's reports are prepared.
Frequently asked
Common questions from evaluation teams.
Do kiosks require internet connectivity?
Yes. Kiosks are web-based and require an internet connection to record check-ins. Standard school Wi-Fi is sufficient — no specialized network infrastructure required.
Can multiple capture methods be used simultaneously?
Yes. Many deployments use QR scanning at the main entrance, scantron processing in classrooms, and manual entry for late arrivals. All channels write to the same unified attendance record.
How are detentions generated?
When a student exceeds the configured unexcused-absence threshold (default: 3), the system auto-generates a pending detention linked to the originating absence records. The threshold is adjustable per tenant.
How does the multi-school architecture work?
Each school is provisioned as a fully isolated tenant with its own subdomain or custom domain, isolated data, and independent configuration. Districts and networks receive a centralized superuser console for cross-tenant administration.
Where is data hosted?
Deployments can be targeted to the region that matches your compliance requirements. Specific hosting and residency details are covered on the demo call to align with your policies.
Modernize attendance management at your school.
Schedule a 30-minute walkthrough on a working tenant. Our team will review your deployment requirements and answer technical questions.