Turn your project details into useful planning templates with 10 free, editable AI prompts. Create project charters, task plans, timelines, budgets, risk registers, status reports, and more. Each prompt includes clear placeholders and output instructions, making it easy for beginners to customize the results for their own projects.

What this prompt pack does

• Creates tailored project management templates from your goals, team details, deadlines, and budget.
• Organizes tasks, responsibilities, risks, communication, and approval decisions into editable tables and checklists.
• Helps you track progress and prepare clear status reports, change requests, and project handovers.

Tips for this prompt pack

• Add specific deliverables, team availability, and constraints so the templates reflect your actual project.
• Write “unknown” when information is missing, then review the AI’s assumptions, calculations, and suggested assignments.
• Keep your project details consistent across prompts; reuse the charter and task list when generating later templates.

How to use the prompts

• Choose the template you need and copy its complete prompt into your preferred AI chat tool.
• Replace every [bracketed placeholder] with your details, or write “unknown,” then submit the prompt.
• Answer follow-up questions, review the draft, and copy the finished template into your document or spreadsheet.

 10 Free Prompts for Project Management Templates

Replace the text inside [square brackets] with your project details. If you do not know an answer, write “unknown.” Each prompt works independently, and you can reuse earlier outputs in later prompts.

1. Project Charter and Scope Template

Act as a project planning assistant. Create an editable project charter that helps a small team agree on what we are delivering.

My project details:

• Project name and type: [name; website launch, client campaign, event, etc.]
• Problem to solve and intended result: [details]
• People who will use or benefit from the result: [audience]
• Project manager, sponsor, and team: [names or roles]
• Target start and finish dates: [dates]
• Available budget and currency: [amount and currency]
• Required deliverables: [list]
• Work explicitly outside this project: [exclusions]
• Main constraints: [staff availability, tools, approvals, etc.]

Create these sections:

1. A plain-language project overview of no more than 100 words.
2. A table separating included work from excluded work.
3. A success-measures table: Goal | Current baseline | Target | How we will check it.
4. A deliverables table: Deliverable | Acceptance criteria | Approver.
5. A milestone table with target dates, followed by assumptions and decisions still needed.

Keep the charter concise and easy to edit. Do not invent budgets, dates, approvals, or measurable targets. Use “To confirm” for missing facts and label suggested targets as proposals.

If the intended result or deliverables are too unclear to draft meaningfully, ask up to three focused questions first.

2. Project Task Breakdown and Action Plan

Act as a practical project coordinator. Turn my project into an editable task plan that shows exactly what needs to happen.

My inputs:

• Project objective: [objective]
• Deliverables or project charter: [paste details]
• Team members, skills, and availability: [details]
• Deadline: [date]
• Tools or working method: [details]
• Maximum preferred task size: [number of work hours]
• Known approvals and constraints: [details]

Group the work into phases and create a table with:

Task ID | Phase | Deliverable | Specific task | Owner | Estimated effort in hours | Predecessor task IDs | Priority | Status | Definition of done.

Use action verbs and break large tasks into smaller steps. Include relevant review, testing, approval, and handover work. Define “done” with a checkable result, such as an approved document or a completed test.

Distinguish effort hours from elapsed calendar time. Use only valid task IDs for dependencies and check that there are no circular dependencies. Label estimated effort and proposed owners clearly; use “Unassigned” when no suitable owner is known.

Finish with the first three actions to take and a short list of missing information that could change the plan. Do not add deliverables beyond the supplied scope.

3. Project Timeline and Milestone Schedule

Act as a project scheduler. Build an editable schedule from my task list and show whether my deadline is realistic.

My inputs:

• Project start date: [date]
• Target completion date: [date]
• Tasks, owners, effort estimates, and dependencies: [paste task list]
• Working days and hours: [e.g., Monday–Friday, four project hours per person per day]
• Team availability and other commitments: [details]
• Holidays or unavailable dates: [dates]
• Review and approval waiting times: [details]
• Fixed milestones: [deliverable and date]

Create a schedule table:

Task ID | Task | Owner | Duration in working days | Predecessors | Proposed start | Proposed finish | Milestone or deliverable.

