Libraries · logistics & pm · planning

Project Planning

Charters, scope statements, work breakdowns, schedules, and RACI matrices: the planning artifacts that get a project off the ground and keep everyone pointed the same way.

PROMPTS 22 // OPEN SAMPLES 2 // FREE WITH ACCOUNT 20

Project Charter

OPEN SAMPLE

Drafts a project charter from your goals, constraints, and stakeholder list. Use it at the start of any project to get sponsor alignment and scope boundaries written down before work begins.

PROJECT NAME ·ORGANIZATION NAME ·SPONSOR NAME AND TITLE ·PM NAME AND TITLE ·TARGET COMPLETION DATE ·BUSINESS NEED OR PROBLEM ·BUDGET CEILING ·STAKEHOLDER LIST

## Context
You are a project management assistant helping me draft a project charter for [PROJECT NAME] at [ORGANIZATION NAME]. The project sponsor is [SPONSOR NAME AND TITLE]. The project manager is [PM NAME AND TITLE]. The target completion date is [TARGET COMPLETION DATE]. The project addresses this business need or problem: [BUSINESS NEED OR PROBLEM]. Budget ceiling: [BUDGET CEILING]. Key stakeholders: [STAKEHOLDER LIST].

## Task
Draft a project charter with these sections:
1. Project purpose: one paragraph. What problem this solves and why it matters now.
2. Scope summary: what is included and what is explicitly excluded.
3. Objectives: three to five measurable outcomes, each written as "By [TARGET COMPLETION DATE], [measurable result]."
4. Key deliverables: a bulleted list.
5. Constraints and assumptions: two separate bulleted lists.
6. Stakeholders: a table with name, role, and interest in the project.
7. High-level timeline: four to six milestone rows with milestone name and target date.
8. Budget ceiling: state the figure and note that detailed estimates follow in the planning phase.
9. Authority and approval: who approves scope changes and who signs off on completion.

## Standards
- Plain professional language. Short paragraphs.
- Do not invent dates, dollar figures, percentages, or metrics I did not provide. Where a field is needed and not given, write "[TO BE CONFIRMED]" and flag it.
- Objectives must be specific and measurable. If the business need as stated does not support a measurable objective, flag it rather than invent one.
- Keep the full charter under 600 words.
- This is not legal or financial advice. Contracts and budgets require review by the appropriate authority.
- If any named input is missing or ambiguous, ask before drafting.

BEFORE YOU RUN IT

Project name, sponsoring organization, and the business problem the project solves
Sponsor and PM names with titles, and a list of key stakeholders and their roles
Target completion date and approved budget ceiling from your planning documents
Any known constraints (regulatory, technical, resource) and assumptions already agreed to
Confirm all dates, budget figures, and metrics come from your actual planning records, not estimated by the AI
Keep personnel details, contract values, and vendor names out of the prompt unless your AI tool is approved for that data

VERIFY BEFORE IT LEAVES YOUR HANDS

Every date in the charter was supplied by you, not generated by the AI
Budget ceiling matches your approved authorization document exactly
Objectives are measurable as written; reject any objective the AI made up that you did not supply
Scope exclusions cover the boundaries you actually discussed with the sponsor
Stakeholder table matches your actual roster; AI does not know your org chart
Every [TO BE CONFIRMED] placeholder is resolved before the charter goes to the sponsor for signature
No confidential personnel or contract details were included in the prompt or appear in the output

Sample output

Sample output. Generated by AI from sample inputs:

Project Charter: Atlas Warehouse Consolidation
Northwind Industrial Supply | Prepared June 2026

Project purpose
Northwind operates two regional warehouses that were never designed to work together. Duplicate inventory, split shipments, and redundant staffing cost the company time and money every week. This project consolidates operations into one upgraded facility by end of Q3 2026, reducing per-order fulfillment time and eliminating duplicate overhead.

Scope summary
In scope: physical relocation of inventory from Site B to Site A, rack installation, updated inventory management system configuration, and staff redeployment plan.
Out of scope: system procurement (already contracted), HVAC upgrades at Site A, and any customer-facing portal changes.

Objectives
- By September 30, 2026, complete physical consolidation of all Site B inventory into Site A.
- By September 30, 2026, achieve a picking error rate no higher than the current Site A baseline of [TO BE CONFIRMED].
- By October 31, 2026, reduce fulfillment labor hours per order by [TO BE CONFIRMED] percent compared to the pre-consolidation combined baseline.

