Project plan template with a ready Gantt timeline
You have a deadline, a team and a list of things in your head. This prompt has your todo.is agent turn them into a real project plan: scope, work breakdown, a dated timeline with dependencies, owners, risks and a budget, in a spreadsheet you can update every week.
The prompt
- Create a project plan for [PROJECT NAME AND GOAL]. It starts on [START DATE] and must finish by [DEADLINE]. The team: [TEAM MEMBERS AND ROLES]. Budget: [BUDGET OR NONE]. What I know so far: [SCOPE, KNOWN TASKS AND CONSTRAINTS]. Include: goal and success measures, in scope and out of scope, phases and milestones, a task list with owner, start date, end date, duration and dependency, a simple Gantt chart, a risk register (risk, likelihood, impact, mitigation, owner), budget by phase, and a weekly status-update format. Flag any part of the timeline that looks too tight. Deliver an Excel file (tasks and Gantt on one sheet, risks and budget on others) and a 2-page Word summary for stakeholders.
What to change
- [PROJECT NAME AND GOAL]: e.g. "Move our online store to a new platform without losing sales".
- [START DATE]: e.g. "January 5, 2027".
- [DEADLINE]: e.g. "March 31, 2027", or "as soon as realistic".
- [TEAM MEMBERS AND ROLES]: e.g. "Maya (PM), Jo (developer, 50%), external designer".
- [BUDGET OR NONE]: e.g. "$25,000" or "internal time only".
- [SCOPE, KNOWN TASKS AND CONSTRAINTS]: Notes are fine, or attach a brief, proposal or meeting notes.
Example result
- Project: Store platform migration
- Goal: move the Linden & Co online store to a new platform by March 31 with no more than 2 hours of downtime.
- Success measures: all 1,200 products and customer accounts moved, conversion rate back to normal within 2 weeks, SEO traffic loss under 5%.
- Scope
- • In: products, customers, order history, redirects, payment and shipping setup, theme
- • Out: new loyalty program, mobile app (phase 2)
- Phases and milestones
- 1. Discovery (Jan 5 to Jan 16): requirements signed off
- 2. Setup and design (Jan 19 to Feb 13): theme approved
- 3. Data migration (Feb 2 to Feb 27): test import 100% clean
- 4. Testing (Mar 2 to Mar 20): no critical bugs open
- 5. Launch (Mar 23 to Mar 31): live, redirects verified
- Sample tasks
- • Export product data | Jo | Feb 2 to Feb 4 | depends on: platform account
- • Map old URLs to new URLs | Maya | Feb 9 to Feb 13 | depends on: product export
- • Test checkout on 5 devices | Jo | Mar 9 to Mar 11 | depends on: payments setup
- • Launch night cutover | Jo + Maya | Mar 24 | depends on: sign-off
- Tight spots
- • Data migration and theme design overlap while Jo is at 50%. Consider moving the theme to the external designer fully.
- • Only 3 days of buffer before the deadline. Suggest launching March 24, not March 30.
- Risk register
- • Redirects missed, SEO drops | likely | high | full URL map + crawl after launch | Maya
- • Payment setup delayed | possible | high | start provider approval in week 1 | Maya
- • Customer passwords cannot migrate | likely | medium | plan a friendly reset email | Jo
- Budget by phase (illustrative)
- • Discovery 5% | Design 35% | Migration 25% | Testing 15% | Launch 10% | Contingency 10%
- Weekly status format
- Done this week / Next week / Risks and blockers / Decisions needed / Overall: green, amber or red
How to do it with todo.is
- Copy the prompt and replace the brackets with your project, dates, team and budget.
- Paste it into todo.is and attach any brief, proposal or meeting notes you already have.
- Your agent builds an Excel plan with a Gantt sheet, risk register and budget, plus a short Word summary.
- Each week, send your agent what moved and ask it to update the plan and write the status report.
Tips for a better result
- Write down what is out of scope. It is the easiest way to stop scope creep later.
- Add a dependency to every task that waits on another. That is what shows you the real critical path.
- Keep 10 to 15% of time and budget as contingency. Plans without a buffer are usually late.
- Count part-time people at their real availability, not as full-time.
- Set a recurring to-do every Friday that asks you for progress and returns an updated status email draft.
project plan template: FAQ
- What should a project plan include? Goals and success measures, scope, milestones, a task schedule with owners and dependencies, risks, budget, and how progress will be reported.
- Is a Gantt chart necessary? Not always, but it helps when tasks depend on each other or several people work in parallel. For small projects, a dated task list can be enough.
- What is the difference between a project plan and a project proposal? A proposal asks for approval or funding and explains why the project matters. A plan explains how it will be delivered once it is approved.
- Can I open the plan in Google Sheets? Yes. The Excel file opens in Google Sheets, Excel or Numbers. Simple formulas and the Gantt bars made with cell colors carry over.
JavaScript is required to use the todo.is app.