Explain how you converted work hours into duration using each person’s availability. Schedule dependent tasks after their predecessors finish unless I explicitly allow overlap. Include approval waiting time and avoid assigning more work than a person’s stated capacity.

Add a compact weekly view showing the main work and milestones. Compare the proposed finish with my target date. If the deadline cannot be met, show the gap and two realistic adjustment options with tradeoffs.

Do not invent missing estimates. Mark dates affected by missing inputs as provisional and identify the information needed to confirm them.

4. RACI Roles and Responsibilities Matrix

Act as a project operations assistant. Create an editable responsibility matrix so everyone knows who does the work and who approves it.

My inputs:

• Project name and objective: [details]
• Tasks, deliverables, and key decisions: [paste list]
• Team members and their roles: [list]
• Sponsor, client, and final approvers: [details]
• Known limits on authority or availability: [details]

Start with a short beginner-friendly explanation of:

• Responsible: does the work.
• Accountable: owns the outcome and final decision.
• Consulted: provides input before the work or decision is completed.
• Informed: receives updates.

Create a matrix with tasks or decisions as rows and my supplied people or roles as columns. Use R, A, C, I, or a dash. Use R/A when the same person both performs the work and owns the outcome.

Give every completed row exactly one Accountable owner and at least one Responsible person. If the inputs do not support an assignment, flag the gap instead of inventing authority. Mark inferred assignments as “Proposed.”

Finish with a responsibility-check table listing missing owners, unclear approval rights, and possible workload concentration. Keep consultation and update lists limited to people who need them.

5. Project Budget and Expense Tracker

Act as a project budget coordinator. Create an editable budget tracker that helps me compare planned costs with expected final spending.

My inputs:

• Project name and scope: [details]
• Approved total budget and currency: [amount and currency]
• Planned work, purchases, quantities, and rates: [details]
• Actual spending to date: [details or unknown]
• Unpaid commitments and remaining work estimates: [details]
• Contingency reserve: [amount, percentage, or unknown]
• Tax and fee information: [supplied rules or unknown]

Create a table with:

Cost ID | Category | Item | Quantity | Unit cost | Planned budget | Actual cost to date | Estimated remaining cost | Forecast total | Budget variance | Notes.

Use these definitions:

• Forecast total = actual cost to date + estimated remaining cost.
• Budget variance = planned budget − forecast total; a negative value means an expected overspend.

Show how quantity and unit cost produce each planned amount. Include unpaid commitments in remaining costs only once. Keep the contingency reserve separate from ordinary expenses and explain whether it is included in the approved total.

Provide a summary comparing the approved total with forecast spending. Explain the calculations in plain language and give reusable spreadsheet formulas using column letters.

Leave unknown values blank or marked “To confirm”; never treat unknown spending as zero or invent tax rates.

6. Project Risk Register and Response Plan

Act as a project risk coordinator. Create an editable risk register with practical actions for my specific project.

My inputs:

• Project objective, deliverables, and deadline: [details]
• Team, budget, tools, suppliers, and dependencies: [details]
• Known uncertainties or concerns: [list]
• Problems that have already happened: [list]
• Available people who can own responses: [names or roles]
• Risk review frequency: [weekly, fortnightly, etc.]

Create a table with:

Risk ID | Possible future event | Cause | Effect on the project | Likelihood, 1–5 | Impact, 1–5 | Score | Priority | Early warning sign | Prevention action | Contingency action | Owner | Review date | Status.

Define the likelihood and impact scales in plain language before using them. Calculate the score as likelihood × impact. Use priorities of Low for 1–4, Medium for 5–9, High for 10–15, and Urgent for 16–25. Explain that these are draft scoring rules for this register.

Separate supplied risks from additional suggested risks. Label unsupported ratings as provisional and explain their basis. Distinguish prevention from what we will do if the event happens.

List existing problems separately as issues with an action and owner. Finish with the three risks to review first. Do not present a risk score as an exact probability.

7. Stakeholder Communication Plan

Act as a project communication coordinator. Create an editable communication plan that gives each stakeholder the information they need without unnecessary meetings.

My inputs:

• Project name, objective, and duration: [details]
• Stakeholders and their roles: [team, sponsor, client, suppliers, etc.]
• Information each group needs: [details]
• Decisions and approvals required: [details]
• Preferred channels: [email, chat, shared document, meeting, etc.]
• Team locations, time zones, and working hours: [details]
• Maximum recurring meetings per week: [number]
• Known escalation rules: [details or unknown]

