What it does
The status board is the oversight view for requirements. Its Matrix view lays out people against requirements. You see every status at a glance, with summary counts for complete, pending review, missing, overdue, rejected, expired, and expiring soon. Its Review queue view is where staff open pending submissions, check evidence, and approve or reject them.
Who it's for
Program directors, program administrators, coordinators, and institution administrators track compliance this way from the institution or administration portal. Organization administrators get an organization-wide board from the organization portal. Reviewers use the same board's review queue.
How it works
The matrix. The board scopes to an organization, institution, or program. It lays out assignments as a grid — people as rows and requirements as columns. Flip that with the People rows / Requirement rows toggle. Each cell shows the assignment's status. Selecting a cell opens submission details, if any exist. Filter by status, requirement type, or assignee role. You can also filter by due-date range, compliance-document requirements only, or a text search. Results are paginated for large cohorts.
Reviewing submissions. The Review queue button switches to a list of submissions awaiting a decision. Each row shows the person, requirement, program, submitted date, and due date. From each entry, select View to see the submission and its documents, Approve (with a confirmation step), or Reject. Rejection always requires a written reason. The submitter sees that reason when the requirement returns to their checklist for resubmission.
Submitted documents. The Documents page lists submitted requirement documents across your scope, filterable by program, with viewing and downloading of the attached files.
Before you start
You need review permission in the institution, administration, or organization portal to approve or reject.
Know the scope you want to check — organization, institution, or program — before you open the board.
Have your written rejection reason ready if you plan to reject a submission — it must be 10 to 500 characters.
Do this
Open the Status board page (
/requirements/status-board) → you should see the matrix with its summary counts.Select the Review queue button → the display switches to a list of submissions waiting for a decision.
Find the submission you need to act on in the list view and select View → confirm you can see the submitted documents and details.
To approve, select Approve on that row, then confirm Approve requirement? in the dialog by selecting Approve again → you should see the entry leave the queue.
To reject, select Reject on that row, enter a written reason of 10 to 500 characters in the dialog, then confirm → the submission returns to the assignee's checklist as rejected, and the entry leaves the queue.
You're done when
✓ Approved submissions no longer appear in the Review queue display.
✓ Rejected submissions show back on the assignee's personal checklist with your reason attached.
✓ The Matrix display's summary counts reflect your decisions.
Boundaries and limits
A rejection reason is required and must be between 10 and 500 characters; it is shown to the submitter.
Approving or rejecting is only possible for submissions in pending review; decisions are recorded with the reviewer and timestamp.
"Expiring soon" in the summary means an approved requirement with an expiration date within the next 30 days.
Download access to submitted files is permission-gated to the submitter and authorized reviewing staff, via short-lived secure links.
The board is scoped — organization, institution, or program — and only shows assignments you have access to.
The matrix paginates by assignee; it's a monitoring and review surface, not an export tool.
Loading, a failed load, and an empty board are three different states. While the board is checking assignments it shows "Loading requirements…" and the summary tiles show a dash instead of a count. A failed load shows "Couldn't load requirements" with a Try again button. "No requirements assigned yet" appears only after the board loads successfully and finds zero assignments in the scope you're viewing.
Common questions
Q: Can I see just the submissions that need review? A: Yes. Switch to the review queue tab — it shows only pending-review assignments that have a submission attached.
Q: What does the person see when I reject their submission? A: The requirement returns to their checklist marked rejected, along with your written reason, and they can resubmit.
Q: Can I track one program at a time? A: Yes. The board can be scoped to a single program, and organization administrators can view the whole organization from the organization portal.
Q: Why does a cell say there are no submission details? A: The assignment exists but the person has not submitted anything yet — its status is still missing or in progress.
Q: The summary tiles show dashes, or the board says it couldn't load. Are there no requirements? A: Dashes mean the summary hasn't loaded yet. "Couldn't load requirements" means the request failed — select Try again. "No requirements assigned yet" appears only when the board loaded successfully and this scope truly has no assignments.
Related articles