Readiness dashboard

Monitor outstanding speaker tasks, stats, and go-live risk from the readiness dashboard.

What readiness shows

Admin readiness (often the admin home or /admin readiness view) aggregates whether the program is ready to run: outstanding tasks, counts, and generated-at timestamps. It is the single pane for program managers during the final weeks before show day.

Readiness is derived from portal tasks and related program state. It is not a separate spreadsheet. If the numbers look wrong, fix tasks and completions rather than hard-coding status fields.

How to use it daily

Open readiness at the start of the program stand-up. Sort or filter outstanding items. Assign follow-up owners outside the tool if needed, but drive task completion back through the portal so the dashboard clears honestly.

  1. Open the readiness dashboard for the event.
  2. Review stats: completed versus outstanding tasks and related counts.
  3. Drill into outstanding items and contact speakers or staff.
  4. Confirm portal completions clear the items after speakers act.
  5. Optionally pull JSON via CLI for reporting agents.
  6. Re-check after large decision batches or schedule moves.

CLI reporting

Keys with reports:read and events:read can fetch readiness without an admin browser session. Optional --overdue-only narrows the view when supported. Agents should treat the JSON schema as stable for dashboards and stand-up bots.

speakerops reports readiness --event <eventId> --json
speakerops reports readiness --event <eventId> --overdue-only --json

Interpretation tips

A green-looking count can hide critical path tasks (AV, legal, keynote headshots). Tag critical templates so humans still read the outstanding list. Readiness is not a substitute for schedule conflict review.

  • Watch critical templates separately from bulk bio tasks
  • Compare outstanding counts day over day
  • Confirm generatedAt is fresh when debugging caches
  • Pair readiness review with schedule conflict review weekly

When readiness stays red

If outstanding never decreases, speakers may not be receiving portal access (allowlist, email) or tasks may be mis-templated. Verify a single speaker end-to-end: allowlist → magic link → portal → complete one task → readiness tick.