Key deliverables
- Finalized floor layout plan for Site A
- Completed rack installation
- Migrated and reconciled inventory records
- Staff redeployment plan with training schedule
- Consolidated operations go-live sign-off

Constraints
- Budget ceiling: $220,000 (approved)
- Site B lease expires October 1, 2026 (hard deadline)
- No fulfillment disruption during peak August order period

Assumptions
- Site A rack permits are approved by July 15
- Current Site B staff will be offered positions at Site A
- Inventory system vendor will support migration with two on-site days

Stakeholders
| Name | Role | Interest |
|---|---|---|
| Dana Rosenthal | VP Operations (Sponsor) | On-time delivery, cost control |
| Marcus Webb | Warehouse Director (PM) | Operational continuity |
| Yolanda Ferris | IT Manager | System migration |
| Site A and B Supervisors | Operations leads | Staff transition |

High-level timeline
| Milestone | Target date |
|---|---|
| Charter approved | June 20, 2026 |
| Floor layout finalized | July 10, 2026 |
| Rack installation complete | August 1, 2026 |
| Inventory migration complete | September 15, 2026 |
| Go-live | September 30, 2026 |
| Site B cleared | October 1, 2026 |

Budget ceiling: $220,000. Detailed estimates to follow in the planning phase.

Authority: Scope changes require written approval from Dana Rosenthal. Project completion sign-off: Dana Rosenthal and Marcus Webb.

Note: Two objectives contain [TO BE CONFIRMED] placeholders. Confirm baseline metrics before sponsor signature.

CUSTOMIZATION

For government or defense projects, add a section for applicable regulations, contract numbers, and contracting officer information. For smaller projects, trim the stakeholder table to three rows and drop the budget narrative. If your organization has a standard charter template, paste the section headers into the Context block and the AI will follow that structure instead.

Download .md

Scope Statement

Writes a formal scope statement that clearly defines what the project includes and what it does not. Use it to prevent scope creep and set shared expectations with stakeholders before detailed planning begins.

FREE WITH ACCOUNT

Work Breakdown Structure

Builds a work breakdown structure (WBS) from your deliverables list. Use it after the scope statement is approved to break deliverables into manageable work packages before scheduling begins.

FREE WITH ACCOUNT

Milestone Plan

Builds a milestone plan with target dates, owners, and completion criteria from your project objectives and constraints. Use it to give leadership a high-level schedule view before the detailed task schedule is built.

FREE WITH ACCOUNT

Project Schedule Outline

OPEN SAMPLE

Builds a task-level schedule outline with durations, dependencies, and assigned roles from your WBS and milestone plan. Use it to turn your work breakdown into an ordered task list ready to load into a scheduling tool.

PROJECT NAME ·ORGANIZATION NAME ·PROJECT START DATE ·TARGET COMPLETION DATE ·WBS OR TASK LIST ·MILESTONE LIST ·ROLES AND RESOURCES ·WORKING DAYS PER WEEK ·NON-WORKING PERIODS

## Context
You are a project management assistant helping me build a schedule outline for [PROJECT NAME] at [ORGANIZATION NAME]. Project start date: [PROJECT START DATE]. Target completion date: [TARGET COMPLETION DATE]. WBS or task list: [WBS OR TASK LIST]. Key milestones with dates: [MILESTONE LIST]. Available roles or resources: [ROLES AND RESOURCES]. Working days per week: [WORKING DAYS PER WEEK]. Known non-working periods (holidays, blackout windows): [NON-WORKING PERIODS].

## Task
Build a schedule outline as a table with these columns:
- Task ID (sequential)
- Task name
- WBS reference (if provided)
- Duration (in working days)
- Predecessors (task IDs this task depends on)
- Assigned role
- Milestone flag (yes or no)
- Notes (constraints or assumptions for this task)

After the table:
1. Calculate the total schedule duration in working days and confirm whether it fits within the start and end dates.
2. Identify the critical path: the chain of tasks where any delay pushes the end date.
3. List the top three schedule risks visible from the task list and dependencies.

## Standards
- Durations are in working days, not calendar days. Account for [WORKING DAYS PER WEEK] and the non-working periods I listed.
- Do not invent durations or dates for tasks where I have not provided enough information. Write [ESTIMATE NEEDED] and flag it.
- Critical path is based on the dependencies I provide, not assumptions.
- Do not add tasks outside the WBS or task list I provided.
- Schedule risks must be grounded in the task list and constraints, not pulled from a generic risk library.
- Recompute the total duration from the task durations before stating whether the schedule fits. Show the math.
- If any named input is missing or the task list is incomplete, ask before building the schedule.

