Sign up →
Help Center › Workflow
Workflow

A weekly client status workflow

Use dashboards, reports, and the portal to replace manual status chasing.

The weekly status update is usually rebuilt by hand because the tool the team works in is not the one the client can see. This workflow removes that gap.

Keep the board current as work happens

Status reporting only works if the board is true. Moving tasks when the work actually moves, rather than before a status meeting, is what makes everything downstream trustworthy.

Give the client portal access instead of a status email

A client who can open their portal stops asking for updates. Progress, deliverables, and outstanding decisions are visible without anyone writing a summary.

Review outstanding decisions before the client does

Check what is sitting in Client Review before the client looks. If something has been waiting on you rather than them, fix it first. Arriving at the meeting already knowing that is what makes it short.

Publish a saved report rather than rebuilding one

Use a stored report definition so the same numbers appear every week. Rebuilding a report by hand each week is where inconsistencies enter and where the hour goes.

Send a branded PDF only when it is genuinely needed

Some clients want a document. Export the same governed report as a branded PDF rather than assembling a separate deck, so the sent version and the live version cannot disagree.

What success looks like

  • The client can answer their own status questions, the weekly report is generated from a saved definition rather than rebuilt, and the meeting is about decisions rather than recap.

Common mistakes to avoid

  • Updating the board only in time for the status meeting, which makes it a performance rather than a record.
  • Rebuilding the same report weekly by hand.
  • Sending a deck whose numbers do not match what the client sees in their portal.
Questions

Common questions

It changes what it is for. The recap is already visible, so the meeting can be about decisions and risks.

Both are available on Studio and above.

Need help applying this workflow?

Tell us how your team works and we will help you set this up on a real project.