Assignment pending
- Time limit
- The published due date.
- Entry / exit triggers
- Enters when the task is published; exits when the assignment is received.
- Data validation
- The student is enrolled in the subject.
- Dynamic permissions
- The subject's teacher.
Student follow-up stops being a quarterly report and becomes a live status.
Let's model your operationA student who falls behind is spotted late because the data is scattered: attendance in one place, assignments in another, and mentoring notes in the advisor's head. Falling behind isn't a data point you look up: it's a status that should open on its own and alert the right person.
The things that exist in your business, each one in a single place.
Enrollment, history and past support.
Skills, criteria and thresholds.
Task, due date and grading status.
Attendance and participation.
Agreements, family and follow-up.
Each stage stops being a label and starts carrying its own rules.
The same work, split between people, agents and machines depending on the moment.
The student enters «Falling behind» without waiting for the report card.
The stage triggers Glup as soon as the threshold is crossed.
Aimee cross-checks attendance, assignments and the subjects where there's already been extra support.
If it's a one-off, the student gets a nudge. If it's a pattern, the advisor and the family are called in.
The plan is saved on the Student record and the status is re-evaluated automatically.
Falling behind shows up at grading time, when fixing it already costs three times as much.
Falling behind is a status that opens on its own and escalates to the advisor once it stops being a one-off.
It's here to decide who handles what, and when, so people keep the part only they can do: judgment, relationships and exceptions.
Let's model your operationDon't see yours? It works the same way. Write to us and we'll look at your specific case. Let's talk about your case