Skip to main content

Baton :: Client Sign-Off on Tasks

Learn how to require client sign-off on tasks in Baton, what clients experience, and how sign-off status is tracked throughout a project.

Written by Krista Roberts

Vendors can now require a client to formally sign off on a task before a project can be marked complete. This turns client acceptance into a tracked, auditable step — closing the gap between "done" and "agreed it's done."

Enabling Sign-Off on a Task

On any eligible task, flip the sign-off requirement toggle in the task drawer. Once enabled, you'll see a confirmation below the task title: "[Client name] will be asked to sign off once this task is marked complete."

Client View:

The moment that task is marked Complete, Baton automatically emails the client's project lead to review it.

Note: The following task types are not eligible for sign-off:

  • Hidden tasks

  • Tasks assigned to clients

  • Optional tasks

The sign-off toggle will be disabled on ineligible tasks. Additionally, once a task has been signed off, the requirement cannot be removed and the task status cannot be changed.

Important: For client notification emails to be sent, the project must have a client project lead attached to it.

Sign-Off Statuses

Tasks requiring sign-off display a status badge throughout the task list and timeline so you always know where things stand:

  • Pending — Task is complete and awaiting client sign-off

  • Approved — Client has signed off

  • Stuck — Client has rejected the task and sent it back

On incomplete tasks that require sign-off, a signature icon appears next to the task title as a visual indicator.

What Vendors See

In the task drawer, vendors see the current sign-off status at the top. On a completed task awaiting sign-off, the drawer shows: "[Client name] must sign off on this task before this project can be completed" along with a Resend sign-off email link to nudge the client without leaving the task.

Once signed off, the drawer shows who approved it, when, and any note they left — plus a Revoke sign-off option if the client needs to pull back an earlier approval.

What Clients Experience

When a task requiring their sign-off is marked complete, the client's project lead receives an email notification. If multiple tasks are reminded at once (via the "Almost there" modal), they're batched into a single email.

From the email, the client clicks Review & sign off to open the task. Inside, they see a clear prompt: "This task is ready for your sign-off — The team marked it complete. Review the work, then sign off to close it out."

Clicking Sign off or Reject opens a modal where the client can:

  • Sign off — confirms the work meets expectations

  • Reject — sends the task back to the team with an optional note

Any note the client leaves is saved as a comment on the task so feedback stays attached to the work. Clients can also revoke a prior sign-off at any point directly from the task.

When a vendor PM receives a sign-off, they get an email notification showing which task was approved, who signed off, and any note left — with a link to view all tasks awaiting sign-off on that project.

Activity Feed & Audit Trail

Every sign-off action is logged in the task's activity feed, including:

  • When the sign-off requirement was enabled (and by whom)

  • When the sign-off request email was sent and to whom

  • When the client signed off or rejected

  • When a sign-off was revoked

  • If a vendor removes the sign-off requirement, that's logged too

Completing a Project with Pending Sign-Offs

A project cannot be marked complete until all required sign-offs are approved. If you attempt to complete a project with outstanding sign-offs, an "Almost there" modal appears showing exactly which tasks are still pending.

From this modal you can review each task or click Remind customer to send a batched reminder email to the client covering all tasks currently awaiting their review.

Sign-Off in Templates

The sign-off requirement carries through project templates. If you enable sign-off on a task in a template, every project created from that template will include the sign-off requirement by default — so your standard playbooks can build client approval in from the start.

Additional Notes/FAQs

  • A task that requires sign-off can't be made Optional, and an Optional task can't require sign-off.

  • A task that requires sign-off can't be reassigned to the client's organization (made "external"), and external tasks can't require sign-off.

  • A task that requires sign-off can't be hidden from the client.

  • An approved task can't be moved out of its Complete status — the client must revoke first.

  • A vendor can't remove the requirement from a task that's already approved (client revokes first).

  • Turning the requirement off resets the sign-off and withdraws any pending request (no email).

  • Bulk edit: the "Organization" and "Hide from all non-vendor users" fields are disabled when any selected task requires sign-off.

Did this answer your question?