Progress tracking
Attention flags run on the same signals progress tracking rolls into each student's status badge.
Student Attention: Know Who Needs a Look, and Why
Student attention is how MitzvahManager turns the facts it already tracks about each student into a short, explainable list of who needs a look right now. Opinion-free signals — days since last practice, overdue milestones, days until the service — are measured against rules your organization owns, and every rule that fires becomes a flag that says exactly why. New organizations start with a sensible default rule set, so it works on day one, and administrators can tune the rules to match how their program actually runs.
The system has three layers. Signals are computed facts about a student — how many days since they last practiced, how many milestones are overdue, how many days until their service — with no judgment attached. Rules are conditions your organization sets over those signals, each with a severity and an audience. When a student meets a rule's conditions, it produces a flag: a single item that names the rule and shows the actual numbers behind it. Because a flag always carries its "why," the list is something staff can trust and act on rather than a black box.
You do not have to configure anything to get value. Every new organization starts with a default rule set that mirrors the checks most B'nai Mitzvah programs already do in their heads — no upcoming appointment, overdue assignments, low recent practice, an approaching date with incomplete milestones, overdue or at-risk milestones, and open blockers. Until an administrator changes them, those defaults are what drives the flags, so the students list is useful the first time you open it.
Programs differ, so the rules are yours to shape from the Health tab in Organization settings. Adjust a threshold — how many days without practice counts as low, how close a service date is before it matters — change a rule's severity between info, warning, and critical, decide whether a rule is visible to all staff or administrators only, and scope a rule to a program type or a specific program. Turn off rules you do not want, and add your own conditions over the same catalog of signals.
Flags surface where staff already work. On the students list, a student's highest-severity flag drives the status badge and lets you sort the roster so the students who need attention rise to the top. On a student record, the flags fold into Priority Actions with their explanations and a link to where you resolve each one. Tutors see the flags targeted to their caseload; administrators see the whole program, so a director running a large cohort can tell at a glance who is coasting and who needs a call.
No. Every organization starts with a default rule set covering the common checks, so students are flagged from the first time you open the list. Tuning the rules is optional.
Every flag names the rule that fired and shows the real signal values behind it — for example, "No practice in 12 days (threshold: 7)" — so the reason is always visible rather than a mystery score.
Yes. Each rule has an audience, so you can target a rule to all staff or to administrators only, and tutors see the flags relevant to their caseload.
Yes. A rule can be scoped to a program type or a specific program, so a check that only matters for one track does not flag everyone.
Attention flags run on the same signals progress tracking rolls into each student's status badge.
Flags surface on the students list and sort the roster so who needs attention rises to the top.
Milestones from a program are the source of the overdue- and at-risk-milestone signals rules can use.
Join synagogues and tutors who manage their programs with confidence.
Get Started