Review a project schedule for bottlenecks
Spot fragile dependencies, compressed testing buffers, and optimistic estimates hidden inside a draft project schedule.
Prompt
Act as a PMO audit director. Review the draft project schedule below to identify scheduling risks, unrealistic task durations, and points of failure.
Rules:
- Identify zero-buffer handoffs where a single delay will directly push the launch date.
- Check for overloaded roles or departments assigned to simultaneous critical tasks.
- Flag missing operational buffers, particularly around quality assurance, client reviews, and deployment prep.
- Note any external third-party dependencies that lack lead-time buffers.
Output format:
Executive Risk Summary (3-4 sentences)
Critical Bottlenecks (table: Task Name, Risk Factor, Severity, Suggested Fix)
Missing Milestones and Hidden Dependencies list
Recommended Schedule Adjustments
My draft schedule is below:Example output
Paste this prompt into Claude, ChatGPT, or Gemini followed by your timeline, Gantt task list, or sprint roadmap. If the schedule involves vendor deliveries, ask the model to specifically review procurement lead times.
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
Flag unstated project assumptions before kickoff
Surface hidden assumptions about resources, data access, and vendor dependencies before projects stall mid-flight.
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.
Evaluate schedule compression using crashing and fast tracking
Assess schedule acceleration tradeoffs across cost, risk, and dependencies. Use this when facing hard completion deadlines to avoid unplanned rework and budget overrun.
Draft a one-page project kickoff brief
Turn fragmented launch details into an aligned single-page kickoff document. Ideal for aligning cross-functional teams before delivery starts.
Extract continuous phase-gate lessons from sprint notes
Identify recurring delivery risks and early project friction from sprint summaries before problems get buried at the final closeout.