Each team serves a block of Sundays (two, in the pictures). The home page lists the upcoming blocks; yours is marked your team. Admins can do everything a leader can, for any team, when a leader is away: edit, approve and publish a block, and approve or assign subs. A block starting within two weeks that still isn't approved shows on the admins' Needs you list too.

Needs you at the top lists what's waiting on you, most urgent first: sub offers to approve (with Approve and Decline right there), your team's blocks starting within 6 weeks that aren't approved, sub requests on your Sundays in the next 3 days that nobody has taken, and serious alerts. The red … needs you in the top bar shows how many.
Short of volunteers (admins) shows, when the upcoming schedules have a room with fewer adults than the rules need, which rooms are short on how many Sundays and by how many adults, and roughly how many more eligible adults each team would need to fill every room. Teens don't count, and a room with a kids-per-adult ratio needs enough for the kids expected. It's counts only, from the schedules already made; People to ask on the Teams page is where to start.
Open your block to see the proposed schedule. The scheduler fills every room following the rules (two adults per room, at least one woman, couples together, training current, fair turns). The line under the title says whether it found any rule problems: problems with your church's rules, checked against your settings and Planning Center's data.

Symbols next to names: ♀/♂ gender, ★ that Sunday's teacher, ☆ can teach, and a colored dot for someone from another team.
Changing the schedule
Tap a person to select them. Then tap someone else to swap them, tap Move here on another room, Remove them from that Sunday, or Make teacher. Use Add someone to bring in a team member who isn't serving that day. Every change is re-checked right away, and Undo takes it back. Regenerate starts over with a fresh proposal, a different one each time that still keeps every rule (Undo brings back the one before). Proposals also try not to put people in the same room, or as backup, as on their team's last turn.

The map
Map shows the building for one Sunday and service. Rooms in use are colored by age group (the legend is under the plan), and each person is a circle with their initials; a dashed circle is a sub. Tap a room to list who's there, with full names. Drag a person to another room (or tap them, then the room) to move them. Choose your main service's first half (in the demo, Second Service, first half) to see the groups that meet together.
Rooms shows the same Sunday and service as a grid, one card per age group with its rooms and who's there, and the backups. It needs no floor plan and no zooming on a phone. Until a church draws its floor plan, Map shows this grid too. To move someone, use the List. On a phone, pinch (or + / −) to zoom and drag the background to move around; Fit goes back to the children's rooms.

Print (next to the service picker) opens that Sunday's maps, one page per service, to print and post at check-in, with full names in each room. Until the block is approved, each page says DRAFT.
Sub requests on your block
Your block lists its Sub requests: open ones and who was asked, offers waiting for you, and which are covered and by whom. When someone offers to sub you get an email with Approve and Decline links. They open the app (sign in if you need to) on that one offer, and you tap once more to confirm. Approve puts them in the slot (the rules are checked again), Decline opens the request again. Offers still waiting after a day (two hours close to Sunday) are emailed to you and the admins again. Admins can approve too, and for an emergency any team's leader can. You can also Ask every team now, Cancel, or Assign… a sub yourself (no approval needed). A sub doesn't undo your approval. Settings → Admins, features can turn approval off. Where a sub is a trade, each request says which of the sub's Sundays the person they cover takes in return, or that they owe the sub a Sunday. When you Assign… a sub, the earliest of their Sundays that works is used.
If the block was already published, a sub request says what to change in Planning Center.

Someone called out by text or phone
When someone tells you they can't make it, by text, a call or in person, record it on your approved block: Someone called out? → the Sunday, who, and when they told you (a week or more ahead, within 48 hours, or the day itself), with a reason and an optional note for leaders only (leave out health details). It asks for a sub for them, the same way the app does when they ask, and it's an emergency in the last 24 hours (every team asked, leaders and admins emailed). They get an email saying it's noted and that they stay on the schedule until a sub is found. If you already found someone, use Assign… on the new request under Sub requests.