BEFORE YOU RUN IT

Approved WBS or task list with dependencies you have identified
Project start and hard completion dates from the approved charter
Key milestone dates, especially any hard external deadlines
List of available roles or resources and any known availability constraints
Non-working periods: company holidays, blackout windows, seasonal shutdowns
Confirm all dates, resource counts, and durations come from your planning records, not the AI
Keep individual employee names and salary details out of the prompt

VERIFY BEFORE IT LEAVES YOUR HANDS

Recount total working days yourself against a calendar, accounting for non-working periods
Verify the critical path by tracing predecessor chains manually for at least the longest sequence
Confirm no tasks were added that fall outside your approved WBS or scope
Check every [ESTIMATE NEEDED] flag and replace with a real estimate before loading into your scheduling tool
Milestone dates in the schedule match the approved milestone plan
Schedule risks are grounded in your actual constraints, not generic boilerplate
Review the full schedule with the team before baselining it in your project tool

Sample output

Sample output. Generated by AI from sample inputs:

Schedule Outline: Atlas Warehouse Consolidation
Northwind Industrial Supply | Start: June 2, 2026 | End target: September 30, 2026 | 5-day work week | Blackout: August 2-31 (fulfillment peak)

| ID | Task | WBS | Duration (days) | Predecessors | Role | Milestone | Notes |
|---|---|---|---|---|---|---|---|
| T1 | Charter approved | 1.6.1 | 0 | None | Sponsor | Yes | Project start milestone |
| T2 | Site A layout survey | 1.1.1 | 3 | T1 | Warehouse Director | No | Must access Site A during off-peak hours |
| T3 | Draft floor layout | 1.1.2 | 5 | T2 | Warehouse Director | No | |
| T4 | Layout review and approval | 1.1.3 | 3 | T3 | Sponsor | Yes | Target July 10 |
| T5 | Submit rack permits | 1.2.1 | 2 | T4 | Facilities Lead | No | External dependency; permit turnaround [ESTIMATE NEEDED] |
| T6 | Permits received | 1.2.1 | 0 | T5 | Facilities Lead | Yes | Hard target July 15 |
| T7 | Schedule rack installer | 1.2.2 | 3 | T6 | Facilities Lead | No | |
| T8 | Rack installation | 1.2.3 | 10 | T7 | Contractor | No | Must complete before August 2 blackout |
| T9 | Load inspection | 1.2.4 | 2 | T8 | Third-party inspector | Yes | Target August 1 |
| T10 | System reconfiguration | 1.3.2 | 8 | T4 | IT Manager | No | Vendor support days included |
| T11 | Inventory record audit | 1.3.1 | 5 | T1 | Warehouse Supervisors | No | Can run parallel to layout work |
| T12 | Physical inventory transfer | 1.3.3 | 15 | T9, T10, T11 | Warehouse Supervisors | No | Starts September 1 after blackout |
| T13 | Post-transfer count verification | 1.3.4 | 3 | T12 | Warehouse Supervisors | No | |
| T14 | Staff redeployment plan | 1.4.1-4 | 20 | T1 | HR Lead | No | Runs parallel; complete by September 20 |
| T15 | Go-live acceptance | 1.5 | 0 | T13, T14 | Sponsor | Yes | Target September 30 |

Total working days on critical path: T1-T4-T6-T8-T9-T12-T13-T15
Working days available June 2 to September 30, excluding August 2-31: approximately 83 days.
Critical path length: 0+3+5+3+2+0+3+10+2+15+3+0 = 46 days. Fits within available time with buffer, but only if permits arrive on schedule.

Schedule risks:
1. Permit turnaround (T5-T6) is external. If permits slip past July 15, rack installation cannot finish before the August 2 blackout, pushing go-live past September 30.
2. The August 2-31 blackout freezes the physical move window. Any task starting the physical transfer (T12) must wait until September 1 regardless of readiness.
3. Vendor support days for system reconfiguration (T10) are not yet confirmed. A vendor scheduling conflict delays T10 and T12.

CUSTOMIZATION

Load the output table directly into your scheduling tool (Microsoft Project, Smartsheet, Asana, or similar) by matching column names. For larger projects, run the schedule one phase at a time to avoid truncation. Add a resource column for capacity planning if more than one person shares a role. For agile projects, swap duration in days for story points and replace the critical path section with a sprint-by-sprint rollup.

