Support coaching-capacity budget
Calculate the coaching time a lead actually has after queue work and other commitments, compare it with agreed development needs, and make the trade-off explicit.
A recurring invitation does not create coaching capacity. If the lead is also clearing escalations, covering a queue and interviewing candidates, the same hours may already have several owners.
Use this budget when a team grows, a player-coach takes on queue work, or development conversations repeatedly slip. It complements the coaching 1:1 template: that template helps run the conversation; this one tests whether the work around it has room to happen.
1. Agree the planning boundary
Work with the lead rather than reconstructing their week from surveillance. Use scheduled working hours after agreed leave and other availability adjustments. Record planned and observed work separately. Do not count evenings or skipped breaks as spare capacity.
| Planning field | Fill in |
|---|---|
| Lead, team and week | [names / dates] |
| Scheduled available hours | [hours / basis] |
| Reports and relevant support needs | [count / onboarding / complexity / accommodations] |
| Queue and escalation responsibilities | [scope / coverage commitment] |
| Coaching definition | [conversation / observation / preparation / follow-up] |
| Review owner and date | [manager / date] |
Keep confidential development details in their appropriate records. The shared budget needs time and task categories, not private performance narratives.
2. Copy the weekly time ledger
Use mutually exclusive categories. If QA review prepares a coaching conversation, count that time once and say where.
| Commitment | Planned hours | Observed hours | Evidence or assumption | Can it move? / decision owner |
|---|---|---|---|---|
| Personal customer queue | [ ] | [ ] | [roster / workload] | [owner] |
| Escalations and incident cover | [ ] | [ ] | [recent pattern / allowance] | [owner] |
| Meetings and operating reviews | [ ] | [ ] | [calendar] | [owner] |
| QA work outside coaching preparation | [ ] | [ ] | [scope] | [owner] |
| Hiring, onboarding and administration | [ ] | [ ] | [planned work] | [owner] |
| Other committed work | [ ] | [ ] | [description] | [owner] |
| Explicit unplanned-work allowance | [ ] | [ ] | [reason / avoid double count] | [owner] |
| Total non-coaching commitments | [sum] | [sum] |
Available coaching hours = scheduled available hours − total non-coaching commitments.
Keep a negative result visible. It describes overcommitted work before coaching begins; replacing it with zero would hide the size of that problem.
3. Estimate coaching demand
Agree the development goal and cadence with each person. Different needs can justify different activities and durations; this table is not a universal meeting quota.
| Person or confidential reference | Activity and agreed cadence | Sessions this week | Conversation / observation minutes | Preparation minutes | Follow-up minutes | Total hours |
|---|---|---|---|---|---|---|
| [reference] | [activity / cadence] | [n] | [m] | [m] | [m] | [n × sum of minutes ÷ 60] |
Total demand is the sum of the last column. Capacity gap = total demand − available coaching hours. A positive gap requires a decision; a negative gap leaves time that may be useful for uncertainty or other work.
For fortnightly activity, plan the actual scheduled week or average over two named weeks. Do not quietly assume every week receives half a session.
4. Fictional worked example
All figures are invented. A lead has 40 available hours. Queue work consumes 16, escalations 6, meetings 5, other QA 3, and hiring/administration 4. Those commitments total 34 hours, leaving 6 for coaching.
Twelve people each have one planned session requiring 30 minutes together, 10 minutes of preparation and 5 minutes of follow-up. Demand is 12 × 45 ÷ 60 = 9 hours. The gap is 3 hours.
| Scenario | Non-coaching hours | Available coaching | Demand | Gap |
|---|---|---|---|---|
| Current 12 reports | 34 | 6 | 9 | 3 |
| Add 2 reports with the same planned activity | 34 | 6 | 10.5 | 4.5 |
| Remove 4 queue hours with agreed replacement coverage | 30 | 10 | 9 | -1 |
The third scenario only works if someone owns the displaced queue coverage. It does not create free labor or establish that twelve reports is an appropriate span for every team.
5. Record the trade-off
| Decision | Work reduced, reassigned or added | Receiving owner / coverage | Effective date | Check after two actual weeks |
|---|---|---|---|---|
| [change] | [hours and task] | [accepted responsibility] | [date] | [sessions delivered / quality / queue consequences] |
Possible decisions include removing low-value meetings, moving recurring administrative work, adding coverage or changing development activities with the affected people. Do not relabel a rushed status update as coaching just to make the ledger balance. Revisit the budget when an incident, hiring wave or cohort of new starters changes the work.
Sources and limits
The U.S. Office of Personnel Management performance-management cycle treats ongoing monitoring and employee development as management work. The team lead and support manager guides describe the support-specific remit. This original worksheet makes time assumptions visible; it does not establish an ideal span, prove coaching effectiveness from hours alone or replace individual support and workload discussions.
Continue exploring