Brainforge Knowledge

client-hour-overage-communications-playbook

7 min read

Client Hour Overage Communications Playbook

Purpose: Guide for CSOs and Service Leads to proactively and reactively communicate with clients when dedicated hours exceed billed hours. Ensures transparency, manages expectations, and creates opportunities for scope expansion.

Domain: Delivery Operations / Client Communications

Audience: CSOs (Client Success Officers), Service Leads

Owner: Delivery Operations

Status: Draft

1. Overview

What is an Overage?

An overage occurs when actual hours dedicated to a client engagement exceed the hours being billed under the current SOW or retainer agreement.

Why This Matters

  • Transparency — Clients trust us when we’re honest about time investment
  • Expectation management — Prevents surprises that erode trust
  • Scope expansion — Creates natural opportunities to discuss additional value
  • Margin protection — Without communication, overages become absorbed without recognition
  • Relationship health — Proactive outreach strengthens the partnership

When to Use This Playbook

  • Client is approaching their billed hour threshold (proactive)
  • Client has exceeded their billed hour threshold (proactive)
  • Overage has already occurred and needs explanation (reactive)
  • Service Lead notices hours trending over and wants to coordinate CSO outreach

2. Trigger Definitions

Proactive Triggers

ThresholdTimingPrimary Action
80% of budgeted hoursEarly warningInform client of trajectory; confirm priorities for remainder of period
90% of budgeted hoursAdvanced warningDiscuss what’s driving usage; propose scope options if applicable
100% of budgeted hoursAt budgetFormal communication; present options (expand scope, reprioritize, pause)

Reactive Triggers

ScenarioTimingPrimary Action
Overage already realizedPost-hocExplain what happened; present recommendation
Unexpected scope expansionDiscoveryCommunicate new work that exceeded original scope
Client-requested additionsAs they occurConfirm understanding; discuss billing treatment

3. Roles & Responsibilities

CSO (Client Success Officer)

  • Primary owner of client communication
  • Pulls hour data from Operating.app
  • Drafts and sends client-facing messages
  • Owns relationship and tone
  • Coordinates with Service Lead before outreach
  • Escalates to Service Lead if technical explanation needed

Service Lead

  • Provides context on what’s driving hours
  • Flags concerning trends early
  • Helps frame technical work for client understanding
  • Participates in calls/meetings when appropriate
  • Escalates to CSO if client relationship concerns arise

Coordination Requirements

ScenarioRequired Coordination
First outreach at 80%SL notifies CSO; CSO confirms message with SL
100% threshold communicationCSO drafts; SL reviews for technical accuracy
Reactive overage explanationSL provides root cause; CSO frames for client
Client pushback or objectionCSO leads; SL provides supporting data

4. Timeline & Workflow

Proactive Workflow

[Operating.app data]
        │
        ▼
   ┌─────────────┐
   │ Hour review │ ◄── Weekly (CSO responsibility)
   └──────┬──────┘
          │
          ▼
   ┌─────────────┐
   │ Check       │
   │ thresholds  │
   └──────┬──────┘
          │
    ┌─────┴─────┐
    ▼           ▼
< 80%       80%+
    │           │
    ▼           ▼
Continue   ┌─────────────┐
monitoring │ Alert SL &  │
           │ coordinate  │
           └──────┬──────┘
                  ▼
           ┌─────────────┐
           │ Draft client│
           │ communication
           └──────┬──────┘
                  ▼
           ┌─────────────┐
           │ Run through │
           │ humanizer   │
           └──────┬──────┘
                  ▼
           ┌─────────────┐
           │ Send/       │
           │ schedule   │
           └─────────────┘

Communication Timeline

StageWhenWho InitiatesFormat
MonitorOngoingCSOOperating.app review
80% alertWithin 2 business days of data refreshCSO → ClientEmail or Slack
90% alertWithin 1 business day of thresholdCSO → ClientEmail (preferred)
100% communicationWithin 1 business day of thresholdCSO → ClientEmail with call option
Post-overageWithin 3 business days of realizationCSO → ClientEmail with call option

5. Client Communication Templates

5.1 Proactive: 80% Threshold — Early Warning

When to use: Client has used ~80% of billed hours with remaining time in the period.

Tone: Informational, collaborative, forward-looking

Channel: Email or Slack (match client’s preference)

Subject: Quick update — You’re at ~80% of your [monthly/quarterly] hours

Hi [Client Name],

I wanted to give you a quick heads-up: you’re currently at about 80% of your allocated hours for [current period]. We’ve been working on [brief description of work] and wanted to make sure we’re aligned on priorities for the remainder of the [period].

Here’s where we’ve been focused:

  • [Workstream 1: brief description]
  • [Workstream 2: brief description]

With the remaining ~20%, we recommend prioritizing [recommendation]. Does that align with your expectations, or is there anything else you’d like us to focus on?

