Build an execution-ready project timeline for [PROJECT NAME]. The objective and success measure are: [OBJECTIVE AND SUCCESS MEASURE]. The deadline or target launch date is [TARGET DATE]. Use this context: - Scope, deliverables, and exclusions: [SCOPE] - People, roles, availability, and decision maker: [TEAM AND CAPACITY] - Known dependencies, constraints, and risks: [DEPENDENCIES AND RISKS]
- Current date or planned start date: [START DATE]
First, identify the critical path: tasks that cannot slip without moving the target date. Then produce a timeline table with these columns: workstream, task, owner, start, finish, dependency, deliverable or acceptance criterion, and status. Break work into meaningful handoffs rather than vague phases. Include discovery or requirements sign-off, build or production, review, approval, launch or handover, and a contingency buffer where they apply.
Use realistic sequencing. Do not assign the same person overlapping full-time work without flagging a capacity conflict. If dates are uncertain, state assumptions and use relative timing rather than false precision. Add a milestone list with a decision owner and the consequence of missing each decision date.
Finish with: the top five risks; a weekly update format containing done, next, blocked, and decision needed; and a short “first 7 days” action list. Ask up to 3 clarifying questions only if a required input is missing.
Before answering, verify every task has one accountable owner and a completion test, and check that dependencies run in a possible order with no circular or impossible dates.Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [PROJECT NAME] | Enter a short name for the project. | Customer onboarding refresh |
| [OBJECTIVE AND SUCCESS MEASURE] | Enter the outcome to achieve and how the team will know it succeeded. | Launch a new onboarding email series; increase trial-to-activated rate from 34% to 42% within 60 days |
| [TARGET DATE] | Enter the fixed deadline or intended launch date. | November 18, 2026 |
| [SCOPE] | Enter the deliverables, major work, and explicit exclusions. | Audit current emails, write six emails, design templates, configure HubSpot workflow, QA and launch; excludes in-app onboarding changes |
| [TEAM AND CAPACITY] | Enter each contributor's role, availability, and the person who makes final decisions. | Avery: lifecycle marketing, 60%; Priya: copywriter, 50%; Nolan: designer, 30%; Mei: marketing ops, 25%; Avery approves final copy |
| [DEPENDENCIES AND RISKS] | Enter known approvals, vendors, systems, deadlines, and likely sources of delay. | Need product analytics event list by October 22; legal review for claims; HubSpot template approval; designer unavailable November 3-7 |
| [START DATE] | Enter the current date or planned project start date. | October 14, 2026 |
How to use
- Write the scope as deliverables and exclusions, not a broad project name.
- Paste the completed prompt and compare the critical path with the dependencies you already know.
- Confirm each named owner accepts the task and that their finish date precedes the dependent task's start.
- Follow up with: “Replan this timeline if the analytics event list arrives one week late, showing the new critical path.”
Variations
Executive roadmap
Use when leaders need milestones and choices rather than a task-level plan.
Create a one-page executive roadmap for [INITIATIVE] from [START DATE] through [TARGET DATE]. The intended outcome is [OUTCOME]. Organize it into [NUMBER] phases with milestone dates, accountable executive, required decision, key dependency, and measurable exit criterion. Use these constraints: [CONSTRAINTS]. Show only decisions and milestones that change timing, budget, or scope. Flag assumptions and the two largest schedule threats. Verify that each milestone has one decision owner and a measurable result.
Client timeline
Use when sharing an implementation plan with a client or external partner.
Draft a client-facing implementation timeline for [PROJECT] starting [START DATE] and targeting [GO-LIVE DATE]. Include [DELIVERABLES], the responsibilities of [OUR TEAM] and [CLIENT TEAM], and these dependencies: [DEPENDENCIES]. Present weekly or dated milestones, client review windows, acceptance criteria, and the effect of late client inputs. Keep internal staffing details out. Flag dates that depend on unconfirmed client actions. Check that every requested client action has a deadline and named owner.
Recovery plan
Use when a project is behind schedule and needs an honest revised plan.
Create a project recovery timeline for [PROJECT]. Original target: [ORIGINAL DATE]. Current status and completed work: [CURRENT STATUS]. Remaining work, owners, and dependencies: [REMAINING WORK]. Constraints: [CONSTRAINTS]. Identify the schedule variance, propose a realistic revised critical path, and give three options: preserve scope, reduce scope, or add capacity. For each, state impact on date, risk, and required decision. Do not hide missed work. Check that revised dates respect dependencies and actual owner availability.
Tips
- Set acceptance criteria at handoffs, such as “legal-approved copy in the shared folder,” rather than marking a task complete when someone says it is done.
- Keep a decision deadline separate from the final deadline; late approvals are a common hidden critical-path risk.
- Use one accountable owner per task even when several people contribute, or blockers will have no clear escalation path.
- Add a buffer before launch for QA and rollback planning instead of treating the launch date as the final production date.
FAQ
How detailed should a project timeline be?
Include enough detail to expose handoffs and dependencies. A task should normally produce a concrete artifact, approval, or operational state.
What is the critical path?
It is the sequence of dependent tasks that determines the earliest possible completion date. Delaying any task on it delays the project unless something else changes.
Should every task have dates?
Use dates where commitments are known. For uncertain work, use estimates with stated assumptions and revisit them at a regular cadence.