Planner Inputs
Fill the fields below, then submit to generate your plan.
Formula used
This planner combines effort with capacity:
- Baseline Effort (hours) = Total Effort or Tasks × Avg Hours
- Adjusted Effort = Baseline × (1 + Buffer%) × Risk Multiplier
- Net Hours/Person/Day = Daily Hours − (Meetings/Week ÷ Workdays/Week)
- Effective Team Hours/Day = Team × Net Hours × Efficiency% × (1 − ContextSwitch%)
- Workdays Needed = Adjusted Effort ÷ Effective Team Hours/Day
- Finish Date adds the required workdays using the selected workweek pattern.
How to use this calculator
- Enter a project name and, if possible, a start date.
- Choose an effort method: provide total effort hours, or provide tasks and average hours per task.
- Set your team size, daily hours, workdays per week, and expected weekly meeting time.
- Adjust efficiency, context switching, buffer, and risk to match real conditions.
- Press Submit to view results above the form, then download CSV or PDF.
Example data table
Use “Use Example” to auto-fill these values.| Project | Tasks | Avg hrs/task | Team | Daily hrs/member | Meetings hrs/week | Efficiency | Buffer | Risk |
|---|---|---|---|---|---|---|---|---|
| Website redesign | 80 | 2.5 | 3 | 6 | 4 | 80% | 15% | 3 |
Example result expectation: around 16–20 workdays, depending on overhead and focus.
Effort Inputs That Stay Honest
Start with either a direct effort estimate or a task count with average hours per task. For example, 80 tasks at 2.5 hours creates 200 baseline hours before any adjustments. When you enter total effort hours, the planner treats it as the baseline and skips the task conversion, helping you keep estimates consistent across teams and project phases. For early discovery work, try a smaller batch of tasks and update the average after two iterations for accuracy.
Capacity That Matches Real Days
Daily capacity is not the same as the workday length. The calculator subtracts meeting time, then applies efficiency and focus. With 3 people, 6 hours per day, 4 meeting hours weekly, and a 5 day week, each person loses 0.8 hours daily to meetings. Net time becomes 5.2 hours, then efficiency and context switching scale it to an effective team throughput. If you run a six day week, the same meetings spread thinner, increasing net hours and shortening timelines overall.
Risk, Buffer, And Focus Loss
Buffers protect delivery when scope shifts and dependencies slip. A 15 percent buffer adds planned slack without hiding risk. Complexity applies a multiplier from 1.00 to 1.28, so a high risk project may need 28 percent more effort than the baseline. Context switching models fragmentation; moving from 10 to 20 percent can noticeably extend the schedule even if effort stays fixed.
Deadline Feasibility Check
When you add a deadline, the planner counts workable days between start and deadline using your chosen workweek pattern. It then computes required team hours per day and compares that value to your effective capacity. A positive delta means the plan is feasible; a negative delta signals you should raise staffing, reduce overhead, or trim scope.
Turning Results Into Action
Use the estimated workdays and finish date to set milestones and reviews. If tasks per workday look too aggressive, split tasks further or increase buffer. Teams often operate with 70 to 85 percent efficiency and 3 to 8 meeting hours weekly; tune inputs to reflect your norms. Export the report to share assumptions, track changes, and revisit estimates after each sprint or major handoff.
FAQs
What if I only know total effort hours?
Enter total effort hours and leave task fields empty. The planner will treat that number as baseline effort, then apply buffer, risk, meetings, efficiency, and focus to estimate workdays and a finish date.
How is the finish date calculated?
If a start date is provided, the tool converts estimated workdays into a calendar finish date using your selected workdays per week. Non working days are skipped for 5 and 6 day schedules.
Why do meetings reduce capacity?
Meeting hours are spread across the workweek and subtracted from daily hours for each member. This prevents overestimating delivery time when recurring syncs, reviews, and planning consume working hours.
How should I set the efficiency percent?
Use 70–85% for most knowledge work. Higher values fit stable, repeatable tasks; lower values fit onboarding, heavy review, or shifting requirements. Adjust after observing actual throughput for one iteration.
What does risk complexity change?
Risk complexity increases adjusted effort using a multiplier. Low complexity keeps effort close to baseline, while very high complexity adds more allowance for uncertainty, integration, and rework that is hard to predict.
Can I share results with my team?
Yes. After submitting, download CSV for spreadsheets or PDF for quick sharing. Exports include your inputs and key results, making assumptions visible and easier to review during planning and updates.