Open Coaching → Coach queue to prioritize work in your visible scope. The queue can surface a blocker awaiting a response, a submission awaiting review, an overdue next action, an overdue intervention, or incomplete onboarding. Use the kind, due state and cohort filters when the list is large. A separate Unanswered questions panel links to community threads; those questions follow community access rules and are not enrollment queue items.
From signal to evidence
Find the signal in Coach queue and follow its link. A submission signal belongs in Coaching → Deliverables reviews for an authorized reviewer; an unanswered question opens its community thread.
For individual follow-up, open Coaching → Member monitoring and select the member's enrollment. Check the program/path, due work, submission status, blockers, earlier sessions and interventions before deciding what to do.
At Mike Academy, Nina sees Maya's overdue follow-up in the October Builders intake. She opens Maya's Agentic AI Developer enrollment, checks the earlier intervention and the latest demo submission, then decides whether a new conversation or tracked action is needed. If the submission itself needs a verdict, she uses the review screen only if her assignment covers Maya's enrollment. Mike can coordinate a separate live for the cohort; that does not clear Maya's individual follow-up.
Information
An empty queue can mean there is no work, a filter excludes it, or your enrollment scope is empty. Clear the kind, urgency and cohort filters first. If the screen says you have no assigned scope, ask the school operator to check your assignment; refreshing the list cannot widen it. The unanswered-question panel also disappears when there are no accessible unanswered threads.
The Enrollments API exposes enrollment context reads. Coach queue and its community handoff are school-screen workflows, not a public work-queue endpoint. Read roles and assignments for the permission boundary.
