I would like to suggest the implementation of a highly valuable feature for process governance and data quality: the ability to define required custom fields based on the task status.

Currently, ClickUp allows custom fields to be marked as required only at the moment of task creation. However, in many operational workflows, certain fields do not need to be completed when the task is created, but should become mandatory as the task progresses through different statuses.

In more structured process management environments, it is common for each stage to require specific information to ensure workflow integrity. Without status-based enforcement, it becomes possible to move a task to the next stage without filling in critical data, which can:

Tools such as Pipefy, HubSpot, and Kommo already support conditional required fields by stage/phase, preventing cards from advancing unless the required information for that specific stage has been completed.

Implementing this functionality in ClickUp would significantly elevate operational control, especially for teams that rely on the platform as a structured system for process management and automation.

This improvement would be extremely valuable for organizations that depend on consistent data and well-defined workflows.

I work in an industrial engineering designer. Here we prepare dozens of documents every day. For us, each task in a list in ClickUp is a document. Each document will pass through the hands of at least 3 people: the creator, the verifier and the issuer (who sends the document to the client). It would be really nice if I could lock the statuses as follows: only the developer can move the task from status "to do" to "in verification", only the developer can move from status "in verification" to "ready to send" or "not ready for sending" (returning the activity to the creator), and at the end, when the document is ready, only the sender can move the status from "ready for sending" to "sent". Please help me with this, it's something that already exists in other applications and would be very useful for us here at the company.

Please add native status transition validation. When a task is moved into a specific status, ClickUp should block the change if required Custom Fields are missing and show a prompt listing what’s missing.

Example: If moving to “Ready for Review”, require [Field A] and [Field B]. If either is blank, prevent the move and prompt the user to complete it.

Allow validation rules on both standard and custom fields. For example with Status equals In Progress, start date and due dates are required

It'd be great if we could create role permissions by List, in order to permit who can change from specific status to another one. Example: just the approvers role (for this list) can change to approved status or can change some fields.

Some complementary requests: