How Agencies Get Client Sign-Off Without the Email Thread

Agencies get client sign-off by moving review out of email and into one shared surface where the draft, the markup, and the approval state all live together. Orbitable's Dock is that surface: a client sees what is waiting, marks it up with pins directly on the draft, sends it back, and approves it into a Library, with no forwarding, no "which attachment is the latest one", and no internal notes leaking into the client's view.

What actually breaks in an email approval thread

Email was never built to be a review tool, and the failure modes are always the same ones.

• Version drift. Three people reply to different points in the chain and nobody is sure which attachment is current.
• Feedback with no anchor. "Can we tweak the second paragraph" means something different to the writer than to the client, because the comment lives in the email body, not on the draft.
• Deadlines go unstated. There is no shared view of what is due when, so "urgent" gets typed into every subject line until it means nothing.
• Internal candour gets redacted. Before anything goes out, someone has to check that a Slack-style aside to the team hasn't been left in the thread by accident.
• Approval is implicit. "Looks good" is not a status. Somebody still has to chase confirmation that this is the final, sign-off version.

None of this is a client problem or an agency problem specifically. It is what happens when review and approval are bolted onto a tool designed for correspondence.

How the Dock replaces the thread

The Dock is a client-facing review surface, not a shared inbox. A client or stakeholder logs in and sees exactly what is waiting for them, marks it up with pins placed on the specific point of the draft they are reacting to, and sends it back. The agency revises against those pins, the cycle repeats until it is right, and the client approves the draft into a Library, where it becomes the record of what was actually signed off.

Clients can also raise new requests directly in the Dock rather than starting a fresh email chain, and those requests carry SLA targets, so both sides can see what is due and when without anyone having to restate it.

Email versus the Dock at a glance

Pins, revisions, and the Library

A pin is markup attached to the actual point on the draft it refers to, not a paragraph of prose trying to describe where. That single change removes most of the ambiguity that makes revision cycles slow: the writer opens the draft and sees exactly what the client meant, rather than reconstructing it from a sentence buried in an email.

Once a client approves a draft, it moves into the Library. That is where signed-off work accumulates, so an agency and its client both have a single place to point to when someone asks "what did we actually agree" six weeks later, instead of scrolling an inbox.

SLA targets and who can see what

Every request raised in the Dock carries an SLA target, so a client knows when to expect a first draft or a revision without needing to ask, and an agency has a stated deadline to work against rather than an unspoken expectation. That single piece of shared visibility removes a large share of the "just checking in" messages that clog an inbox on both sides.

Access is deliberately narrow. A client is given a Dock-only seat: they see what is queued, in review, or approved, and nothing else. Internal team notes are never visible to a client, so an agency's team can leave candid internal comments on a draft without redacting anything before it reaches the client's view.

Where the Dock sits in your plan

The Dock ships as standard on the Agency plan ($1,999/mo) and on Enterprise. On Founder ($89/mo) and Team ($349/mo) it is a $49/mo add-on. Reviewing work in the Dock never costs credits, so a client can go back and forth on markup as many times as a revision cycle needs without an agency watching the meter.

The Dock is also where Autopilot's weekly plan gets signed off. Autopilot proposes a plan, one focus and three to five missions with a stated why-now, a carry-over list, and an explicit not-doing list, but it only proposes. Approval happens in the Dock, so the same surface a client uses to sign off on a draft is the surface an agency uses to sign off on what the fleet works on next.

FAQ

Does the Dock replace email entirely for client communication?

It replaces email specifically for review and sign-off, which is the part of the relationship that generates the most thread sprawl. Drafts, pins, revisions, and approvals happen in the Dock instead of an inbox. Agencies still use whatever channel they like for everything else, the Dock just removes approval as a reason to open email.

Is the Dock included in every Orbitable plan?

It is included on the Agency plan ($1,999/mo) and on Enterprise. On Founder ($89/mo) and Team ($349/mo) it is available as a $49/mo add-on. Reviewing work in the Dock never uses credits on any plan.

Can clients see the agents or internal work in progress?

No. A client is given a Dock-only seat, which shows what is queued, in review, or approved, and nothing about the internal agent workspace. Internal team notes on a draft are never visible to a client, so a team can comment candidly without redacting anything before a client sees it.

What happens to work after a client approves it in the Dock?

Approved drafts move into the Library, which becomes the running record of everything the client has actually signed off on. That gives both sides one place to point to instead of hunting through old email attachments for the version that was actually agreed.

Can clients request new work directly through the Dock?

Yes. A client can raise a new request from inside the Dock rather than starting a separate email chain, and that request carries an SLA target so both sides know when to expect a response without having to state it separately.