This morning
On a Sunday, This morning: every room at the top of Schedules opens one page for the morning: every room's scheduled people, grouped by service, and the rooms short of adults at the top. If your admins picked the Check-Ins locations (Rooms page), it also shows how many kids and volunteers checked in to each room and the kids per adult, refreshed every minute. Leaders and admins only.

Sign-in sheets on that page prints a sheet per room for the coming Sunday, for paper sign-in, a backup when Check-Ins is down, or to record attendance afterwards. Each lists the children checked in on 3 of the last 8 Sundays, by full name and grade, with a box to tick, a line for whoever picks them up to sign, and blank rows for visitors. Its heading says the room's grades and its room number (from the floor plan), and a box reminds volunteers of the room's rules from Settings: how many adults, kids per adult, a woman in the room, and that teen helpers don't count as adults. A child goes in the room for their grade in Planning Center; with no grade, the room for their age; with neither, the room they were last checked in to. Admins see every room; a leader, the rooms they're scheduled in that Sunday. Nothing on it is saved.

Who didn't come
Once a Sunday has passed, your approved block has Who didn't come? with everyone who was scheduled that day. Tick anyone who didn't come (untick to undo), then say whether they let you know:
- No word: a no-show.
- Told us too late: they called out by text, a call or in person, with no time left to find a sub.
If your volunteers check in with Planning Center Check-Ins, an admin can turn on Our volunteers check in under Settings → Reminder emails. Each name then says whether Planning Center saw them check in, and Tick the … who didn't check in ticks the rest at once. You still look before you tick: someone may have forgotten to check in.
The two count separately in the stats. By default, two no-shows or three late call-outs in the alert period raise an alert (Settings → Alerts). Call-outs made in the app (a sub request or an emergency) are counted already.
If nobody was missing, press Everyone came under that Sunday. The morning after each Sunday (at the reminder hour), the team's leaders get a short email, "Who didn't come?", linking here, unless someone has already ticked a name or pressed Everyone came. A team with no leaders sends it to the admins. Admins can turn it off under Settings → Reminders.

Letting volunteers sign up
By default the leaders make the schedule. An admin can let volunteers sign themselves up instead (Settings → Admins, features and time zone), in one of two ways. Every sign-up is checked against the church's rules, the same as a sub, so nobody can pick a place that breaks one.

- Empty places: on a schedule that still has gaps, press Open the empty places for sign-up. Anyone on any team who could fill one gets an email, and the places show under Sign up on their My schedule page. You approve or decline each sign-up on the block page (or from Needs you); approved people are added to the schedule without sending it back for approval.
- Whole block: before anyone edits a block's schedule, press Open this block for sign-up. Your team picks their own Sundays and rooms; the schedule shows their picks as they come in (couples sign up together). While it's open you can't edit or approve it. Close sign-up and fill in the rest schedules everyone else around the picks, keeping every pick the rules allow. Then review and approve it as usual.
Volunteers can withdraw a sign-up while it's still waiting.
Approving and publishing
When there are no rule problems, tap Approve schedule (if there are fairness notes, tick that you've reviewed them first). Only the leaders of the team serving that block can approve. Any later change sends it back for approval. Approving it again asks Why did it change? in a line ("Ann is away on the 9th, so Bo takes her room"), and everyone the change affects is told, with what changed.
Approving is your confirmation of the schedule. Arkrooms builds it and checks it against your settings and what Planning Center says, but it doesn't certify that rooms are staffed safely or that your requirements are met: a training date or background check entered late, or someone who doesn't turn up, is beyond what it can see. The Sunday view's counts and alerts are the same: a help, not a guarantee.

Publish to Planning Center then adds everyone to the Planning Center plans as Confirmed, with their room as the position, so they see it in Planning Center and Church Center; Arkrooms has already emailed them. (Choose Unconfirmed under Settings → Publishing if your leaders send Planning Center's scheduling email themselves: Planning Center doesn't send it for people another app adds.) Publishing never removes anyone; someone covered by a sub or trade is marked Declined there, "Covered by" the person who took their place. (It's turned on once the room positions exist in Planning Center.)