# Write every Asana project status update from one desk

> One screen that ranks your projects by how long they have gone without an update, drafts each one for you, and rolls the set into a client-ready doc.

- Workflow type: app
- Services: Asana, Google Docs, Slack Bot
- Categories: Operations, Marketing
- Published: 2026-08-14

## What it does

- Lists every project on the team you pick, one row each, showing the last status update, how many days old it is, the colour it was set to, how many tasks are overdue, how much was finished in the last seven days, and what is due next.
- Sorts the most neglected projects to the top and flags anything that has gone more than fourteen days without an update.
- Opens a drafting panel already filled in from that project's recent activity, so you edit a real starting point instead of a blank box, then posts the update to the project for real.
- Compiles the projects you reviewed into a single client-ready or exec-ready document and drops the link into your Slack channel.

## What you'll need

- An Asana account with the projects you manage, and permission to post status updates on them
- A Google account so the summary document can be created and shared
- A Slack workspace and a channel where the finished document should be posted

## Prompt

Build me a status review desk for the projects I run in Asana. It is the one screen I open each week to write the status update for every project I own, and it should let me get through the whole round in a single sitting instead of clicking into each project separately.

The main view is a list of projects, one row each. At the top I pick the scope: an Asana workspace and optionally a team, loaded with the Asana Get Multiple Projects operation. Important constraint: there is no operation that lists the projects inside a portfolio, so do not design around portfolio membership. Scope the list by team or workspace, then let me narrow it by ticking individual projects into a saved review set.

Each row shows the project name, the latest status update with its author and date (from Get Status Updates), how many days old that update is, the status colour it was last set to rendered as a labelled chip, how many tasks are currently overdue, how many tasks were completed in the last seven days, and what is due next with its date. The task counts come from Get Multiple Tasks scoped by project, reading due dates and completion state; use Get a Task when I open a row and need the full record of a specific task such as the next due one.

Sort the list so the most neglected project sits at the top: age of the last status update first, then overdue task count as the tiebreaker. A project that has never had a status update counts as the most neglected of all. Any project whose last status update is older than fourteen days gets a clear "needs attention" flag on its row, and show a count of flagged projects above the list so I know how much work is ahead of me.

Opening a row slides out a drafting panel that is already filled in from that project's recent task activity, so I am editing a starting point rather than staring at a blank box. The draft should suggest a status colour and cover what was completed in the last seven days, what is overdue and who owns it, what is due next, and any risks the task data implies. Give me an editable body and a status colour picker with the project values on_track, at_risk, off_track, on_hold, complete, and dropped. Posting publishes a real status update on the project using Create a Status Update. Warn me in the confirm step that Asana sends the update to everyone following the project. After posting, refresh that row in place so the age resets and the flag clears, and keep unposted drafts saved per project so nothing is lost if I get pulled away.

Once I have worked through the list, a button compiles the projects I select into one summary document. Create the document with the Google Docs Create Document operation and fill it with Batch Update Document: a heading with the reporting period, a short overall roll-up, then one section per project covering progress, timeline, and risks. This is the outside-facing version meant for a client or an exec, so keep it curated: no internal task-by-task chatter, no assignee-level detail, no task identifiers. Then post the document link to a Slack channel I choose using the Slack Bot Send a Message operation, with a one-line intro naming the period and the projects covered.

Remember my setup per user: the workspace and team I picked, my saved review set of projects, my default Slack channel, and the last summary I exported. The same person should open the same list every week without reconfiguring anything, and two people using the app should each get their own list.

The app should be read-only until I press post or compile. Show when the data was last refreshed with a manual refresh control, and if I lack permission to post on a project, disable that project's post button with a short reason rather than hiding the row.

## How to customize

- Change the fourteen-day mark that decides when a project counts as needing attention
- Pick which team or workspace the list is built from, then save a smaller set of projects as your weekly review list
- Change the sections in the exported document and which Slack channel gets the link

## FAQ

### Does this post a real status update on my Asana projects?

Yes. When you hit post, the update appears on the project exactly as if you had written it in Asana, with the colour you picked. Asana sends it to everyone following that project, so the app asks you to confirm before it goes out.

### Can I review projects from more than one team?

You choose a workspace and optionally a team to build the list from, then tick the specific projects you want in your review set. That saved set can mix any projects you can see, so you are not limited to one team once it is set up.

### Will I get the same list of projects next week?

Yes. Your scope, your saved review set, and your Slack channel are remembered against your own login, so you open the same list every week without setting it up again.

### Do I have to write each update from scratch?

No. Opening a project gives you a draft built from that project's recent activity: what was completed in the last seven days, what is overdue, and what is coming up next. You edit the wording and the colour, then post.

### Is the exported document safe to send to a client?

It is written as the outside-facing version, covering progress, timeline, and risks rather than internal task-by-task chatter. You can read and edit the document in Google Docs before you share it any further.

Use this prompt in General Input: https://www.generalinput.com/prompts/write-every-asana-project-status-update-from-one-desk