Many programs require a short prospectus before you're cleared to write the full proposal — a brief, lower-stakes document meant to get early sign-off on your general topic and approach before you invest serious time in detailed proposal writing.
| Section | Length |
|---|---|
| Working topic and rationale | Half a page to a page |
| Tentative research question(s) | A few sentences |
| Anticipated methodology | A paragraph — general approach, not full design detail |
| Preliminary sources | A handful of key citations showing the gap exists |
A prospectus is intentionally lighter than a full proposal — committees use it to catch fundamental problems (an infeasible topic, an already-answered question) before you've invested weeks in detailed design work.
Because the prospectus is shorter and less formal than a proposal, students sometimes rush it — and then get sent back to revise anyway, losing the time the lighter-weight step was meant to save. A prospectus written carelessly often surfaces the same structural problems (vague gap, mismatched methodology) that a careless proposal would, just earlier in the process.
Treat prospectus feedback as a preview of proposal feedback. If your committee flags a weak rationale or mismatched methodology at the prospectus stage, that same issue will resurface at the proposal stage if left unaddressed — fixing it now is cheaper than fixing it twice.
A defensible topic, rationale, and approach — clearing the way for your full proposal.
No — this step varies significantly by institution and department. Check your program handbook; some go straight from topic approval to full proposal.
Usually some refinement is expected and normal — the prospectus approves a general direction, not a locked-in design. Major pivots may need a new prospectus review depending on your program's rules.
Faster than full proposal review since the document is shorter, but still subject to your committee's general turnaround time — building in buffer time here matters just as much as at later stages.