You can have next Sunday planned in under an hour.
Scheduling is keyboard-first and responds as fast as you type. Every slot comes with capacity-ranked suggestions, and the bullpen knows who to ask when someone declines. Scout was built around the person who plans the week.
Sunday, ready by 1:00 p.m.
This is the order next Sunday gets built in Scout, start to finish.
- 0:00
Open Scout. The serving schedule for next Sunday is already drafted from your template.
- 0:08
Five slots are empty. Scout suggests ranked candidates for each one, with capacity, reliability, and fairness already weighed.
- 0:18
Send the assignments. Confirmations arrive in the member app. Replies surface in your inbox as they come in.
- 0:31
Two people decline. The bullpen suggests three eligible recruits for each opening, and you send the invites in two clicks.
- 0:44
Open Run of Show. Worship pulls in last week’s set with key and BPM. You add a baptism between the second song and the message.
- 0:53
Share the ROS link with the production team and print labels for kids check-in. Sunday is planned.
The whole sequence takes under an hour, every Tuesday.
Three things that make the hour possible.
Scheduling that ranks itself
Every candidate is ranked before you start.
Scout reads who’s confirmed to show up, who’s declared they can do this role, and how recently they’ve served. Each slot shows you ranked candidates the moment you open it, with capacity, reliability, and fairness already weighed.
How Scout handles servingBullpen recruitment
When a slot empties, Scout already has three names for it.
Scout knows who’s declared they’re open to serve in this role and never been asked. You invite three of them with one click, and their answers land in the member app as confirmations and declines rather than messages you have to read through.
See bullpen + invite flowRun of Show your team can share
One source of truth for the volunteer team and the production team.
Dual time columns (clock time and show time) calculate themselves, and a shareable link prints cleanly. The volunteer roster sidebar reads from the same data as your assignments page, so the two screens never disagree.
Read the Run of Show feature
What Scout says to you.
Scheduling notices come to the person doing the scheduling, at the moment of the ask instead of in a report afterward.
How the intelligence worksMarked a recent serve “difficult”, and they're scheduled again Sunday.
On the schedule itself, right where your cursor is, before the ask goes out.
Marked their last Worship serve “difficult.” Asked again 3 weeks later, and declined.
Two events from different weeks in one sentence, so a quiet no reads as a pattern instead of a scheduling inconvenience.
Pastors are the ones who fall in love with the dashboard. Ops coordinators are the ones who decide whether a church keeps the software, so Scout was built around their experience first.
Scout product principle
What Scout doesn’t do for scheduling yet.
- Scout doesn’t auto-text declined volunteers their backup options. It surfaces who to invite next; you press the button.
- Scout doesn’t resolve conflicts between two services where the same person is double-booked yet. It shows you the conflict; you choose.
Try Scout on a real Sunday and see how it holds up.
- Keyboard-first
- Instant feedback
- Bullpen suggestions
- Run of Show built-in