Littera API
Papaya Tutor · –Tutoring sessions
Student hours
Whole series, not the date range.
Sessions per week
Attended, absent and no-tutor sessions, by ISO week.
Attendance rate per week
attended ÷ (attended + absent). No-tutor sessions don't count.
Actual minutes by group
Attendance distribution
How many students fall in each attendance-rate band.
When sessions happen
Sessions by weekday and hour, 07:00–20:00 US Central. The number is how many sessions start in that hour; darker = more; the red dot marks attendance below 70%.
Tutor demand by hour
For each hour: the most sessions running at once on a single day (that is how many tutors you need at that hour) versus how many different tutors currently cover it. Includes upcoming sessions.
Students with sessions in the period
| Student | Grade | Sched. | Attended | Absent | No tutor | Min plan | Min actual | Rate | Engag. | Mastery | Last |
|---|
Click a student to open their full profile.
Punctuality and connection · students
Attended sessions only. A student is late after 5 minutes of tolerance; joining 4 minutes in counts as on time. Reconnections come from the session events report.
Most late arrivals
Most reconnections
Leave earliest
Most punctual
Tutor performance in the period
| Tutor | Sessions | Taught | Missed | Reliab. | Students | Student att. | Min actual | Engag. | Last |
|---|
Reliability = sessions taught ÷ (taught + missed by the tutor). Click to open the tutor's profile.
Punctuality and connection · tutors
No tolerance for tutors: one second after the scheduled start already counts as late. Joining early is fine (0). Leaving is measured against the scheduled end. Reconnections come from the session events report.
Earliest joiners
Latest joiners
Most reconnections
Leave earliest
Tutor pool assigned by Littera
Availability measured over the timeslots configured in Littera (Mon–Fri, 07:00–19:00 Central, next 90 days).
| Tutor | Languages | Subjects | Avail. days | % timeslots | Avail. until |
|---|
Thresholds
Students on an absence streak
Consecutive absences in their latest sessions. No-tutor sessions don't break the streak.
Students with low attendance
Rate below the threshold, with a minimum of decided sessions.
Students arriving late
Students who joined more than 5 minutes after the session start at least once (a 5:00 PM session is late from 5:05:01 PM), grouped by school. Past attended sessions with a join time.
Repeated names in the same school
Two records with the same name in the same school. It is usually the same child loaded twice in Littera with two different district IDs; sometimes they really are two children. Check it with the district.
Sessions without a tutor
MISSED sessions grouped by assigned tutor and program. This is on the tutor or the assignment, not the student.
Executive summary
Scheduled sessions for one day or one week and how covered they are. To cover = no tutor assigned; accepted, pending and declined come from the tutor's answer in the confirmation center. Cancelled sessions and backup reservations are left out.
Scheduling progress by district
Click a district to see its schools. Coverage = accepted / total. Regions will come when the district-to-region mapping exists.
| District / School | To cover | Accepted | Pending | Declined | Total | 1:1 | Group | Coverage |
|---|
Tutor capacity & usage
Assigned = tutors in the Littera pool. Active = with at least one session in the period. Hours used = scheduled minutes of the sessions with a tutor. Capacity = free hours the tutors declared in their availability, summed over the weekdays of the period. Today Littera only has the regular type.
| Tutor type | Assigned | Active | Sessions | Hours used | Capacity | Utilization |
|---|
More data from Littera
Reports built on what the Snowflake share brings and the email reports never had: every tutor assignment, waiting room times, when sessions are created and cancelled, observers. They use the filters above.
Some of these reports need the Snowflake ingestion; with the email reports they come out empty.
Tutor reliability
How each tutor's assignments ended. No-show rate = no-shows / (accepted + no-shows). Replaced = another tutor took the session (subbed) or Littera removed them. Join = minutes after the start they joined (negative = early).
| Tutor | Assignments | Accepted | No-shows | Declined | Replaced | No-show rate | Avg join (min) | On time |
|---|
Tutor changes
Sessions where a tutor was replaced, removed, declined or did not show, how much notice there was, and whether the session still ended up with a tutor.
| Notice | Changes |
|---|
Waiting room
How long students waited for their tutor: from the moment the student was ready (never before the start) until the tutor joined. Waited = 2 minutes or more.
| Tutor | Students | Waited | Avg wait (min) | Max (min) |
|---|
Cancellations
Per week (Monday, Central). Late = less than 24 hours before the start. Hours before = when Littera recorded the cancellation, against the start.
| Week | Scheduled | Cancelled | Late | Rate |
|---|
How far ahead sessions are booked
Days between the session's creation in Littera and its start.
| Booked | Sessions | Share |
|---|
Roster coverage
Students in Littera's latest roster and how many have a session booked (not cancelled) in the period. Never scheduled = enrolled in Littera with no tutoring booked yet.
| School | District | In roster | Scheduled | Attended | Never scheduled | Rate |
|---|
Pool by subject
Enabled tutors offering each subject against the sessions of that subject in the next 14 days.
| Subject | Tutors | With availability | Upcoming sessions | Per tutor |
|---|
Session Observer
Of the sessions held, how many had an observer inside, and what each observer did.
| Observer | Sessions | Minutes | Districts |
|---|
Sessions
| Date | Status | Outcome | Min | Student | Program | Tutor | Subject | Ratio | Backup | Littera ID |
|---|
Click a session to see who joined, when, and for how many minutes.