Skip to content
Pondara Pondara docs

Manage overdue work

Two queues drift if you don’t watch them: assignments past the due date and evidence pending verdict beyond the SLA. Both are visible from your home; both have one-click paths to clear. This guide walks through the rhythm.

Before you begin

  • You are signed in as a trainer.
  • You have at least one cohort with active assignments and recent engagements. New trainers often have empty queues — that is the steady state.

The two queues

Assignments past due

A scenario you assigned with a due date that the learner has not started by the date. The right rail on your home shows the count; click it to open the assignments view filtered to overdue.

Evidence pending verdict

An AI signal in the Bandeja that has been waiting on your verdict for longer than 7 days. Same right-rail count; click it to filter the Bandeja.

From your home

Both counts surface on the home so the queues never go invisible. Clicking either filters the matching surface — the assignments view or the Bandeja — to just the overdue items. Clear from the top.

Bulk actions on overdue assignments

Select multiple overdue rows and:

  • Update due date. Push the deadline forward. The learner sees the new date on their home and the reminder rhythm restarts.
  • Reassign. Move the assignment to a different learner in the cohort.
  • Send reminder. Fire a fresh reminder to the assigned learner without changing the date.
  • Cancel. Drop the assignment. The learner sees it disappear; no engagement record is left behind.

The right action depends on why the assignment slipped. A learner on leave: update the due date. A learner who left the cohort: reassign or cancel. A learner who silently abandoned: send a reminder before escalating.

Overdue evidence is on you

The Bandeja queue is different — only you can clear it. There is no “reassign” path for an AI signal. Open the row and render the verdict. See render a verdict.

If the dialogue is one you cannot judge confidently — the field is adjacent to yours but not your specialty, say — you can ask the org admin to reassign the cohort or the specific learner. That is rare; in most cases, render the verdict you can defend and let the disagreement loop carry the rest.

Escalation

Items in either queue past 7 days are visible on the org admin’s overview. The admin sees counts per trainer and per cohort. They do not edit your verdicts — that would break the single-writer guarantee — but they may contact you, reassign learners, or escalate to Pondara if the volume suggests a tooling issue.

When something goes wrong

  • The overdue count on your home doesn’t match the filtered view. Refresh; the count and the filter pull from the same source but cache for a moment.
  • You cancelled an assignment by mistake. Re-assign the same scenario to the same learner. The new assignment is a fresh row; there is no undo.
  • A reminder fires repeatedly to a learner on leave. Cancel the assignment and re-create when they return. There is no “pause” today.