A part-time church secretary's job description usually says ten or fifteen hours a week. The actual demand on that role rarely respects the number. Every ministry leader has something they need, every request feels urgent to the person making it, and nobody but you is keeping a running total of how full your week already is.
The result, left unmanaged, is a job that quietly grows to fill whatever hours you are willing to give it — nights, weekends, the hour before your own family dinner. The fix is not working faster. It is deciding, in advance, what you will say no to, so the decision is made once instead of forty times a year under pressure.
Same-day requests, unless someone is in crisis
Someone stops by your desk Tuesday morning and asks if you can pull a list, print a program, or draft an email “today, if you can.” Nine times out of ten, today is not actually required — it is just the day they thought of it. Decline the same-day frame and offer a real one: “I can have that to you by Thursday.” Reserve genuine same-day turnaround for actual emergencies: a death in the congregation, a pastoral crisis, something breaking before Sunday morning. Everything else can wait for your normal queue.
Tasks that belong to the person asking
A volunteer coordinator who wants you to personally call every person on a serving schedule to confirm they are still coming is asking you to do their job, not yours. A small group leader who wants you to track down who has not attended in three weeks is doing the same thing. Your role is to keep the records that make those jobs possible — the roster, the attendance history, the contact list — not to execute every task that touches a record you maintain. A useful test: if the task requires a relationship with the person involved, it belongs to whoever has that relationship, not to the office.
A line that works
“I can pull you the list of who hasn't served in a month, but the calls need to come from you — they know you, not me.” That sentence draws the line without making anyone feel dismissed: you did the part that was actually yours.
Being the unofficial IT department
In a lot of small churches, the secretary becomes the default answer to “who do I ask about the projector, the Wi-Fi password, or why my church email won't open on my phone.” If troubleshooting technology is not in your job description, it should not quietly become your afternoon. Point people to whoever actually owns that equipment, or to a short written guide, rather than becoming the person who gets summoned every time a cable comes loose.
Open-ended research and one-off design requests
“Can you look into what other churches our size are doing for small groups” or “can you make us a nicer bulletin design, you have an eye for that” are both real work, and both are the kind of open-ended task that can eat an entire week if you let it, because there is no natural stopping point. If a task does not have a defined scope and a defined deliverable, ask for one before you start: “How many hours should I put into this, and what does done look like?” If nobody can answer that, it is not ready to be handed to you yet.
Being the keeper of every password and login
It is tempting, and often true, that you end up knowing the login to the bank portal, the church email, the giving platform, and half a dozen subscriptions, simply because you were the one who set most of them up. Resist becoming the sole person who can access any of it. Insist that a second person — a treasurer, a pastor, a trustee — has real access to anything financial or account-critical. This protects the church if you are out sick or leave the role, and it protects you from being blamed for delays caused by information only you had.
Requests that arrive after hours
A text at 9 p.m. asking you to update the Sunday bulletin, or an email sent Friday night expecting a reply Saturday morning, trains people to treat your evenings as office hours if you respond. You do not have to ignore the message. You do have to let it wait until your actual working hours, every time, so the pattern never sets. A short auto-reply or a standing statement — “I check email during my scheduled hours, Tuesday and Thursday mornings” — does most of this work for you without a single awkward conversation.
Where your records can carry more of the load
A fair number of these requests exist because the information people want is scattered somewhere only you can find it. If serving schedules, giving history, and contact details live in a shared record instead of your personal spreadsheets, a volunteer coordinator can check who is scheduled without asking you, and a pastor can see attendance trends without waiting for your next free hour. SundayBridge keeps that kind of record in one place a church can look at without going through the office every time. It will not make the requests disappear, but it moves some of them from “ask the secretary” to “check the record,” which is the whole point.
If your church is still building that shared directory the team trusts, it is worth doing before you try to hold any new boundaries, because half of what gets asked of a secretary is really a symptom of nobody else being able to find the answer themselves.
Give the no a landing place, not just a wall
A boundary that only says no eventually reads as unhelpfulness, even when it is not. Pair every decline with a next step: a day it will get done, a person who should actually own it, or a place the answer already lives. “I can't do this today, but I can Thursday” is a boundary. “No” by itself, said enough times, is how a good working relationship with your pastor and volunteers starts to fray. Building a predictable weekly rhythm for your own hours makes this easier, because you can point to the rhythm instead of improvising a reason every time.
What this protects, beyond your calendar
Every hour spent on a task that was not really yours is an hour not spent on the things only you can do well: keeping records clean, closing the loop on a guest nobody followed up with, getting the giving statements out on time. Protecting your hours is not selfishness. It is how the part of the job that actually needs a competent person still gets done, instead of being crowded out by whatever felt urgent to somebody else that week. A church that runs its volunteers the same way — without a few people quietly absorbing everything — tends to keep its part-time staff longer too.