20 Percent Time or Two Hours? Cost Your MSP Lab Time

Cost the Proposal on the Right Hours

The model begins with 2,080 paid hours a year. Dividing by 52 calendar weeks gives a 40-hour paid week, so a literal 20% allocation on that basis would be eight hours. The proposal here is two hours in each working week, not a model recommendation to allocate either percentage.

The model's available-hours input is 1,660 hours a year, based on deducting eight weeks off and 100 administrative hours from paid time.

For a hypothetical employee on that schedule, calculate working weeks as 52 minus eight, giving 44. Assume the proposed lab block runs for two hours in each of those weeks: 44 times two equals 88 scheduled lab hours, before any missed or changed sessions.

The model's service-utilization input is 70% of available hours. For this hypothetical employee, calculate 1,660 times 70% to get 1,162 service hours; subtract that from 1,660 to get 498 hours remaining for internal work. Check what is already planned there before subtracting the proposed lab time from service capacity.

In the hypothetical case where all 88 lab hours displace service work, subtract 88 from 1,162 to get 1,074 service hours. Dividing 1,074 by 1,660 gives about 64.7% service utilization. It is a worked capacity sensitivity, not a new target. Your actual cost depends on the sessions scheduled and the work they displace; if the time was already included, don't deduct it again.

Keep the Cash Budget Separate From the Time

The US model separately budgets $2,500 per person annually for training-related spending, including certifications, conference travel, and coaching membership. That allowance doesn't buy the technician extra working hours. Check the course or lab cost alongside the time required to use it.

The person's salary is already in payroll. Don't add the same salary again as a new cash expense because the calendar now says training. If you want an allocated labor value, have finance multiply the planned lab hours by burdened annual pay divided by available annual hours, keeping that basis explicit.

The capacity decision is separate. If lab time displaces service work, determine what will move or what cover will actually cost. Don't call every displaced hour lost hourly billing when the technician delivers a recurring service.

The model's position is to maintain healthy margins so the business can pay good people well. Budget this work within that operating plan. A training benefit that depends on hidden overtime or an unowned queue hasn't been fully planned.

Give the Lab a Task Someone Can Verify

Pick a task tied to work the team needs to perform on its standard stack. Write the intended demonstration before the session. Avoid assigning a broad topic such as learn the platform and leaving the technician to guess what completion means.

For a hypothetical example, the task could be practicing an approved recovery procedure in a suitable test environment. Name the expected result and the point where the technician should stop and ask for help. Keep live client changes outside the lab unless they are separately authorized through the normal process.

Ask for a usable output. That might be a corrected procedure or a demonstrated skill another person can check. Don't make course attendance the only evidence when the purpose was to improve delivery capability.

A course playing behind the ticket window is a screensaver with ambitions. Protect attention for the agreed work. If coverage repeatedly interrupts it, the manager needs to change the plan rather than tell the technician to be more committed.

Protect the Block With a Coverage Decision

Have the service lead and dispatcher choose the working slot against the real roster. Identify who receives new work while the technician is in the lab. Keep time for any reviewer or coach in the same capacity decision.

Define what can interrupt the block and who makes that call. If an actual service need displaces it, record the reason and decide whether to reschedule. A cancelled session shouldn't remain recorded as completed training.

Don't call the policy an innovation growth hack. State the task, the protected hours, and the person covering the queue. Those decisions are what make the benefit available in practice.

• The service lead owns the training priority and confirms that the work fits the capacity plan.
• The dispatcher owns the queue coverage and records a service interruption that displaces the block.
• The technician owns the agreed practice task and records what was completed or blocked.
• The reviewer owns the demonstration check and the specific feedback needed for the next attempt.
• The finance owner checks external spending and keeps allocated labor distinct from additional cash cost.

Look for a Return Without Inventing One

Start with evidence that the technician can perform the intended task using the maintained record. Review the result and note any prompts or corrections still needed. A certificate can be useful evidence of course completion without proving readiness for every client scenario.

Then inspect comparable work on the service desk. Keep the relevant task category and check the actual effort or escalation reason against the problem the lab addressed. A change in the mix of work can change the result even if the technician's skill hasn't changed.

Don't promise a fixed reduction in tickets or a guaranteed retention improvement. The model provides no return rate for this proposal. Record the output and the delivery change you observe, then examine other explanations before attributing it to the lab.

Use the existing service review to decide whether to continue the task, change the teaching approach, or choose the next skill. Keep a useful result available to the rest of the team. A procedure that only its author can follow still has work left in it.

Approve the Next Block With the Work Attached

Start with the proposed two-hour allocation and the real working weeks it will cover. Place it inside the existing internal allowance where that genuinely fits; otherwise show the service capacity it displaces. Make the queue-cover decision before the slot appears on the calendar.

Give the technician an observable task and a named reviewer. Record whether the time happened and what the person demonstrated. That gives you a funded practice plan to assess, rather than a percentage that looks generous in a job ad and disappears on the desk.