Create a table with:

Audience | Purpose | Information to share | Channel | Frequency or trigger | Sender | Action expected | Response deadline | Record location.

Include updates for normal progress, approval requests, and urgent blockers. Suggest asynchronous updates when a meeting is unnecessary. Keep any proposed meeting schedule within my stated limit.

Add a simple escalation path showing what happens when a blocker or unanswered approval threatens a milestone. Mark any proposed response times or authority assignments for confirmation.

Finish with a reusable meeting-notes structure containing decisions, actions, owners, and due dates. Use only supplied names and channels; do not invent contact details. Specify the time zone whenever suggesting a meeting time.

8. Weekly Project Status Report

Act as a project reporting assistant. Turn my notes into a concise, editable weekly status report for stakeholders.

My inputs:

• Project name and reporting period: [details]
• Report audience: [client, sponsor, internal team, etc.]
• Approved goals, milestones, and budget: [details]
• Work completed this week: [notes]
• Work planned for next week: [notes]
• Current dates, spending, risks, and blockers: [details]
• Decisions or help needed: [details]
• Previous report, if available: [paste or leave blank]

Create:

1. An executive summary of no more than 100 words.
2. A health table for scope, schedule, budget, and risks, with a status and supporting evidence for each.
3. A completed-work table linking achievements to deliverables.
4. A next-week plan with owners and due dates.
5. A blockers-and-decisions table with impact, action needed, owner, and deadline.

Use Green for supported on-track performance, Amber for a threat needing attention, Red for a confirmed breach of an approved limit or milestone, and Unknown when evidence is insufficient. Explain each rating briefly.

Keep completed work separate from planned work. Do not invent progress percentages, positive results, approvals, or spending figures. Highlight conflicting notes and missing evidence under “Needs confirmation.”

9. Project Change Request and Impact Assessment

Act as a project change coordinator. Create an editable change request that helps the decision-maker evaluate a proposed change before approval.

My inputs:

• Project name and current approved scope: [details]
• Current deadline and approved budget: [details]
• Requested change: [specific addition, removal, or revision]
• Requester, request date, and reason: [details]
• Expected benefit: [details]
• Affected deliverables, tasks, or team members: [details]
• Available cost and time estimates: [details or unknown]
• Decision-maker and decision deadline: [details]

Create these sections:

1. Request summary and business reason.
2. Before-and-after scope comparison.
3. Impact table covering schedule, cost, people, quality, dependencies, and risks.
4. Options: keep the current plan, approve the requested change, or use a smaller alternative.
5. A recommendation based on the supplied evidence.
6. Decision record with status “Pending,” approver, decision date, and conditions.
7. An implementation checklist to use after approval.

For every time or cost impact, distinguish a supplied estimate from a proposed estimate or an unknown. Identify any new work that would replace existing work rather than simply adding it.

Do not mark the request approved or silently alter the baseline. If evidence is insufficient for a recommendation, state what must be confirmed first.

10. Project Closure and Handover Checklist

Act as a project delivery coordinator. Create an editable closure report and handover checklist so the project can finish with clear ownership of anything remaining.

My inputs:

• Project name, goals, and original success measures: [details]
• Planned and actual completion dates: [dates]
• Approved budget and final or latest known costs: [details]
• Deliverables and evidence of acceptance: [details]
• Outstanding tasks, defects, or unresolved issues: [list]
• Person or team taking over: [details]
• Files, instructions, access, and training to hand over: [details]
• Post-project support period: [details or unknown]
• Team feedback and lessons: [notes]

Produce:

1. A short project outcome summary.
2. A comparison table: Goal or deliverable | Planned result | Actual result | Evidence | Acceptance status.
3. A handover checklist with item, location, receiving owner, due date, and completion status.
4. An outstanding-work table with impact, next action, owner, and target date.
5. A lessons-learned table connecting each observation to a specific improvement.
6. A closure approval section with approver, date, and status left for completion.

Distinguish delivered work from formally accepted work. Mark unknown final costs and missing acceptance evidence clearly. Do not claim success, completion, transferred access, or approval without supporting information.