Session identity
Link the attendance row to the date, class, subject or activity where it was taken.
ATTENDANCE FACTS AND FOLLOW-UP
Student attendance tracking software for daily exceptions
Give school administrators a cross-class view of attendance facts, explanations and unresolved follow-up while the SIS remains authoritative for official reporting.
The first view shows the populated school-wide register; mobile entry, shared follow-up and cross-session trends provide the evidence behind the numbers.
Free for up to five users. No credit card required.
Adapt fields, workflows, and dashboards without code. Explore 1,000+ app templates and use cases
The gallery shows populated sample data in Jodoo. Open a view to inspect the records and decisions, then install a copy to adapt fields, roles and workflow.
4 attendance statespresent, late, explained and unexplained
Mobile entryfor the point of attendance
Separate follow-upwithout changing the original fact
Capture attendance at the session, not later from memory
A reliable record retains who, where, when and how the attendance status was observed.
Student identity
Use the authoritative student ID with the name displayed for everyday use.
Attendance state
Distinguish present, late, absent explained and absent unexplained rather than using one free-text field.
Timing and recorder
Retain arrival or departure time and the staff member who recorded the fact when relevant.
Keep follow-up separate from the attendance fact
An attendance record should not be rewritten to hide whether an explanation arrived later.
Explanation request
Show which absence needs family contact or supporting information and the next action date.
Repeated lateness
Make patterns visible while preserving each individual session record.
Support or safeguarding handoff
Use the school’s approved pathway for concerns; do not expose sensitive safeguarding detail in a broad operations register.
Resolved follow-up
Record the explanation, outcome and completed date while retaining the original attendance state.
Move from percentage to a useful response
A trend matters when it directs a proportionate action for a student, class or operating process.
Same-day exception
Prioritize unexplained absence and departures that require prompt confirmation.
Class pattern
Review whether repeated lateness or absence clusters around a timetable, transport or activity issue.
Follow-up backlog
See open work by owner and due date instead of assuming a message was sent.
Data quality
Identify missing sessions, duplicate rows and unresolved explanations before reporting.
Keep each state tied to a clear next step
The operational response should follow policy and remain visible to the appropriate role.
| Attendance state | Check | Next step |
|---|---|---|
| Present | Was the session recorded completely? | No follow-up unless the record is incomplete |
| Late | Is the time and reason known? | Record, explain or review a repeated pattern |
| Absent explained | Is the explanation sufficient under policy? | Close or request supporting information |
| Absent unexplained | Has required contact occurred? | Start same-day follow-up or approved escalation |
WHY SCHOOLS BUILD THIS IN JODOO
Make class exceptions visible without rebuilding the student system
Jodoo gives school administrators a configurable layer for session capture, explanations and owned follow-up around the SIS.
A school team can build an operational attendance-exception layer in hours while keeping statutory reporting in the approved SIS.Capture the class fact quickly
Keep the mobile entry focused on student, session, status, time and observation.
Separate fact from follow-up
Preserve the original attendance state while contact, explanation and correction work continue.
See unresolved work across classes
Give attendance staff a cross-class queue for unexplained absence, repeated lateness and missing evidence.
Adapt to policy without code
Change allowed statuses, follow-up fields and operational dashboards when school rules change.
Use Jodoo for operational attendance work around the SIS
This page is for school-wide, cross-class exception handling rather than a teacher-only tracker.
Strong Jodoo fit
Mobile session entry, explanations, cross-class follow-up queues and configurable operational views.
Keep authoritative records
Keep enrollment, statutory attendance reporting and sensitive safeguarding casework in approved systems.
Reconcile deliberately
Use stable student and session IDs and define how corrections return to the official record.
Questions about student attendance tracking software
Can teachers record attendance on a phone?
Yes. The example includes a focused mobile form for student, class, session date, status, time and explanation context.
Does this replace a school SIS?
No. Use the SIS as the authoritative student and statutory attendance system when required. Jodoo can support local collection or configurable exception follow-up.
Can the system track explanations after the session?
Yes. Keep the original attendance fact and record the later contact, explanation, evidence request and resolved date in a related follow-up record.
Can dashboards show absence and lateness patterns?
Yes. Dashboards can summarize sessions, attendance states and open follow-up, with drilldown to the underlying rows.
EXPLORE THE POPULATED APP
Test the attendance exception, not just the roll call
Open the populated register, submit a mobile attendance row and inspect how an unexplained absence becomes visible follow-up.
Try the attendance App