Fill open cohort seats from the waitlist the moment they open
Every hour, WebRun opens Prenda, checks each pod's enrolled count against its capacity, updates the waitlist tracker in Google Sheets whenever a seat opens, and posts admin a Slack alert naming the cohort, the open seat, and the next family in line.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I get alerted when a microschool cohort seat opens up?
WebRun checks every cohort's enrolled count against capacity in Prenda each hour. When a seat opens, whether from a withdrawal or an unfilled spot, it reorders the waitlist tracker in Google Sheets by request date and posts a Slack alert naming the cohort and the next family in line, so admin can make the offer within hours instead of days.
- Open seats get filled from the waitlist in hours, not whenever someone remembers to check
- Admin always knows exactly who is next in line for every cohort
- Every pod's real time capacity lives in one waitlist sheet instead of scattered notes
Built for microschool admins · Prenda guides · learning pod founders · enrollment coordinators
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.prenda.comin a real browser with your saved login - no setup, no API keys. -
1
Prenda - check each cohort's open seats
WebRun opens Prenda to check each cohort's open seats. - Open Prenda and check each pod's enrolled count against its capacity
- Note any cohort that just filled or just opened a seat from a withdrawal
Done when Every cohort's current capacity and open seat count is confirmed.
-
2
Google Sheets - update the waitlist order
WebRun opens Google Sheets to update the waitlist order. - Update the waitlist tracker with each cohort's current fill status
- Reorder the waitlist for any cohort with a newly open seat by request date
Done when The waitlist sheet reflects every cohort's live capacity and order.
- 3
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it offer the seat to the next family automatically?
No. It only alerts admin in Slack with who is next in line. Reaching out to offer the seat is always a human decision and a human message.
How does it decide waitlist order?
By request date within each cohort, so the family who joined the waitlist first is always surfaced first when a seat opens.
What counts as an open seat?
Any cohort where Prenda's enrolled count drops below capacity, whether from a withdrawal, a transfer, or a seat that was never filled.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.