Skip to content

Attendance

School Admin Teacher Student Parent

Attendance records one daily status for every enrolled student. Teachers and the office mark it by hand. Gate devices that recognise faces can also mark it. Each night the system marks anyone still unrecorded as absent and tells their parents. Families see the result under My Attendance.

Attendance has four screens: Mark Attendance, Attendance History, Devices and Attendance Policy.

Partially implemented

The register, history, devices and policies all work. There is no screen for holidays or weekly offs, and marking by period is not built yet. Read Holidays and weekly offs before your first working week.

Before you start

  • SOL has switched on Attendance for your institution. It is included by default.
  • An academic session is marked current. See Academic sessions.
  • Students are enrolled in a division for the current session. The register lists enrolled students, not everyone on file. See Add a student.
  • Teachers have teaching assignments for their divisions. Without one, a teacher's register is empty. See Teaching assignments.
  • For gate devices only: SOL has registered the device and allotted it to your institution.

Where to find it

SidebarPage headingWho sees it
Attendance → Mark AttendanceAttendanceAnyone who can mark attendance (School Admin, Teacher)
Attendance → Attendance HistoryAttendanceAnyone who can mark attendance
Attendance → DevicesAttendance devicesSchool Admin, Teacher
Attendance → Attendance PolicyAttendance policySchool Admin, Teacher
My Institution → My AttendanceAttendanceStudents and parents

Most staff pages follow the working-scope picker in the top bar. The page description then reads "<unit> and everything under it."


Mark the daily register

The daily register, with Present and Absent buttons on every row

Step by step

  1. From the sidebar choose Attendance → Mark Attendance.
  2. Use the top-bar picker to choose the division you are marking. A teacher's picker lists only the divisions they teach.
  3. The date starts at your institution's today. To mark another day, use Previous day / Next day or type a date.
  4. For most classes, click Mark rest present. Confirm with Mark present in the Mark everyone else present? dialog. Only rows that are still unmarked change.
  5. Correct the exceptions one row at a time:
    • Present: click Present. It saves straight away.
    • Absent, late or excused: click More, choose Absent, Late or Excused, then answer "Why is <name> marked …?". Pick a suggested reason or type one in Or type a reason…. Click Save.
  6. Check the counter ("X of Y marked") and the Not marked card. When both show everyone accounted for, you are done.

Marking a student absent, late or excused

Use More on the student's row, choose the status and give a reason — every status other than Present needs one. Mark absences one row at a time.

Reasons parents understand

The suggested reasons are: late — "Bus was late", "Medical appointment", "Overslept"; absent — "Off sick", "Family emergency", "No reason given"; excused — "Approved leave", "Official activity", "Religious observance". The reason is saved with your name and the time.

The teacher's register looks the same, limited to their own divisions:

A teacher's register for their campus

What the register shows

ItemMeaning
On the registerStudents enrolled in the chosen division(s) this session
PresentPresent, late and half-day students together; the hint says how many "arrived late"
AbsentStudents marked absent
Not markedNobody has recorded anything yet ("Nobody has said they were away")
Roll, Student, DivisionFrom the student's enrolment. The name opens the student record
First seenThe first device punch of the day. "+Nm" means N minutes late
StatusThe marking buttons. People without permission to mark see no buttons here

Statuses you can set by hand are Present, Late, Absent and Excused. Half day is set only by devices, based on the policy's sessions.


Attendance history

  • Staff (Attendance → Attendance History): choose a Range (Last 30 days, Last term (90 days), Last 180 days) and an Up to date. Then pick a unit in the top bar. The page shows Students, Average attendance and Below 75%, plus an Attendance by student table (Present, Absent, Late, Attendance %). "Not recorded" means no register was taken for that student in the range. It is not the same as 0%. The 75% line is fixed in the app and cannot be changed.
  • Excused days don't count against a student's percentage.

What students and parents see (My Attendance)

Parents open My Institution → My Attendance. They see "Every day recorded for your child." If they have more than one child, a Child picker appears. There is also a monthly calendar (The month) and a Day by day list with in and out times.

A parent's My Attendance page with calendar and day-by-day list

Students

Students can see their attendance for the last 30 days on My Profile, under The institution's record.


Devices (face-recognition gates)

SOL registers each physical unit and allots it to your institution. Your institution then names it, maps people to it, and checks that punches arrive.

Step by step

  1. From the sidebar choose Attendance → Devices (heading Attendance devices).
  2. Click Add device. In Set up a device:
    • Serial: choose one of the units SOL allotted to you. If a unit is missing, ask SOL support.
    • Name: for example "Main gate".
    • Where it is: a unit, or leave Whole institution. This only describes the device. Attendance counts for the person, not the door.
    • Latitude / Longitude: optional. Fill in both or neither.
    • Click Save device. You see "<name> added. It will appear here once it calls in."
  3. Enrol faces on the terminal itself. The terminal gives each enrolled person a number. That number appears in Recent device activity as Device user.
  4. Click Map somebody. Choose Student or Staff, find the person, enter the Device user id, then click Map. You see "Mapped. Their next punch will land on the register."
  5. To check the whole chain, click Test on the device row. Enter a Device user id and click Send a test punch. "Punch accepted. It becomes attendance within a minute." means it worked.

