Top view of a minimalist schedule planner with Monday header. Perfect for organizing daily tasks with goals section.
Photo by cottonbro studio on Pexels

Adoption

Part of Customer success team operations

Planning caseload from account complexity

Estimate a success manager's workload from account tasks, timing and dependencies, then compare demand with available time.

Plan an individual success manager’s caseload by estimating the work each account will generate in the same period, then checking whether the work fits their available time. Estimate preparation, conversations, follow-up and coordination for each account, and check when the work falls as well as the total. The planned caseload is the set of accounts whose estimated hours fit available capacity, including peak periods.

Define the manager's job

First settle which work belongs to the role. Does the manager coordinate implementation, run ongoing outcome reviews, prepare for renewals or handle technical questions until another team accepts them? The answer changes the load.

Record specialist and customer-side dependencies separately from the manager’s hours: they affect timing, but should count as manager effort only when the manager is expected to do the work. This distinction helps identify delays caused by another team’s backlog.

Choose a planning period that shows when work arrives. Accounts may look manageable across a quarter yet require decisions from the same manager in one week, so check both estimated hours and peaks.

Translate complexity into work

For each account, note the sources of coordination: active customer teams, variation from a standard workflow, unresolved integrations or permissions, decisions involving several stakeholders, and how often material change occurs. Treat these as current planning inputs. A difficult rollout may become routine; an established account can become complex after a new use case.

Use each factor to identify the activities the manager is expected to perform, rather than assigning the factor a score. A standard setup might need a short customer conversation and a later check; a rollout involving several policy owners might need preparation, decision meetings and further coordination. Estimate the time for those activities from the manager’s own records, not from a generic complexity rating.

Estimate the load by period

List each active account on one line of a worksheet. Use the inputs below to identify the work, its timing and the assumptions that need checking.

Input / Planning question

Expected work
Which customer decisions or reviews are due?
Manager time
What preparation, meeting, follow-up and internal coordination will they create?
Timing
Could several accounts peak together?
Dependencies
Which tasks rely on specialists or customer owners?
Uncertainty
Which estimate could change quickly?

For each account, break the estimate into planned activities the manager owns: preparation, customer conversations, follow-up and internal coordination. For each activity, multiply the expected occurrences in the period by its estimated duration, then sum the activity hours for that account. Use the manager’s calendar or time records for comparable work; where there is no record, mark the estimate as an assumption and update it after the work occurs.

Calculate available hours for the period as rostered work hours minus leave, shared programmes, internal work and any time reserved for exceptions. Compare total account demand with those available hours, then repeat the comparison for shorter intervals in which work clusters. The planned caseload is the accounts whose estimated hours fit capacity across the period and its peaks.

Add shared programmes, internal work, leave and an explicit allowance for exceptions to the worksheet. Use the team’s observed work where available, mark new estimates as assumptions and revise them after real cases.

Workload peaks across a quarter

  • Week 1–4: Renewal prepHigh demand for contract reviews and stakeholder alignment
  • Week 5–8: Implementation phaseMultiple customer decisions and coordination tasks due
  • Week 9–12: Outcome review & planningFollow-up on KPIs, goal setting for next quarter

Key inputs for caseload planning

  • Expected work: Which customer decisions or reviews are due?Yes
  • Manager time: What preparation, meeting, follow-up and internal coordination will they create?Yes
  • Timing: Could several accounts peak together?Yes
  • Dependencies: Which tasks rely on specialists or customer owners?Yes
  • Uncertainty: Which estimate could change quickly?Yes

Rebalance the work

The load does not fit when estimated manager hours exceed available hours in the period or in a peak interval. Identify the account activities creating the excess, then recalculate after changing their timing or assignment.

Where customer commitments allow, shift an activity away from a peak or reassign an account to a manager with available time. A repeatable question may suit shared guidance or a pool; a continuing decision across several teams may need a coordinator with protected time, while a technical backlog needs a service owner.

When moving an account, transfer its goals, open decisions and customer update commitments. Include those commitments in the receiving manager’s estimate and check that their period and peak capacity still fit.

At the next planning review, compare estimated with actual preparation and follow-up, not only meeting time. Look for work repeatedly missed in the estimate and customer actions delayed by the load, then adjust the assignment or time estimates using that evidence.

More from Adoption