How to use a Righthand with ClickUp

Make a ClickUp review about delivery exceptions

Use Righthand with ClickUp to prepare an exception brief for one list or project. The output should surface work that needs a decision: missing owners, uncertain dates, or unresolved dependencies. It should not simply restate every task description in a longer document.

ClickUp's Get Tasks reference describes list task retrieval and its filters, including subtask handling. Make inclusion explicit. A report covering parent tasks alone should not claim that all delivery work has been reviewed.

Map the workspace's own fields

Give the list identifier, status meanings, expected assignee rules, and relevant custom-field mappings. An illustrative client-delivery list might use Delivery date, Client approval, and Dependency owner. Those are example workspace fields, not guaranteed built-in properties.

Inspect the available tools in integrations. If task reads or custom fields are unavailable, use an approved export with task identifiers and its snapshot time. Preserve timestamp units and time-zone interpretation rather than converting a due date through a guess.

A complete first-run request

On Monday at 10 AM America/Los_Angeles, review the linked client-delivery list including the specified subtasks. Return a private exception brief for tasks due this week. Show task ID, current status, assignees, source due value, relevant custom fields, and source link. Flag missing client approval according to the attached policy and distinguish blank from unavailable fields. Do not update status, assign people, or contact clients. Send to me for delivery-lead review and reconcile the included task count and filters.

This example is illustrative. A status named “Ready” needs the team's definition before it can be treated as approval to deliver.

Make the expected result specific

An example item might read: “Homepage package; status Internal review; due Thursday; client approval field blank; final delivery should remain an owner decision.” A parent task marked complete with an open subtask should produce a mismatch for review, not automatic reopening.

Keep multiple assignees visible when the task has them. If the workflow requires one accountable owner, ask the lead to select that person instead of silently choosing the first name returned. Separate an unavailable custom field from a confirmed empty value.

Reconcile before changing anything

On repeat runs, match by task ID even if the task moves between lists or its title changes. Compare the updated status and dates before repeating an escalation. Record whether the source was a live read or an export so the reviewer knows the freshness of the evidence.

Pagination, archived-task filters, and excluded subtasks can produce a deceptively small queue. Report incomplete coverage. If the owner approves supported updates, reread the exact tasks afterward and compare the results with the change proposal.

Use Righthand connection permissions for the selected list's access and review rules. Check plans before expanding the brief into a recurring delivery responsibility across several teams.