How to run a church staff meeting worth the hour

A church staff meeting worth an hour has three fixed segments, in this order: 15 minutes of calendar and logistics, 30 minutes on the one or two decisions that actually need the room, and 15 minutes of prayer and personal check-in, deliberately last, not first, so it doesn't eat the agenda.


15. 30. 15. In that order. Illustration: a kitchen timer with a gold winding button.
The short answer

Run the meeting in three fixed segments: 15 minutes of calendar and logistics, 30 minutes on the one or two decisions that actually need the room, and 15 minutes of prayer and check-in, placed last on purpose. That order, more than any single agenda item, is what separates a meeting that produces decisions from one that produces updates.

This is written from inside the room, not from a business-meeting template with "church" pasted over it. The specific failure is one every executive pastor recognizes: the meeting opens with prayer requests and personal check-ins, which matters pastorally, runs long because it should, and by the time the actual decisions come up there are ten minutes left and everyone's watching the clock. It's one rhythm in the weekly cycle covered in our guide to the church operations playbook.

CoLabor Staffing places full-time Christian co-laborers with churches and Christian-owned businesses, and this same agenda is close to what a co-laborer would run if they were sitting in your Wednesday morning meeting taking notes. The structure below doesn't require hiring anyone. It requires one person willing to hold the clock.

Why do most church staff meetings feel like a waste of time?

Three things, almost always in combination: no fixed agenda, pastoral care and operational decisions mixed together with no boundary between them, and no named owner for whatever gets decided. Take any one of those away and the meeting still works. Leave all three in place and an hour a week disappears with nothing to show for it.

The pastoral-mixing problem deserves its own sentence, because it's the one most staffs don't see coming. A team that genuinely loves each other will let a prayer request turn into a fifteen-minute conversation, because stopping it feels cold. That instinct is right in a small group. In a staff meeting with a facility decision and a volunteer gap still on the table, it's the reason the meeting runs long every single week and nobody can point to why.

The real cost

An hour a week across a five-person staff is five staff-hours. Run that for a year and a meeting nobody trusts has quietly cost the church a quarter of a full-time role in wasted time. Fixing the agenda is cheaper than any hire.

What's a 60-minute agenda that actually works?

The three-segment staff meeting
MinutesSegmentPurpose
0-15Calendar & logisticsUpcoming dates, facility and volunteer flags, quick updates that need no discussion
15-45DecisionsThe one or two items that actually need the whole room's input, each assigned an owner and a date before moving on
45-60Prayer & check-inPersonal and pastoral, placed last so it never gets cut short by time pressure

Our recommended structure. Adjust the split for a smaller staff, but keep the order: logistics, decisions, then people.

The 30-minute decisions block is deliberately capped at one or two items, not five or six. A meeting that tries to decide six things in 30 minutes decides zero things well. If the agenda is running long every week, the fix usually isn't a longer meeting. It's a shorter list, with the extra items pushed to a smaller working conversation outside the room.

What does a filled-out agenda actually look like?

Here's the structure above, filled in as a real agenda you can copy, rename, and send out before your next meeting.

Weekly staff meeting agenda

Staff Meeting, Week of [date]

Time: [60 minutes] · Attendees: [core staff names] · Agenda owner: [name]

Calendar & logistics (15 min)

  • Upcoming dates and events on the next two weeks' calendar
  • Facility or volunteer flags that need a quick heads-up, not a discussion
  • One-line updates from each ministry area

Decisions (30 min)

  • Decision 1: [the specific question the room needs to answer]
  • Decision 2 (if there is one): [the specific question]
  • Each decision closes with a named owner and a date, recorded here before moving on

Prayer & check-in (15 min)

  • Personal updates and prayer requests
  • Closing prayer

Action items from last week (review at the top of the next meeting)

  • [Item], owner [name], status [status]

What belongs on the agenda, and what belongs in a different conversation?

Operational decisions stay on the agenda: the calendar, a scheduling conflict, a vendor choice, anything that needs the room to weigh in before it moves forward. Pastoral care conversations move to one-on-ones. This isn't a statement that pastoral care matters less. It's a statement that a group meeting is the wrong setting for it, and that mixing the two is exactly what turns a 60-minute meeting into a 90-minute meeting that still didn't decide anything.

A useful test for anything about to be added to the decisions block: does this need the whole room, or does it need one conversation with one person? A scheduling conflict between two ministries needs the room, because both leaders are sitting in it. A staffer's personal struggle needs a private conversation with their supervisor, not a group discussion with an agenda item number next to it.

Who should run the meeting, and who sets the agenda in advance?

One person owns the agenda and circulates it before the meeting, not the morning of and never built live in the room. If staff are seeing the topics for the first time when the meeting starts, the meeting will spend its first ten minutes figuring out what it's even for. That circulation should go out at least a day ahead, giving anyone with a decision item enough time to think it through instead of reacting live.

The agenda owner and the meeting's presiding leader don't have to be the same person. A lead or executive pastor can run the room while someone else, an administrator or operations-minded staffer, builds the agenda, watches the clock, and makes sure the prayer segment doesn't quietly swallow the decisions block. Splitting those two roles is often what makes the discipline stick past the first few weeks.

How do you make sure decisions actually get followed up on?

Every decision leaves the meeting with a name and a date attached, not just a general sense that "someone will look into it." The next meeting opens by reviewing last week's action items before anything new gets added. Skip that review once and the agenda quietly loses its authority; staff learn that decisions made in the room don't actually have to happen.

The review itself should take two minutes, not fifteen. Read the list, mark each item done, in progress, or stalled, and move on. The point isn't a status meeting about the status meeting. The point is that everyone in the room knows the group's word means something, which is the entire reason a staff meeting is worth having at all.

How often should this meeting happen, and who needs to be in the room?

Weekly, with core staff only, the people whose work actually intersects week to week. Save an occasional all-staff or all-hands meeting for announcements that need everyone, and don't let the weekly operational meeting swell to accommodate it. A bigger room produces a slower meeting, not a better one.

A church running multiple ministries with part-time and volunteer leads often faces pressure to invite "just one more person" who might be affected by a decision. Resist it by default. If a decision genuinely needs someone outside core staff, invite them for that single agenda item and let them leave, rather than growing the standing meeting to include everyone who's ever touched an adjacent ministry.

Where this fits in the week

This meeting is usually the midweek anchor for confirming the coming Sunday. See the full weekly church office checklist for how Tuesday and Wednesday's confirmation tasks feed into it.

The follow-through this agenda depends on, someone tracking action items and keeping the next meeting honest, is the kind of recurring work a co-laborer runs. See how it works.

Common questions

What should be on a church staff meeting agenda?

Calendar and logistics first, the one or two decisions that need the room second, and prayer or personal check-in last.

How long should a church staff meeting be?

About an hour, with a fixed time budget per segment so no single topic can eat the whole meeting.

Should prayer be part of a church staff meeting?

Yes, but placed deliberately at the end so it doesn’t crowd out the operational decisions the meeting also needs to make.

Who should set the agenda for a church staff meeting?

One named owner, circulated before the meeting starts, not built live in the room.

The CoLabor team

We place full-time Christian co-laborers with churches and Christian-owned businesses, and we publish what church staffing actually costs. Here is how it works.