A proposal has one job: to convince a supervisor or committee that your study is worth doing, that you know how to do it, and that it can be finished in the time available. Proposals get sent back for predictable reasons, and almost all of them are structural.
Enter your topic and this tool lays out every required section, from the problem statement through to the work plan and budget, together with the specific failures that most often trigger a revision request.
This is the paragraph readers judge you on. It must name a specific thing that is not known or not working, for a specific population, in a specific setting. "Little research exists on X in Y" is not a problem statement — absence of research is not in itself a problem worth funding or supervising.
State what the consequence of not knowing is: a policy made without evidence, a group whose needs are undocumented, a practice that may not work. Then your significance section has something concrete to build on, and your gap has a reason to matter.
Research questions, objectives, methodology and expected outcomes must line up one-to-one. Objective 2 should be answerable by the method described for it, and a reader should be able to pair each question with its objective without guessing.
Misalignment is the most frequent reason for revision, and it is usually visible at a glance: three questions and five objectives, or a causal question with a cross-sectional survey behind it. Lay them out side by side and check the correspondence before you submit.
Name your design and say why it suits your questions. Specify the population, the sampling frame, the sampling technique and the sample size — with its justification, not just its value. Describe your instruments and how you will establish validity and reliability.
Then name the actual analysis: which tests, which comparisons, which analytic approach. "Data will be analysed using SPSS" says nothing — SPSS is software, not a plan. A committee needs to see that you know what you will do with the data once you have it.
A timeline by month or week for each phase makes feasibility visible, and it is where over-ambition shows. If data collection is allotted two weeks in a district that takes a day to reach, the plan will not survive contact with reality.
Include real costs: travel, printing, transcription, software, incentives. Even where nobody is funding you, costing the project demonstrates that you have thought it through and sometimes reveals that a design is unaffordable before you commit to it.
Objectives that do not match the questions. A methodology that cannot answer what was asked. A sample size with no justification. A literature review that summarises without identifying a gap. A timeline that does not fit the time available. Ethics left unaddressed.
Every one of these is cheaper to fix before submission than after. Read your draft as a sceptical examiner would and ask the obvious question at each section: how do you know, and how will this actually work?
Commonly 3,000 to 5,000 words for a Master's proposal, but departments vary widely. Follow your own guidelines over any general figure.
The aim is the single overall purpose. Objectives are the specific, measurable steps that achieve it — usually three to five.
A condensed one: enough to establish the themes and demonstrate the gap. It expands into the full chapter later.
Expected outcomes, yes — what you anticipate finding and why it matters. Frame them as expectations, never as conclusions.
Most often because the objectives do not match the questions, the methodology cannot answer them, or the sample size is unjustified. All three are structural and fixable.