The weekly reporting cadence that ends "how are we doing?"

A reporting cadence earns trust the first time someone pushes back on it. On the Saturday before this week, the client's founder replied to the monthly lead report. The "leads assigned" figure said 462, out of roughly two thousand leads. That looked wrong to him, and he said so, politely and in writing.

The reply was posted into the shared Slack channel on Monday and worked in a thread, five replies long, until the calculation was explained and the tick went on. That is the whole point of reporting on a schedule. The question landed on a number everyone could see, instead of turning into a meeting about what the numbers even are.

Requests travel the same road. When the client asks for a change, someone types "raise a ticket here" and a bot logs it to the task board and posts the ticket back into the channel, like the one below. Two weeks earlier, a request about how dead-end leads get marked became a tracked ticket the same evening it was raised. It shows up again in this week's Friday report. Chat is where things surface; the board is where they live.

On Monday morning, before the workday started, the week's schedule landed in the client's inbox. Every meeting booked for 3 to 9 August, who is running it, the client on the other side, and the borrowing-capacity position behind each one. The subject line carries the week and the count.

Nobody assembled it. A workflow reads the tracker the team already keeps, shapes it into the same table every time, and emails the people who run those meetings. When bookings move, the report sends again with an updated count. The second row in this list is exactly that. Monday's thirteen meetings became Tuesday's nineteen. The report is there before the week's first check-in call, so the call can be about decisions instead of collecting numbers.

On Thursday, the client's operations coordinator sent her testing notes on the notification work. The verdict, verbatim. "All good on the received email notifications. No duplicate emails were received and the generated lists are correct."

This is what the cadence is for. The reports do not just arrive. The people they serve check the machinery and sign off its behaviour in writing.

Monday showed what was scheduled. Friday shows what happened. The status document for the week appears in the client's shared Drive folder, on a Friday schedule so consistent that the folder's timestamps agree to the second. Seventy-one dated reports span the last year and a half.

The shape never changes. Focus This Week. In Review. Key Wins. Next Week. The delivery team owns the words inside it, which is the part that should never be automated. Machines are good at collecting the week. Deciding what it meant is a human job.

Late on Friday afternoon, four more emails closed the week, one for each pipeline. Discovery, 35 meetings. Strategy, 16. Property Macro, 18. EOI, 5. The meetings the week opened with now carry outcomes, and nobody compiled anything by hand.

There is no exotic platform under any of this. The client's tools stay where they are. An n8n instance on their own infrastructure reads from them on a schedule. Monday and Thursday for the meeting reports, daily for the lead counts. It shapes the data, sends the emails, and logs every run to a health tracker that a human actually checks. The Friday status document keeps the same weekly rhythm in the shared folder. The document above is the evidence for it, exactly as the client reads it.

This is the workflow that sends the Monday report. A schedule trigger, a sheet read, a formatting step, a Gmail send, and a logging tail. Two deactivated nodes are still parked on the canvas from an earlier version. Real systems look like this.

It is not flawless, and that is worth saying out loud. When we took these screenshots, the instance's own dashboard counted 2,504 successful runs against 322 failed ones across every workflow it hosts, not just the reporting ones. The difference between automation you trust and automation you babysit is not a zero failure rate. It is that failures land in front of a human instead of hiding.