Launch vs Asana

A campaign is the durable object in Launch. It owns the assets, systems, requirements, approvals, and history attached to it. The same object carries the campaign from scan to go-live.

Asana organizes work into tasks, projects, and portfolios. An approval is a kind of task. Rules act on tasks within a project.

Preflight is an automated test a campaign must pass before it is allowed to go live. It covers twenty-one requirements in six groups. No person can mark a requirement complete.

Asana rules trigger actions on tasks, such as moving a task or assigning it. Approvers then decide by hand: Approve, Request changes, or Reject.

Launch asks for two approvals, always in the same order: brand, then legal. People approve. Launch records who approved, against which rule version. A committed launch is read only for everyone but the current approver.

In Asana, the requester sets the approval status to Ready for Review and assigns the approver. The approver sets it to Approved or Changes Needed and reassigns the task. Feedback on images and PDFs uses proofing comments.

Launch rules cover brand, language, claims, legal, and accessibility. Rules are versioned. Every evaluation names the version that produced it. Exceptions are scoped, owned, tied to a rule version, and time bound.

Asana calls its automation Rules. They work on tasks within a project, and rule actions appear in the task activity feed and in a rule activity log.

Scan checks what is live across a company’s public web presence and connected systems. A domain scan needs no account and no credentials. A team can see how live assets differ from what was approved.

Asana’s API lets scripts read information from inside Asana and react when things change. Webhooks deliver a list of events to an endpoint, and Asana says most arrive within ten minutes.

Every Launch integration is read only, except Slack messaging, which the customer enables. Scan and Preflight read from connected systems. See the integrations page for what is connected today.

Asana offers an API and webhooks. Its documentation lists staying in sync with software such as Slack or Salesforce, and rules can receive incoming web requests.

Every action is written to an append-only log with the actor and a timestamp. Minimum retention is two years. Exports are logged under the exporting user.

Asana describes its audit log as an immutable log of important events in an organization. The audit log API is limited to Service Accounts on Enterprise+ and legacy Enterprise, or to Enterprise domains with the Compliance Management add-on.

Approvals belong to named people. Launch records who acted and when. Read the Launch security page for current controls. This page states no certification.

Asana approvals are assigned to a chosen approver on a task. Confirm current security controls and certifications in Asana’s own documentation.

Scan checks and Preflight evaluates without anyone asking. People decide, and people fix content where it lives. Launch reports; it does not change your systems.

Asana rules automate routine work on tasks in a project. They can connect to other tools through pre-built apps, and they can receive webhook triggers from other tools.