How one BC team got a week back every month

Every month, a small BC communications team produced a report. And every month, the report ate the team.

Not the writing. The hunting. The material for the report already existed: in Slack threads, in inboxes, in someone's memory of a project from six weeks ago. Assembling it meant chasing eight people for updates, nudging the ones who forgot, decoding the ones who answered in fragments, then stitching everything into one document after the fact. By the time it was done, the information was stale and the team was cranky. Sound like any recurring report in your life?

The diagnosis took one working session: the team wasn't bad at reporting. The report was bad at collection. It demanded information in a format and moment that suited the document instead of the people.

The prescription was one page: put the collection where the team already lives. So we built them a Slack bot. It knows the reporting calendar, knows who owes what, asks each person for their piece at a sensible time, keeps track of who's answered, and nudges the stragglers so a human never has to be the nag. When the pieces are in, it drafts the report in the team's own voice. A person reviews, edits, approves. Nothing goes anywhere without human eyes.

That approval step matters more than the AI does. The bot is confidently mediocre at knowing what's important; the humans are excellent at it and were just drowning in the fetching. Split the job along that line and both sides get better.

What changed: 35 hours a month back. The team counted it themselves and told us; we didn't ask. That's most of a working week, every month, returned to work someone actually chose to do. Reporting went from a project to a review.

The part worth stealing even if you never hire anyone: the fix contained no exotic technology. It was one boring insight (collect where people already are), one bot, and one rule about human approval. Most of the businesses we look at have a version of this hiding somewhere, a recurring chore that's really a collection problem wearing a deadline. If you can name yours right now, you're closer to fixing it than this team was. Naming it is the first half of our assessment anyway; the second half is putting the fix and its price on one page.