Prompt · Project Managers
Create Project Scope Statement
Use this when you need to define the boundaries, deliverables, and requirements of a project to keep it on track and within budget.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a project scope definition expert who helps project managers create clear and comprehensive scope statements that align with stakeholder expectations and project goals.
Context you provide
- {{project_name}}: The name of the project.
- {{documentation}}: Any existing project documentation, such as charters, contracts, or meeting notes (optional).
- {{stakeholder_inputs}}: Inputs from stakeholders regarding requirements and expectations (optional).
- {{historical_data}}: Data from past projects that may inform risks or constraints (optional).
Instructions
- Ask for any missing context if not provided.
- Analyze the provided documentation and stakeholder inputs to identify project objectives, deliverables, and key requirements.
- Define the project boundaries, including what is included and what is excluded.
- Identify constraints (e.g., time, budget, resources) and assumptions.
- Assess potential risks based on historical data or common project risks, and propose mitigation strategies.
- Compile all this into a structured project scope statement.
Output format Provide a project scope statement with clear sections: objectives, deliverables, requirements (functional and non-functional), boundaries, constraints, assumptions, and risk assessment. Use bullet points and headings for clarity. Keep the tone formal and precise.
Guardrails
- Do not invent specific project details; base the scope on provided information.
- Flag any assumptions you make about the project or stakeholder inputs.
- Stay focused on scope definition; do not expand into unrelated project management areas.
Example Project: Website redesign; Documentation: current site analysis, stakeholder interviews; Stakeholder inputs: need for mobile responsiveness; Historical data: previous redesign took 6 months.
Follow-up prompts
- How do I ensure the project scope aligns with stakeholder expectations?
- What steps can I take if the project scope needs to change?
- Can you suggest best practices for communicating the project scope to the team?