Skip to content

Migrating from monday.com or Asana approvals to DueReason

monday.com and Asana sell approvals only as an add-on inside work-management plans. See what one approval step gains from a signed grant.

Updated · 7 min read

In short

  • monday.com adds approvals through the AppFox marketplace add-on, and Asana ships them natively on its Advanced and Enterprise tiers - in both cases as a feature of a broader work-management suite, not a standalone product, priced only as part of the parent plan's per-seat pricing.
  • Approving a status or a step there still means a task or item marked approved inside that tool's own board - not a signed, independently verifiable object another system can check before it acts.
  • DueReason does not replace monday.com's boards or Asana's projects and tasks - it answers the one approval question a step asks, with a signed grant, a hash-chained ledger and an agent-native surface behind the answer.
  • Moving one approval step over does not mean moving the whole board: keep monday.com or Asana for the work you track there, and add DueReason for the one decision that needs a record someone else can verify.

If your team tracks work in monday.com or Asana and has bolted an approval step onto a board or project - a status column, a custom field, or (on monday.com) the AppFox approvals add-on - this walks through what that approval step does today, and what changes if you move just that one step to DueReason.

What monday.com and Asana do today

monday.com and Asana are both work-management platforms built around boards, projects and tasks, not approvals specifically. monday.com adds an approval capability through AppFox, a marketplace add-on that attaches an approve/reject action and status to items on a board; Asana ships approvals natively as a task type on its Advanced and Enterprise plans, where a task can be marked "Approved," "Rejected" or "Changes requested" by an assigned approver. In both cases, approvals are priced as part of the parent suite's per-seat plan - there is no separate price for "the approvals feature" on its own, for either product.

Because the parent tool is a general work-management suite, an approval step inside it is one status or task type among many a board or project can have, not a decision object with its own identity, signature or lifecycle independent of the item that carries it. The approval lives and dies with the task or board it is attached to.

What happens after an item is marked approved

An approval in monday.com (via AppFox) or Asana blocks or flags an item until the assigned approver acts, then the item's status changes and whatever is watching that board or project - a person, an automation recipe, an integration - picks up from there. What is not part of that mechanism is a signed, independently verifiable object the next system checks before it acts - the trust sits in the item being marked approved inside that board's own database, the same gap the Jira Service Management migration guide describes for a workflow status with no record a downstream system can check on its own. Both tools are also built around a status or field living inside their own board or project; nothing in that mechanism is a published, agent-native way to file and wait on a request from outside the tool entirely.

The same shape in DueReason

monday.com's boards and Asana's projects are general-purpose work trackers, so no single DueReason template replaces the whole board - DueReason answers the approval question one step asks, not the rest of the task tracking around it. Map the step, not the board: if the step you want to move gates spend, Payments and refunds or Vendor onboarding from Settings → Templates cover that shape directly; for a step with no close template match, a custom DueReason action models the same approve/reject question with its own approver group and its own evidence field in place of the item's attached file or comment.

Whichever action models the step, once a request is decided DueReason issues a signed, single-use grant bound to the exact payload - the amount, the recipient, the change being requested - which whatever acts next verifies, rather than trusting that an item's status column says "Approved."

What changes, not just what moves

  • A grant the acting system checks, not a status column trusted at the source. DueReason's signed grant is bound to a hash of the exact payload and verified by whatever executes the decision, so a changed amount or target after approval is refused rather than carried out because an item happened to be marked "Approved."
  • A hash-chained ledger, not a board's own activity feed. Every step of a request - filed, each answer, what happened after - is a ledger event from the start, checkable on its own without opening the board or project that hosted the approval.
  • An agent-native surface, not a status that only changes when someone opens the board. The same actions are reachable from @duereason/sdk, the MCP server, the GitHub Action or the REST API, so a pipeline or an agent can requestApproval() and waitForApproval() without a board, project or task involved at all.
  • DueReason does not replace the board. It has no Kanban or list view, no task assignment, and no project timeline - it is not a work-management suite and does not try to be.

Moving one approval step over

  1. Pick the one approval step you want to move - not the whole board or project - and find the closest DueReason template (Payments and refunds, Vendor onboarding) or define a custom action if nothing close exists yet.
  2. Recreate the people assigned as approvers on that item or task as members of the action's approver group, in place of the AppFox approver field or the Asana approval assignee.
  3. For items still created by hand, the console request form replaces opening the board and setting the item to "pending approval": pick the action, attach whatever the item used to collect, write a reason.
  4. For items your automations create automatically (a monday.com automation recipe, an Asana rule), requestApproval() and waitForApproval() from @duereason/sdk (or the no-code webhook recipe if you would rather not write a backend) replace the point where the automation set the item's status to pending.
  5. Replace whatever reads the item's "Approved" status back into the rest of your board or into a downstream integration with a check of decided.status and a verification of decided.grant before the step that actually acts - the system doing the work should check the grant, not just the status column.

What has no direct equivalent

DueReason has no Kanban board, no task list, no project timeline, and no general work-management features - it is not a monday.com or Asana replacement and does not try to be. If the real value you get from either tool is the whole board - the tasks before and after approval, the assignments, the timelines - keep it for that and add DueReason around the one step that needs a signed, independently verifiable decision rather than expecting a native replacement for the work tracker itself.

Questions

Does moving to DueReason mean leaving monday.com or Asana?
No. DueReason replaces one approval step at a time, not the board or project it lives on. Keep monday.com or Asana for the work you track there, and point the one step that needs a signed, verifiable decision at a DueReason action instead.
Does DueReason do task tracking and boards like monday.com or Asana?
No, and it is not trying to. DueReason answers one question - is this action approved, by whom, with what evidence - and reaches that answer through @duereason/sdk, the MCP server, the GitHub Action or the REST API, rather than offering boards, task lists or project timelines.
What do monday.com and Asana charge for approvals?
Neither sells approvals separately: monday.com's AppFox add-on and Asana's native approval task type are both priced as part of the parent suite's per-seat plan, with no standalone approvals price published by either vendor. DueReason is free today for one organization with up to five members, all core features included.
Do I need engineering to move one approval step over?
No. Picking the closest template, adding people to its approver group, and filing requests from the console form is console-only setup, the same as setting an item to pending approval on a board; engineering is only needed once you want an automation or an agent to request approval through the API instead of a person using the form.
Can I self-host instead of using the hosted product?
Yes. Self-hosting runs on one Postgres database and one pre-built image started with Docker Compose, with no board or workflow configuration of its own - the same actions, grants and ledger work the same way whether you use the hosted product or run it yourself.

Move one approval step to DueReason

Keep monday.com or Asana for the board around it - point requestApproval() and waitForApproval(), or the console request form, at the one step that needs a signed, verifiable decision.

Create your account

Sources

This guide explains the regulation as we read it; it is not legal advice. Check the official text and your national law, which may add obligations.

Start with DueReason

Create a free account, try it live, or talk to us about your workflow.

Get product updates