Capstone Proposal Help

A capstone proposal is a formal document submitted to faculty for approval before major work begins. The proposal demonstrates that you've thought carefully about your project, that it's feasible and meaningful, and that you understand the scope of work involved. Capstone proposals vary by discipline and institution, but generally require defining the problem, outlining your approach, justifying significance, establishing timeline and resources, and demonstrating feasibility. The proposal serves multiple purposes: it secures faculty approval and guidance, it forces you to think through your project rigorously before investing time, and it creates a contract between you and your advisor about what you'll deliver. A strong proposal gets approved quickly; a weak proposal gets sent back for revision, delaying your work. This guide covers proposal components, what faculty look for, common rejection reasons, and strategies for writing proposals that get approved on the first submission.

Capstone proposal components

Title (one line)

Clear, specific, not overly long. Example: "Strategic Analysis of Market Entry Opportunities for Company X" not "A Look at Company Strategy."

Problem statement (1-2 pages)

• What problem/question are you addressing? Clear, specific, significant to your field
• Why does it matter? Significance to the field, to a community, to an organization
• What's unknown or uncertain? What gap will your project fill?

Project approach/methodology (2-3 pages)

• How will you address this problem? Your plan (analysis approach, implementation plan, research design)
• What will you do? Specific activities and timeline
• What will you produce/deliver? Written paper, implementation, prototype, analysis report

Scope and limitations (1 page)

• What's included? Clear boundaries of what you'll cover
• What's not included? What's deliberately out of scope
• Why these boundaries? Realistic given time and resources

Timeline (1 page)

• Milestones: Key phases and when they'll be completed
• Realistic: Matches your available time while managing other courses/work
• Specific dates: Not vague "mid-semester" but actual target dates

Resources and support (1-2 pages)

• What do you need to do this project? Data access? Research equipment? Software? Organizational permission?
• Do you have access? Have you confirmed you can get what you need?
• Advisor support: Who will mentor you? What's their expertise relevant to your project?

Literature review (2-3 pages)

• What's been done before? Brief synthesis of relevant research/work in your area
• What gaps exist? How does your project fill those gaps?
• Shows preparation: Demonstrates you've thought about your project in context of existing work

What faculty look for in proposals

• Clear problem/question: Faculty need to understand what you're doing and why it matters
• Feasibility: Can you actually do this in your timeframe with available resources?
• Scope appropriate: Not too narrow (minimal learning), not too broad (unachievable)
• Preparation evident: Literature review and thought show you've prepared
• Realistic timeline: Schedule shows you understand what's involved
• Alignment with program: Does this fit your discipline/major? Will it develop skills you're meant to learn?
• Professional quality: Writing is clear, organized, free of errors

Common proposal rejection/revision reasons

• Scope too broad: "I'll study all aspects of healthcare" is too much. Narrow to specific focus
• Scope too narrow: "Survey 5 people about one topic" lacks depth. Expand scope or choose more substantial project
• Feasibility unclear: "I'll implement a company-wide system" without confirming organizational support is risky. Confirm before submitting
• No clear outcome: "I'll learn about X" is a learning goal, not a capstone outcome. Produce something: paper, analysis, prototype
• Weak justification: "This interests me" is insufficient. Why does the field/community care? Frame in context of the discipline
• Timeline unrealistic: Attempting too much in too little time. Be honest about constraints
• Missing resources:**Faculty asks "How will you access that data?" and you don't have an answer. Secure resources before submitting
• Writing quality poor: Grammar errors, unclear prose, disorganized. Proposal reflects your professionalism. Polish it