Evidence-first diagnosis helps workflow owners correct the cause of stalled work instead of automating around a symptom. You’ll inspect dependency, section, approval, and task evidence, classify the blocker, and compare your diagnosis with a supplied AI recommendation. You’ll decide whether to accept, modify, or reject the proposed fixes, then identify the smallest supported correction. This content reflects Asana as of October 2026. AI Teammates require a supported Asana plan and Asana AI to be enabled for the organization. Availability and usage depend on the organization’s AI configuration and available AI Requests. You do not need live AI Teammate access for the required activities in this module; supplied examples and evidence provide the same analysis and decision-making pathway. You can complete the Asana activities in a supported web browser; no desktop software installation is required.

Deterministic automations are most reliable when a clear trigger should produce a predictable action. You’ll configure assignment, section-movement, and reminder automations, then test normal and exception paths for accuracy and unintended effects. You’ll validate that each automation performs only the bounded workflow step it is designed to handle. This content reflects Asana as of August 2026. Beyond-basic Rule configuration may require a Starter plan with a paid seat. If custom Rule configuration is unavailable in your Asana environment, use the supplied Rule-builder evidence and testing pathway to make the same Rule-design and testing decisions. You can complete the Asana activities in a supported web browser; no desktop software installation is required.

Variable campaign requests require bounded instructions, relevant context, explicit outputs, and representative testing. You’ll specify a smart workflow for request classification, predict expected results, and evaluate supplied outputs against the intended behavior. You’ll identify where the design succeeds and where a focused correction is needed. This content reflects Asana AI as of August 2026. AI Studio is available on Asana Starter, Advanced, Enterprise, and Enterprise+ plans when Asana AI is enabled by an admin. Available capabilities and AI Studio credit limits vary by plan and configuration. Available AI Studio capabilities and usage limits depend on the organization’s plan and AI configuration. You do not need live AI Studio access to complete the required activity in this module. You’ll use supplied configuration examples, request evidence, and outputs to complete the same specification, prediction, and evaluation decisions. You can complete the Asana activities in a supported web browser; no desktop software installation is required.

Automation choices should reflect input structure, variability, judgment, impact, reversibility, and review needs rather than a preference for more AI. You’ll compare automations, AI Studio, AI Teammate handoffs, Dash-informed insight, and human-only handling across campaign workflow steps. You’ll recommend the least-complex suitable treatment and define a proportionate human-review checkpoint. This content reflects Asana AI and Dash as of August 2026. AI Studio is available on supported paid Asana plans when Asana AI is enabled. Available AI Studio capabilities and usage limits depend on the organization’s plan and AI configuration. AI Teammates are available on supported paid Asana plans when Asana AI is enabled for the organization. Access and usage depend on organizational AI settings and available AI Requests. AI-enabled Dash requires supported Asana access and administrator-enabled AI. You do not need live access to these capabilities for the required activity; supplied examples and scenario evidence provide the same comparison and decision-making pathway. You can complete the Asana activities in a supported web browser; no desktop software installation is required.

Reliable AI automation depends on diagnosing observable errors, making narrow revisions, and proving that a change improves behavior without creating regressions. You'll revise instructions or context, define a re-test plan, compare expected outcomes across representative inputs, and establish human-review, data-boundary, approval-log, and release controls. This content reflects Asana AI as of August 2026. AI Studio is available on supported paid Asana plans when Asana AI is enabled. Available AI Studio capabilities and usage limits depend on the organization’s plan and AI configuration. If you do not have access, use the supplied evidence and re-test materials. You can complete the activities in a supported web browser; no desktop software installation is required.

A reliable intake chain connects submitted information to routing, ownership, stage, and status without losing traceability. You'll configure or specify a co-marketing request flow and test normal and exception inputs from submission to final task state. You'll use the test evidence to determine whether the automation is ready or requires correction. The scenario is fixed in August 2026. Forms and custom automations are available on Asana Starter and higher plans, subject to workspace permissions. If the needed features or collaborators are unavailable, use the supplied editable pathway and simulated test records to make the same design and testing decisions. You can complete the Asana activities in a supported web browser; no desktop software installation is required.

