Buyer Problems

How to Track Client Approvals Without Digging Through Email

"Looks good!" in a two-week-old email thread is not an approval record. Here's what a durable one actually needs, and how to build it with requests instead of chasing threads.

Nadia KovachNadia Kovach6 min read
A date stamp pressing down onto one printed photograph among a scatter of unopened envelopes on a table.

Marisol approved the homepage design on a Tuesday. She said so in an email: "Looks good, let's move forward!" Three weeks later, in a dispute about a last-minute logo swap she insists she never signed off on, someone at the agency has to go find that email, confirm it was actually about the homepage and not the earlier draft, and work out whether "looks good" covered the logo or just the layout.

It did. Sort of. The same email also said "can we tweak the logo placement a bit?" which either means the homepage was approved with one open item, or means nothing was approved at all. Nobody can say for certain, because the email was a message, not a decision. A message describes a feeling. An approval has to describe a state, and it has to say whose state it is.

Approval is a transition, not a tone

"Looks good" is sentiment. It tells you the client is pleased, which is nice, and it tells you nothing enforceable. A real approval record answers five questions without anyone interpreting anything:

  • What exactly was being approved (which item, which version)
  • Who approved it (Marisol, specifically, not "the client")
  • What they decided (approved, or rejected, with a note)
  • When they decided it (a timestamp, not "a while back")
  • What happens next if the decision wasn't a clean yes (a task, with a named owner)

Email can hold all five pieces of information. It just never holds them in one place, never timestamps a decision apart from the small talk around it, and never connects the decision to the work that follows from it. The information ends up spread across three threads and a Slack DM, and finding it later means reading, not looking something up.

Hands sorting through a thick stack of printed pages at a table.

Give the client a channel that isn't reply-all

In Team and Tricks, a client like Marisol doesn't get a teammate account. She gets guest access to one project, here, the website rebuild, and nothing outside it. She never shows up in the Members list. She is never assigned a task. She doesn't take a paid seat. What she can do, once the agency turns it on for her specifically, is raise a request.

A request is the right shape for this because an approval isn't owned work. Marisol isn't doing a task. She's being asked for a decision, and the agency needs that decision in a form that outlives the thread it arrived in. When a guest raises a request, it routes automatically to the organisation's owners, admins and managers, nobody has to remember to loop in the right person, and Marisol doesn't have to guess who the right person even is.

What the record actually looks like

The agency sends the request with the specific thing attached: homepage design, v3, with a note naming exactly what changed since v2. Any message inside that request can be marked as asking for approval, a distinct action from an ordinary reply, and a different thing entirely from the manager approval that governs a timesheet. When Marisol replies and approves, her decision sits against a timestamp, attached to that specific request, attached to that specific project. Nobody cross-references which email client she was using or scrolls past an out-of-office autoreply to find it.

Here's the shape of what you end up with, written out as a reference, not a new screen to configure, it's just what the request thread already contains once you use it this way:

Item:          Homepage design, v3
Requested by:  Agency (sent via Request)
Recipient:     Marisol (guest, Website Rebuild project)
Decision:      Approved, with a note flagging the logo placement
Timestamp:     Oct 14, 2:41pm
Note:          "Logo needs to sit higher, everything else is good"
Resulting task: "Adjust logo placement, homepage v3", assigned to Dana

That last line is the part email can't do on its own. The approval and the follow-up aren't the same thing, and the request doesn't pretend they are. It records the decision and who signed off on it; the task is a separate piece of work, assigned to a person, tracked on its own. If someone later asks "did the client ever actually approve the homepage," the answer isn't a search through a mailbox. It's the request thread, with the decision and the timestamp sitting right there.

One printed proof pinned alone to a corkboard, signed and dated.
One approval, one place, one record, not a thread to re-read.

What Marisol never gets to touch

It matters just as much what she can't do. She can't see the agency's internal project chat about whether the logo placement was Dana's mistake or Marisol's second-guessing, that chat is closed to guests entirely. She can't be assigned the "adjust logo placement" task; that stays with Dana, a teammate, because approving a design and building it are different jobs done by different people. She can't open the timesheet, and she can't see any other client's project sitting in the same organisation. Comments on the request itself are off unless the agency switches that on for her specifically, same as TAI, same as seeing who else is on the team. None of that is withheld to be stingy. A client approving a design doesn't need the agency's billing argument, and handing her that view wouldn't make her approval any more real.

Why this beats a shared spreadsheet too

Some agencies solve this with a spreadsheet instead: item, approver, date, status, column after column. It works until someone forgets to update it, which is the same failure mode as a stale task board, the record is only honest if updating it is free, and a spreadsheet makes updating it a separate chore from actually getting the approval. A request thread doesn't have that problem, because the approval and the record are the same action. Marisol isn't filling out a form about her decision. Her decision is the record.

The logo dispute never needs to happen twice. Next time there's a "wait, did we actually approve that," the answer is one request thread away, not a Tuesday three weeks back that somebody at the agency half-remembers and the client remembers differently.

Continue Reading