More than one device

Map somebody always maps to the first device in the list, and you can't pick a different device there. If your institution has several gates, check the Device column in Who the devices know after mapping. Ask SOL support before relying on the other gates.

Ignore the "new token" warning in the Test dialog

The Test dialog says it "issues the device a new token". Devices use a credential managed by SOL, so you don't need to do anything to the unit after a test.

Fields

FieldRequiredWhat to enter
SerialYesA unit SOL allotted to you (chosen from the list)
NameYesA name staff recognise, e.g. "Main gate"
Where it isNoThe unit the device belongs to; default Whole institution
Latitude / LongitudeNoBoth or neither
Device user id (mapping)YesThe number the terminal gave the person at face enrolment, not their admission number

Reading the device page

  • Last heard from: "Never" means the unit has not called in yet.
  • On the hardware (mapping sync): Pending, Synced or Failed. Faces sync to the hardware in the background about every 15 minutes.
  • Recent device activity (last 50 punches): the Outcome column says why a punch did not become attendance, for example an unknown device or an unmapped device user.

Attendance policy

The policy sets when the day starts, how much grace late arrivals get, and what a device punch means. Onboarding creates a default policy: once a day, a "Day" session from 08:00 to 14:30, 10 minutes grace.

Step by step

  1. From the sidebar choose Attendance → Attendance Policy. In effect today shows the rule now in force for each part of the institution.
  2. Click New policy and fill in New attendance policy (fields below).
  3. Click Save policy. New punches are judged against it straight away.

A change never rewrites the past. Each policy starts from a date, and older days keep their old rule. A policy that has not started yet shows a Scheduled badge. You can remove it with the bin icon ("Remove this scheduled change?"). A policy already in effect cannot be removed. Create a new one from a later date instead.

Fields

FieldRequiredWhat to enter
Applies toYesWhole institution (default) or one unit. A unit's own policy overrides the institution default for that unit
How attendance is takenYesOnce a day, Morning & afternoon, Every period or Device punches only
Starts applying onNoLeave blank: the first policy for a scope applies from the beginning; later ones start today
Grace minutesYes0–240 (default 10). Arriving within this many minutes of a session opening is on time
A device punch marks somebody presentOn by default. Turn it off if a person must confirm the register
SessionsYes1–8 rows of Name, Opens, Closes (default "Morning 08:00–13:00"). Names must be different and each session must close after it opens

"Every period" is not active yet

You can choose Every period, but lesson-by-lesson registers are not built. Attendance is still recorded once per day.

A policy for the whole institution needs a school-wide role. A teacher can only set one for their own classes.


Holidays and weekly offs

No screen for holidays or weekly offs yet — this affects every parent

Your institution can't enter holidays or change its weekly off days in the app. When onboarding, SOL sets Sunday as the only weekly off.

Every night the system goes through the previous day. If that day was not a holiday or weekly off, it marks every enrolled student with no record Absent and sends each parent a message: "Our records show <child> did not attend on <day>. If that is wrong, please contact the office."

So on a public holiday, or on a Saturday at a five-day school, every student is marked absent and every parent is messaged, unless SOL has entered the holiday or weekly off for you. Before term starts, send SOL support your holiday list and weekly off days.


What happens next

  • Each mark is saved with your name, the time and the reason, and is recorded in the Audit trail.
  • A later device punch does not overwrite a status marked by hand.
  • Nightly (about 01:30): unrecorded students on a working day are marked Absent and their parents are notified. This only happens if a policy and a current academic session exist. Messages depend on the notification service. See Announcements.
  • Parents see the day on My Attendance. The office sees it in Attendance History and Reports.

Who can do this

TaskSchool AdminTeacherStudentParent
Mark the registerYesTheir own divisionsNoNo
Attendance History (staff view)YesTheir own divisionsNoNo
My AttendanceSee warning aboveLinked children
Add devices, map people, policiesYesSees the pages; limited to their own classesNoNo
Unmap a person, remove a scheduled policyYesNoNoNo

Anyone who can mark attendance can change any past date. There is no lock on older registers.

Common problems

SymptomWhyFix
"Say why — this is recorded against the student"You clicked the quick Absent button, or chose a status without a reasonUse More → Absent and give a reason
Ticked students were marked present when you clicked AbsentThe selection-toolbar Absent button confirms "Mark everyone else present?"Correct each student through More
"Nobody on this register — No students are enrolled in this division for the current year."No enrolments in that division for the current sessionEnrol the students. See Add a student
A teacher's register is emptyNo teaching assignment, or no current sessionSee Teaching assignments
Every student marked absent on a holiday; parents messagedHolidays and weekly offs have no screenAsk SOL support to enter them; correct the day with More → Present
Serial list says "No devices allotted to this institution"SOL has not allotted a unit to youContact SOL support
"That class is outside the ones you work with."A teacher tried to act on a division they don't teachChoose one of your own divisions
A device punch doesn't appear on the registerPerson not mapped, or mapped on another deviceCheck Recent device activity → Outcome and Who the devices know
Nobody is ever late or absent from device punchesNo policy in effect ("No policy yet…")Create a policy

Something on this page doesn't match what you see? Contact SolAssists support.