Critical campaign alerts need a controlled backup path when one delivery method is not sufficient. You’ll define the fallback condition, recipient, timing, message, and required action, then test both the normal path and a missed-alert path. You’ll determine whether the design preserves continuity without creating duplicate noise or loops. Use the supported Asana features available in your workspace in a web browser. Automation triggers and actions depend on your plan and permissions. If a needed feature or recipient is unavailable, use the supplied configuration pathway and simulated test records to make the same continuity decisions. No paid upgrade, fictional-user invitation, or desktop installation is required.

Conditional intake reduces clarification work by asking every requester for essential information and showing relevant follow-up questions only when needed. You'll translate a social-creative brief into core questions and two branching paths, then test the form with representative requests. You'll validate branch completeness, relevance, and integrity before the form is used for production intake. This content reflects Asana as of August 2026. Forms branching is available on Asana Advanced, Enterprise, and Enterprise+ plans, subject to workspace permissions. If you don't have access to Forms branching, use the supplied editable pathway to complete the equivalent design and testing decisions. You can complete the Asana activities in a supported web browser; no desktop software installation is required.

Complete request data creates value only when routing logic sends work to the correct owner and workflow stage. You'll map asset type, channel, urgency, and campaign context to routing decisions, then test standard and ambiguous requests. You'll correct misrouting or use a controlled fallback before the process goes live. This content reflects Asana as of August 2026. Asana Forms and custom automations require supported workspace access. If a required feature is unavailable, use the supplied worksheet pathway to make and test the same routing decisions. You do not need to upgrade your plan for this activity. You can complete the Asana activities in a supported web browser; no desktop software installation is required.

Shared workflow components reduce drift when teams can distinguish centrally managed standards from legitimate project-specific work. You’ll identify the shared custom fields, automations, and sections that make up a Bundle, compare those components with connected-project evidence, and distinguish central standards from local context. You’ll also classify proposed changes as additive or disruptive and use a pre-change impact review to identify dependencies, communication needs, approval requirements, and rollback or mitigation considerations before a central update moves forward. This content reflects Asana as of August 2026. Bundles are available on Enterprise and Enterprise+ plans. Live Bundle editing requires bundle admin or editor permission. If you don’t have that access, use the supplied Bundle evidence to complete the same impact analysis, validation, and governance decisions. The supplied-evidence pathway is analysis only; no live Bundle configuration is required. Access note: Bundles require an Advanced plan plus workspace-admin access. When that access is unavailable, use supplied Bundle evidence to complete the same impact-analysis, validation, and governance decisions. Do not describe supplied-evidence analysis as live Bundle configuration.

Controlled Bundle rollout requires pre-change impact review and post-change evidence from every connected project. You'll assess risks, make a go or no-go decision, and compare expected and observed field, automation, and section states. You'll document any exception and assign remediation that protects both the shared standard and legitimate local constraints. This content reflects Asana as of August 2026. Bundles are available on Enterprise and Enterprise+ plans. Live Bundle editing requires Bundle admin or editor permission. If you don’t have that access, use the supplied before-and-after Bundle evidence to complete the same rollout validation and remediation decisions. You can complete the Asana activities in a supported web browser; no desktop software installation is required.

An effective intake-to-production workflow connects request capture, routing, automation, review, and governance decisions into one operational process. Starting with a supplied seasonal campaign scenario, you will design an evidence package that shows how work enters the workflow, how requests are routed, where deterministic automations apply, where AI-assisted decisions require review, and how shared standards and fallback controls support reliable execution. You will create seven connected project components: an intake-to-production workflow map, intake and routing evidence, automation configuration and test evidence, an automation decision matrix, a fallback notification design, a Bundle standardization and change-impact analysis, and a governance implementation rationale. Together, these submissions show what should happen, what was tested, what evidence supports the decision, and where human accountability remains necessary. Who this is for: This project is for marketing operations specialists who design, maintain, and govern automated workflows that route campaign work through a marketing team.