The 38 overdue tasks come back in three piles you can clear in ten minutes: finished but not closed, genuinely late, and never a real task. Each with the comment that proves it.
The project has 140 tasks and 38 are past due. About a third were finished weeks ago by people who never came back to tick the box, and two intake forms feed the same board, so “Update the pricing page” exists twice with different owners.
A companion reads every one of the 140 with its comment history, sorts the overdue ones, pairs the duplicates, and shows you the batch before anything changes.
01
What comes back from a 140-task project?
A companion lists the project’s tasks and sections, pulls each overdue item with its comment history, and sorts them into three piles: finished but not closed, genuinely late, and never real in the first place.
Duplicates fall out of the same pass, because text search across the workspace is part of the surface. “Update the pricing page” filed twice under two owners comes back as a pair with both due dates shown. You pick which one survives.
02
How does intake stop producing duplicate tasks?
Requests arrive as email, as a message, as a paragraph in a doc.
A companion reads the request where it lives, searches the workspace for a near-duplicate first, and only then drafts: a name describing the outcome, notes with the real context, a due date, an owner, custom fields.
Then it puts the task in the right section rather than the default bucket. For intake that starts outside Asana, this is the same shape as the operations workflows: read the source, structure it, stage it, let a person approve.
03
Finish the steps that leave Asana
Writing a task from a customer email.
Checking a vendor’s site before closing a procurement task. Pulling numbers out of a spreadsheet into the status update. A companion signed in as you finishes those in the same pass and writes the result back onto the task.
The research workflows are the same motion with a different destination.
04
What it writes, and what waits for you
It creates and updates name, notes, completion, due date, assignee and custom fields, moves a task into a section, comments through Asana stories, and creates or deletes a project.
Asana’s own AI, as of this writing, sits on the full data model inside a single project, including rules, portfolios and goals. The pass above is the one that starts somewhere else and ends on the board.
Yes. Asana is a native integration. A companion lists workspaces and projects, searches and reads tasks, creates and updates them, moves tasks between sections, comments via stories, and lists users. Changes to shared projects wait for your approval.
Yes, and the useful part happens before creation: a companion searches the workspace for a near-duplicate first, then drafts the task with notes, a due date, an assignee and custom fields, and shows it to you before it writes.
Ask for the overdue list split by evidence: closed in fact but not in Asana, genuinely late, or never a real task. A companion reads each task’s comments to make that call, then hands you one batch to approve instead of 38 clicks.
A companion reads freely and stages writes: creating, updating, moving or deleting anything on a shared project asks you first. Deletions are permanent in Asana, which is exactly why they sit behind an approval step.
Both are native integrations, so one companion reads the thread where a decision was actually made and updates the task that depends on it. Download Strawberry free, paid plans start at $20 a month.
Asana Strawberry