Questions
A seder that did not happen. A boy who came late and left early. A rebbi who marked a cancelled seder anyway. These are the same answers the app gives your staff from inside it, so what you read here is what they will read there.
The thing a yeshiva does eight times a day, and the awkward cases that come with it.
Attendance opens on today's sedarim. Tap the one you are marking, then P, L or A for each boy. If you run a single class and there is only one thing to mark, today's screen skips the chooser and opens your roster; on any other date you always pick.
One day at a time, laid out either by shiur or by block: by shiur puts each class's sedarim together, by block puts each seder's classes together. A seder running right now is badged Now, and it is never opened for you — you pick it.
If the rest of the room was marked and he was not tapped, he reads as presumed absent, and that does count against his percentage — flagged as unconfirmed rather than as a mark you made. If hardly anybody in the room was marked, the whole seder reads as not recorded instead and is left out of everybody's percentage.
Mark him late and type the minutes beside it. A lateness with no number is still a lateness — the app takes it and reports it as late.
A lateness inside the school's grace window — a few minutes — shown in a softer colour on reports so single-digit lateness does not read as a serious infraction. It is worked out when the report is drawn rather than stored, so changing the grace minutes changes past reports too. Marking is unaffected.
It does not, by default. A seder with no end has no length, so it stays out of the minutes figure — though it still counts as one seder, and an absence still shows on his report and the calendar. Best fix is to give it a real end time on the schedule. Or set what it is worth in Settings, Attendance defaults.
Yes. Catch up lists the sedarim you were meant to mark in the past 48 hours and have not, grouped by day, so you can work through them without hunting for dates. Anything older is one tap away at the bottom of the page. A seder the app closed by itself is still there, badged auto-closed, and opens on a restore banner rather than a roster.
On the seder's card in Attendance there is a Mark whole yeshiva pill — one screen holding every shiur, which is how shacharis, mincha and a farbrengen are meant to be taken. A maggid shiur who teaches the subject in more than one class gets the same screen under Mark all my classes, holding just his.
Exactly as you would a class. The seder shows in your list with the group's name where a shiur's name would be, and tapping it opens the same marking screen. When one seder runs several groups there is a Mark all groups screen that takes them in one pass.
The attendance calendar is one screen with three modes: by day, by subject and by bochur. The same marks, laid out three ways, so you can read a week across a class or a month down one boy.
A seder that did not happen should not leave anybody absent. This is the part schools ask about most.
For one seder, cancel it and nobody is counted absent for it. The marking screen calls off the sitting it is showing; Cancellations, A subject takes one seder off the whole yeshiva or one shiur. Do not enter several one at a time: a stretch with nothing in its place is A few hours, and a programme that took the slot is Something else is running.
Open Cancellations, pick A whole day, then A late start. Give the new start time; it names every seder that would already have been over and cancels those. One still running at that time carries on, and says so. Over a range you can set a time per day. This is one date, not a permanent weekday change.
Open Cancellations, pick A whole day, then A few hours. Give the hours, or tick and nothing after for the rest of the day. Everything wholly inside them is cancelled, by name. One only partly inside keeps running and keeps its marks; a tick takes it off too. Nothing is recorded as running in its place.
It turns on one question: is anything running in that time. If nothing is, it is a late start or a few hours off under A whole day, and the app records a hole and nothing else. If a programme took the slot, use Something else is running, which will not save without a name for it and then shows what it displaces.
Open Cancellations and pick One shiur. Choose the shiur, the days, then either the whole day or only the sedarim you name. Those blocks are cancelled for that shiur alone, so every other shiur carries on and nobody in the shiur is counted absent. This is the one cancellation a rebbi can make himself, for the sedarim he manages.
Yes. Cancellations, A subject, the seder, then At a different time. Or A whole day, A seder at a different time, which is the same flow. Give the day and the new hours; leave Ends blank for no set finish. Nothing is cancelled, everyone is still owed a mark, and lateness moves with it. For every Thursday, set a weekday time on Schedule instead.
It depends who cancelled it. If a person cancelled the seder, the day counts for nobody, marks or no marks — the marks stay on file and start counting again the moment the day is un-cancelled. If the app closed it by itself after nobody marked it for two days, any real marks on it do still count.
A cancelled seder has a Restore beside it under the cancellations, and an override has an Undo all that puts back everything it moved, retimes included. A whole day and a late start come back seder by seder, because that is what they wrote. A leave is deleted from the same list; an exemption is switched back on from the boy's own page.
Two groups of doors. Cancel a seder covers a subject, one shiur, a whole day — which also holds a late start and a few hours off — and something else running in its place. Excuse a boy covers leaving early, arriving late, away, and off a subject for a window or with no end date. A rebbi gets one shiur; off a subject and a whole day are hanhala.
The page lists the last thirty days and everything still to come. An older one has not been undone: the day it covered is still cancelled everywhere it counts. It has simply fallen off this list.
Excused is a modifier on a mark, not a fourth box beside P, L and A. Mark him late or absent and tick excused; the marking screens can also do both in one tap on a boy with no mark yet. An E on its own is not a mark at all, and marking him present clears it.
Three different things. A cancelled seder counts for nobody, so it leaves everybody's percentage. A boy on a recorded leave is off the roster for it — not expected, so never absent. An excused absence is different: it is a real absence with a note on it, still counted, and shown separately as excused.
Record it under Cancellations. A leave has an end date even when nobody knows the real one — it becomes a review date, so he returns to the roster instead of disappearing from every count with nothing to bring him back.
Open Cancellations, pick Leaving early, and answer yes to is he coming back today — then give the time he is back. Only the sedarim while he is out are excused and he is expected either side of them. Arriving late asks the mirror question. Away, only part of the day, records the same thing.
Open Cancellations, pick Away, give the day, then choose sedarim rather than the whole day. Name the ones he misses and he is off the roster for those and expected for everything else that day, all as one arrangement with one thing to undo. If it is a stretch of hours rather than named sedarim, tick only part of the day and give the times instead.
For a rebbi who would rather hold a sheet, and for a zal with no signal.
Yes. Print a sheet for the seder, mark it by hand, then photograph it — the scanner reads the page when it sees the printed code and shows you every row to confirm before anything is written.
No, and that is on purpose: two columns hold about thirty-six names, so a seder with ninety boys would not be legible. Print per class instead, either one day or a whole week at once. The roster on a printed sheet is frozen at the moment you print it.
It reads a handwritten digit only when it is sure, and it abstains far more often than it answers — a misread 7 would become a plausible lateness nobody would ever catch. When it abstains you tap the number, with the cell shown large beside the buttons.
It leaves the row on skip, which writes no record at all rather than a guess. Every row is shown to you before anything is saved, and a minutes digit it did read is tagged as read from the sheet, so you can see which ones it answered and which you did.
No. The page reads the sheet inside your own browser and sends only the printed code and the row decisions, so the picture itself never leaves the phone. The camera captures by itself once it can read the printed code cleanly.
Marks for what was learned, and a monthly read on limud, avodah and middos.
Tests live under Marks. Enter the test once, then the scores for the class.
It is every test mark the class has, with two kinds left out: a test a boy was excused from, and a mark that a retest replaced. So a retest does not sit in the average beside the mark it was meant to fix.
A way to score a whole class on something without setting a test: pick the subject, the class, the category and the day, then tap a number for each boy. The title writes itself. A boy you leave blank is not scored at all rather than given a zero.
Because the category is what stops twenty daily taps from drowning one bechina. Scores are averaged inside their own category first and the categories are then weighted, so a subject with no categories set up has nothing to file a quick score under.
The rubric is how a boy is scored on the things a test cannot measure. It is kept separate from grades and never combined with them into one number.
A month or a zman, whichever your school chose, and each tile counts how many boys are scored in the period running now. With no zmanim set up it falls back to monthly by itself.
The dimensions are split by what you do: a maggid shiur gets the learning ones, a mashpia the avodah and middos ones, and hanhala see all of them. It only decides who fills the sheet in, and hides nothing from a report.
One boy's picture, and what happens after the marking turns something up.
Search his name in the search box at the top of the menu and pick him — that opens his report. From Reports you can also open his class, then his name on the by bochur list. Either way you land on the same three lenses: attendance, tests and a calendar.
Yes. A boy who joined part way through is counted from the day he joined, and a boy who left is counted up to the day he left — not for the weeks either side. Taking somebody off a roster is a date rather than a deletion, so it never rewrites a month that has already been reported on.
A daily phone notification, not an email, so it needs notifications switched on for your account on that device. It only reaches things with a due date: a knas with no date set is never chased by anything. It also stops after a fortnight of being overdue, and hanhala get one summary for the school rather than one per boy.
Almost always because it was given with no due date. Nothing chases an undated consequence: it is in nobody's overdue count and the nightly phone notification skips it, so it stays outstanding with nothing pointing at it. Give a due date unless it is being collected on the spot.
The details that decide whether it feels built for a yeshiva or adapted to one.
Yes, and it is a school-wide choice rather than a per-screen one. A boy with no Hebrew name on file still shows his English name, so no row is ever left nameless.
That was a defect and it is fixed — every time the app writes now reads as 12 hour with am/pm, in the app and in email alike. There is no setting for it, and nothing to switch on. The setting people look for here is Date display, which chooses the Hebrew or the English calendar rather than the clock.
When a seder you are the marker for goes unmarked, the app reminds you a few times over the next two days, each one less gentle than the last. Mark it and the reminders stop immediately. After two days it closes the seder by itself and stops asking — that day then shows as auto-closed rather than as your fault, and you can still mark it afterwards.
Messages holds three tabs: announcements, direct messages and tasks. Only hanhala can start an announcement, and it can either allow replies or ask only for an acknowledgement, with the seen and acknowledged counts shown beside it.
A job given to one member of staff, with a due date worked out in the school's own timezone so it never reads as overdue a day early. Your open tasks sit on your dashboard and under the tasks tab in Messages.
There is a report button in the menu with four kinds: something is broken, a number looks wrong, an idea, and a question. It carries your message, the page you were on and who you are — never a screenshot and no boy's details — and a person reads it.
Inside the app there is an assistant that answers from the full manual, including the parts only a hanhala sees, and it says when it does not know rather than guessing. Before that, ask a person.