Requesting approvals

When work needs sign-off, request it on the task — the decision, the comments, and a snapshot of exactly what was approved all stay attached to the work. There are two flavors: client approvals on shared tasks, and internal reviews between teammates.

Client approvals

On a client-visible task, the approval bar reads Request approval:

1. Pick the client contact to tag (the @-mention dropdown)
2. Click Submit

What happens next:

• The task's title and description are snapshotted — the approval history records what the work looked like at the moment you asked, so later edits can't muddy what was approved
• The client sees an "Awaiting client approval" banner on the task in their portal, with three options: Approve (comment optional), Request changes, or Decline (comment required for both)
• Their decision comes back to you as a notification, comment included

While it's pending you can Send reminder (nudges the contact) or Cancel request. After a "changes requested," revise and Resubmit — each round is preserved in the approval history on the task, snapshots and all.

Internal reviews

On an internal task, approvals run between teammates. Set a reviewer on the task first — without one the bar reads "No reviewer assigned — set a reviewer to request approval." Then Submit sends it to them.

The reviewer sees Approve / Request changes / Decline right on the task (changes and declines require a comment, same as the client flow). Anyone else sees "Awaiting approval from @reviewer" with the reminder and cancel options.

Habits that keep approvals fast

• Make the description complete before submitting — it's what gets snapshotted, and it's what the client reads to decide
• One approval per deliverable — if a task bundles three deliverables, the decision means less
• Use reminders, not new requests — resubmitting resets the round; a reminder doesn't