The Monday Morning Church Staff Report: The Internal AI Workflow to Build First

A Monday morning church staff report is a one-page summary of everything that came into your church during the past week: new guests, connect cards, event sign-ups, contact forms, missed calls and messages nobody has answered yet. An internal AI workflow can read those sources overnight on Sunday and write the page before the staff meeting. Nobody outside the staff ever sees it, which makes it the safest first AI project a church can take on.

This is the last part of our seven-part series on AI for churches. It ties the others together, and if you only build one thing, we would suggest this one.

Why this is the one to build first

The other six ideas in this series all talk to the public: guest follow-up, a website chat bot, volunteer scheduling, sermon content, event sign-ups and prayer request routing. Each one sends messages to people outside your staff, so each one needs care.

The Monday report sends nothing to anyone. It reads what already arrived and tells your team about it. If it gets something wrong, a staff member notices in the meeting and nothing has gone out under your church's name. That makes it a low-risk way to learn what AI is good at and where it needs watching.

It also solves a problem nearly every church has: the information exists, but it is scattered across six places and one person's memory.

What scattered looks like

On a typical Monday, here is where last week's contact with your church is sitting.

• Connect cards in a basket or a church management system.
• Website contact forms in an inbox.
• Event sign-ups in a form tool.
• Voicemails on the office phone.
• Direct messages on Facebook and Instagram.
• Texts on the pastor's personal phone.
• A conversation in the lobby that somebody meant to write down.

Each staff member knows their own piece. Nobody sees the whole. So the staff meeting opens with "did anyone call the family who visited two weeks ago?" and a pause.

What goes on the page

A good Monday report fits on one page and answers five questions.

1. Who is new? First-time guests from Sunday, with what they wrote on their card and who came with them.

2. Who came back? Second and third-time guests. They are easy to miss, because nobody is handing them a card anymore.

3. Who needs a call, and from whom? Anyone who asked a question, requested a visit, or raised something a pastor should hear, with a suggested owner.

4. What is unanswered? Messages, forms and voicemails older than two days with no reply. This list should be empty. When it is not, it is the most important part of the page.

5. What do the numbers say? A few counts, the same ones every week: guests, returning guests, sign-ups by event, volunteer gaps for next Sunday, open requests.

It ends with a short "decide today" list: the three or four items that need a name next to them before the meeting ends.

A sample report

Here is roughly what a staff member would read at 8am.

Week of October 4. 6 first-time guests (2 families, 2 individuals). 3 returning guests. 14 new sign-ups for the fall serve day, 41 total. 2 volunteer gaps for Sunday: nursery at 9am and parking at 11am.

New guests. The Alvarez family, two children aged 6 and 9, asked about the kids' program. Thank-you sent Monday. Suggested owner for a call: Karen. One guest wrote "new to the area, looking for a small group". Suggested owner: Mike.

Needs attention. A contact form from Thursday asking about a funeral service has no reply. A voicemail from Friday about the food pantry has no reply.

Decide today. Who calls the Alvarez family. Who answers the funeral inquiry this morning. Who fills nursery at 9am.

That is a staff meeting that starts with decisions, not with trying to remember.

What stays out of the report

An internal report still needs limits. These are the ones we would set.

Private prayer requests. Anything a person marked for the pastor only does not appear, not even as a count with a description. See our post on prayer requests for why.

Giving information. Who gave, how much, or who stopped. It does not belong in a staff summary, and the workflow should not have access to it.

Children's medical and custody details. The report can say a form is missing. It never includes what a form contains.

Pastoral care notes. Counseling and care conversations stay with the pastor.

Speculation. The report says what happened: a form came in, a card was filled out, a message is unanswered. It does not guess at anyone's spiritual state or predict who is "at risk of leaving".

The rule of thumb: if you would not read it aloud in a staff meeting with a volunteer in the room, it does not go on the page.

How the workflow runs

1. Sunday night: it gathers the week's entries from each source you have connected.
2. It matches people across sources, so the family on a connect card and the same family on the VBS sign-up are one line, not two.
3. It checks each item for a reply and marks what is still open.
4. It writes the page in the same order every week, in plain sentences.
5. Monday at 7am: the report arrives by email or in your staff chat.
6. In the meeting, owners are assigned. Those names go back into the list, so next week's report can show what was done.

Step six is what turns a report into accountability without anyone having to nag.

You can build a hand-made version this week

You do not need AI to try this.

1. On Sunday afternoon, one person opens each inbox and list and writes down the week's new names and open questions in one shared document, under the five headings above.
2. Open Monday's staff meeting with that document, before anything else.
3. Put a name next to every open item before you leave the room.

Do it for four weeks. You will learn which sources matter, which ones nobody checks, and how long it takes. If it takes one person an hour every Sunday and the meeting is clearly better for it, that hour is what a workflow would give back.

How we would build it, and what it costs

We would start by listing every place a message or a name can reach your church, connect the ones that can be connected, agree on what stays out, and send you the report for three or four weeks alongside your normal meeting so you can tell us what is missing or wrong. Because nothing goes to the public, we would expect this to be the quickest of the seven to get right.

Because it is internal and reads only what you connect, a Monday report is a smaller job than a full set of agents. Our AI builds start at $1,500 for setup plus from $300 a month, and the price depends on how many sources it reads. Setup is half to start and half when it is live, and the monthly fee is only collected once it is running. You get a fixed price in writing first. Details are on our AI services page.

The whole series

• AI agents for small businesses and churches: the overview.
• Part 1: Guest follow-up
• Part 2: A chat bot for your church website
• Part 3: Volunteer scheduling
• Part 4: Turning one sermon into a week of content
• Part 5: Event sign-ups
• Part 6: Prayer requests, routed with care

Frequently asked questions

What is the best first AI project for a church? An internal weekly summary for the staff. It reads what already came in, such as connect cards, forms and messages, and writes one page for Monday's meeting. Nothing is sent to the public, so the risk is low and the staff can judge its accuracy every week.

What should a weekly church staff report include? New guests, returning guests, anyone who needs a call and who should make it, messages that have not been answered, and a few consistent numbers such as sign-ups and volunteer gaps. It should end with a short list of decisions to make in the meeting.

Is it safe to let AI read our church's messages? It depends on what you connect. Connect contact forms, connect cards and sign-ups. Keep giving records, private prayer requests, counseling notes and children's medical details out entirely. Ask whoever builds it to state in writing which tools hold your data and who can see it.

How is this different from a report in our church management system? Most systems report on what is inside that system. A staff report pulls from several places at once, including website forms, voicemail and social media messages, matches the same person across them, and highlights what has gone unanswered.

How long does it take to set up? For a church with three or four sources, a few weeks, including a trial period where staff check the report against what they know. Most of the time goes into agreeing on what should and should not appear.

We are a church in North Florida. Can we talk it through? Yes. Surf's Up Social is based in St. Johns County and works with churches across St. Augustine, Jacksonville, Orange Park, Fleming Island and Ponte Vedra. Book a free 30-minute call and we will list every place a message can reach your church today. That list alone is worth the half hour.