I need a practical project timeline for [PROJECT NAME AND OUTCOME]. Build it from these constraints: [SCOPE AND DELIVERABLES], [DEADLINE AND KEY DATES], [TEAM AND AVAILABLE CAPACITY], [KNOWN DEPENDENCIES AND RISKS], and [CURRENT PROJECT STATUS]. First, identify the critical path: the sequence of work that would move the final date if it slips. Separate true dependencies from work that can happen in parallel. Do not assign a task to a person who is not listed, and do not assume full-time availability unless I state it. Produce: 1. A short planning assumptions section, including any dates or capacity constraints that make the deadline unrealistic. 2. A timeline table in chronological order with workstream, task, single accountable owner, contributors, start date, finish date, predecessor, concrete completion criteria, and status. 3. Milestones at meaningful decision or handoff points, not merely calendar checkpoints. Include approval gates, testing, launch readiness, and post-launch follow-up when relevant. 4. A critical-path section showing the tasks that cannot slip and the latest safe decision dates. 5. A risk and contingency table with trigger, likely impact, owner, mitigation, and fallback plan. 6. A weekly operating rhythm: what the team reviews, who resolves blockers, and what changes require timeline reapproval. Use working days where possible and flag uncertainty instead of filling gaps with invented estimates. Before finalizing, check that every deliverable has an owner and acceptance criterion, and that no task starts before its required predecessor finishes. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [PROJECT NAME AND OUTCOME] | State the project and the measurable result it must produce. | Launch a customer referral program that can accept sign-ups and issue credits. |
| [SCOPE AND DELIVERABLES] | List what is included, excluded, and the concrete outputs due. | Landing page, referral rules, tracking, support playbook, and launch report; exclude new mobile-app work. |
| [DEADLINE AND KEY DATES] | Give the final deadline plus fixed events, approvals, or blackout periods. | Launch October 28; legal review by October 10; no production releases October 21-23. |
| [TEAM AND AVAILABLE CAPACITY] | List each available person, role, and any capacity limits. | Maya, product manager, 60%; Devin, engineer, 50%; Priya, designer, 30%; Lena, legal reviewer. |
| [KNOWN DEPENDENCIES AND RISKS] | List outside teams, approvals, systems, vendors, and likely risks. | Needs Stripe coupon setup and legal approval; tracking vendor may need five business days. |
| [CURRENT PROJECT STATUS] | Describe completed work, work in progress, and unresolved decisions. | Referral rules are drafted; design has not started; engineering estimate is pending. |
How to use
- Paste the prompt and replace every bracketed input with project facts.
- Check the critical path against known approval and vendor lead times.
- Confirm each row has one accountable owner and a measurable completion criterion.
- Follow up with: “Turn this into a weekly status template with red, amber, and green definitions.”
Variations
Executive roadmap
Use when leaders need decisions and tradeoffs rather than task-level detail.
Create an executive roadmap for [INITIATIVE] from [START DATE] to [END DATE]. Use [STRATEGIC GOALS], [MAJOR WORKSTREAMS], [DECISION MAKERS], and [KEY CONSTRAINTS]. Produce a one-page table with quarterly or monthly outcomes, decision gates, dependencies, investment needs, and the consequence of delay. Add a short section naming the three decisions leaders must make next. Do not invent budgets or dates; flag missing evidence. Check that each milestone represents an observable business outcome, not activity.
Agency timeline
Use when client approvals and deliverable handoffs drive the schedule.
Build a client-facing delivery timeline for [CLIENT PROJECT] using [DELIVERABLES], [CONTRACT DEADLINE], [CLIENT REVIEW PROCESS], and [AGENCY TEAM]. Produce a polished weekly schedule with agency responsibilities, client inputs, review windows, revision limits, acceptance criteria, and handoff dates. Include a assumptions section and a delay protocol that shows how late client feedback affects launch. Do not promise turnaround times unsupported by the inputs. Check that every approval has an owner and a deadline.
Recovery plan
Use when an existing project has slipped and needs a credible reset.
Create a recovery timeline for [PROJECT] after [WHAT SLIPPED]. Use [ORIGINAL PLAN], [WORK REMAINING], [CURRENT TEAM CAPACITY], and [FIXED COMMITMENTS]. Identify the actual causes of delay, then give three options: protect scope, add capacity, or move the date. For each, show revised milestones, risks, and decisions required. Recommend no option unless the evidence supports it. Check that the revised schedule includes testing, approvals, and contingency rather than compressing them away.
Tips
- Build the timeline around acceptance criteria such as “legal-approved referral terms published,” not vague verbs such as “complete legal.”
- Treat review periods as tasks with owners and due dates; approval queues are often the real critical path.
- Give one person accountability for each task even when several people contribute.
- Keep contingency attached to a specific risk trigger, such as a vendor setup not completing by a stated date.
FAQ
Should a project timeline include every small task?
Include tasks that create a handoff, decision, dependency, or meaningful risk. Keep personal to-do items in the team’s execution tool.
How do I handle uncertain estimates?
Use ranges or explicit assumptions and identify the date when the estimate must be validated. Do not present a guessed date as committed.
Can AI choose the project owners?
It can propose roles based on the people you provide, but accountability should be confirmed by the project sponsor or team lead.