The administrator is finishing the bulletin when a room request arrives, followed by a reimbursement question and a call about Sunday’s volunteers. None of those requests is unreasonable. Together, they can make the agreed work impossible to finish in the agreed hours.
A job description that ends with “other duties as needed” will not resolve that problem on its own. The administrator and supervisor need a shared answer to what takes priority, who can make decisions, and what waits when the week fills up.
Agree on the essential outcomes
Choose a small number of outcomes, then connect routine tasks to them. For example:
- People can reach the church — Monitor the agreed phone and inbox. Decision owner: Administrator within published hours.
- Weekly information is accurate — Collect and prepare announcements. Decision owner: Editor, with a named reviewer.
- Records are maintained — Process approved contact updates. Decision owner: Authorized records staff.
- Requests reach the right person — Route room, care, or finance questions. Decision owner: Relevant ministry or finance lead.
- Work continues during absence — Maintain instructions and backup access. Decision owner: Supervisor and backup staff.
Adjust the list to the role's actual hours. A table should clarify responsibility, not quietly add five jobs to one person's week.
State authority and limits
Write down which requests the administrator can approve, which spending decisions belong to finance, and which conversations need a pastoral leader. Identify who handles technical problems beyond routine use of office tools.
Agree on office hours, response expectations, and the route for urgent matters. A personal phone number should not become the only continuity plan.
A practical conversation might sound like this: “The funeral printing needs to happen today. To make room, we’ll move the routine directory update to Monday, and the ministry lead will collect the event details.”
That is a priority decision with consequences. “Please prioritize everything” leaves the administrator responsible for a choice they may not have the authority to make. The supervisor should help name what moves, stops, or goes to someone else.
Set a complete-request standard
For an announcement, require the approved date, time, location, contact, and deadline. For a room request, include setup and cleanup needs. For a reimbursement, use the finance team's process.
Use wording that makes the next step easy: “I can include this once you confirm the room and start time. Please send those by Wednesday at noon.” Give leaders enough notice of the deadline, and agree who decides when a late exception is necessary.
The administrator should not have to renegotiate the same boundary with every request.
Use software for named pieces of work
TimelyChurch can keep people records, events, room bookings, announcements, forms, and assigned Follow-ups within the church system. Event Prep Tasks can also appear in eligible assignees' My Tasks.
Choose one repeated interruption to improve. If the administrator keeps answering “Who is buying supplies?”, a visible task owner may help. If they are mediating priorities between two ministries, leadership still needs to make that decision.
Configure permissions around responsibilities. Sharing a website or task role should not require opening every sensitive record to every helper.
Review the work after a month
Keep a brief record of recurring interruptions and work that could not fit into the agreed hours. Discuss it with the supervisor without treating the record as a minute-by-minute productivity score.
Ask what can be clarified, delegated, simplified, or stopped. Test the backup person's ability to complete a routine job using the instructions.
A sustainable office role has enough capacity to respond thoughtfully when a person needs help. Clear ownership and a realistic workload make that possible more reliably than another list of duties.
When ownership is clear but the information still arrives in too many places, explore TimelyChurch. Try one repeated office job—an event request, an assigned preparation task, or an announcement handoff. Software earns its place when it reduces avoidable chasing and leaves the administrator time to help the people who need them.