ChatGPT prompt for a project schedule

Create an execution-ready project schedule for [PROJECT]. The required outcome is [DELIVERABLE AND ACCEPTANCE CRITERIA], the deadline or target window is [DEADLINE], and the available people and constraints are [TEAM AND CONSTRAINTS]. Here is the work already known: [KNOWN WORK AND DEPENDENCIES].

Ask up to 3 clarifying questions only if a required input is missing, especially scope boundary, deadline, owner availability, approval lead time, or a dependency outside the team’s control. Then produce a schedule that can be copied into a project tracker.

Include:

1. Scope and milestones: define what is included, excluded, and the 4–7 measurable milestones. Each milestone needs a completion criterion, not just a date.
2. Work breakdown table: list work package, task, owner role, estimated effort, planned start, planned finish, predecessor, output, and status. Break work into tasks normally no longer than 5 working days; identify tasks that cannot be split.
3. Critical path: state the dependency chain that determines the earliest finish, plus tasks with little or no float.
4. Operating cadence: give the weekly status update format, decision log fields, and escalation trigger for a blocked task.
5. Risk register: list the five most likely schedule risks, early-warning signal, mitigation owner, and contingency.
6. First two weeks: specify the exact actions, owners, and decisions needed to establish the baseline.

Use working days and state assumptions about holidays, time zones, and parallel work. Do not assign a named person without my input; use role names where necessary. Do not disguise an impossible deadline: if estimates and dependencies do not fit [DEADLINE], show the gap and give scope, staffing, sequencing, or date options. Before answering, check that every task has one accountable owner, every milestone has acceptance criteria, and no task starts before its predecessors finish unless an explicit overlap is justified.

Create a schedule-recovery plan for [PROJECT] using [CURRENT STATUS], [ORIGINAL DEADLINE], and [REMAINING TEAM CAPACITY]. Identify completed work, remaining work, blocked work, and changed dependencies. Recalculate the critical path from today and quantify the schedule gap in working days. Offer three recovery options: scope reduction, resequencing or parallelization, and added capacity, with impact on quality, cost, risk, and final date. Recommend one option based on [PRIORITY]. Build a revised weekly schedule with owners and decision deadlines. Do not assume overtime or added staff unless stated.

Turn [PROJECT DETAILS] into a client-facing delivery timeline for [CLIENT]. Produce a one-page table with phases, client-visible deliverables, target dates, client responsibilities, approval windows, and dependency notes. Use plain language and avoid internal staffing estimates. Mark dates as tentative when they depend on [UNCERTAIN DEPENDENCIES]. Add a short change-control section defining how late feedback, added scope, or missing materials affect timing. Do not promise dates that conflict with the supplied plan. End with the next three client actions required to maintain the timeline.

Create a detailed run sheet for [EVENT] on [DATE] at [LOCATION OR PLATFORM]. Include setup, technical checks, speaker or presenter calls, attendee communications, live-program cues, contingency steps, teardown, and post-event follow-up. For each row give start time, duration, owner role, required materials, dependency, and backup action. Account for [TIME ZONES OR ACCESSIBILITY NEEDS] and build in decision points for go/no-go issues. Add a contact escalation tree using roles only. Before answering, check for impossible overlaps and ensure critical equipment or approvals are checked before guests arrive.