Calculate three-point task duration estimates
Convert optimistic, most likely, and pessimistic day estimates into PERT weighted averages and standard deviations. Use it for project planning.
You getA Markdown calculation table with columns, total Estimated Duration and estimation Confidence Commentary
Prompt
Act as a project estimation expert. Calculate three-point PERT estimates for the list of tasks provided below.
Follow these rules:
- Calculate the Expected Duration (E) for each task using the standard formula: E = (Optimistic + 4 * Most Likely + Pessimistic) / 6.
- Calculate the Task Standard Deviation (SD) using: SD = (Pessimistic - Optimistic) / 6.
- Round all calculated values to one decimal place.
- Sum the expected durations to show the total expected timeline for the entire batch.
Output format:
1. A Markdown calculation table with columns: Task Name, Optimistic (O), Most Likely (M), Pessimistic (P), Expected Duration (E), Standard Deviation (SD)
2. Total Estimated Duration (sum of E values in days)
3. Estimation Confidence Commentary (noting which task carries the widest variance and highest delivery risk)
My raw tasks with their three time estimates are below:Example output
In ChatGPT, Claude, or Gemini, paste the prompt followed by your tasks and their 3 estimate numbers (e.g., Task 1: 3, 5, 12 days). Ask as a follow-up: 'What is the 95% confidence interval for this overall project timeline?'
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Audit project estimates for hidden optimism bias
Spot hidden assumptions, under-budgeted handoffs, and optimistic delivery timelines within detailed project task breakdowns.
Build a realistic buffer strategy for uncertainty
Calculate and place project buffers based on risk drivers rather than arbitrary task padding, protecting your schedule without inflating delivery dates.
Calculate critical path and task float
Identify sequence bottlenecks and calculate total float to see which delayed tasks directly shift your final delivery date.
Analyze timeline and budget trade-offs for scope requests
Turn vague stakeholder feature requests into clear trade-off scenarios. Use this when clients or leaders request additions without considering cost or delay.
Diplomatic pushback against scope creep
Draft a polite, professional response that acknowledges an out-of-scope request, explains project tradeoffs, and offers clear paths forward.
Audit a RACI chart for split accountability
Identify dangerous governance flaws, duplicate owners, and delivery bottlenecks in an existing RACI matrix. Use this before launching high-stakes projects.