What did you personally do last week that somebody else could have done?

It's 9:40 on a Tuesday night, and the pastor, we'll call him Mark though he isn't any one person, is at his kitchen table formatting Sunday's bulletin, because the volunteer who usually does it had a sick kid and texted him at 6.

He is not annoyed. That is the part worth noticing. He opened the file, found last week's template, started fixing the line break that always lands wrong in the second column, and never once thought this is not my job. It has been his job long enough that it stopped being a question.

Mark is a composite, built out of patterns that repeat across a lot of church operations conversations, not out of any one man's calendar. What follows is his week, day by day. Not because it is remarkable. Because it isn't. It is one piece of the pastor's capacity problem, and it is the piece that hides best, because nothing in it looks like a crisis.

Monday: the bulletin, the building, and the budget line nobody flagged

Monday morning, 8:15. Mark opens the bulletin skeleton to drop in the sermon title, the service order, and the missionary update that came in Saturday night. The template fights him for a while. Forty minutes.

Three minutes before that, at 8:12, a volunteer had sent him a photo: the toilet in the east hallway, running since Sunday. She texted him because his is the number she has. He texts the plumber, gets a callback at 10:40, gives him a window Wednesday, then texts her back so she knows it is handled. Thirty-five minutes, scattered across the morning in pieces small enough that he would swear it took five.

Then the finance report. There is a line, $1,240, tagged "Facilities, other." Nobody flagged it. He notices it because he reads everything. The vendor portal login has been in his name since the bookkeeper left, so he is the only person who can go look. Fifty minutes later he knows it was the parking lot lights, which is fine, and which he could have known in four minutes if anyone else had the password.

Two hours and five minutes before lunch on Monday. Not one of those minutes needed a pastor. All three of them needed somebody, and there was no somebody.

Tuesday: the software problem that was never his to fix

Tuesday is study day. It is blocked on the calendar 8 to 1, and everyone on staff knows it, and Mark has protected it for six years the way you protect the one thing that keeps you sane.

The check-in tablets went down before second service on Sunday. Volunteers wrote kids' names on masking tape for an hour. The children's director asked him Sunday afternoon what he wanted to do about it, which is a reasonable question to ask, and he said he'd handle it, which is where the whole thing goes wrong.

9:15 Tuesday he opens the support chat. Twenty-five minutes in a queue. The agent needs the account owner to verify, and the account owner is a staff member who left in 2023, so the password reset goes to a mailbox nobody controls anymore. He calls the phone line. Hold. Escalation. They promise a callback. The callback comes at 12:40, which is the last block of study time, and takes twenty minutes, and resolves it.

Three hours and ten minutes of Tuesday, gone. Notice where it does not come from. The sermon still happens Sunday. The sermon is not negotiable, so the hours do not come out of the sermon. They come out of Tuesday night at the kitchen table, which is where we found him at the top of this page.

Wednesday: the email that could have waited, and the one that couldn't

Two emails arrive Wednesday morning, twenty minutes apart.

The first is from a family in the church. Their grandmother died Tuesday night. They want to talk about a service. Mark calls within the hour and stays on the phone for forty minutes, and for most of it he is not talking. That forty minutes is the most important thing on his calendar all week, and it is the only thing on his calendar all week that could not have been done by anybody else alive.

The second email says "Action required: your subscription renews in 3 days." Church management software. The price is going from $3,900 to $4,800 a year. It has been sitting in his inbox for nine days, not because he did not see it, but because acting on it means pulling the actual usage numbers, comparing two plan tiers, and making a call. That is maybe forty minutes of careful work for a person with access and a spreadsheet. It has sat nine days because the person is nobody, so the person is him, and he is the one human in the building with the least room left in his week.

There is the line the whole week is drawing, and it is worth saying out loud. One of those emails required Mark. The other required a person. Any competent, trustworthy, vetted person with access and an afternoon. The church had no such person, so the vendor renewal floated up until it landed on the guy who was also writing Sunday's sermon.

By Friday: the tally

Here is Mark's week, added up.

Mark's week, illustrative composite

Sunday services and Sunday morning presence	8:00
Preaching prep and study	9:00
Pastoral care: the funeral call, a hospital visit, two counseling appointments	6:30
Staff meeting, elder meeting, one-on-ones	5:00
Bulletin, the facility call, the finance line	4:15
Check-in software and the dead vendor account	3:10
Scheduling, email, and admin nobody owns	6:05
Total	42:00

Illustrative. These hours were written for this story, not measured. Mark is a composite and so is his week. This is not research, it is not a survey, and it should never be quoted as one. Its only job is to be specific enough that you can hold it next to yours.

The bottom three rows add to thirteen hours and thirty minutes. A third of the week, run by the one person in the organization whose time is hardest to replace, on work that a trained generalist could have run without him.

Thirteen and a half hours is not the scandal. Here is the scandal. Nobody decided it. There was no meeting where a board looked at a pastor's week and voted to spend a third of it on software accounts and vendor renewals and a running toilet. It accumulated. Every piece of it arrived one at a time, each one small enough to just handle, and none of them ever left. That is where the rest of your week actually goes, and it is also why what a church your size should actually be staffed for is usually a number nobody at the church has ever run.

And Mark is not struggling. He would not use the word burnout. He would tell you the week was normal, because it was.

The question

So do the exercise. It only works if you actually do it, and it takes about fifteen minutes.

Get paper, not a document. Go back through last week the way we just went through Mark's, day by day, and write down everything you personally did. All of it, including the four-minute things, because the four-minute things are where the week actually goes. Then read the list twice. The first time, mark everything that required you specifically. The second time, look at what is left.

Do not decide anything yet. Do not fix it, do not fire anyone, do not build a system. Just answer the question honestly, which is harder than it sounds, because most of us have been answering it rhetorically for years.

What did you personally do last week that somebody else could have done?