What Is a Design Approval Receipt?

A design approval receipt is a record that captures four things: who approved a design, which version they approved, on what date, and against what scope. It converts a client's informal "looks good" into a dated, attributable decision you can point to later.

It's the design equivalent of a signed change order. Where a comment thread records the conversation about a design, an approval receipt records the decision about it: the moment a specific version was formally accepted and a round of work was closed.

What an approval receipt includes

A complete approval receipt has four parts:

• The version. A specific, frozen state of the work, not "the website," but the website exactly as it existed at the moment of approval. This prevents disputes about what was approved.
• The approver. A named individual who made the decision, not a vague "the client." Decisions need an owner so accountability is clear.
• The date. The moment the round closed, which establishes a clear before-and-after for any later requests.
• The scope. What was being approved, this page, this round, this deliverable, so that a future request can be clearly identified as falling inside or outside it.

Together these four turn an opinion into a record.

What an approval receipt looks like in practice

Concretely, a receipt is a single line you can produce in seconds:

Approved by Maria Chen (maria@client.com) on 8 June 2026 at 14:32. Version: homepage and pricing, review link #41. Scope: round 2 of 2.

That line does work no comment thread can. It names the person with authority, freezes the exact thing approved, timestamps the decision, and bounds the scope. When a request arrives later, you hold it up against this line and the answer is immediate: inside scope, or a new round.

Why it matters

Without an approval receipt, there's no defined point at which a piece of design work is "done." Every project stays implicitly open, because nothing ever formally closed. This is the root cause of most scope creep: a client requesting changes to previously-accepted work doesn't perceive the request as new, because from their side the conversation never ended.

An approval receipt inserts a clear endpoint. After it's recorded, any new request is visibly a new request, which can be scoped, scheduled, and billed separately rather than absorbed as another unpaid revision.

There's a second benefit that's easy to miss: the receipt protects the client too. It tells them exactly what they committed to and when, which removes their own uncertainty about whether things were settled. A good approval record is not a weapon you hold over a client. It's a shared fact you both rely on.

Approval receipt vs feedback

Feedback and approval are often confused because they happen in the same place. They are different artifacts:

• Feedback is continuous and open-ended, the client reacting to the work, suggesting changes. There's always more of it.
• An approval receipt is discrete and final, a single act that closes the round.

A tool can be excellent at collecting feedback and still produce no approval receipts at all, because the two require different mechanics. Feedback collection optimizes for the conversation; approval optimizes for the decision.

How to create one

You can produce an approval receipt manually: a signed PDF, a dated change-order email, or a logged entry in a spreadsheet, as long as it captures the four parts above. The friction with manual methods is that the closing step is easy to skip, which is exactly when disputes occur.

Some Framer review tools, like Lyba, build the approval receipt into the workflow: when a client signs off on a version, the receipt is recorded automatically, so closing a round is part of the process rather than an extra step you have to remember.

FAQ

What is a design approval receipt? A record of who approved which version of a design, on what date, against what scope. It turns an informal "looks good" into a dated, attributable decision you can point to if a client later asks to change approved work.

How is an approval receipt different from a signed contract? The contract sets the terms of the engagement up front. The approval receipt records a specific decision during the project: that a named person accepted a specific version on a specific date. You need both. The contract defines the rounds; the receipt proves a round closed.

Do I need an approval receipt for every round? Yes, if you want each round to be defensibly closed. A receipt per round is what lets you treat any later request as new work rather than a continuation, which is the whole mechanism for controlling scope.

Can I create approval receipts without special software? Yes. A dated change-order email or signed PDF works if it captures version, approver, date, and scope. The risk is purely that the manual step gets skipped under pressure, which is when scope creep takes hold. Tools like Lyba record it automatically so it doesn't get skipped.

Related: How to get a client to formally sign off on a design · Feedback vs approval