By Wednesday afternoon, the bulletin still isn't written, three people have texted about whether the fellowship hall is free on Saturday, and somewhere in a shoebox or a spreadsheet is a contribution that needs to be recorded before year-end statements go out. None of this is an emergency. All of it is due by Sunday. This is what church administration actually is: not one big job, but a stack of small, recurring ones that all come due on the same forty-eight hours, week after week, whether or not anyone planned for them to.
Most churches never write this rhythm down. The person who runs the office — paid staff, volunteer, or the pastor doing it between everything else — carries it in their head, which works fine until they're sick, on vacation, or replaced. This page is the order of operations: what the job actually contains, how the week is supposed to move, and where the recurring failure points are. Where a specific piece deserves more depth than a paragraph here can give it, there's a link to a guide that goes further.
Picture a church of about 120 people with eight volunteers who help run the office in some capacity — a Sunday school teacher who also prints name tags, a retired accountant who reconciles the giving once a month, a deacon who fields the facility calls. That's not an unusually small operation; it's close to the median for congregations this size. Each of those eight covers a sliver of the job about once every seven weeks, which means none of them does it often enough to remember the details without a note somewhere. The rhythm has to be written down for exactly that reason — not because any one person is careless, but because no single person touches every part of it often enough to hold it all in memory.
What the job actually is
Ask five small-church staffers what “church admin” means and you'll get five different answers, because the job is really a bundle of unrelated skills that happen to land on one person: part writer, part scheduler, part records clerk, part first point of contact for anyone who calls or walks in. It is worth writing down what the role covers, because “whatever needs doing” is not a job description — it's a way for things to fall through the cracks the moment the person doing it changes. A written job description for the role turns a vague sense of who does what into something you can hand to a new hire, a volunteer, or your own future self on a bad week.
The honest version of the job description for most congregations in the 60-to-250 range is closer to ten hours a week than forty. That's not a shortfall — it's the actual shape of the work once you strip out the tasks that feel important but aren't weekly. The question isn't how to find more hours; it's how to spend the ten you have on the handful of things that genuinely have to happen this week, which is the whole subject of running an office on ten hours a week. Everything below this heading is really an attempt to fill in the details of that short list.
Titles cause more confusion than they should. “Church secretary” and “office administrator” describe the same work in most congregations this size — there's no meaningful line between them until a church is large enough to have a staff hierarchy with budget authority attached to the title. If you're deciding what to call the role, or what to call yourself, the practical answer is whichever name already matches how your church talks about the job, since the title on the business card changes nothing about which ten hours get worked.
The week, in order
A church office doesn't need a complicated system. It needs a short, repeatable sequence: things that happen every day no matter what, things that happen once a week on a fixed day, and things that only need attention once a month. Sorting your actual tasks into those three buckets is a smaller project than it sounds like, and separating daily admin work from weekly and monthly work is usually the single change that makes a chaotic office feel manageable, because it stops every task from competing for the same fifteen minutes of attention every morning.
In practice, the week has two anchor days. Monday is triage: whatever happened over the weekend — visitor cards, a facility issue, a voicemail from Saturday night — gets processed before it goes stale, which is the entire logic behind a Monday morning church office checklist. Friday is the opposite: not intake but a final check that nothing about Sunday is still an open question — the bulletin printed, the room set up, the guest speaker confirmed. A Friday checklist built specifically to catch what Sunday needs is less about doing new work and more about verifying that work already done actually happened. Between those two days sits the bulk of the writing, recording, and scheduling that makes up the rest of the week.
This is where a part-time schedule matters as much as the task list. A person working ten hours a week does better spread across four short mornings than crammed into one long Tuesday, because the office generates work every day — a phone call Wednesday, an email Thursday — and a single weekly block means everything in between sits untouched until the next session. Building a part-time schedule that actually holds up against a real week, rather than the idealized one on paper, is worth doing once and revisiting every few months as the church's actual rhythm shifts.
The bulletin is the weekly proof of life
Of everything a church office produces, the bulletin is the one artifact that goes out every single week without fail, which makes it a useful stress test for the whole operation. If the bulletin is consistently late or thrown together at the last minute, that's rarely a writing problem — it's a sign that the deadline for content isn't firm enough or isn't known by the people who owe you announcements. A fixed weekly production checklist with a hard cutoff for submissions does more to fix a chronically late bulletin than any amount of individual effort on a Thursday night.
The related question — exactly how far in advance the bulletin should be ready — matters more than it sounds like it should, because “as soon as possible” isn't a deadline anyone can plan around. And once it's produced on time, it's worth asking whether it's actually read, or whether it's the same three announcements rearranged. Writing a bulletin people actually read is a different skill from producing one on schedule, and both are worth getting right, since a bulletin nobody reads is ten hours of effort a week functioning as decoration.
The calendar is where offices actually break
More small-church admin conflict traces back to the calendar than to anything else, because a calendar with no single owner isn't really a calendar — it's a hope that everyone checked the same thing before booking a room. The fix isn't a better tool. It's answering who is actually supposed to own the church calendar and then making sure every ministry leader knows that person's name. Once ownership is clear, most of what looks like a scheduling problem turns out to be a communication problem that resolves itself.
The recurring failure pattern is depressingly consistent: two groups book the same room for the same Saturday because they checked different calendars, or no calendar at all. Understanding why calendar conflicts keep happening and how to actually stop them usually comes down to consolidating onto a single shared calendar that every relevant person actually looks at, rather than a bulletin board in the hallway and three people's memories. A shared calendar the whole staff and key volunteers actually use is a free, low-effort fix that solves more conflicts than most churches expect from something that costs nothing.
Ownership and a shared calendar solve most conflicts, but not all of them. Some rooms genuinely need a formal request — the sanctuary for a wedding, the kitchen for a large event — where a simple sign-up doesn't give the calendar owner enough information to say yes safely. A short, consistent request process gives people a clear way to ask and gives the owner enough detail to catch a conflict before it's booked, rather than after.
Records: what to keep, and for how long
Every church accumulates records it never quite decided how to handle: giving history, membership rolls, old meeting minutes, background check results, insurance paperwork. Left undecided, the default becomes “keep everything forever in a filing cabinet,” which is expensive in space and useless when you actually need to find something. The better approach is deciding, once, exactly how long a church should actually keep each category of record and writing it down so the decision doesn't have to be relitigated every time someone eyes the filing cabinet with a trash bag.
A written records retention schedule your church will actually follow turns that decision into something repeatable rather than a judgment call made under pressure the one time someone asks “can we throw this out?” It doesn't need to be elaborate. It needs to exist, and it needs to distinguish between records with a natural expiration and the small handful — incorporation papers, baptism and membership records — that a church should never discard at all. SundayBridge keeps the people, giving, and serving records a church enters day to day in one searchable place with a CSV export, which helps with the finding part of this problem; it doesn't replace the retention decision itself, which is a policy question a person still has to answer.
What breaks first when the rhythm slips
It's worth being specific about what actually goes wrong when a church skips the writing-it-down step, because “we'll figure it out” sounds reasonable until it isn't. The bulletin is usually the first casualty, because it's the most visible weekly deadline — it either goes out or it doesn't, and everyone notices. The calendar is the second, but more slowly: nothing looks wrong until the Saturday two groups show up for the same room, by which point the damage is a hallway argument rather than a missed memo. Records fail last and quietest of all — nobody discovers a gap in giving history or a missing background-check renewal until the exact moment they need it, which is usually the worst possible time to discover it.
None of these failures are dramatic on their own. A late bulletin gets forgiven. A double-booked room gets rescheduled with an apology. A missing record gets reconstructed, eventually, from memory and old email. What actually costs a church is the accumulation: three or four of these in a single season, each one small, each one absorbed by whoever's at the desk that week, until that person is quietly doing the work of a much bigger staff for the same ten hours. The rhythm doesn't break loudly. It erodes, one skipped step at a time, until the office is permanently behind and nobody can point to the single decision that caused it.
When it's just you
A lot of church administration in congregations this size is done by one person who also preaches, or teaches, or works a separate full-time job, which means the real constraint isn't skill or effort — it's hours. The honest starting point is admitting that finding time for admin work at all is the actual problem for a bivocational pastor, not a lack of organizational technique. No system fixes a schedule that has no slack in it; the goal is smaller, protected blocks of time used consistently rather than one long session that keeps getting bumped by whatever feels more urgent that day.
Inside those limited hours, not every task deserves equal weight. Some genuinely have to happen this week; others can wait a month without consequence. Deciding what actually gets done with only a few hours available is a skill worth practicing deliberately, because the alternative is doing whatever feels most urgent in the moment, which is rarely the same as what matters most. Part of that skill is learning what to say no to as a part-time secretary without feeling like you're letting the church down — a request that isn't urgent this week is allowed to wait, and saying so out loud, kindly, is part of the job.
There's a version of this that shows up specifically for the pastor rather than the office staff: the person preaching Sunday is often also the person the office routes email to during the week, which means sermon preparation competes directly with routine correspondence for the same limited hours. Treating those as two separate jobs with two separate time blocks, rather than one long undifferentiated stretch of “work,” is a small change that protects both.
Building a team so it isn't just you
The single biggest risk to a small church office isn't a bad system — it's a system that lives entirely in one person's head. If that person is out sick for two weeks, or leaves without much notice, the church doesn't just lose a staffer; it loses the institutional knowledge of how the office actually runs. The fix is deliberately building a volunteer admin team before you need one, even in a church too small to hire additional staff. Two or three volunteers who each know a piece of the operation is a real safety net; one overworked person with everything memorized is not.
Handing off work doesn't mean losing track of it. The goal is delegating office tasks while still knowing what's been done, which usually means clear task boundaries and a simple way to check status, not constant oversight. When a new person does take over the role — staff or volunteer — training them well in the first month matters more than any onboarding document, because most of what makes the job work is timing and judgment that's hard to write down completely. A written job description and a retention schedule get someone started; a few weeks shadowing the actual weekly rhythm is what makes it stick.
The one-page version of all this
Everything above — who owns the calendar, when the bulletin is due, how long records live, what a volunteer can decide without asking — is the kind of thing every long-serving church secretary eventually carries around correctly in their head. The problem is that it stays in their head. The single highest-leverage thing a small church can do is get it out of one person's memory and onto paper, even informally. A one-page office handbook covering the whole job doesn't need to be a policy manual. It needs to answer the five or six questions that come up every time someone new touches the office, so the next person doesn't have to rediscover them by trial and error the week you're on vacation.
None of this requires new software to start — a shared document and an honest hour of writing gets you most of the way there. What software genuinely helps with is the part that's hard to keep straight by memory once a church passes a hundred people: who's given what, who's serving where, which follow-up nobody has picked up yet. That's the part of the office SundayBridge was built to hold, at a flat $19 a month regardless of church size — but the rhythm itself, the who-owns-what and when-it's-due decisions, is work only your church can do, on paper, once, and then defend.