Define What a Client Approval Covers Before Work Proceeds
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A client replies, Looks good, go ahead. The account manager sees permission to proceed; the designer sees approval of the layout; the production lead assumes the copy is final. If the conversation contains several files and unresolved comments, each interpretation may point to a different deliverable.
Before work proceeds, connect the reply to an explicit approval object: a named deliverable, a fixed version, a defined set of elements, an authorised reviewer, any conditions, and one permitted next action. When the reply does not establish those points, record it as feedback or a decision needing clarification—not as unrestricted approval.
The practical tool is a short approval packet followed by a response brief. The packet tells the client exactly what decision is being requested. The response brief tells staff what that decision permits. This is an operating practice for maintaining evidence of a client decision, not a test of legal enforceability.
1. Make the approval object smaller than the project
A project is usually too broad to approve in one message. A website can contain approved layouts, provisional copy, untested forms, and an unresolved launch date. Calling the whole website approved conceals those differences.
Define the approval object at the level where a decision changes what someone may do next. For example, approval of a desktop layout may permit responsive design work without permitting publication. Approval of final copy may permit production without accepting the design.
Each request should establish:
- Object: the deliverable or component under review.
- Version: the exact revision, including a stable reference.
- Decision scope: the elements the reviewer is accepting or rejecting.
- Reviewer authority: the person or role designated to make that decision.
- Conditions and exclusions: what must happen first and what is outside this decision.
- Next permitted action: the specific work this decision can release.
A useful test is whether a colleague who missed the conversation could identify both what is accepted and what remains blocked. If they need to infer either from tone, the approval object is incomplete.
2. Freeze the reference before asking for a decision
A link to a live working file is convenient, but it may show different content after the client responds. Preserve the reviewed state before sending the approval request. Depending on your tools, that could be a read-only export, a retained revision, or a snapshot with a revision identifier.
Use a reference that staff can distinguish from neighbouring revisions. Include the project, component, version, and date where useful. Avoid relying on names such as final or latest: they describe an intention, not a durable identity.
Keep the review message, the referenced version, and the resulting decision together in your chosen record. The goal is not to create several copies of every conversation. It is to preserve enough context to reconstruct the decision without searching multiple channels.
There is a trade-off between speed and granularity. One approval for every small element creates review fatigue; one approval for an entire project hides unresolved work. Group elements when they share a reviewer and next action. Split them when their conditions, owners, or release consequences differ.
3. Send a packet that names the decision
Fictional worked example: All names, dates, identifiers, and project details below are hypothetical. An agency is preparing a landing page for Cedar Lane Workshops. The client has reviewed several drafts, but the agency needs a clear decision before building the page in a staging environment.
The following filled packet could be placed in a project record and sent as a single review message.
Filled hypothetical approval packet
- Packet reference: CLW-LP-AP-07.
- Approval object: Workshop landing-page design and copy for staging implementation.
- Version reference: CLW-LP-v04, dated 12 May 2026; retained read-only PDF, CLW-LP-v04-review.pdf, containing desktop and mobile layouts with embedded copy.
- Review location: The retained PDF attached to this packet. The working design file is not the approval reference.
- Decision requested: Accept or request changes to the listed elements so the agency can prepare the staging build.
- Designated reviewer: Mara Chen, client marketing lead, recorded at project kickoff as the decision owner for page design and copy. Budget changes and publication require separate decisions.
- Elements in scope: Page order; desktop and mobile layout; headline and body copy; image selection; button label; footer contact details.
- Excluded elements: Form behaviour, analytics configuration, live destination links, accessibility testing results, and publication date. These are not being presented as approved.
- Known open issue: Footer contact email still shows the old address.
- Proposed condition: Replace the footer email with workshops@cedarlane.example before staging implementation.
- Next permitted action: Build the accepted design and copy in staging after the condition is verified.
- Actions not permitted by this decision: Publish the page, change the budget, or treat excluded items as accepted.
The request accompanying this packet could say: Please approve CLW-LP-v04 for staging implementation, request changes, or approve it subject to the footer-email correction described above. Please identify any other conditions. This request does not include publication approval.
The packet exposes the known defect instead of quietly asking the reviewer to accept an inaccurate file. It also prevents a staging decision from becoming a launch decision through shorthand.
4. Turn the reply into a response brief
In this hypothetical example, Mara replies: Approved for staging once the footer email is changed to workshops@cedarlane.example. Keep the rest of v04 as shown. Please send the staging page before anything goes live.
That response contains a version reference, a condition, and a boundary. Staff still need a concise operational record that separates the client's decision from the agency's verification work.
Filled hypothetical response brief
- Packet and version: CLW-LP-AP-07; CLW-LP-v04.
- Response received: 13 May 2026, from Mara Chen, in the review thread attached to the packet.
- Authority check: Mara is the recorded decision owner for design and copy. This reply does not establish authority for additional spending or publication.
- Decision: Conditional approval for staging implementation.
- Approved elements: Page order, desktop and mobile layout, headline and body copy, image selection, and button label as shown in v04.
- Condition: Replace the footer contact email with workshops@cedarlane.example.
- Excluded elements: Form behaviour, analytics configuration, live destination links, accessibility testing results, and publication date remain outside this approval.
- Condition owner: Agency designer updates the footer; project lead checks the resulting file against v04.
- Current work status: Staging implementation blocked pending the footer correction and verification.
- Condition-completion evidence: Pending. Retain the corrected revision and the project lead's check before releasing work.
- Permitted next action after verification: Build in staging and send a review link to Mara.
- Still blocked: Publication and any representation that excluded items have been accepted.
Record the client's response faithfully. If staff add an interpretation, label it as an interpretation rather than rewriting it as something the client explicitly approved. Send that interpretation back for confirmation when it changes the work boundary.
5. Make conditional approval a controlled handoff
Conditional approval is useful when a bounded correction does not require another full review. It becomes risky when the condition is subjective or expands the deliverable.
For the hypothetical packet, replacing one specified email address is checkable. Making the page more premium is not. A subjective condition requires clarification or another revision because staff cannot objectively establish when it has been met.
Before treating a condition as satisfied, record:
- The exact change required.
- The person responsible for making it.
- The evidence used to check it.
- The person responsible for that check.
- Whether the client must review the corrected version again.
In the worked example, the project lead could retain CLW-LP-v04a and confirm that only the specified footer email changed. If that check instead finds a changed headline or a different mobile layout, the earlier approval should not silently cover those edits. Identify the differences and request a targeted decision.
Where the request did not establish who may verify a condition, clarify that before release. An agency's internal check should not substitute for a client review that the client expected to perform.
6. Recover from vague, conflicting, or misplaced approvals
A vague response does not require restarting the entire review. Ask the smallest question that resolves the missing decision.
When the version is unclear
In a hypothetical exchange, the client replies positively beneath a thread containing two revisions. Respond: To confirm, does your approval cover CLW-LP-v04, the PDF attached to packet CLW-LP-AP-07, for staging implementation only? Keep the decision unresolved until the reference is clear.
When the reviewer is not the decision owner
A helpful stakeholder may give valuable feedback without having authority to release work. Preserve that feedback, then route the approval request to the designated reviewer. If the client changes the decision owner, record that change explicitly rather than inferring it from a forwarded message.
When reviewers disagree
Do not assemble an apparent approval from incompatible comments. Summarise the conflict, identify the affected element, and ask the decision owner to resolve it. Unaffected elements may proceed only if their scope and next action are genuinely separable.
When the file changes after approval
Retain the approved reference and describe the difference in the new revision. Ask for a decision on changed elements where possible; a full re-review may be unnecessary. Never replace the old file and leave its approval attached as though nothing changed.
When work has already started
Pause the affected work, record which version staff used, and separate completed work from assumptions still awaiting confirmation. Tell the client what needs clarification without presenting the team's assumption as their decision. Silence or an expired internal deadline should not be converted into approval.
7. Keep decision status separate from work status
A single approved label cannot show whether conditions remain open or whether the next action has happened. Maintain separate descriptions for the decision and the work.
- Decision status: Awaiting decision, changes requested, approved, or conditionally approved.
- Work status: Blocked, ready for the named next action, in progress, or completed.
This distinction lets staff record conditional approval without prematurely releasing production. It also prevents completed staging work from being mistaken for permission to publish.
Use the team's existing project record, document store, or CRM if it can retain the necessary references and discussion. These are recommended recordkeeping practices, not claims that any particular product provides approval controls. A short manual record is preferable to an elaborate workflow that staff bypass.
8. Test the next approval before expanding the process
For the next deliverable, prepare one packet, name one decision owner, and state one permitted next action. Ask a colleague who was not in the client conversation to identify the approved version, accepted elements, exclusions, conditions, and current release status.
Log any missing answer and the clarification needed. Then review whether work began before the record supported it and whether the retained version still matches what the client saw. These are observable checks, not a promise that disputes or rework will disappear.
The immediate measure of success is simple: a staff member can explain what may happen next, point to the decision supporting it, and identify what remains blocked—without interpreting a vague expression of enthusiasm as blanket approval.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications