The Monday briefing: what your admin should see first each week

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 vacation, nobody looks.

What helps is 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 under each day is how that job usually gets done today.

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 probably on vacation. Someone who came every week since January and has missed the last five is worth a call. The briefing is for the second person.

Why a reason works better than a score

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 gives them something to work with. “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 kind of judgment, and a reason invites it.

That’s why our assistant keeps this commitment. Shows its reasons. Every flag says why, and links to the records behind it. No unexplained scores. There’s more on this in why a reason beats a score.

Drafts that a person sends

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, in your organization’s voice, using what you know about them. Someone on your team 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 we build to, 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.

1. Write down the four questions: who arrived, who is drifting, which group went quiet, which gifts or renewals stopped
2. For each one, decide which tool holds the answer and who can pull it
3. Agree what “drifting” means for your community, in a sentence a new staff member would understand
4. Pull the lists on Monday morning, before the staff meeting
5. Next to each name, write the reason and one next step
6. Give each item one owner. An item with two owners has none
7. 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 in one place for everyone, on the same person, the briefing stops being a Monday project. A built-in AI assistant tells your team who needs them this week, and why, and drafts the next step. Your team decides.

We build the Monday briefing into the Community tier, one for each staff member and each leader, with the drafts that follow it. Your assistant runs in your cloud, on your own data, under your own account. It sees only what the person asking may see, never trains anyone’s model on your members, and drafts rather than sends. AI usage is paid to your own provider at cost, like hosting, with no markup and no platform fee. We estimate it in your scope.

The AI Assistant page lists everything it does, which tier each part is in, and the full set of commitments it keeps. If you’d like to see how it would work for your team, Book a 30-minute call.

Further reading: what the assistant does, and the rules it keeps, why a reason beats a score, and AI and your member data: eight questions to ask any vendor.