KAO workspace
Ratings, touchpoints, owners, and meeting context stay together in one private chapter workspace.
Approved access
Use the credentials approved by your Head Rush Officer.
New officer request
Your Head Rush Officer must approve the request before you can enter the workspace.
Choose a rushee. Add a score, a note, or the next touchpoint.
In focus
Assignment, rating freshness, and touchpoint context appear here.
Last 72 hours
Queue
0Stale Alerts
0Pending Approvals
0Unassigned
0Weighted totals, ownership, and live packet readiness.
Select a rushee to review packet readiness, ratings, and ownership.
Photo, assignment ownership, and meeting prep status.
Select a rushee to edit identity, contact, and packet details.
Keep linked rushees grouped across assignments and packet prep.
No package deal linked for this rushee yet.
Review the queue, pin a candidate, or open their full packet.
Your shared shortlist.
Select a member to inspect same-state opportunities and assignment ownership.
Capacity and pressure across the rush team.
Select a member to view rushees from the same state.
Timeline, goals, and officer chat in one coordinated command surface.
One shared calendar for rush events and scheduled touchpoints.
Use one shared drawer for meals, events, and one-on-one follow-up.
Subscribe once to the chapter rush calendar for events and touchpoints.
Loading rush calendar link...
Assign measurable goals and track progress automatically each week.
Auto metrics update from real actions: ratings, touchpoints, rushee adds, chat, and rush events.
Live officer communication with mentions, tags, and engagement stats.
Discord-style rush coordination. Use @username for mentions and Shift+Enter for new lines.
Promote an approved Rush Officer to Head Rush Officer and review the current head team.
Head Rush Officers can reset approved rush team passwords when someone gets locked out.
Head Rush Officers can remove Rush Officers here if they need to clean up the active rush team.
Archive the current season and reset for the next rush cycle. Only one archive is retained.
A single SQLite archive is kept and replaced on each new season reset.
Rushees, ratings, touchpoints, and rush-season participation counters reset to zero.
Rush Officers and Rusher accounts are removed so the next season starts with a clean team roster. Head Rush Officer accounts remain.
Download backups, confirm leadership alignment, and verify that meeting decisions are complete before archiving the season.
Use Command, Team, and Admin to rebuild the next season with a clean roster, clean assignments, and updated rush team access.
Collect rushee submissions in Google Forms, download the responses CSV, and import it here.
Recommended questions: First Name, Last Name, Class Year (F/S/J), Hometown, Phone Number, Instagram Handle.
Create the form with the six supported fields.
Keep one row per rushee in the connected sheet.
Use Google Sheets to export a CSV, then upload it above.
Duplicates by Instagram handle are skipped automatically.
Recent import activity is mirrored here so you can trust what reached the roster.
Assign rushees directly and build shared assignment teams.
Use backups before major roster changes or season reset actions.
Leadership, assignments, and storage health are surfaced here so you do not need to leave the console.
Use Admin for exports, storage review, and season transitions so the rest of the product stays execution-focused.
Use the summary cards above before drilling into leadership, roster tools, or storage actions.
Role visibility, imports, backups, and system confidence in one place.
Recent imports, backups, and season control events.
