We built this to pull late and missing assignments straight from the LMS in real time. Instructors and students see exactly what's overdue before things get out of hand.
At the institution, instructors were flying blind. The LMS gradebook shows grades, but it doesn't flag what's missing. To figure out which students had late or unsubmitted work, instructors had to open every assignment, cross-reference due dates, and mentally piece together who was falling behind. With 30+ students and dozens of assignments per course, that's an enormous cognitive load every single week.
Students had it worse. Most didn't realize they'd missed something until the grade showed up as a zero, sometimes weeks after the due date. The LMS calendar helps if you check it, but most students don't. There was no proactive nudge, no central dashboard, no "here's everything you owe right now" view.
The result was predictable: late submissions piled up, instructors intervened too late, and students who could have self-corrected never got the chance. The data was all there inside the LMS. Nobody could see it in a way that mattered.
Instructors couldn't easily see who was falling behind without manually clicking through every assignment in the gradebook.
Students didn't realize assignments were overdue until grades dropped. By then, the damage was done and motivation was gone.
Cross-referencing due dates, submission statuses, and student rosters ate hours every week. Time instructors didn't have.
There was no mechanism to catch at-risk patterns early. Interventions happened reactively, after students were already in trouble.
Built a secure LTI 1.3 launch flow using Firebase JWT for token validation. Instructors and students click a single link inside the LMS and land directly in the dashboard. No extra login, no account to create.
Connected to the LMS REST APIs via Guzzle HTTP to pull assignment metadata, due dates, submission statuses, and grade data. The sync runs on every dashboard load and caches intelligently, so instructors always see current data without hammering the API.
Designed two distinct interfaces: an instructor view that shows all students with late or missing work across every assignment, and a student self-service view that shows only their own outstanding items. Both use color-coded urgency indicators to prioritize what needs attention first.
Built a classification engine that categorizes every overdue assignment by severity: recently missed (yellow), significantly overdue (orange), and critically late (red). This visual hierarchy lets instructors triage their outreach and helps students understand which items to tackle first.
Let's talk about how a real-time assignment tracker could work for your institution.
Start a ConversationOne click from inside the LMS. No separate credentials, no new accounts. The dashboard launches with full context. Role, course, and enrollment data are already loaded.
Syncs with the LMS gradebook on every load. Late and missing assignments surface instantly. No manual cross-referencing, no stale data.
A roster-wide view of every student's outstanding work. Sort by student, assignment, or urgency level. See who needs outreach at a glance.
Students see their own overdue items the moment they open the dashboard. No guessing, no digging through the gradebook. Just a clear list of what's due and what's late.
Yellow for recently missed, orange for significantly overdue, red for critically late. Instructors and students both know exactly where to focus first.
Pulls assignment data, due dates, and submission statuses directly from the LMS API. No manual data entry, no imports, no copy-paste from spreadsheets.
The full roster view showing every student with outstanding assignments. Color-coded urgency bars make it obvious who needs intervention, with sorting options by student name, assignment, or days overdue.
A clean personal view listing every late or missing assignment with due dates, days overdue, and urgency level. Students can act on it before instructors need to step in.
The three-tier urgency classification in action. Yellow, orange, and red indicators help instructors and students figure out what to tackle first.
I used to spend the first 20 minutes of every week clicking through the gradebook trying to figure out who hadn't turned something in. Now I open the dashboard and it's all right there, color-coded, sorted, ready. I'm reaching out to struggling students days earlier than I used to.
The biggest surprise was how much impact a simple, clear view of overdue work had on student behavior. We didn't add gamification, rewards, or notifications. Just a dashboard that showed students what they owed. Many started self-correcting within 48 hours of first seeing it. Sometimes the problem isn't motivation; it's awareness.
Setting up LTI 1.3 with JWKS endpoints, platform registration, and token validation is a lot harder than a basic OAuth flow. But it's worth it. Instructors and students stay inside the LMS, don't create new accounts, and don't wonder "where do I find that tool again?" That's the difference between a tool people actually use and one they forget exists.
Early prototypes used one shared interface. Instructors wanted roster-wide views with sortable columns and bulk actions. Students wanted a personal checklist. Serving both from the same screen made neither group happy. Splitting into role-specific dashboards, driven by the LTI launch context, was the turning point for adoption.
Every project starts with a conversation. Tell us about your assignment tracking challenges and let's figure out what a real-time dashboard could look like for you.
No pitch. No pressure. Just a conversation about what might work.