Client Approval and Launch Communication

SOP: Client Approval and Launch Communication

Last Updated: June 2026 Owner: CSM

Purpose

Keep clients informed around previews, approvals, launches, and completed work without announcing something before it is technically verified.

Golden rule

CSM owns client communication. The specialist owns technical sign-off. Nick/Ops approves high-risk live actions when required.

When to use this SOP

Use this for:

• website preview links
• website launch notices
• GBP verification/change coordination
• GHL funnel/form/workflow previews
• LSA setup or budget/lead changes
• special request completion
• client approvals before visible changes

Before sending a preview or launch note

Confirm:

• responsible specialist says it is ready
• preview/live URL works
• known issues are either fixed or clearly stated
• approval needed from the client is specific
• no DNS, indexing, billing, budget, or ad change is being implied without approval

Client approval request format

Use this structure:

1. what changed
2. what the client should review
3. what approval means
4. what is not changing yet
5. deadline or next step

Launch notice format

Use this structure:

1. work is live or completed
2. where to see it
3. what Tekton already checked
4. what to report if the client notices an issue
5. what happens next

What not to do

• do not say something is finished because a task moved to in_review
• do not announce launch before specialist sign-off
• do not imply client approval covers DNS, billing, ads, indexing, or budget changes unless explicitly included
• do not leave the client with a preview link and no requested action

Definition of done

• approval/completion message is sent or drafted
• specialist sign-off is documented
• client has a clear next step
• TaskTracker/client record has the message and status