GuidesChurch staff
You don't have another evening to give this.
A day job, a church, a family. The half hour you actually have on a Thursday should go into deciding something, not into opening six screens to work out what there is to decide.

The half hour is real, and it is all there is
It is Thursday, somewhere after nine. The kids are down. You worked all day at the thing that actually pays, you have a lesson to finish for Sunday, and you have opened the laptop because there is church work waiting and this is when it gets done.
You have about half an hour before you are no longer any use to anybody.
That is the whole design constraint, and almost no church software is built as though it were true. The tools assume an office. They assume somebody arrives at nine, opens the system, and works it. What they hand a person with half an hour is a search box and a menu.
And before anyone at a larger church skips this one: the shape is the same at a thousand people with twenty staff. The pastor there has no unstructured half hour either, because his week is meetings. He is not hunting for the family who stopped coming; he is trying to work out which of his twenty people is quietly drowning, and he will usually find out by resignation letter.
The cost is not the work. It is the looking.
What actually eats the half hour is worth being precise about, because it is not the part people assume.
The pastoral work itself is small. A phone call is ten minutes. A text to a grieving family is two. Writing a note to the volunteer who covered twice takes one. If somebody handed you a piece of paper that said do these four things, you would be done before the coffee went cold and you would go to bed feeling like a pastor.
What eats the evening is finding out what the four things are.
You open the directory. Nothing tells you anything, because a directory is a filing cabinet and filing cabinets do not volunteer information. So you check attendance. Then giving, because it has been a while. Then the group leaders' notes, if anyone wrote any. Then your own email, which is where half the church's actual pastoral traffic lives. Four of those six screens tell you nothing happened, and here is the quiet cruelty of it: a screen that says nothing happened looks exactly like a screen you did not check.
So you either check them all every week, which is the half hour gone with nothing decided, or you check some of them and carry a low background hum about the ones you skipped. Most people do the second one. That hum is not a character flaw. It is the predictable output of a system that made you responsible for the searching.
Storing is not the same as having already decided
Every system stores. That part is solved and has been for twenty years. The thing worth paying for is whether it has done any thinking before you arrived.
The test I would put to any of them is this. Open it cold after nine days away. Does it tell you what changed and what it thinks you should look at, or does it hand you a search box and wish you luck?
Most of what that requires is unglamorous and comes down to sorting. A list of open follow-ups ordered so the most overdue sits on top is worth more than a hundred filters, because a filter asks you a question and a sort answers one. Every filter is a small tax on a tired person. Every sensible default sort is a decision somebody already made so you would not have to.
The other half is having the nerve to show nothing. A page that displays nine sections every week, six of them zeros, is teaching you to skim, and once you are skimming you will skim past the one that mattered. A page that hides the seven with nothing to say is telling you something with its shape before you have read a single number.
Neither of those is clever. Both of them are the difference between a tool that costs you an evening and a tool that gives you one back.
The one thing you must never automate is the reaching out
Now the dangerous part, and it is dangerous precisely because it is aimed at tired people.
Once a pastor is stretched thin, the pitch that lands hardest is the one offering to do the caring for him. Automatic birthday texts. Automatic notes to people who have not been seen. Automatic messages when somebody's giving stops. It sounds like mercy, and every one of those is a real feature you can buy this afternoon.
Think about that last one for a second, though, because it is the one that will cost you a family.
Giving stops for a reason. Sometimes the reason is that somebody is annoyed with you. Far more often the reason is a job that ended, a diagnosis, a marriage coming apart, a parent moving in. Those are the exact households where an automated message from the church, however warmly it was worded eighteen months ago by somebody who has since left, arrives as a bill. There is no template that fixes this. The problem is not the wording, it is that the church sent something without knowing.
So the line is not where the sales page puts it. The software may do the remembering, which it is better at than you are. It may do the drafting, which saves you the blank page. It must not do the sending.
And for the handful of triggers where an automated message could land on grief, being able to switch the sending off is not good enough. A setting is a thing a tired man forgets, or a thing a well-meaning volunteer flips on in his second week because it seemed helpful. Those categories should be structurally incapable of messaging a member at all: not off, but absent.
The one nobody is watching is the one reading this
Every church system in existence watches the congregation. Attendance, giving, guests, groups, engagement, whatever they are calling it this year. Not one of them watches the people doing the work.
Which is strange, because the person most likely to quietly break in a small church is not a member. It is the volunteer who has run sound eleven Sundays in a row because saying no felt like letting people down. And in a large church it is the staff member carrying nine open situations while everyone assumes somebody else has them.
Both facts are already sitting in the records. Nobody looks, because nobody was ever asked to, and because the person best placed to notice is the person with the least time to go looking.
What that deserves is a plain line on a page you already open: this person has served four Sundays running, this one is carrying five open follow-ups. Not an alert. Not red. Not a suggestion about what to do. The software can see the count; it cannot possibly know whether those four Sundays are grinding someone down or are the best month they have had in a year. It should say the fact, once, in the same flat voice it uses for everything else, and then get out of the way.
And if you are bivocational, read that paragraph again with yourself in it. Nobody is watching your load either, because you are the office. The same page is the only place it will ever show up.
How we do it
How Stewara does it
Stewara was built by a bivocational pastor and is run every Sunday by the church he pastors, which is why the half hour above is not a persona exercise. It is the schedule the thing was written in.
The follow-up queue is sorted so the most overdue sits on top, and it is the only counted badge in the whole application: one number, on one rail item, and it turns red only once a day has actually passed rather than the moment a task comes due. Nothing else in Stewara carries a badge, because a second one would immediately make the first one ignorable.
The Monday debrief assembles yesterday into one panel on your home screen, and it is on the free tier, so a church paying nothing still gets it. Every section self-hides, so a quiet week is a short page. It opens itself on Monday and Tuesday and collapses from Wednesday, because by then it is history and you have a job to get to.
“Team watch” sits at the bottom of that panel and reads out two things: that somebody “has served 5 Sundays straight — might be due a Sunday off”, and that somebody “is carrying 4 open handoffs”. Four Sundays is the threshold, three handoffs is the threshold, and there is nothing on those rows to click. The instruction the code gives itself is the whole design: “The software NEVER acts.”
On the automations, the line falls where this article argues it belongs. Every watcher ships switched off. The built-in ones create a staff follow-up and never message a member, and the panel says so on its face: “These quietly create a staff follow-up on someone's care timeline — never a message to a member.” Birthdays get a fifth kind of action, “Prepare a personal text for someone to send”, which drafts the words and puts them in a queue for your own thumb, because a birthday text that arrives from a system is worse than one that arrives late from a person.
And the giving one cannot be turned into a message at all. Not off by default: structurally unavailable. Build a recipe on a lapse in giving, choose a text, and the server rewrites it back to a task, every time the recipe is read, forever. The reason is written into the file so nobody quietly undoes it: a lapse may be a job loss or a diagnosis, and no template keeps an automated message from reading as a payment reminder.
Two things to know before you count on any of this. Nothing pastoral is emailed or pushed at you. The follow-ups, the handoffs, the flags, the debrief and Team watch are all waiting on the screen when you open it, which is the trade this article argues for, but it does mean you open it. And of those, only the follow-up queue is on the phone today; the debrief and Team watch are on the web.
The short version
The half hour is the budget. Everything below is about spending it on the work instead of on the search for the work.
- The pastoral work is small. Finding out what it is takes the whole evening, and that is the part software should be buying back.
- Count the screens you would have to open on a Thursday night to know whether anything needs you. If it is more than one, the feature list does not matter.
- A sensible default sort is worth more than a page of filters. One asks you a question; the other answers one.
- Let it remember and let it draft. Do not let it send. And on anything that could land on grief, it should be incapable rather than merely switched off.
- Whatever you use should count what your people are carrying, not only what the congregation did. Including, if you are the one reading this, yours.