Download .md

RACI Matrix

Builds a RACI (Responsible, Accountable, Consulted, Informed) responsibility matrix from your task list and team roster. Use it to close accountability gaps and eliminate duplicate ownership before the project kicks off.

FREE WITH ACCOUNT

Kickoff Deck Outline

Outlines a project kickoff presentation with slide titles, key points per slide, and the owner who speaks each section. Use it to build a complete deck agenda before opening your presentation software.

FREE WITH ACCOUNT

Effort and Duration Estimate Notes

Estimates effort in person-hours and duration in working days for each task in your schedule, then recomputes totals so math errors do not hide in your plan. Use it when you need documented estimate rationale before you baseline the schedule.

FREE WITH ACCOUNT

Resource Plan

Plans people and resources across the project schedule, identifies over-allocation, and surfaces conflicts. Use it before finalizing the schedule to confirm you have the people you need when you need them.

FREE WITH ACCOUNT

Assumptions and Constraints Log

Documents every assumption and constraint identified during planning in a structured log with owners and review dates. Use it to track the beliefs your plan rests on and flag them before they become risks.

FREE WITH ACCOUNT

Success Criteria and KPIs

Defines measurable success criteria and key performance indicators (KPIs) for the project, tied to the business objectives. Use it before kickoff to align the team and sponsor on what done looks like and how it will be measured.

FREE WITH ACCOUNT

One-Page Project Brief

Writes a one-page brief that gives sponsors and approvers the facts they need to say yes, no, or ask better questions. Use it at the start of any project that needs sign-off before work begins.

FREE WITH ACCOUNT

All 135 prompts in this library are free with a VetsLearn account: every prompt, every checklist, synced to your account.

Unlock free with an account →

Communication Plan

Builds a structured communication plan that maps who hears what, how, and when throughout a project. Use it during planning to prevent information gaps and set expectations before work starts.

FREE WITH ACCOUNT

Stakeholder Register

Builds a complete stakeholder register that captures each stakeholder's role, influence, interests, and engagement approach. Use it during project initiation to avoid being surprised by who can block or shape the project.

FREE WITH ACCOUNT

Dependency Map

Maps the cross-team and cross-system dependencies that could stall a project if they are not tracked and owned. Use it during planning to surface who is waiting on whom before the schedule locks.

FREE WITH ACCOUNT

Phase Gate Plan

Defines the phase gates for a project with clear exit criteria so approvers know exactly what they are reviewing before work proceeds. Use it at the start of any multi-phase project that requires formal go/no-go decisions.

FREE WITH ACCOUNT

Project Budget Outline

Builds a structured project budget outline organized by cost category, with a subtotal and grand total that the user must recompute independently. Use it to organize cost estimates before a budget is formalized for approval.

FREE WITH ACCOUNT

Charter from Kickoff Notes

Turns raw kickoff meeting notes into a structured project charter that captures scope, objectives, constraints, assumptions, and approvals. Use it immediately after a kickoff meeting while the details are still fresh.

FREE WITH ACCOUNT

Agile Backlog Starter

Drafts an initial product backlog from a project brief, user research notes, or stakeholder requirements. Use it at the start of an agile project to convert a requirements list into prioritized user stories ready for sprint planning.

FREE WITH ACCOUNT

Sprint Plan

Produces a sprint plan from a prioritized backlog, team capacity, and sprint goal, with work assigned and any risks called out before the sprint starts. Use it at the beginning of each sprint to align the team on what will be done and how.

FREE WITH ACCOUNT

Rollout and Adoption Plan

Plans a phased rollout and adoption approach for a new system, process, or product, with adoption milestones and risk mitigations for each phase. Use it before a go-live to ensure the people side of the change is as planned as the technical side.

FREE WITH ACCOUNT

Project Closeout Plan

Builds a structured closeout plan that captures what needs to happen before a project is formally closed: final deliverables, lessons learned, handoffs, and sign-offs. Use it in the final phase of any project to prevent the common failure of work trailing off without a clean ending.

FREE WITH ACCOUNT

All 135 prompts in this library are free with a VetsLearn account: every prompt, every checklist, synced to your account.

Unlock free with an account →

This library is not legal or financial advice. Contracts, statements of work, and budgets should be reviewed before you rely on them.
AI output is a first draft. Recompute every total. Every date, status, and metric must come from your own project records, not the AI.
A red, amber, or green status is your call, supported by the facts. Keep confidential customer, vendor, and personnel details out of the prompt.