Plan one repeatable release.
Start with one unit: an episode, an article or a defined release package. Use one row per person and combine all their tasks. The starting values are an illustrative team, not a recommended staffing ratio.
Inputs stay in this page and are not saved by the tool. Copy your assumptions into the project plan before leaving.
Calculate the capacity for each person.
For each person, multiply available weekly hours by the share left after the buffer. Divide that by their hours per release. The smallest result limits the team; round it down to complete releases.
In the starting example, the editor has 24 hours and a 20% buffer, leaving 19.2 hours. At eight hours per release, that is 2.4 releases. The writer can support 3.2 and the reviewer four, so the estimate is two complete releases per week. The editor has 3.2 hours left after those two releases.
A person doing both research and writing belongs in one row with the combined time. Listing them twice as two independent roles would overstate the hours available.
Check the assumptions before making a promise.
This estimates steady weekly capacity. It does not schedule dependencies, waiting for approval, holidays or the elapsed time to finish the first release. Those belong in the actual production plan. An estimate of zero complete releases means the entered hours do not finish a whole release within one week; work may carry across weeks.
Use measured working time where you have it. Include the usual review and revision effort in hours per release; leave the buffer for uncertainty. A mixed slate needs a defined package or a separate resource plan, because a podcast and a short do not necessarily consume the same work.
The assumptions worksheet preserves the release definition, people, estimate and unresolved dependencies for the next planning conversation.
Questions about the work.
What does the buffer do?
It reserves a percentage of each person’s available project hours before calculating capacity. The 20% starting value is an editable example, not a benchmark for every team.
Why can spare hours remain when the team is at capacity?
Work is constrained by the limiting person and rounded to complete releases. Spare writing time cannot automatically replace editing time. Use the result to discuss task allocation, scope or the next release.
Can I plan several formats at once?
Define a repeatable package, such as one episode plus two original shorts, and enter each person’s combined hours for that package. For an irregular mix, use a resource schedule that assigns hours to each actual job.
Tell us what you want to make.
Tell us about the channel or idea, the team you have and where you need help. We’ll discuss the scope on a 30-minute call.
Book a 30-minute call rishwajeet@machinehouse.media