Back to tutorials
Scheduling
Readiness And Flex
Review who is ready, who needs follow-up, and who can flex into another mapped role.
Who uses it
Event leads and reviewers
Where it lives
Event Workbench > Readiness
Goal
Staff can act on readiness gaps without turning the event into a spreadsheet exercise.
Before You Start
- GearCheck readiness mode.
- Mapped roles/specs.
- Recent member verifications.
Steps
1
Refresh readiness
Readiness compares current signups to terminal GearCheck verification sessions for the mapped build.
2
Act on gaps
Open the verification thread, send a reminder, bench an unready signup, move a flex-ready member, or approve a manual exception.
3
Keep labels compact
Launch readiness uses compact labels such as Ready, Needs Improvement, Missing Check, Role Not Mapped, and Staff Exception.
Launch Checklist
- Mapped roles show readiness.
- Unmapped signup-only roles stay valid but do not imply scoring.
- Manual exceptions are audited.
Common Pitfalls
- Assuming a member is missing because they failed; they may have no matching build check.
- Using readiness on signup-only events.