WORKFLOWS / PROJECTS AND CHANGE
Work out what a change will affect.
Before changing a date, deliverable, or working arrangement, identify the affected work and prepare the decisions and updates that need to follow.
WHAT THIS WORKFLOW PRODUCES
A change review with specific next actions.
One place to see what is changing, what might be affected, and whose agreement is needed. Keep confirmed consequences separate from questions that still need an owner to answer. In the example below, a linked task suggests something to investigate; it does not automatically mean the task should move.
MOVE THE CUSTOMER LAUNCH BY ONE WEEK
ILLUSTRATIVE PROPOSAL · NOT YET AGREED
THE OPERATING METHOD
Understand the workflow without AI.
Write down the proposed change before discussing its consequences. Work out what depends on it, ask the right people, and update the agreed commitments together. AI is introduced only after the method makes sense on its own.
Define the change
Record the current agreement and the proposed replacement.
YOUTrace the effects
Check linked work, commitments, documents, and dates.
YOUCheck with owners
Confirm what changes and what can stay as it is.
YOUChoose an approach
Agree on the change, an alternative, or a smaller scope.
YOUUpdate and communicate
Amend the relevant records and tell the affected people.
YOUFinish with the agreed changes recorded where people do the work. A review document alone does not change anyone's commitment.
WHERE THE FACTS LIVE
Use the systems where the work already lives.
Select a bounded set of projects and reference material. You do not need to connect every company system to review one change. Named tools link to their pages in the library.
WORK AND DEPENDENCIES
Tasks, milestones, linked work, owners, and comments.
PEOPLE AND TIMING
Relevant meetings, owner replies, and availability.
THREE WAYS TO RUN IT
Choose how much machine.
The useful progression is from thinking through one change to investigating its records, then coordinating a repeatable review. None of the versions should silently reschedule a project. The tools named are examples. Use what your organization already runs, provided the connection is supported and approved.
LEVEL 1
Check the possible consequences.
Give AI the old agreement, the proposed change, and the known commitments. It prepares a short impact review and questions for the people who can confirm the consequences.
Use this version when you need a second pass before accepting a deadline, scope, or ownership change.
WHAT THIS VERSION REDUCES
Missing an obvious affected area or sending a vague "any concerns?" message.
WHAT A PERSON STILL DOES
Which consequences matter and whose agreement is necessary.
MAIN LIMITATION
Possible consequences are suggestions to check rather than established facts.
Build this version, step by step 4 steps, one action each. Prompts carry a Copy button.
Write the change down in one line: what it is now, what it would become.
BEFORE AND AFTER
For example: the launch moves from 12 October to 19 October. Include the current date, owner, deliverable, or arrangement and the proposed replacement, and the reason if you know it.
List the commitments that already exist around it.
KNOWN DEPENDENCIES
The milestones, the teams affected, the promises already made to customers or partners, and anything that must not move.
Ask for an impact review.
Review this proposed change. Separate confirmed effects from possible effects and missing information. For each material uncertainty, name the question an owner needs to answer. Do not assume every related task needs to move.
Get the owners to answer, then decide.
THE CHECK
- Every important question has an answer from the person who owns that piece of work.
- The updates the AI drafted match what was agreed.
LEVEL 2
Inspect the connected work.
Connect the AI assistant to the project system and approved reference files. Have it inspect linked tasks and their context, then explain the specific evidence behind each proposed follow-up.
Use this version when consequences are spread across task comments, project documents, and several people's work.
WHAT THIS VERSION REDUCES
Opening multiple records and comparing them with the proposed change.
WHAT A PERSON STILL DOES
Whether the records are current and which affected owners must be consulted.
MAIN LIMITATION
Undocumented dependencies and offline promises will not reliably appear in a connected search.
CONNECTION NOTE
Connected calendars can reveal scheduled events within the account's permissions. They do not establish workload, contractual flexibility, or a person's agreement to a new deadline.
Build this version, step by step 5 steps, one action each. Prompts carry a Copy button.
Tell the AI where it may look.
NAMED PROJECT
Name the affected project, the linked work you know about, and the reference documents that matter. Unrelated projects and private conversations stay out.
Have it read the tasks themselves and their comments.
TASKS AND CONTEXT
Through Asana's official AI connection, it reads the task details and comments and follows the links between tasks. Where the connection cannot reach something, give it that record by hand and note the gap.
Ask for a source beside every effect.
LINK AND REASON
Each line names the item affected, where the AI found it, what could happen, and what still needs confirming. Anything unrelated stays off the list.
Get the owners' answers.
THE CHECK
- Each owner has been asked a specific question about their piece.
- A deadline that looked fixed may have room, and a dependency may already be gone.
Ask for the exact edits and the message.
BEFORE AND AFTER
The AI drafts the task changes and a short message to the people affected. Read the edits before any of them are applied.
CAPABILITIES CHECKED AGAINST OFFICIAL DOCUMENTATION
Asana's MCP tools reference documents task context, retrieval, search, and actions; it does not promise a complete company-wide dependency map. Source, checked September 6, 2026.
Asana's API documents retrieval of a task's specified dependencies; the direction of the relationship matters. Source, checked September 6, 2026.
LEVEL 3
Run an agent-assisted change review.
Mark a change request ready for review. A configured agent retrieves the relevant records, identifies unresolved effects, and drafts a versioned change plan. Approved updates are applied through separate, controlled actions.
Use this version when launches, client projects, or cross-team initiatives repeatedly change and the same review work is being redone.
WHAT THIS VERSION REDUCES
Repeated investigation and assembling a coordinated set of proposed changes.
WHAT A PERSON STILL DOES
Trade-offs, material risk, external commitments, and authorization to change the plan.
MAIN LIMITATION
An agent cannot guarantee complete impact coverage. Maintain an explicit list of the sources checked and owners consulted.
TOOL OPTIONS
Make can coordinate a cross-app review, and n8n runs the same shape with its agent node; Make's agent product is in open beta. For changes contained in Asana, AI Studio and a review task cover the same steps without a separate connector. A connected AI chat is usually enough for infrequent changes.
DO NOT DEPEND ON NOTIFICATIONS
Do not make an entire project depend on receiving every change notification. Event delivery can be incomplete. An explicit review request and a check of pending reviews make the process easier to supervise.
Build this version, step by step 6 steps, one action each. Prompts carry a Copy button.
Record the change as a request in the project.
ONE CHANGE ID
The record holds the before, the after, the reason, the project affected, and who decides. The review starts only when someone marks the record ready.
Give the agent a fenced area to investigate.
ALLOWED RECORDS
Through Make or n8n, hand it the current project, the linked records, and the chosen documents. Say how far it may follow links and when it has to stop and ask.
Let it prepare the questions and a proposed plan.
CONFIRMED OR UNRESOLVED
The agent decides which records to inspect next within that fence, then produces a list of effects with sources and a specific question for each owner. A person checks the questions. Each one goes to its owner as a task marked "Needs answer"; when the owner sets it to "Ready", the run picks up again from here with the answer. Nothing waits on a notification.
Write down the exact edits and get them approved.
APPROVED VERSION
Store each proposed change with the record it targets, the old value, and the new value. The approval step refers to that exact version.
Check that nothing moved in the meantime.
THE CHECK
- Every affected record is read again right before it is updated.
- If a value no longer matches the approved version, the run stops and asks for another review.
Apply the edits one at a time and confirm each.
COMPLETED OR NEEDS ATTENTION
The agent applies the approved edits one by one and saves the result of each. If one fails, it shows what was done so far and alerts the owner. It reports completion only after re-reading the updated records.
CAPABILITIES CHECKED AGAINST OFFICIAL DOCUMENTATION
Asana's events documentation records the limits of event delivery. Source, checked September 6, 2026.
Make's Asana integration documents project and task operations for configured workflows. Source, checked September 6, 2026.
Make AI Agents can use tools inside a scenario; the agent product is documented as open beta. Source, checked September 6, 2026.
n8n documents a tool-using agent node as an alternative orchestration approach. Source, checked September 6, 2026.
Asana AI Studio documents human approval checkpoints as a native alternative. Source, checked September 6, 2026.
WORKS EVEN BETTER WITH
Keep the approved change on record. If it creates new work or moves responsibility, follow through with a clear scope or handover.
Decision Log → | Turn a vague request into a workable project → | Prepare a handover someone can use →