ClickUp Dependencies Guide: Blocking, Waiting On and Rescheduling for Gulf Approval Chains

Quick answer

A ClickUp dependency links two tasks so one blocks the other, or waits on it, until the blocking task reaches a Done status. Dependencies are available on every plan, created in tasks, in views or by Automations, and with the Reschedule Dependencies ClickApp a moved date shifts every task waiting behind it.

A fit-out contractor in Abu Dhabi showed us the whiteboard outside the project manager's office. Fourteen lines, each ending in the same three words: waiting on consultant. The consultant, when we asked, had four items open, not fourteen. The other ten were waiting on the contractor's own drawings, on a supplier in Sharjah, or on nobody at all; they'd been written there in March and never wiped. Nobody could say which of the four actually held up the handover.

That's the problem dependencies solve, and it isn't a Gantt problem. It's a question of which tasks are really waiting on which, who gets told when the wait ends, and what happens to the dates behind a task that slips. We covered Gantt view, critical path and baselines in our Gantt guide; this guide is about the relationship itself, how you create it, and how teams in the UAE, Qatar and Kuwait use it for the approval chains that run their projects.

What a dependency is, and what it isn't

ClickUp has two kinds of Dependency Relationship, and they're mirror images. Blocks means this task stops another from being completed. Blocked by, which ClickUp also calls waiting on, means this task can't be finished until another is. "Finished" has a precise meaning here: the blocking task counts as complete when it moves into a Done status, the status group we explained in our statuses guide, not when someone writes "done" in a comment.

Two things a dependency is not. A Task relationship links tasks that are related but not dependent, a reference rather than a gate. A Custom Relationship groups tasks from a List into a field and can pull their data into Relationship columns. Use those for "see also". Use a dependency only when one task's completion unlocks another. Dependencies are available on every plan, and anyone with edit or full permission, guests included, can create them, which is exactly what you want when the consultant's engineer is the guest. One limit to know before you plan a mobile-first rollout: ClickUp's documentation states that task dependencies aren't available in the mobile app.

Where you create them: tasks, views, slash commands, Automations

You don't need a chart. From a task, open the Related section and click the plus, or use the ellipsis menu and hover over Relationships, then choose This task blocks or This task is blocked by and search for the other task or create it on the spot. Once one exists, the dependencies sit in a strip above the description, where a plus adds another and an x removes it. In a description or comment you can type /blocking, /waiting or /link to and pick the task.

In List, Board and Calendar views a dependency icon appears beside the task name; clicking it, or right-clicking the task, opens the same modal. List view can also show a Dependencies column, where you add and unlink tasks without opening them, which is how we run review sessions with a client: one List, one column, every wait visible. In Gantt view the link is an arrow from the blocking task to the one it blocks, drawn by dragging from a task's connector and removed with a double-click. Automations can create dependencies too, through the Add Relationship action or when they create a task or subtask. One caution: the Clear all dependencies option on a task is permanent.

Modelling a Gulf approval chain

Here's where most Workspaces go wrong: they link everything. A dependency should model a handoff where a Done status really unlocks the next piece of work, and in Gulf projects those handoffs are usually external. A design submission waits on the consultant's review. The permit waits on no-objection certificates from the municipality, civil defence and the utilities. Mobilisation waits on the permit. A progress claim waits on the consultant's certification, the sequence we laid out in our procurement approvals guide.

Model the external step as a task of its own, with the reference number, the date lodged and the expected response in Custom Fields, owned by whoever on your side chases it. Your internal work is then blocked by that task, and when the clerk marks the NOC received and moves it to Done, the wait ends in ClickUp at the same moment it ends in reality. Make the consultant a guest with edit permission on the review List and they can set the dependency themselves. We'd keep chains short, five or six links, and we'd never link two tasks just because they happen in the same week.

Warnings, notifications and the unblocked trigger

