DocsUser guideReview & decide

Review & decide

Decisions are two steps on purpose: stage them all, read the list once, then send.

  1. Open Submissions. The tabs across the top are the whole pipeline — All, Accepted, Accept Queue, Pending, Decline Queue, Declined, Withdrawn, Drafts.

    The Devcon Berlin submissions inbox with status tabs and one pending proposal
    Search, plus track and status filters, sit above the table.
  2. Click a row to read the whole thing: the abstract, every answer, the speakers, uploaded files and any evaluator scores.

    The submission drawer for the Devcon Berlin proposal, showing the abstract and speaker
  3. Set the status to Accept Queue or Decline Queue. Nothing is emailed yet — the speaker sees no change at all.

    The Accept Queue tab with one staged proposal and a banner counting it
    Tick several rows to stage them in one go.
  4. A banner counts what is staged. Read the queue one last time — this is the only moment it costs nothing to change your mind.

    “Review the queue” filters the table down to exactly what is about to go out.

  5. Press “Send acceptances” (or “Send declines”) and confirm.

    The confirmation dialog before sending the acceptances
    The dialog counts what is going out. Accepted speakers also get their onboarding tasks created.
  6. At a real event this table is hundreds of rows deep — the same tabs, the same two-step decision.

    A submissions table for a large event with many proposals across every status
    A different, much larger event — so you can see how the pipeline reads at scale.
Sending is the point of no return for the speaker — the email has left. The status can still be changed afterwards, but the message cannot be unsent.
Running a scored review with a panel? That lives under Evaluation: bundle evaluators, submissions and rounds into a plan, and each evaluator gets their own “My evaluations” link.