Submissions Review

Overview

Submissions Review is the work queue for activity submissions that need a staff decision. Reviewers use it to inspect answers, leave remarks, approve items, reject items, and coordinate programming or content follow-up.

Dashboard route

• /ems/manage/submissions-review?id=:eventId

Inputs and controls

Input or control	What it changes	Before using
Refresh	Reloads activity forms and submissions.	Use before acting if multiple reviewers may be working the queue.
Search	Filters by submitter, username, form, answer text, status, or review remarks.	Clear search before reporting queue size.
Pending review group	Shows submissions with submitted status, grouped by activity form.	Work these first because they still need a decision.
Rejected submissions group	Shows submissions with rejected status, grouped by activity form.	Use when an applicant asks for reconsideration or staff needs to approve a rejected entry later.
Form group header	Shows the activity form title, description, and matching submission count.	Confirm the form before deciding because different forms may have different review criteria.
Row status badge	Shows submitted or rejected.	Rejected entries can be opened and approved later if staff changes the decision.
Details	Opens read-only submission details.	Use when you need to inspect answers without entering a decision.
Notify	Opens the attendee notification composer for that submission.	Use for follow-up questions or decision context outside the approve/reject action.
Actions	Opens the review modal.	Use only after reading the answers and confirming the form.

Detail and review modals

Modal field or action	What it does	Before using
Submission title	Shows the submitter or submission display name.	Confirm this is the intended entry before deciding.
Submitted and reviewed timestamps	Shows when the entry arrived and, if applicable, when it was previously reviewed.	Use for late submissions or appeals about timing.
Answers panel	Renders the activity form’s question labels and submitted answers.	Read every required answer and any file/link fields.
Existing review remarks	Shows prior remarks on detail view when present.	Preserve useful context if reopening a rejected item.
Review remarks	Stores decision remarks. Optional for approvals, required for rejections.	For rejections, include enough detail for future staff to understand why.
Approve	Changes the submission to approved.	Confirm scheduling, production readiness, capacity, and public implications.
Reject	Changes the submission to rejected.	Remarks are required. Use this when the submission should not proceed or needs substantial rework.
Close	Leaves the modal without changing status.	Use when the decision is not ready.

Page states

State	Meaning	What to do
No pending submissions right now	There are no submitted entries matching the current search.	Clear search before treating the queue as empty.
No rejected submissions	There are no rejected entries matching the current search.	Use this as a quick history check, not a production-readiness check.
No submissions match the current search	The current search filtered everything out inside a form group.	Clear or narrow the search differently.

Flowchart context

Active Event Workflow maps “Check Activities” and “Resolve activity issues” to this page. Accepted records can be reviewed later in Approved Submissions.

Common mistakes

Do not approve submissions that still need scheduling, rooming, or content review unless the team has a separate process for those follow-ups.

If a submission was approved by mistake, review it in Approved Submissions, notify the submitter if needed, and coordinate correction through the responsible programming or content lead.