ChatGPT project plan prompts: separate the problem, evidence, options, and decision

A request to “write a project plan” can omit the assumptions needed for a decision

ChatGPT can help turn scattered notes into a project-plan outline, a list of discussion points, or a draft for an internal meeting. But if you provide only a topic, the result can become a generic structure without a clear problem, verified evidence, decision owner, or decision to make.

OpenAI’s prompt guidance recommends clear objectives, enough context, a specified format and tone, and iterative improvement after reviewing the output. For a project plan, separate the problem, audience, verified facts, hypotheses, options, constraints, and requested decision so an AI draft does not replace human judgment.

Practical guides to plan writing commonly put the purpose, audience, format, required information, costs, and expected outcome up front. A structure such as 6W3H can reveal missing planning details, but AI-generated figures or market statements are not evidence. Verify sources, budgets, KPIs, and delivery feasibility with the responsible people and primary materials.

Six fields to separate in a project-plan prompt

1. State the decision in one sentence: whether to start an initiative, change a priority, or move to the next research step. This gives the meeting a clear outcome.
2. Separate the problem from the audience. Mark the current pain, people affected, and business impact as either verified observations or hypotheses.
3. Set evidence rules. Name allowed sources, dates, units, and unverified items, and tell ChatGPT not to invent facts, figures, or market context.
4. List options and constraints. Include the status quo, budget, staffing, timing, policy, and dependency constraints so the draft does not assume an impractical route.
5. Fix the output sections: summary, background, problem, options, recommendation rationale, delivery plan, KPI, risk, open questions, and meeting decision.
6. Keep review boundaries. Market sizing, ROI, legal questions, personal data, competitor comparisons, and budget approval need source checks and human ownership.

Four inputs to prepare for a project-plan draft

How to shift the brief for internal project plans

ChatGPT project-plan prompts to try

Organize the project notes below with 6W3H for an internal planning review. Do not add facts, figures, market trends, or customer feedback that are not in the input. Mark every point as Verified, Hypothesis, or Open. List missing information as questions. Then create a project-plan outline in this order: requested decision, background, problem, audience, options, delivery conditions, measurement, risks, and next checks. Notes: """[paste notes here]"""

Use only the verified information below to create a project-plan outline for [meeting audience] to decide [decision requested]. Format: [slides / document]. Length: [slide count or word count]. For every section, include: conclusion, evidence used, unresolved items, and the decision needed in the meeting. Include the status quo among the options and list benefits, constraints, and needed follow-up for each. Do not estimate effects or costs; label unknown figures ‘needs confirmation.’ Information: """[paste background, problem, audience, options, constraints, and source highlights]"""

Review the project-plan draft below before approval. Before rewriting it, classify statements as: 1) verified facts, 2) hypotheses or assumptions, 3) claims that need a source, 4) items needing budget, legal, privacy, or operating review, and 5) unclear decision requests. Do not make legal or business-viability conclusions. Briefly explain why each item needs checking and suggest a responsible review role. Draft: """[paste draft here]"""

FAQ