Skip to content
ToolDeck

Agency & Client Ops

Client Project Status Digest

A Friday digest of every client project's status, blockers, and next steps.

Saves about ~1 hr per week

What it does

  • Pulls project status from your PM tool
  • Summarizes progress, blockers, and next steps
  • Posts a Friday digest to Slack
  • Flags projects that haven't moved this week

How it works

  1. Project status pulled from Notion/PM tool
  2. AI writes the digest summary
  3. Friday 5pm Slack post
  4. Stalled projects flagged

What's included

  • PM tool connection
  • Digest prompt
  • Friday schedule

Set it up yourself

Follow these 4 steps in order. You will need accounts for: Slack, Notion.

Step 1: Connect your PM tool

  1. Create the internal integration (Notion: internal integration token, ⋯ → Connections on the database).
  2. Give it read access to the projects database.
  3. Ensure each project row has: Status, Client, Updated On, Blockers (optional).
  4. Test a query returns the projects.
  5. Note the databases' property names exactly.

Watch out: Property-name consistency is the trap — the flow reads 'Updated On' by name; if a project row uses a different date property it silently reads empty.

Step 2: Add the summary prompt

  1. Build: 'Summarize this projects list. For each: status, key progress, blocker (or none), next step. Flag any project with no update in 7 days. Keep it scannable.'
  2. Instruct: no invented progress.
  3. Paste with API key.
  4. Test on one week's data.
  5. Tighten if the summary is too long for a digest.

Watch out: 'No invented progress' again — a digest line 'client launch complete' when it isn't creates panic and erodes trust.

Step 3: Set the Friday schedule

  1. Create the Slack webhook for the channel (e.g. #projects).
  2. Schedule the flow Friday 5pm.
  3. Post the digest to Slack.
  4. Post stall flags as a separate short line.
  5. Test the timing once.

Watch out: Send after the team's last update of the week — a Friday 5pm digest misses Thursday-night updates and reads stale.

Step 4: Add the stall rule

  1. Compute days-since-update per project from the Updated On date.
  2. Flag any project idle 7+ days.
  3. In the digest, list stalled projects as 'needs a poke'.
  4. Test with a deliberately stale project.
  5. Use the flags to follow up with owners on Monday.

Watch out: The stall flag is the operational value: a Friday summary of statuses is a report; the stall flag is the thing that prompts an actual action.

Frequently asked questions

What does the Client Project Status Digest automation do?

A Friday digest of every client project's status, blockers, and next steps. Pulls project status from your PM tool

How much time does Client Project Status Digest save?

It is estimated to save ~1 hr per week. Actual savings depend on your volume.

Which tools does Client Project Status Digest use?

It works with Slack and Notion.

What does Client Project Status Digest include?

PM tool connection, Digest prompt, Friday schedule.

Can I set up Client Project Status Digest myself?

Yes. The do-it-yourself guide on this page walks through 4 steps, from getting access to testing the finished automation.