Three quiet features turn a diagram into behaviour. First, ClickUp notifies you when a dependency is added or unlinked, and when a task becomes unblocked. Second, an admin can switch on the Dependency Warning ClickApp, for the whole Workspace or chosen Spaces, so anyone who tries to close a task still waiting on another sees a warning. It doesn't forbid the close; it makes the person think, which on a Thursday afternoon before Eid is enough.

Third, and the one we use most, Automations have a Task or subtask unblocked trigger. The NOC task moves to Done, the mobilisation task is unblocked, and the Automation assigns it to the site manager, sets its status to Ready and posts a comment with the next steps. Nobody has to notice. Pair it with the Add Relationship action and a new project created from a Form can arrive with its first dependencies already drawn.

Rescheduling: when one date moves everything

A marketing team in Kuwait linked sixty tasks across a campaign, switched on rescheduling, and watched one delayed photoshoot push the launch into the first week of Ramadan. The feature did what it was told. The chain was wrong.

The Reschedule Dependencies ClickApp, in the Scheduling & Dates section of the App Center, is on every plan. When a blocking task's start or due date changes, every task waiting on it anywhere in the Workspace moves by the same number of days, earlier or later. Two conditions must hold: the blocking task needs a due date and the blocked task needs a start date; tasks without them stay put, which is the most common reason "rescheduling doesn't work". By default closed tasks move too; you can untick Trigger even when dependencies are closed. With the Skip Non-Working Days ClickApp active, where your plan includes it, the shift respects the Workspace work schedule, so a task pushed onto a public holiday lands on the next working day, and a Sunday-start week in Doha or Kuwait is handled by the schedule you set, not by assumption. In Gantt view only visible tasks reschedule, and you can turn the behaviour off in Customize when you want to move a bar by hand.

Templates, duplicates and recurring tasks: what carries over

Dependencies travel, but not always the way people expect. Apply a Space, Folder or List template and only the dependencies between tasks inside the template come with it; links to work outside it have to be redrawn. Duplicate a task, a List or a whole Folder and the dependencies inside the copy are recreated between the new tasks, while a dependency on a task outside the copied location points to the original. Recurring tasks include their dependencies by default, and you can exclude them in the recurring settings, which matters for the monthly compliance tasks we described in our recurring tasks guide: a renewal that waits on last month's instance is rarely what you meant. Dependencies also stay visible on a task after it's Done or Closed, so the record of who waited on whom survives the project.

A two-week rollout

Keep it small. Week one: pick one live project, draw its real chain on a whiteboard with the consultant in the room, and strip it to the handoffs that matter. Build the chain in a List template with the dependencies inside it, turn on Dependency Warning and Reschedule Dependencies for that Space only, and set the work schedule. Week two: run the project, create the unblocked Automation for the two or three handoffs that are always late, and review on day ten what moved on its own and what someone moved by hand. Then copy the template to the next project.

Three mistakes to avoid

We see the same three on almost every rescue.

• Linking everything. Sixty dependencies in a campaign List make every slip a landslide. Link handoffs, not neighbours.
• Expecting rescheduling without dates. No due date on the blocking task, no start date on the blocked one, no movement. Set both before you switch the ClickApp on.
• Leaving the authority out. If the municipality has no task, nothing in ClickUp is waiting on it, and the whiteboard comes back.

How BuyClickUp helps

BuyClickUp is an independent ClickUp partner operated by Inspark, a Salesforce and ClickUp consultancy serving the UAE, Qatar and Kuwait from Dubai. We map approval chains with your consultants and authorities in the room, build them into List templates with the dependencies, warnings and unblocked Automations already in place, and train your team in English or Arabic. Tell us about your projects through our contact page, or take the free ClickUp readiness assessment.

ClickUp is a trademark of Mango Technologies, Inc. BuyClickUp is not ClickUp. This article reflects ClickUp's help documentation as of October 2026; feature availability, including the scheduling ClickApps, varies by plan and changes over time, so confirm current details in your own Workspace.