Translate an external partner’s problem into a feasible, ethical, assessable capstone project with clear scope, deliverables, roles, data access, milestones, and risk controls.
This prompt has variables that can be replaced with your own information. Copy and use it with your preferred LLM, or try it out in the LearnerBox Prompt Playground.
Act as an experienced capstone coordinator and university-industry partnership manager.
Develop a capstone project scoping template using the information below.
Program and student level:
{{program_level}}
Industry partner and sector:
{{partner_context}}
Partner problem or opportunity:
{{problem_statement}}
Academic learning outcomes:
{{learning_outcomes}}
Project duration and team structure:
{{duration_team}}
Data, access, and resource conditions:
{{data_resources}}
Institutional and partner constraints:
{{constraints}}
Scoping requirements:
1. Rewrite the partner problem as a neutral, researchable, and feasible project challenge.
2. Distinguish:
- partner need;
- student learning purpose;
- project objective;
- project question;
- deliverables;
- exclusions; and
- success criteria.
3. Check alignment with program learning outcomes.
4. Define project scope using:
- in scope;
- out of scope;
- assumptions;
- dependencies;
- constraints; and
- decision rights.
5. Define partner, faculty, student, and coordinator responsibilities.
6. Identify required data, system access, interviews, site access, software, equipment, and subject-matter support.
7. Include confidentiality, intellectual property, publication, data protection, ethics, safeguarding, and conflict-of-interest questions.
8. Create realistic milestones and review gates.
9. Define deliverables that are academically assessable and useful to the partner without guaranteeing implementation results.
10. Identify risks involving:
- scope creep;
- unavailable data;
- delayed partner feedback;
- confidentiality;
- unrealistic expectations;
- student capability;
- technology;
- safety;
- ethics; and
- project continuity.
11. Create a rescoping and escalation procedure.
12. Do not invent partner commitments, data access, IP terms, approvals, or implementation authority.
13. Flag all items requiring legal, ethics, data protection, safety, or institutional approval.
Present the result as:
{{output_format}}
Include:
- project title;
- partner context;
- problem statement;
- academic alignment;
- objectives and research questions;
- in-scope and out-of-scope items;
- deliverables and success criteria;
- roles and responsibilities;
- data and resource requirements;
- milestones and review gates;
- risk register;
- approval checklist; and
- rescoping process.Replace each variable shown in double curly brackets with accurate information from your own professional context.
{{program_level}}
Example: Example: Final-year undergraduate information systems capstone
Identify the academic program and student level.
{{partner_context}}
Example: Describe the organization, sector, operational context, and contact roles.
Use authorized, non-confidential partner information.
{{problem_statement}}
Example: Describe the problem, current state, desired improvement, and why it matters.
State the need without presuming a solution.
{{learning_outcomes}}
Example: Paste the capstone or program learning outcomes.
The project must remain academically assessable.
{{duration_team}}
Example: Example: 12 weeks, team of four students
State time, team size, and supervision pattern.
{{data_resources}}
Example: Describe available data, systems, interviews, sites, software, equipment, and support.
Only confirmed access should be treated as available.
{{constraints}}
Example: Provide confidentiality, IP, ethics, legal, safety, budget, and implementation constraints.
Use actual institutional and partner requirements.
{{output_format}}
Choose the format used for partner and academic approval.
A complete capstone scope document containing partner need, academic alignment, feasible boundaries, deliverables, roles, access requirements, milestones, risks, approvals, and rescoping procedures.
These characteristics describe the type of thinking, customization, and output structure involved in using this prompt effectively.
This breakdown explains how the prompt’s major components work together to guide the AI toward a useful, reliable, and well-structured response.
Positions the AI as a capstone coordinator and university-industry partnership manager.
Defines program, partner, problem, learning outcomes, team, resources, and constraints.
Requires a feasible and governable capstone project scope.
Prevents invented commitments, access, approvals, IP terms, and implementation authority.
Requires scope, alignment, deliverables, roles, resources, milestones, risks, approvals, and rescoping.
Program, partner context, problem, outcomes, duration, resources, constraints, and output format.
AI-generated responses can contain errors, omissions, unsupported assumptions, outdated information, or recommendations that do not reflect your jurisdiction or professional context.
Verify calculations, evidence, regulations, standards, policies, and professional recommendations before relying on the result. The qualified professional remains responsible for the final decision.
Return to the specialization page to explore additional professional workflows and prompt templates.
Customize the template for your professional context or open it directly in the Prompt Playground for guided AI practice.