Let me know if you’d like to hop on a quick call to discuss.

Best, [CSO Name]

5.2 Proactive: 100% Threshold — Formal Communication

When to use: Client has reached or exceeded their billed hour threshold.

Tone: Transparent, solutions-oriented, partnership-focused

Channel: Email (with call option)

Subject: Your hours for [period] — where we are and next steps

Hi [Client Name],

I want to be transparent with you: we’ve reached 100% of your allocated hours for [current period]. Here’s what we’ve accomplished and what I’d recommend for next steps.

What we delivered:

  • [Deliverable/outcome 1]
  • [Deliverable/outcome 2]
  • [Deliverable/outcome 3]

Your options moving forward:

  1. Expand scope — We can continue at the same pace with additional hours. I can prepare a brief scope adjustment for your approval.

  2. Reprioritize — If there are lower-priority items we can pause, we can be more selective about what we work on for the remainder of the period.

  3. Pause and reassess — We can stop active work and reconvene to discuss priorities before the next period begins.

My recommendation is [option #1 or #2 based on context], but I want to make sure this works for you. Would you have 15 minutes to discuss? I’m happy to jump on a call or we can trade notes here.

Thanks for being a great partner to work with — I appreciate the chance to make sure we’re set up for success.

Best, [CSO Name]

5.3 Reactive: Post-Overage Explanation

When to use: Overage has already occurred and needs to be explained.

Tone: Accountable, clear, constructive

Channel: Email (with call strongly recommended)

Subject: Quick recap on hours — [period] wrap-up

Hi [Client Name],

I want to walk you through what happened with hours this [period] and make sure we’re aligned going forward.

What drove the overage:

  • [Root cause 1 — be specific, e.g., “additional discovery work on X that wasn’t in the original scope”]
  • [Root cause 2 — e.g., “faster-than-expected progress on Y required more QA than anticipated”]

What this means for your engagement:

  • We [absorbed / need to address] the additional hours
  • Here’s what I recommend: [recommendation]

Going forward, I’m proposing:

  • More frequent check-ins (bi-weekly instead of monthly) to catch trajectory earlier
  • A quick 15-minute sync every other week to review where we are against budget

I take responsibility for not flagging this sooner, and I want to make sure we have a system that works better for both of us going forward. Can we set up 20 minutes to discuss?

Best, [CSO Name]

5.4 Slack: Quick Touchpoint (For Ongoing Engagements)

When to use: Brief update within existing Slack channel relationship.

Tone: Brief, friendly, informational

Hey team — quick update. We’re at about [X]% of our allocated hours for this [period]. We’re on track for [deliverable], and I wanted to flag that we may want to talk priorities if we’re looking at wrapping up soon. Let me know if you’d like to sync!

6. Escalation Path

If Client Pushes Back

ResponseAction
”We didn’t approve this”Acknowledge; clarify what was in original scope; offer to review SOW terms
”This is included in our contract”Review SOW together; if genuinely included, absorb and document
”We need to talk to leadership”Offer to join call; prepare executive summary; CSO leads, SL supports
”We can’t afford more”Explore reprioritization options; pause lower-priority work

If Client Requests Formal Review

  1. CSO prepares summary of overage history
  2. SL provides technical detail on what drove hours
  3. Schedule call with client decision-makers
  4. Present options with clear recommendations
  5. Document outcome in client vault

When to Escalate to Leadership

  • Client is formally disputing the overage
  • Overage exceeds 20% of budgeted hours
  • Pattern of repeated overages (3+ periods)
  • Client threatens to reduce scope or end engagement

7. Operating.app Integration

How to Pull Hour Data

  1. Log into Operating.app
  2. Navigate to Clients → Select client
  3. Review Allocations tab for hours vs. budget
  4. Check Time Entries for detail if needed
Client TypeReview Frequency
Active engagementsWeekly
New clients (first 90 days)Bi-weekly
Stable/ongoingMonthly

Data to Track

  • Budgeted hours (from SOW)
  • Actual hours used
  • Remaining hours
  • Utilization trend (increasing/stable/decreasing)
  • Projected overage at period end

8. Anti-Patterns to Avoid

Anti-PatternWhy It Hurts
Waiting until 100%+ to communicateErodes trust; removes options
Blaming the Service LeadUndermines internal team; client sees disunity
Hiding overagesEventually surfaces as bigger problem
Being vague about what’s driving hoursClient can’t make informed decisions
Making commitments without SL inputMay over-promise on technical feasibility
Using templated language without personalizationFeels impersonal; damages relationship

10. Version History

VersionDateChangesAuthor
1.0[Date]Initial draft[Author]

This playbook should be applied with the humanizer to ensure natural, client-appropriate tone. Run through humanizer before sending any client-facing communication.

Graph View