For the person who owns Monday morning
Your church software records what happened.Something should notice.
MinistryFlow reads across the systems your church already uses, works out what needs attention this week, and prepares the work. A person approves anything that reaches a human being.
Works with Planning Center. Read-only to begin with.
Attendance change for the Whitfield household
Why this is here
2 members of this household each attended at least 6 of the 8 weeks before the last 4, and none of the last 4. This is a signal, not a conclusion.
What MinistryFlow can do
The gap
The data exists. Somebody has to notice it.
Every Sunday produces a Monday's worth of follow-through. The information is all in your systems, spread across the ones that hold it, and none of them will tell you what matters.
A normal Monday holds all of this:
- Seven first-time guests from Sunday have not been contacted.
- Children's ministry is short two volunteers for this weekend.
- Six households that came every week have not been in a month.
- Eleven volunteers have not answered a scheduling request.
- The leadership report is due Friday.
None of it is hard to find once you know to look. The problem is that nobody has time to look at everything, every week, forever.
The rhythm
It runs on the week you already have.
There is nothing to remember to check. The work arrives on the morning the work actually starts.
Sunday
People come. Your staff check children in, run services, take headcounts, and nobody writes anything extra down.
Overnight
MinistryFlow syncs what changed and recomputes every signal from your own records.
Monday, 6am
A brief arrives for each staff member, written from those facts and filtered to what that person is allowed to see.
Through the week
You work the inbox. Approve the welcome notes, assign the pastoral ones, dismiss what does not apply and say why.
Whenever you ask
“Where are we short this weekend?” “Who hasn't been contacted?” Same records, same permissions, answers in the inbox rather than in your memory.
Good morning, Dana.
Attendance held steady. Seven people came for the first time — more than any Sunday since Easter — and the week ahead is short on volunteers in one place.
What matters this week
- Seven first-time guests from Sunday have not been contacted.
- Children's ministry is short two volunteers for this weekend.
- Six households that came every week have not been in a month.
- Eleven volunteers have not answered a scheduling request.
- The leadership report is due Friday.
The Monday brief, written from that week’s own records.
The part we will not compromise
It prepares the work. You decide.
MinistryFlow drafts the note, finds the volunteers, assembles the brief. It cannot send a message, write to your church database, or contact anyone without a person approving that exact thing first.
The model never holds a send button
Tools that write or contact people are structurally unavailable to it. Not discouraged by a prompt — absent from what it can call.
Approval is bound to what you read
If a draft changes after you approve it, the approval no longer applies and the work stops.
Some things are never automatic
Anything pastoral is marked for a person to handle, and no setting turns that off.
Every action leaves a record
Who approved what, when, and what the evidence was — written in the same transaction as the change.
01
Your records
Planning Center, synced and normalised. Nothing is copied that the flow does not need.
02
Signals
Computed in code, not by a model. The same week always produces the same answer.
03
A draft
The model phrases it, prioritises it and writes the note. It never decides what is true.
04 · The gate
A person decides
Approve, edit, assign, snooze or dismiss. Nothing passes on its own, and pastoral items cannot be set to pass on their own.
05
It acts, and records
The write happens once, in the worker, with who approved it and what they saw.
The language model holds tools for steps 02 and 03 only. The tools that send a message or write to your church database are not in the set it is given.
What it watches
Six things nobody has time to check every week.
Each one is computed from your own records, and every recommendation shows the evidence it came from.
Who is new
First-time guests, with the check-in that proves it and whether anyone has reached out yet.
Who may be drifting
Households with an established pattern who have stopped coming. Presented as a signal, never as a conclusion.
Where Sunday is short
Unfilled positions with a list of people who are qualified and have not served in the last two weeks.
Who is not connected
People attending regularly who are not in a group, with the groups that actually fit their campus and schedule.
What is waiting on a reply
Scheduling requests nobody has answered, with how long they have been outstanding.
What leadership should know
A weekly brief written from the same evidence, for the people who do not live in the software.
Design partners
We are looking for a few churches to build this with.
Built by Barrett Agentic, in Kansas.