Most peptide businesses decide to hire remote support for one of two reasons: someone is overloaded, or a queue keeps slipping. Both are real signals, but neither tells you how much capacity you actually need. Capacity planning turns those signals into a number you can act on.
The method is straightforward: measure the work, convert it to time, add a buffer, and compare it to available hours. It does not require perfect data, only honest estimates that you refine over time.
Step 1: List the queues
Write down every recurring administrative queue, not every task. A queue is a stream of similar items: new booking requests, intake forms, follow-up tasks, inbound messages, authorization updates, and document routing. Grouping by queue keeps the estimate manageable.
Step 2: Measure a realistic period
Pick a representative period, two to four weeks is usually enough. For each queue, record:
- Total items received.
- Items completed.
- Items still open at the end.
- Peak-day volume.
Peak matters as much as average. A queue with a manageable average can still overwhelm the team every Monday.
Step 3: Estimate time per item
Time each task type on a sample of real work, or ask the person doing it for an estimate and verify with a stopwatch on a handful of items. Record three numbers:
- Touch time, active minutes per item.
- Wait time, time the item sits waiting on someone else (not capacity-consuming, but relevant to turnaround).
- Rework time, minutes spent correcting or redoing items.
Only touch time and rework time consume capacity. Wait time affects turnaround and should be tracked separately.
Step 4: Convert to hours
For each queue: items per week × touch time (minutes) ÷ 60 = weekly hours. Add rework. Then sum across queues. For example:
- 60 booking requests × 8 minutes = 8.0 hours
- 40 intake forms × 12 minutes = 8.0 hours
- 90 inbound messages × 4 minutes = 6.0 hours
- 25 follow-up tasks × 10 minutes = 4.2 hours
- Total: about 26 hours per week
Step 5: Add a service buffer
Do not plan to 100 percent utilization. Add a buffer for breaks, training, absence, and the interruptions that always exist. A common starting buffer is 20 percent, and higher for queues with unpredictable spikes. In the example above, 26 hours plus 20 percent is about 31 hours per week.
Step 6: Compare to available capacity
Now compare the required hours with what the current team can actually devote to these queues. Be honest about how much of a person's day is already absorbed by other work. If required hours exceed available hours by a small margin, redistribution may solve it. A large, persistent gap is a case for adding coverage.
Step 7: Re-check after four weeks
Estimates drift. After a month, compare actual volumes and times to your assumptions. If one queue is consistently larger than estimated, that is your next process-improvement target, not necessarily another hire.
A worked example
A peptide clinic tracks four administrative queues for three weeks. Total estimated workload is 26 hours per week with a 20 percent buffer, rounding to 31 hours. The current coordinator has about 20 hours available for these queues after other duties. The gap is roughly 11 hours, which is not enough to justify a full-time role but is more than redistribution can absorb. The clinic starts with a part-time remote owner for two queues, then reviews after a month. That is a decision grounded in numbers rather than a feeling.
Checklist: capacity estimate
- Queues listed, not individual tasks.
- Representative period chosen (2-4 weeks).
- Volume and peak-day data collected.
- Touch, wait, and rework times estimated.
- Weekly hours calculated per queue.
- Service buffer applied.
- Available capacity stated honestly.
- Gap size compared with options (redistribute, redesign, add coverage).
- Decision reviewed after four weeks.
- Estimates updated with actual data.
Decide from the gap, not from the stress
Once you have a gap number, the choice becomes clearer. A small gap that appears only on peak days may call for batching, better templates, or a shared queue rather than more hours. A sustained gap across normal weeks points to added coverage. A gap concentrated in one queue suggests that queue needs a dedicated owner while others can stay consolidated. Writing the reasoning down also gives you a fair way to evaluate the change later: you can compare the new arrangement against the volumes and times that justified it.
Common mistakes
- Planning to 100 percent utilization. No team sustains it, and the first absence breaks the plan.
- Ignoring peak days. Averages hide the days that cause burnout.
- Counting wait time as capacity. Waiting is not working; conflating the two inflates the case for hiring.
- Never re-measuring. An estimate without a review becomes an assumption.
Capacity planning is not about justifying a hire. It is about giving you the options, redistribute, redesign, or add coverage, with enough evidence to choose. For the role-design side, see Practice Administration and Appointment Scheduling.
Sources and further reading
- Society for Human Resource Management: https://www.shrm.org/
- American Society for Quality (process measurement and improvement): https://asq.org/
- Harvard Business Review: https://hbr.org/
Ready to Give the Workflow an Owner?
Discuss a remote operations role built around your workflow, systems, access requirements, and decision boundaries.
Talk with a Staffing Specialist