Brainforge Knowledge

client-communication-standards

3 min read

Client communication standards (delivery layer)

Purpose: Delivery-specific communication doctrine. Canonical writing, email, and formatting rules live in standards/; this document defines the delivery-layer expectations that protect trust and keep the client story aligned with reality.

Canonical playbook docs:

  • standards/02-writing/Communications/email-communication-standards.md
  • standards/04-prompts/email-client-comms-sop.md
  • standards/02-writing/Communications/slack-client-updates-guide.md

1. Literal statement

We communicate in a way that is structured, reality-based, easy to forward, and consistent with the actual state of delivery.

2. Why it exists

Most client trust is lost through:

  • surprises
  • vague or overly optimistic updates
  • dropped loops
  • conflicting internal and external narratives

Communication is not downstream from delivery quality. It is part of delivery quality.

3. Analogy

The strongest analogies here are:

  • Great agencies — progress is legible, confident, and client-centered
  • Banks and other risk-managed systems — bad news moves early and in a controlled way

Brainforge needs both: visible momentum and disciplined escalation.

4. What good looks like

Good client communication:

  • reflects real delivery truth
  • uses a clear structure
  • makes decisions and asks visible
  • includes something tangible when possible
  • can be forwarded inside the client organization without losing meaning

The default frame is:

  • status
  • risks
  • asks
  • next steps

5. Core delivery communication rules

5.1 CSO is the default external voice

The CSO is the default external voice for commitments and timeline narrative.

What this means:

  • ICs and SLs do not contradict agreed scope or date language in client channels
  • role-specific expertise can absolutely show up in client discussion
  • material commitments and negative timeline changes should be aligned before they are stated externally

5.2 Async-first when it improves clarity

Prefer written updates when they create more clarity, are easier to forward, or reduce unnecessary meeting overhead.

What this means:

  • use meetings for decisions, demos, or high-value alignment
  • do not force meetings for status that can be explained more clearly in writing

5.3 No surprise escalations

Internal leadership should hear from the CSO before the sponsor hears a new material negative.

What this means:

  • yellow flags should surface early
  • client communication should follow internal alignment on material risk
  • “we were still trying to solve it quietly” is not a valid operating habit

5.4 Story matches build

The client narrative should match the actual state of the work.

What this means:

  • do not send “all good” updates while the board and internal discussion show mounting risk
  • if the story changes, update the team first and then the client with a controlled message

5.5 Artifact habit

Weekly touchpoints should include something tangible when possible.

Examples:

  • demo
  • deck
  • document
  • decision memo
  • dashboard
  • shipped capability

This keeps updates grounded in visible progress.

6. Weekly communication expectations

Weekly kick-off

Use the weekly kick-off rhythm to align the client on:

  • what moved last week
  • what matters this week
  • what is blocked
  • what decisions or inputs are needed

Canonical SOP:

  • standards/04-prompts/weekly-kick-off-update-sop.md

End-of-week update

Use the end-of-week rhythm to close the loop on:

  • what was completed
  • what remains in progress
  • what is blocked
  • what next week now looks like

Canonical SOP:

  • standards/04-prompts/end-of-week-update-sop.md

7. Internal-first escalation behavior

Client communication should follow internal alignment when the issue is materially negative.

Examples of material negatives:

  • milestone slip
  • scope conflict
  • major dependency miss
  • resourcing issue that threatens timing
  • feasibility change

The goal is not to delay truth. The goal is to communicate truth in a way that preserves control.

8. Common misses

  • optimistic updates that are no longer true
  • unclear asks hidden inside long text
  • waiting too long to name a risk
  • letting separate people tell separate versions of the same delivery story
  • sending updates with no visible value or no next-step clarity

Last updated: 2026-03-24

Graph View

Backlinks