Ask an admin what they do first on Monday and you’ll hear some version of the same routine. Open the check-in tool. Open giving. Open the email list and the groups spreadsheet. Export two of them, line them up, and try to work out who was new yesterday, who hasn’t been seen in a while, and whether anyone’s gift failed over the weekend.
By the time that’s done, the morning has gone and the list is already out of date. Worse, it depends on one person remembering to look in the right places. When that person is on leave, nobody looks.
The fix isn’t another dashboard. It’s a short list, in the same shape every week, that tells each person on your team who needs them and why. We call it the Monday briefing. This post covers what belongs on it, what doesn’t, and how to run one by hand if you want to start this week.
A week with the briefing in it
Here is a week in an admin’s life, with the briefing at the start of it and the work it sets up through the rest. The line underneath each day is how that job gets done today.
Sunday
After the gathering
Check-ins, gifts and connect cards land on each person’s record as they happen.
Today: A clipboard and a memory.
Monday, 8am
The Monday email
What stood out last week, in a few sentences, with up to three next steps. Then attendance and giving against the four weeks before, and first-time guests.
Today: Open four tools, export, compare.
Monday, 8:10
Who needs you
One list, ranked by who a note would help most: first-time guests, new members not in a group, regulars who haven’t been in, givers who’ve stopped. Each with the reason.
Today: Guess, or wait until someone notices.
Monday, 8:20
Drafts, ready to edit
A short, personal note for each person, written by AI from their record: “you and Carol”, the group that’s missed them. Edit it, then send it by email or as a message in the app.
Today: A blank email, twelve times.
Tuesday
A member asks
“When’s the youth retreat, and what do I bring?” Ask answers from your event page and shows where the answer came from.
Today: The same question in the office inbox, again.
Thursday
A rest week, offered
A volunteer who has served every week for months is on the list, with a note thanking them and offering a week off.
Today: Noticed when they burn out.
Everything after Monday depends on Monday. If the briefing is wrong or too long, the drafts are for the wrong people and the week drifts back to guesswork.
What belongs on the briefing
Four kinds of item earn a place. Each one is about a person or a group, not a number, and each one is something a person on your team can do something about this week.
Who arrived
First-time guests, new members, new sign-ups. Each one with where they came from and what they told you.
Who is drifting
Regulars whose pattern changed. Not everyone who missed a week: people who came every week for months and have stopped.
Which group went quiet
Groups, chapters or teams that stopped meeting, stopped posting or lost their leader.
Which gifts or renewals stopped
Recurring gifts that failed or ended, and memberships coming up for renewal with little activity behind them.
Every item carries three things: who it is, why it’s on the list, and one suggested next step. “Daniel, first visit Sunday, came with his two kids, said he’s new to the area. Next step: a welcome, and the young families group.” If an item can’t be written like that, it isn’t ready for the briefing.
The briefing should also be different for each person. The executive director needs the whole picture. A small group leader needs their own group and nobody else’s. A finance lead needs the stopped gifts and not the care notes. One screen for everyone ends up useful to no one.
What to leave off
The hardest part of a good briefing is what it leaves out. A list that flags everyone gets ignored by the third week.
- Totals that only go up, like all-time member count or page views
- Anything nobody can act on this week
- A flag with no reason attached
- Care notes, for anyone not allowed to read them
- Everyone who missed one week
Totals belong in the monthly board report, where the trend matters. Someone who missed one Sunday is on holiday. Someone who came every week since January and has missed the last five is worth a call. The briefing is for the second person.
Reasons, not scores
Many tools answer “who’s drifting?” with a number: an engagement score of 42, a health rating in amber. The trouble is that nobody on your team can act on 42. They can’t tell what moved it, whether it matters, or what to say when they pick up the phone.
A reason is different. “Came every week until August, has missed the last four Sundays, and her small group stopped meeting in July” tells a staff member what happened, where to check, and what the call is about. They can also look at it and decide it’s fine, because they know she’s caring for her mother this month. A score hides that judgment. A reason invites it.
That’s why our assistant keeps this commitment: Shows its reasons. Every name on the list comes with why it’s there: a first visit, three missed Sundays, a gift that stopped. No unexplained scores. There’s more on this in why a reason beats a score.
Drafts, not automation
Once the briefing has told you who needs you, the next job is writing to them. This is where most of Monday goes: a blank email, twelve times over. It’s also where automation is most tempting and most risky. A welcome that arrives from a robot on Monday morning reads like one.
The better pattern is drafts. The briefing comes with a message already written for each person, using what you know about them. A person reads it, changes what needs changing, and sends it. The member gets a message from someone who looked at their name. Your admin gets their morning back.
Here is the rule the Assistant keeps, word for word:
A reminder about Saturday’s serve day is a fine thing to send automatically once you trust it. A note to someone whose father just died is not, and never will be.
Run one by hand this Monday
You don’t need new software to start. Doing it by hand for a month is the best way to find out what your briefing should hold, and it shows you exactly where your tools don’t share a person.
- Write down the four questions: who arrived, who is drifting, which group went quiet, which gifts or renewals stopped
- For each one, decide which tool holds the answer and who can pull it
- Agree what “drifting” means for your community, in a sentence a new staff member would understand
- Pull the lists on Monday morning, before the staff meeting
- Next to each name, write the reason and one next step
- Give each item one owner. An item with two owners has none
- Next Monday, start by checking what happened to last week’s items
The third step matters most. If you can’t say what drifting means in one sentence, no tool can flag it for you. The member journey guide walks through naming the stages and the evidence for each, which is where those definitions come from.
Where the assistant fits
When every visit, gift, group and sign-up lands on one member record, the briefing stops being a Monday project. The Assistant tells your team who needs them this week and why, and drafts a note for each person. Your team edits it and sends it.
The Monday briefing is part of the Community plan, one for each staff member and each leader, with the drafts that follow it. The Assistant drafts and your team decides what’s sent. Every name comes with a reason, and nothing it reads is used to train AI models. The Assistant is included in the Community plan and above, with no separate AI bill.
The AI Assistant page lists everything it does, which plan each part is in, and the full set of commitments it keeps.