Apply to use it in your courses

You see past sessions of your own course in the app, pick one and export the attendance result as CSV. You upload the file to the SIS yourself; the system has no connection that writes into the school's system, and it never will.

Export in the app is per session. A cumulative term-wide extract is taken from the admin dashboard.

You set the minimum number of minutes a student must have been verified for in order to count as present. If the time is not enough, the record drops to PARTIAL, not ABSENT — not turning up and leaving early are not the same thing.

If the rounds were too sparse to measure the threshold at all, that is marked separately. The student's behaviour is not confused with the system's inability to measure.

When a class is moved to another room or time you enter it in the app. The change is more than a note: reminders shift accordingly and the “impossible travel” flag looks at the correct room.

Class cancellation and make-up classes are separate concepts and are entered from the same screen: treating a cancelled class as a moved one would record absences from a class that never happened.

Attendance taken while there is no network accumulates on your device and is sent when the connection returns. On the queue screen you see what has gone through and what is still waiting.

A submission whose outcome stays uncertain is marked uncertain and is not retried automatically. Silently sending a second time would risk writing a student's record twice.

If the system could not be used at all, you can photograph the paper sheet and attach it to the record. These records are marked with the lowest assurance level and their share is reported — paper is not an escape hatch but a monitored exception.

If you want, you can measure the number of people in the room with the camera and compare it with the number of verifications. Nobody is recognised, no image is saved anywhere, the output is a single number and it is attributed to no student.

The number is a lower bound: students who overlap or sit at the back are not counted, which is why it is shown as “at least N people seen”. How many it counts in a real classroom has not been measured; that is why the feature never runs by itself and changes no attendance record.

If the count fails, the screen tells you so and offers two routes: try again or count it yourself and enter it. The number you enter is not a measurement; it is shown on screen as a teacher statement, is not compared with the verification count and is stored nowhere.

The system watches patterns in the background but gives you no number. The reason: a “not in the room” answer given after seeing the score is no longer an independent observation, and the single ground truth the system relies on is contaminated. You only see “confirm this person” and a short reason.

You can mark by hand a student who has no phone, whose battery is dead or whose verification does not pass. A reason is mandatory. Your manual ratio is reported on the dashboard — that is not an accusation but a transparency instrument.

The teacher is the system's authorised actor and cannot be technically restricted. The only thing that happens is that actions are recorded. In return, the student holds a signed receipt: a record deleted silently is detected.

Ask the student for the receipt number. If they have a receipt, the record was accepted by the system and the loss is on our side. You can verify the receipt from the admin dashboard. If there is no receipt, mark the student manually.

If the student filed an appeal from the app, the appeal comes to you: from the “Student appeals” button on the My courses screen you see appeals for your own sections and accept or reject them with a written reason. The decision cannot be undone, and that is said before you confirm.

Your institution may not have defined the addresses for that university, or may not have enabled the connection. Enabling requires written institutional permission. The CSV route is usable in any case.

If Bluetooth is on, the QR code is not needed; one of the two channels is enough. If neither works, the student can be verified face to face on your device or marked manually.

Invitations are valid for 14 days. A new invitation is generated from the admin dashboard; the old one becomes invalid automatically.

It does not matter — you can use it either way.

If your institution is registered: apply with your institutional email address. If you appear on the faculty roster the institution uploaded, your application is approved immediately and you can start using it. If you are not on that roster, it goes to your institution's administrator. The administrator can also invite you directly.

If your institution is not registered: you can still apply. You use it on your own by uploading your own courses and student rosters with CSV or by entering them by hand; you do not have to wait for your institution to decide. If your institution registers later, your account can be moved there.

If you like, you can forward the institution application form and the school setup guide to your IT department — but that is not a precondition.

Automatic approval: the institution administrator can upload the faculty roster from the dashboard and turn automatic approval on and off. Approval depends on all three of these conditions at once: that you have verified your address, that the institution has enabled this option, and that your address appears on the roster the institution itself uploaded — your email domain is not consulted, because a domain shows neither the institution nor the title. Institution-less mode is still partial: the endpoints have been written and are bound by tests, but there is no app screen that calls them. Every limit is written down, one by one, on the features page.

You decide for each class which methods count as valid: when you open a session you tick the methods you want to use. If you tick face verification only, it becomes mandatory in that class; if you do not tick it, the system runs fully functionally with proximity verification.

Your institution can narrow this menu from the admin dashboard — in an institution that chooses never to enable face verification, the option is not offered to you at all.

The information on the application form goes to your institution's yoklama.ai server. A face template is never sent to the server — if one is used, it stays on the student's own phone.