Review a project schedule for bottlenecks

Spot fragile dependencies, compressed testing buffers, and optimistic estimates hidden inside a draft project schedule.

Prompt

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

Example for: an e-commerce platform migration timeline planned over 8 weeks

Executive Risk Summary

The proposed 8-week schedule contains significant exposure in testing and vendor data migration. Handoffs between database extraction and QA have zero buffer, meaning any migration error will immediately delay launch. Additionally, client sign-off is budgeted for only 24 hours, which is historically unrealistic for enterprise reviews.

Critical Bottlenecks
Task NameRisk FactorSeveritySuggested Fix
Product Data Migration1-day allowance for 50,000 SKUs with no schema dry runHighAdd a 2-day dry run in Week 4 to validate mapping earlier
QA and Bug RemediationOnly 3 business days reserved before production releaseHighExpand testing window to 6 days; shift non-essential tasks post-launch
Payment Gateway SetupDependent on external merchant account approvalMediumSubmit merchant verification documents immediately in Week 1
Executive Acceptance1 business day allocated for UAT sign-offMediumExpand to 3 business days to prevent last-minute blocking
Missing Milestones and Hidden Dependencies
  • No rollback testing window scheduled before going live.
  • Missing load and stress testing milestone for payment gateway concurrency.
  • DNS propagation window is omitted from the cutover plan.
Recommended Schedule Adjustments
  1. Extend overall timeline from 8 weeks to 9.5 weeks to absorb QA fixes.
  2. Conduct data migration script tests concurrently during Week 3 instead of Week 6.
Written by AI from this prompt. Your results will vary.

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.

Keep exploring

More in Project Management
Project Management

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.