The weekly church office checklist, Monday through Sunday
A church office runs on a seven-day cycle built backward from Sunday morning. Monday is cleanup and follow-up from the weekend, midweek is planning and confirmation for the week ahead, and Thursday through Saturday is production for the next service.
A church office week runs on a seven-day cycle anchored on Sunday. Monday clears the weekend's follow-up and data entry, Tuesday and Wednesday plan and confirm the coming Sunday, Thursday through Saturday produce it, and Sunday runs it in real time. The table below lays out the full week, day by day, with who owns each task.
Most church office checklists published online are a bag of categories: answer phones, manage the calendar, coordinate events. No order, no sequence, nothing to tell you what today is actually for. That's not how a church week works. It has one fixed anchor, Sunday morning, and every other day either builds toward it or cleans up after it. This post is the sequence, one of the recurring rhythms mapped in our guide to the church operations playbook.
CoLabor Staffing places full-time Christian co-laborers with churches and Christian-owned businesses, and this checklist is close to a literal description of what a generalist co-laborer runs every week. You don't need to hire anyone to use it. You need one person who owns it.
What has to happen on Monday?
Monday is cleanup, not planning. Everything on it traces back to the weekend that just ended.
- Guest follow-up goes out first, before anything else. First-time guests from the prior Sunday should already be hearing from the church by the time the office opens Monday. See the full 72-hour guest follow-up window for the timeline behind this.
- Attendance and giving from the weekend get entered into the database. This is the raw data every other report in the building depends on. Delay it a day and every downstream number is stale.
- Voicemail and weekend email get triaged. Sort by what's time-sensitive first: a wedding or funeral inquiry outranks a routine bulletin question.
- Any incident from Sunday gets logged and routed. A minor first-aid note, a facility issue someone flagged on the way out, or a complaint that came in after service all need a home before they're forgotten by Wednesday.
- The week's calendar gets a first pass. Before Monday ends, the administrator should know what's actually due this week: which ministries need a room, which events need final numbers, and which volunteer slots are already thin.
Why Monday, not Friday
Some offices push weekend follow-up to Friday, once the week has calmed down. By Friday the guest has already decided whether the church noticed them. Follow-up is a Monday task because the response window is measured in hours, not days.
Most offices underestimate how much of Monday this actually takes. A church running 250 to 300 in attendance on a given Sunday can easily generate a dozen guest cards, several dozen attendance and giving records, and a full inbox of weekend emails. Treating Monday as a light day, a chance to catch up on email, is usually where the weekly cycle starts breaking down before it even gets to Tuesday.
What has to happen Tuesday and Wednesday?
Midweek is where the coming Sunday gets built. Everything here has a deadline that, if missed, becomes a Thursday scramble instead of a midweek task.
- Bulletin and newsletter content deadline falls here. Whatever channel carries Sunday's announcements needs its content locked by Wednesday at the latest; see the full communications calendar for how each channel's lead time stacks against this deadline.
- The coming Sunday's volunteer schedule gets confirmed and gaps get backfilled. This is the checkpoint where a missing greeter or an unstaffed nursery slot should surface, days before Sunday, not hours before. The full mechanics live in our post on volunteer scheduling that survives a cancellation.
- Room and facility requests for the week get finalized. Any ministry that needs a room, a key, or a setup change should have that locked by Wednesday.
The reason these three tasks belong together, and belong midweek specifically, is that each one has a deadline that ripples forward. Miss the bulletin deadline and Thursday's production window inherits a rush job. Miss the volunteer confirmation and Saturday's briefing inherits a scramble to find a body for an empty slot. Wednesday isn't a soft deadline. It's the day the rest of the week either has what it needs or doesn't.
What does the Thursday-to-Saturday production window cover?
This window turns everything confirmed midweek into what actually happens Sunday morning.
- Bulletin or program finalized and printed. Content was locked Wednesday; Thursday is layout, proofing, and getting it to the printer or the screens with a buffer day to spare.
- Reminder texts and emails sent for the weekend. One reminder, on a fixed schedule, not an improvised send whenever someone remembers. See the full rule for what to text and how often.
- Setup crew and first impressions team briefed. A short huddle covering any changes to the normal Sunday flow: a different room layout, a guest speaker, a baptism that needs extra towels and a change of clothes on hand.
- Final headcounts confirmed for any weekend events. Catering, childcare, and room setup all depend on a real number, not last week's guess.
- Signage and directional materials checked. Anything new, a different parking flow, a temporary check-in table, a special event sign, gets printed and staged before Saturday ends, not discovered missing Sunday morning.
Saturday is the last checkpoint before the week goes live. A short walkthrough of the building, confirming rooms are set, signage is up, and the tech booth has what it needs, catches the small misses that a spreadsheet alone won't. This is also where the weekly facility walkthrough naturally lands for churches running one.
What happens on Sunday itself?
Sunday is the one day the office runs in real time instead of on a schedule.
- Someone staffs the office function in real time. Check-in, guest card collection, and the start of the offering count all need a named person, not "whoever's around."
- The first impressions team runs its handoff. Parking, entry, welcome desk, and seating each play a role in whether a first-time guest is actually noticed; see the full breakdown of running a first impressions team.
- What gets captured Sunday feeds directly into Monday's follow-up loop. Guest cards, attendance counts, and any incident notes should already be organized by the time Monday's cycle starts, not sitting in a stack waiting to be found.
The office's job on Sunday is narrower than it sounds: not to run the service, but to make sure everything that happens gets captured cleanly enough that Monday doesn't start from scratch. A guest card sitting in someone's pocket until Tuesday is the single most common way this cycle breaks.
What does the full week look like at a glance?
| Day | Primary task | Owner | Where it lives |
|---|---|---|---|
| Monday | Guest follow-up, attendance and giving entry, weekend triage | Administrator / office manager | ChMS, inbox |
| Tuesday | Bulletin content deadline, volunteer confirmation begins | Administrator, ministry leads | ChMS, shared doc |
| Wednesday | Volunteer gaps backfilled, facility requests finalized | Administrator | ChMS, calendar |
| Thursday | Bulletin finalized, reminder sends drafted | Administrator | Print/design tool, text platform |
| Friday | Reminder texts and emails sent | Administrator | Text/email platform |
| Saturday | Team briefing, final headcounts, setup check | Administrator, first impressions lead | In person, calendar |
| Sunday | Check-in, guest cards, offering count start | Office staff, first impressions team | ChMS, check-in system |
Our own organizing structure for a standard single-service week. Multi-service and multi-campus churches compress or repeat parts of this cycle; the sequence itself doesn't change.
Who should run this checklist if there's no dedicated admin?
The temptation at a smaller staff is to split this across whoever has a free hour that day. That's exactly how a guest follow-up gets missed or a volunteer gap goes unnoticed until Sunday morning: everyone assumes someone else has it.
This is a well-defined, recurring, seven-day cycle, which makes it exactly the kind of work that transfers cleanly to one dedicated person, whether that's an administrator you hire directly or a co-laborer running the same cycle for a published, flat monthly cost. What it should not be is a rotation.
At a smaller staff, the most common failure mode isn't laziness. It's diffusion. Everyone technically knows the checklist exists, and everyone assumes it's covered because it usually is, until the one week it isn't. A named owner doesn't need more hours than a rotation does. It needs one person who can be asked, directly, "did guest follow-up go out this Monday," and who has a real answer.
The front-office layer underneath this
This checklist assumes someone is already covering the phones, the walk-ins, and the day-to-day front-office rhythm. If that piece is missing too, start with what a church secretary actually does all week.
This is the exact checklist a co-laborer runs every week, without you writing it down for them twice. See how it works.
Common questions
What does a church administrator do every day of the week?
Monday clears the weekend’s follow-up and data entry. Midweek plans and confirms the coming Sunday. Thursday through Saturday produces it. Sunday runs it.
What’s the first thing a church office should do on Monday?
Send follow-up to the guests who visited the day before, before anything else on the desk.
Who should be responsible for the weekly church office checklist?
One named person, whether that’s an administrator, an office manager, or a co-laborer, not a rotation among whoever has time.
What happens if the weekly checklist doesn’t get done?
The gaps show up on the following Sunday: a guest never followed up with, a volunteer slot nobody backfilled, a room double-booked because nobody finalized facility requests midweek.