Sign up →
Client approvals

Formal client approvals without ambiguity

Request a decision from a named approver and keep the outcome attached to the work.

Sign up See pricing
The problem

Why informal sign-off keeps costing you

Silence reads as approval

Work ships because nobody objected, and the objection arrives after launch when changing it is most expensive.

Nobody owns the decision

Three people commented, none of them actually approved, and the team had to guess whose opinion counted.

The record is a screenshot

Proving what was agreed means scrolling a thread and hoping the message was not edited or deleted.

How Trellis handles it

Built for the way the work actually moves

Pending, Approved, and Changes requested states

An approval is an explicit state on the task, not an inference drawn from a conversation. Anyone opening the work can see whether a decision is outstanding, granted, or sent back.

Pending, Approved, and Changes requested states

Request

Client approvals
Notify· Both sides are told, so nothing waits on someone noticing.
Recorded· on the task and in the audit log

Decision notes, actors, and timestamps

Every outcome records who decided, when they decided, and what they said. That record sits on the task and in the audit log, so a scope discussion months later starts from evidence.

Decision notes, actors, and timestamps

Notify

Client approvals
Decide· Approved or Changes requested, with a note explaining why.
Recorded· on the task and in the audit log

Approval analytics and automation triggers

See where approvals stall and how long clients take to respond, and let automations request sign-off the moment work reaches your client review stage.

Approval analytics and automation triggers

Decide

Client approvals
Record· Actor, time, and note are stamped on the task and audit log.
Recorded· on the task and in the audit log
The loop

A complete client-delivery loop

From the first request to a recorded decision, in one place.

Request

Ask a named approver, internal or client, for a decision.

Notify

Both sides are told, so nothing waits on someone noticing.

Decide

Approved or Changes requested, with a note explaining why.

Record

Actor, time, and note are stamped on the task and audit log.

Continue

Automations move the work onward based on the outcome.

Questions

Common questions

Yes. Approvers can be teammates or clients, so internal QA and client sign-off use the same mechanism.

The task returns with a recorded note explaining what to change, so the next round starts from a written requirement.

Client approvals and guest Approve access are available on Studio and above.

See the workflow with your own process

Tell us how work enters your team, who delivers it, and where clients make decisions.