Build your capstone project proposal
Start anywhere; the completeness meter tracks how much is drafted. Your work saves to this browser only — hit Save draft before closing the tab and it will be waiting when you come back. The example button loads an illustrative dental-clinic project so you can see the target shape before writing your own.
Capstone proposal template
100% private — runs in your browserShape: [what you'll build or study] + [for whom, where]. Under about 15 words. If a stranger can picture the deliverable from the title alone, it's specific enough.
Course code plus program name. Committees use this to route your proposal to the right rubric.
Typical single-semester capstones run 10–16 weeks (illustrative range — your handbook wins). The draft splits this into an illustrative phase schedule.
Four sentences, one job each. "Interesting topic" is not a problem; "missed appointments cost the clinic X unbooked hours last quarter" is.
Two to four lines, each starting with a measurable verb: measure, compare, build, evaluate, recommend. Vague verbs (understand, explore, look into) invite revisions.
Name the data source and the analysis in the same breath. If the method can't produce a number or artifact that answers an objective, the committee will spot it.
List every dependency and its owner. Proposals fail here more than anywhere: unlisted access needs turn into mid-semester crises.
What the committee looks for, section by section
A proposal is read in five minutes and judged against one question: can this person finish this project? Every section below exists to supply evidence for that verdict. Read your draft against each description and fix the mismatch before you submit.
The title and program line
Committees triage by title. They're checking that the deliverable and the setting are named and that the scope sounds like one semester, not a career. A title with "and" joining two projects usually means you haven't chosen yet — split it and pick one half.
The problem statement
This is where proposals live or die. The committee wants a chain: situation → evidence → gap → consequence. "Evidence" can be your own pilot observation, organization records or published work — but it has to be something other than your enthusiasm. If your problem statement would still be true with the topic swapped out, it's too generic.
The objectives
Two to four, numbered, each opening with a measurable verb. The committee checks that the set is complete but minimal: together the objectives should deliver the title's promise, and no objective should be answerable with "it depends". Every later chapter answers these in order — write them well and the whole paper outlines itself.
The methods
Committees read methods looking for the match to objectives and for the risks you've already priced in: recruitment, permissions, equipment, analysis skills. Name the data source precisely (which records, which people, which period) and name the analysis precisely (what comparison, what chart, what test). Hedged methods read as unstarted methods.
The timeline
Nobody expects week-level accuracy; they expect honesty about order. Ethics before data. Data before analysis. A buffer before the writing crunch. If your timeline shows a artifact build starting before ethics sign-off, the committee will circle it — and they should.
The resources list
This section proves you've talked to the people who own what you need. Name each permission, dataset, tool and helper, and who grants it. A resources list with named owners reads as a project that has already begun.
Weak vs strong proposal wording
The same project can read as shaky or solid depending on sentence mechanics. These pairs are illustrative — swap in your own nouns — but the contrast is the lesson. Click through the tabs.
Measurable verbs, named sources, countable outputs. The weak version promises an opinion; the strong one promises evidence.
Scale down and attach evidence. "Everywhere" is unarguable and therefore unpersuasive; one practice's own numbers move the committee.
Name the data, the comparison and the summary statistic. "Utilize" is the tell of a method that hasn't been chosen yet.
Sequence with dependencies. "Ongoing throughout" usually means "not scheduled", and committees read it that way.
Before you submit the proposal
Five checks that catch most revision requests before they happen. Tap them off once your draft is assembled.
- Every objective uses a measurable verb and together they deliver the title.
- The problem statement cites at least one piece of evidence I didn't invent.
- Each resource in section 7 has a named owner I have actually contacted.
- The timeline puts ethics and permissions before any data collection.
- I checked my program's template and matched its headings where they differ from this draft.
Proposal approved — but the paper is looming?
Once the committee signs off, the writing clock starts. You can get a free price quote for a subject-matched writer to support the drafting while you run the research you proposed.
Frequently asked questions
How long should a capstone proposal be?
Most programs ask for roughly 1,500 to 3,000 words — enough to cover problem, objectives, methods, timeline and resources without padding. Your rubric's page or word limit beats any general range. The draft this builder produces is deliberately lean so you can expand the sections your template emphasizes.
Do I need my full literature review done before proposing?
No — proposals need enough reading to show the gap is real, not the whole review. Cite the handful of sources that define your problem and the closest existing work. Committees know the review deepens after approval; what they punish is a proposal with none.
Can I change my topic after the proposal is approved?
Small method changes are usually fine with a written amendment; a new problem statement is a new proposal. Tell your supervisor before you act, not after. Committees respond far better to an early, documented change than to a defense that quietly doesn't match the approved plan.
What if my supervisor disagrees with my methods?
Ask for the reason in writing and treat it as free consulting — supervisors usually reject methods for feasibility or ethics, not taste. Bring two alternatives to the conversation rather than a defense of the one you had. The builder's methods field forces the level of specificity that makes those talks short.
Where is my draft saved, and is it private?
Your draft lives in this browser's localStorage on your own device — nothing is uploaded, and clearing your browser data removes it. Use Save draft before closing the tab, and download the .txt as a backup before major edits. Treat the browser storage like a napkin, not an archive.
Did the builder get you to a draft?