Skip to content

ClickUp Organization

These are the ClickUp statuses currently managed by the dev team.
By following this workflow, we ensure that everyone (devs, QA, PMs, and managers) has full visibility into where a task stands at any given moment.
Each status represents a clear step in the lifecycle of a task, from preparation to final client delivery.

⚠️ Important: each card should have only one assignee.


When a card has been created but is not yet ready to start.

  • Most often created by PMs and Dev leads.

When additional inputs are required to move forward.

  • Typically tagged here: PMs, UX/UI, Meche, Andrés.

When the card has a clear owner and is ready to begin.


When active work is being done on the card.

  • You should ideally have only one card in progress at a time, since you can’t work on two tasks simultaneously.

(Previously called Dev Testing)
This is the stage for developers to check that everything is correct before moving the task forward.

  • Commonly used by devs to thoroughly test before giving final approval.
  • Frontend devs often use this step with BrowserStack.

When feedback has been provided and fixes or improvements are required.

  • A card in revision usually takes priority before moving forward.
  • If you find an issue during review, you can leave the card in this status for another teammate to address.

When the card is considered complete and ready for manager/lead verification.


When the card is sent to the client and we are waiting for their approval before closing it.

  • Usually the PMs are the ones tagged in this card because they’re the ones waiting for the client’s confirmation.

When the card has been fully finished.

  • Usually closed by PMs, Andrés, or Meche.
  • Also used when it’s an internal card.