To draft a weekly client report with Asana AI, start a status update in the project, choose the AI draft (Smart Status) for the past seven days, then edit before sending: fix the status colour, remove internal names and costs, add figures it cannot see and check every date. It needs Starter or above.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowThe catch most owners hit in week one is sharing, not writing. Posting a status update notifies everyone in the project, and Asana's community team confirmed in October 2026 that you can't hide an update from some project members. So decide where each version lives before you draft: the internal version stays in the working project, which no client should be a member of, and the client version goes out by email or into a separate client-facing project.
What does Asana's AI draft read from your project?
Asana's AI draft reads the work already recorded in the project, such as task names, what was completed, due dates and what is overdue. Smart Status is Asana's name for AI-generated status updates. Asana describes the drafts as flagging open questions, roadblocks and next steps, and the same drafting option works for portfolios and goals as well as projects. Portfolio drafts need the Advanced plan or higher, because portfolios themselves start at Advanced.
Three limits matter for a client report, and all three come from what the draft does not see:
- Project custom fields. Users on Asana's community forum reported in May 2026 that the status draft did not see the project's fields, and an Asana partner replied that he had raised it with Asana and been told it was expected behaviour. Another user complained in November 2026 that it missed task completion dates. If your contract value, percentage complete or variation total lives in a custom field, you add it by hand.
- Anything that never went into Asana. A phone call with the client's facilities manager, a delivery rescheduled by text, a decision made on site: none of it reaches the draft unless someone recorded it in the project.
- Very large projects. A July 2026 forum thread reported subtasks missing from drafts. The suggested explanation was context size, so on a project with hundreds of tasks the draft may skip detail. Splitting a large job into phase projects helps.
The cost side is simpler than most Asana AI features. Asana's community team listed Smart Status and Smart Summaries among the things that do not use an AI request, which means drafting a weekly update every Friday costs nothing beyond the plan. The plan does matter: Asana AI is not on the free Personal plan. Starter is $10.99 per user per month billed annually or $13.49 billed monthly; Advanced is $24.99 or $30.49.
A ten-week office fit-out, reported every Friday
Here's how this plays out for an illustrative nine-person electrical contractor fitting out two floors of offices for a commercial client over ten weeks. The project in Asana has 64 tasks in five sections (Containment, First fix, Second fix, Testing and Handover). Week six has just finished: 11 tasks were completed, two are overdue, and the client owes one decision.
A quick sum on the plan first. Asana sells seats in steps of five once a team passes five users, so nine people need a ten-seat Starter plan: 10 x $10.99 = $109.90 a month on annual billing, or $134.90 a month billed monthly. The weekly report adds nothing to that.
Before the AI draft, the contracts manager spent about 75 minutes each Friday reading through the project and writing an email. The target with the draft is 20 to 25 minutes: two minutes to generate, fifteen to edit, five to send. Those times are illustrative; measure your own for three weeks before deciding whether it worked.
The guidance typed into the draft
Asana lets you add guidance before it drafts (the portfolio and goal version shows it as + Add guidance). Treat that box like a short brief. The contracts manager uses this:
Cover Monday 10 to Friday 14 November only.
Reader: the client's facilities manager, not our site team.
Sections: Summary (two sentences), Done this week, Planned next week,
Needs your decision (with a date), Risks to the programme.
Use plain words, no task codes, no staff or subcontractor names,
no costs or margins, no blame.
Keep it under 250 words.
What came back (illustrative)
Status: On track. The project progressed well this week with 11 tasks completed across First fix and Second fix. Containment on level 2 is complete. Second fix has started on level 1.
Blockers: Fire alarm cable delivery is overdue. "Dave to agree riser access with plasterers" is overdue. Emergency lighting fittings awaiting selection.
Next steps: Continue second fix on level 1, begin testing on level 2.
Most of that is accurate and none of it is ready to send. "On track" is the colour the contracts manager picked out of habit, while two overdue tasks sit on the critical path. A site engineer's first name appears, copied straight from a task title. The fire alarm cable sentence is true but gives the client nothing to do. "Begin testing on level 2" can't happen until the fire alarm cable arrives, which the draft didn't connect. And the variation the client approved on Tuesday, worth an illustrative $3,400 and recorded in a custom field, is missing entirely.
The version the client received
Status: At risk (programme), budget unchanged. Week 6 of 10. Level 2 containment is finished and second fix has started on level 1, so overall we are about 60% complete.
Done this week: 11 items, including level 2 containment and level 1 first-fix sign-off.
Needs your decision by Wednesday 19 November: choose between the two emergency lighting fittings we sent on 7 November. After that date the supplier's lead time pushes testing into week 9.
Risks: the fire alarm cable delivery is three days late, with a new date of Tuesday 18 November. Riser access is shared with the plastering contractor; your project manager's help in agreeing a slot this week would protect the week 8 testing date.
Variations: one approved this week (additional floor boxes, $3,400). Running total: $5,150.
Every change came from the edit pass in the next section. The draft saved the sorting and counting; the person who knows the job supplied judgement, numbers and the client's next action.
What should you edit before the Asana report goes to the client?
Eight edits catch what Asana's AI draft gets wrong, and running them in the same order every week takes about fifteen minutes once the habit sets.
| Check | Why the draft gets it wrong | How to fix it |
|---|---|---|
| 1. Status colour | Asana uses the status you pick (On track, At risk, Off track, On hold or Complete) and can suggest one, but it doesn't know which overdue task is on your critical path | Pick it last, after reading the overdue list. Split it if needed: "At risk (programme), budget unchanged" |
| 2. Every date | Due dates in Asana drift; a task moved in the system may not match what you told the client | Check each date against your programme or the last email to the client |
| 3. "Complete" versus signed off | A ticked task means someone clicked done, not that an inspector or the client accepted it | Use the client's word for finished: tested, certified, handed over |
| 4. Names | Task titles and notes carry staff and subcontractor names, and occasionally a frustrated remark | Remove first names; refer to trades and roles |
| 5. Internal money | Cost notes in task names or descriptions can leak margin | Delete costs unless they are client-facing figures such as approved variations |
| 6. Missing figures | Custom fields such as percentage complete or variation value were reported as unseen by the draft | Add them by hand from the fields or your dashboard |
| 7. Client actions | Blockers are written as facts, not requests | Turn each into "Needs your decision by [date]" with the consequence if it slips |
| 8. Links | Links to Asana tasks only open for people with access to the project | Replace task links with attachments or plain descriptions |
Two of these checks catch most of the embarrassing errors: names (4) and links (8). A client clicking a link that asks them to log in to Asana is a small thing, but it signals the report was pasted, not written for them.
How do you send the client report without exposing the internal project?
Keep the client out of the internal project: paste the edited report into an email, or post it in a separate client-facing project, because anyone with access to a project sees its status updates.
Asana gives you three realistic routes, and the right one depends on how much of your project you want a client to see.
Route 1: paste the edited text into an email
This works on any paid plan and shows the client nothing else. Post the internal version inside the project for your team, then paste the edited client version into an email from your normal inbox. The weakness is record-keeping: the client version lives in email, not Asana. Fix that by attaching a copy of the sent email to a recurring "Weekly client report" task in the project.
Route 2: a separate client-facing project with the client as a guest
Starter and above include unlimited free guests, so a client contact doesn't cost a seat. Create a second, small project holding only milestones and the decisions you need from the client, invite the client as a guest, and post the client version of the status update there. Asana's community team was clear that anyone with project access sees its status updates and that viewer access limits editing, not viewing, so never invite a client into the working project. Starter also includes comment-only projects, which suits a client who should reply but not edit.
Route 3: Asana Client Management's client portal
Asana now sells a separate product for agencies and service firms, Asana Client Management. Its Advanced plan ($24.99 per user per month billed annually) includes a client portal that Asana describes as a branded space for project status, deliverable reviews, feedback and approvals, where account managers control what clients see. Clients use the portal without taking a seat. Its Starter plan ($10.99) has a client directory but no portal. It also comes with an Account Advisor AI Teammate that Asana says drafts client status updates. For a contractor sending one report a week, routes 1 or 2 usually do; the portal earns its place when clients also review drawings or approve variations online.
If you'd like a reusable layout for the client version itself, the client project status report template with RAG ratings pairs well with any of the three routes.
How do you set a Friday rhythm so the AI draft has good data?
Keep the project tidy before Friday, because the quality of Asana's AI draft depends on how tidy the project is at 9am on Friday. Four habits make the biggest difference:
- Thursday close-out (10 minutes, site lead). Tick off finished tasks, move any task whose date has genuinely changed, and leave a one-line comment on anything blocked saying what it's waiting for.
- A status update reminder. Asana can remind the project owner the day before an update is due, so set the cadence to weekly, due Friday.
- A saved layout. Asana lets you save your custom sections and reuse them for the next update. Save the five sections from the guidance above so the internal and client versions keep the same shape.
- One owner. The person who sends the report owns the edit. Splitting writing and checking between two people sounds safer and usually means neither reads the dates.
Asana also announced scheduled rule triggers on its community forum in January 2026, including an action that drafts a status update with AI on a regular cadence and, according to that announcement, doesn't use AI Studio credits. Asana rebuilt rules as "automations" with a new builder in October 2026, so check that the action is available in your project's builder (Customize, then Automations) before relying on it. Even when it works, it produces a draft; the eight edits still happen before the client sees anything. If you are new to the builder, start with five starter automation rules for a small team.
If you want help fitting this into how your team actually runs, I offer one-to-one AI consultations for small businesses.
Where does the Asana AI draft go wrong?
Asana's AI draft goes wrong when it lacks a date range or cannot see project custom fields, as in these realistic failures from the same illustrative fit-out, each caught by one of the eight checks:
- Week 3: the wrong week. Nobody set a date range or guidance, and the draft summarised the project since kick-off. The client received a report repeating week 1 work as news. Fix: the date line is always the first line of the guidance.
- Week 4: "Testing complete on level 1." The tester ticked the task when the readings were taken, before the certificate was issued. The client forwarded the report to their insurer. Fix: check 3, and a task name that says "Certificate issued" rather than "Testing".
- Week 5: a frustrated task title quoted. A task titled after another contractor's mess was summarised as a blocker with the trade named. Fix: check 4, and a site rule that complaints go in a private task, not the shared project.
- Week 7: nothing about the variation. The approved variation lived in a custom field and the draft ignored it, as users have reported. Fix: check 6, and a dashboard chart for variation totals that you read before writing.
When does a teammate or Dash suit the job better than Smart Status?
Smart Status suits one project, one week and one reader; Dash or an AI Teammate suit other jobs, at the cost of AI requests. Two other Asana options exist, and both cost AI requests: each paid plan includes 5 requests per user per month, capped at 50 per account on Starter and Advanced, and extra requests cost $0.50 each prepaid or $0.60 on pay as you go.
- Asana Dash, available from Starter as a chat assistant, can draft status updates and summaries. Asana says Dash only uses a request for complex work such as long-form writing, web search, integrations or handing work to a teammate.
- An AI Teammate reads task fields that the status draft was reported to miss. An Asana partner on the forum suggested exactly that in November 2026: ask a teammate to write the update so it reads the fields and posts a draft for review. Asana's own suggestion for updating people without giving them project access was similar: have a teammate write the update in a task and assign review subtasks. Each successful run uses one request, so a weekly report is about four or five requests a month. The AI Teammates tutorial on meeting prep and follow-ups covers the setup.
If several projects feed one client, a portfolio-level draft on Advanced or a general assistant such as ChatGPT working from an export can be simpler; weekly status reports in ChatGPT from your task list shows that route.
What should you check about client data in Asana AI?
Check once whether your client contracts allow AI drafts before you run them on client projects, and read Asana's position first. Asana says its AI partners, which include OpenAI and Anthropic, don't use customer data to train their models and are required to delete it after each query, and that Asana AI works within each user's existing permissions. A super admin controls whether AI is on, and admins in an organisation without a super admin can turn AI features off but not back on. If a client contract restricts where their information is processed, raise it before the first draft, not after. The Asana AI privacy and admin controls tutorial goes through the settings.
How do you tell after a month whether Asana AI is working?
Tell whether Asana AI is working by keeping a simple four-week log in a task description with four numbers per week:
- Minutes from draft to send. Target: under 25. If it stays above 40, the project data is the problem, not the AI; tighten the Thursday close-out.
- Edits per report. Count changed sentences. A falling count means the guidance is doing its job.
- Client questions after the report. If the facilities manager still phones to ask "so are we on for handover?", the summary isn't answering the question they care about. Put the handover date in the first sentence.
- Corrections sent after the report. Any correction email is a failed check. Note which of the eight it was and move that check earlier.
An illustrative month for the fit-out: 72, 31, 24 and 21 minutes; edits falling from 14 to 6; one correction (the week 4 testing slip). Against 75 minutes a week before, that's roughly three hours saved over the month, plus a client who stopped chasing for updates, which is the part they notice.
If you keep the four-week log in a spreadsheet, try The Complete Excel Course with AI Integration on Coding Liquids.
Questions owners ask about Asana's AI status drafts
Does drafting a status update with Asana AI use up AI requests?
Probably not. Asana's community team said in October 2026 that Smart Status and Smart Summaries don't use a request, and Asana's pricing page lists AI assistance in projects and tasks as included on every paid plan. AI requests are spent by AI Teammates and by the heavier work Asana Dash does, such as long-form writing or handing a job to a teammate, so switching from Smart Status to a teammate changes the cost. Check your request usage in the admin console after the first few drafts.
Can I hide a status update from a client who is a guest on the project?
Not selectively. Asana's community team says anyone with access to a project sees its status updates, and viewer access limits editing, not viewing. Keep the client in a separate client-facing project, or send the edited report by email instead of posting it where they can read it.
Does Smart Status work on the free Personal plan?
No. Status updates themselves are on every Asana plan, including Personal, but Asana's AI features start at Starter, which costs $10.99 per user per month billed annually or $13.49 billed monthly. A two-person team on Personal can still post manual updates with the same structure.
Can Asana draft the weekly update automatically on a schedule?
Asana announced scheduled rule triggers in January 2026, with an action that drafts a status update with AI on a regular cadence. Asana rebuilt rules as automations in October 2026, so check that the action appears in your builder before you rely on it, and keep the human edit step either way.
How do I draft a weekly client status update with Asana AI?
Open the project, start a new status update and choose the AI draft (Smart Status), telling it to cover the past seven days. Then edit it: correct the status colour, delete internal names and costs, add figures the draft cannot see and check every date. Send the edited version by email or from a separate client-facing project, not from the working project.
Further reads
- How Can Account Managers Use AI for Updates and Call Prep? — How an agency turns weekly updates into calmer client calls.
- How Can AI Help Project Delivery? Status Reports, Risks, Handovers — Where AI helps across delivery: status, risks and handovers.
- How Much Does Asana AI Studio Cost? Credits per Plan — Calculate a team's monthly AI Studio credits and AI requests before choosing Asana Starter, Advanced or an add-on.
- How to Set Up an Asana Intake Form That Routes Requests With AI — A roofing firm's Asana intake form, field by field: routing rules, an AI triage rule, response targets, spam checks and a 12-submission test.
Browse all AI-for-business tutorials
Sources: Asana pricing and Client Management pricing pages; Asana status updates, AI and AI Teammates product pages; Asana Help Center article on Smart Status; Asana community forum Q&A from the Q3 2026 release webinar, October 2026 release notes, the January 2026 scheduled triggers announcement and user threads on AI status drafts (all checked 17 November 2026).
