To write a proposal, define the problem or opportunity, identify the reader’s decision criteria, present a specific objective and evidence-based plan, explain the methods, timeline, resources, risks and evaluation process, and end with a clear request. Always follow the assignment, institution or funder’s instructions before applying a general template.

A strong proposal does more than describe an interesting idea. It demonstrates that the idea addresses a genuine need, can be completed using an appropriate method, is realistic within available constraints, and is valuable enough to deserve approval, support or funding.
This guide explains how to plan, structure, write and evaluate a proposal. It covers the common principles shared by academic, research, grant, project and business proposals, while providing additional detail for students and researchers writing research proposals.
Key Takeaways
- A proposal is both a plan and a persuasive argument.
- Its structure should follow the reader’s instructions and evaluation criteria.
- Every objective should connect to a method, output, timeline and success measure.
- Academic proposals must explain the research gap, methodology, ethics and expected contribution.
- Budgets, schedules and claims should be realistic and supported by evidence.
- AI tools may assist with planning or editing, but the writer remains responsible for accuracy, originality, confidentiality and disclosure.
What Is a Proposal?
A proposal is a structured document that asks a person or organization to approve, support, fund or authorize a planned activity. It explains what will be done, why it should be done, how it will be completed, what resources it requires and what results are expected.
A proposal is therefore both:
- A plan, because it describes future activities.
- An argument, because it gives the reader reasons to accept that plan.
A university supervisor may use a research proposal to decide whether a study is academically sound. A funding agency may evaluate whether a project is significant, feasible and worth its cost. A client may assess whether a proposed service solves a business problem. Although the details differ, each reader is evaluating the quality of the proposed decision.
What Questions Should a Proposal Answer?
A complete proposal should enable the reader to answer the following questions:
- What exactly is being proposed?
- What problem, need or opportunity does it address?
- Why is the proposal important?
- What evidence supports the need for it?
- What objectives will be achieved?
- How will the work be carried out?
- Who will complete the work?
- What resources will be needed?
- How long will it take?
- What risks or limitations could affect it?
- How will success be measured?
- What decision or action is requested from the reader?
A weakness in any of these areas can reduce confidence in the entire proposal. For example, an important problem does not compensate for an unsuitable method, and an innovative method does not compensate for an unclear research question.
Types of Proposals
The correct format depends on the proposal’s purpose, audience and decision context.
| Proposal type | Main purpose | Typical audience | Common sections |
|---|---|---|---|
| Research proposal | Obtain academic approval for a planned study | Supervisor, department, admissions committee or ethics committee | Background, problem, literature, questions, methodology, ethics, timeline and contribution |
| Thesis or dissertation proposal | Demonstrate that a degree project is original, feasible and academically appropriate | Supervisory committee or graduate school | Research gap, framework, questions, methods, chapter plan and schedule |
| Grant proposal | Obtain financial support | Government agency, foundation or research council | Significance, objectives, approach, impact, team, budget, risk and evaluation |
| Project proposal | Obtain authorization and resources for a project | Manager, organization, donor or stakeholder | Need, goals, scope, activities, deliverables, schedule, budget and success criteria |
| Business proposal | Persuade a prospective client or partner to accept an offer | Client, buyer, investor or partner | Client problem, solution, scope, qualifications, pricing, terms and acceptance |
| Proposal letter | Make a brief request or introduce a longer proposal | Employer, client, sponsor or administrator | Purpose, need, proposed action, benefit and requested next step |
| Concept note | Present an early-stage idea for initial consideration | Funder, supervisor or partner | Problem, proposed concept, target group, expected value and approximate requirements |
A research proposal should not be written like a sales document, and a client proposal should not contain an unnecessary academic literature review. Begin by identifying the proposal type before selecting a template.
Proposal Versus Related Documents
| Document | Main function | Future or past focused? | Persuasive? |
|---|---|---|---|
| Proposal | Requests approval for planned work | Future | Yes |
| Plan | Organizes activities that may already be approved | Future | Sometimes |
| Report | Presents completed work, evidence or findings | Mainly past | Usually analytical |
| Research paper | Presents an argument or completed research | Mainly completed work | Academic argument |
| Abstract | Summarizes a longer document | Either | Limited |
| Concept note | Tests an initial idea before a full proposal | Future | Yes, but brief |
| Request for proposal | Invites others to submit proposals | Future | Not itself an applicant’s proposal |
A proposal may later become the basis of a project plan, research protocol, contract or thesis. It is not normally the final document because its assumptions may change after approval.
What to Do Before Writing a Proposal
Read the Instructions Before Choosing a Structure
The required instructions override any general advice.
Check:
- Word or page limit.
- Required headings.
- Formatting rules.
- Submission method.
- Eligibility requirements.
- Assessment or review criteria.
- Permitted and excluded costs.
- Required attachments.
- Ethical or regulatory requirements.
- Citation style.
- Deadline and internal approval process.
Create a compliance checklist from the instructions. Reviewers should not have to search for required information, and a technically strong idea may still be rejected when mandatory rules are ignored.
Identify the Audience and the Decision
Ask two questions:
- Who will read the proposal?
- What decision must that reader make?
A disciplinary specialist may expect technical detail. An interdisciplinary panel may need unfamiliar terms explained. A senior manager may focus on cost, risk and strategic value. A supervisor may focus on intellectual coherence and feasibility.
Write for the least specialized important reader without making the proposal superficial. Define necessary technical language and avoid jargon that does not improve precision.
Study the Evaluation Criteria
Convert each review criterion into a question.
For example:
| Review criterion | Question your proposal must answer |
|---|---|
| Significance | Why does this problem matter? |
| Originality | What is new about the idea or approach? |
| Methodological quality | Can the chosen method answer the question? |
| Feasibility | Can the work be completed with the available time, access and resources? |
| Impact | Who may benefit, and how? |
| Value for money | Are the requested resources proportionate and justified? |
| Team capability | Do the people involved have suitable experience and responsibilities? |
| Ethics | Are participants, data, communities and researchers protected? |
Use the reader’s criteria as the backbone of the document rather than adding them after the proposal has already been written.
Gather Evidence
Collect evidence for:
- The size or seriousness of the problem.
- What is already known.
- What remains unknown.
- Why the proposed approach is appropriate.
- Whether the required participants, data, equipment or sites are accessible.
- How long activities usually take.
- What the main costs will be.
- Which risks are foreseeable.
- What comparable projects have achieved.
Do not use evidence merely to make the proposal appear well researched. Each source should help establish the problem, justify a choice or define the context.
Conduct a Feasibility Test
A proposal is feasible when its objectives can reasonably be achieved with the available time, skills, access, technology, funding and ethical permissions.
Before drafting, check:
- Can the target population or data be accessed?
- Is the sample realistic?
- Are the methods affordable?
- Is specialist equipment available?
- Can ethical approval be obtained?
- Is the analysis within the team’s capabilities?
- Does the schedule include recruitment, delays, revision and approval?
- Is the scope appropriate for the degree or funding period?
Reducing the scope is often better than promising more work than can be completed.
How to Write a Proposal Step by Step
1. Confirm the Proposal Type and Requirements
Start by naming the document:
- Research proposal.
- Dissertation proposal.
- Grant application.
- Project proposal.
- Business proposal.
- Proposal letter.
- Concept note.
Next, extract all formal requirements into a checklist. Record the maximum length, mandatory sections, deadline, attachments, evaluation criteria and submission rules.
Do not assume that a template from another university, funder or organization will be accepted unchanged.
2. Define the Decision You Want
State the requested decision in one sentence.
Examples:
- Approve this undergraduate research project.
- Admit the applicant to conduct the proposed doctoral study.
- Fund the project for the requested 24-month period.
- Authorize the department to implement the pilot programme.
- Select the company to provide the specified service.
This sentence may not appear exactly in the final document, but it keeps the proposal focused. Every section should help the reader make that decision.
3. Explain the Problem, Need or Opportunity
The problem section should describe the present situation and explain why it requires action or investigation.
A strong problem statement usually includes:
- The context.
- The specific problem.
- Evidence that the problem exists.
- The people, processes or knowledge affected.
- The gap in current practice or understanding.
- The consequence of leaving the problem unresolved.
Weak statement:
Student writing is an important issue that should be studied.
Stronger statement:
First-year students in the selected programme receive written feedback only after submitting their final research proposals. Consequently, they have limited opportunity to apply feedback during proposal development. The proposed study will examine whether a structured peer-feedback process improves proposal quality before final submission.
The stronger version identifies a context, an observable gap and a reason for investigation without pretending that the results are already known.
4. State the Aim and Objectives
The aim expresses the overall purpose. The objectives divide that purpose into specific tasks or achievements.
Example aim:
To evaluate whether structured peer feedback improves the quality of first-year students’ research proposals.
Example objectives:
- To develop a peer-feedback checklist based on the programme’s proposal rubric.
- To implement two structured peer-review sessions.
- To compare proposal-quality scores before and after the intervention.
- To explore students’ perceptions of the feedback process.
- To identify practical recommendations for future teaching.
Good objectives are clear, logically ordered and achievable. Avoid vague verbs such as “understand” when a more precise action is possible.
Depending on the project, useful verbs include:
- Assess.
- Compare.
- Determine.
- Estimate.
- Examine.
- Explore.
- Identify.
- Measure.
- Develop.
- Test.
- Evaluate.
- Design.
- Implement.
Each objective should later connect to a method, output and success measure.
5. Establish the Evidence and Rationale
The rationale explains why the proposed work is needed and why the selected approach is reasonable.
For an academic proposal, the rationale emerges from the literature review and research gap. For a project proposal, it may come from needs-assessment data, organizational records, consultations or policy requirements. For a business proposal, it may come from the client’s stated problem and operational information.
A useful rationale moves through four stages:
- What is already known or currently done?
- What limitation, inconsistency or unmet need remains?
- Why does that gap matter?
- How will the proposed work address it?
Do not claim that “no research exists” unless a systematic search supports that statement. More defensible wording may be:
- Existing studies have focused mainly on…
- Evidence remains limited in…
- Few studies have compared…
- The findings are inconsistent regarding…
- The issue has not been examined adequately within…
- Current practice does not address…
6. Describe the Approach or Methodology
The approach explains how the objectives will be achieved.
For a general project proposal, describe:
- Activities.
- Work packages.
- Team roles.
- Procedures.
- Technologies.
- Partnerships.
- Quality-control processes.
For a research proposal, explain:
- Research design.
- Setting.
- Population.
- Sampling strategy.
- Sample size or case selection.
- Variables or concepts.
- Data sources.
- Data-collection methods.
- Instruments.
- Data-analysis procedures.
- Reliability, validity or qualitative rigor.
- Ethical safeguards.
Do not simply name a method. Explain why it is suitable.
Weak:
A survey will be used.
Stronger:
An online questionnaire will be used because the study seeks standardized responses from students across several seminar groups. Closed questions will measure the frequency and perceived usefulness of peer feedback, while two open questions will allow participants to describe benefits or difficulties not represented by the fixed response options.
The methodology should demonstrate a direct relationship between the research question and the evidence required to answer it.
7. Define Outputs, Outcomes and Success Measures
These terms are related but different:
- Activities are the actions performed.
- Outputs are the immediate products created.
- Outcomes are the changes expected after those outputs are used.
- Impact is the broader or longer-term difference.
- Success measures show whether the intended result was achieved.
Example:
| Element | Example |
|---|---|
| Activity | Conduct peer-feedback workshops |
| Output | Two workshops and completed feedback checklists |
| Outcome | Students revise proposals using structured feedback |
| Success measure | Improvement in independently assessed proposal-rubric scores |
| Possible impact | Better preparation for later independent research |
Avoid promising impacts that cannot be measured within the project period. Distinguish direct expected outcomes from longer-term possibilities.
8. Prepare a Realistic Timeline
Break the work into stages rather than giving only a start and end date.
A research timeline may include:
- Final literature review.
- Instrument development.
- Ethics submission.
- Pilot testing.
- Recruitment.
- Data collection.
- Data cleaning or transcription.
- Analysis.
- Interpretation.
- Drafting.
- Revision.
- Submission or dissemination.
Identify dependencies. Data collection cannot normally begin before ethical approval, and analysis cannot be completed before usable data are available.
Add reasonable time for:
- Participant recruitment.
- Administrative approval.
- Equipment procurement.
- Failed contacts.
- Data cleaning.
- Supervisor or partner feedback.
- Revision.
- Unexpected delays.
A Gantt chart is useful for complex projects, but a table may be sufficient for a short student proposal.
9. Calculate and Justify Resources
List the resources required and explain why each is necessary.
A simple direct-cost formula is:
Total direct cost = personnel + equipment and materials + travel + participant costs + software and services + dissemination costs
Depending on the institution or funder, the proposal may also include indirect costs, overheads, inflation, taxes or contingency. Apply these only when the rules allow them.
A budget justification should connect each cost to an activity.
Weak:
Software: $1,000.
Stronger:
Twelve-month transcription-software licence: $1,000. The licence will support secure transcription of approximately 80 recorded interviews and reduce the personnel time required for initial transcript preparation. All transcripts will be checked manually for accuracy.
Do not inflate the budget to create room for negotiation unless that practice is explicitly appropriate. Unrealistic figures can undermine the credibility of the entire plan.
10. Address Risks, Ethics and Data
Risk
For each major risk, identify:
- Likelihood.
- Potential effect.
- Preventive action.
- Contingency plan.
- Responsible person.
Example:
| Risk | Likely effect | Mitigation |
|---|---|---|
| Slow participant recruitment | Delayed data collection | Recruit through multiple approved channels and begin invitations early |
| Low survey completion | Insufficient usable responses | Shorten the questionnaire, test usability and send permitted reminders |
| Software failure | Lost work or delayed analysis | Maintain encrypted backups and documented version histories |
| Team-member absence | Delayed activity | Assign secondary responsibility for essential tasks |
Ethics
Research proposals may need to address:
- Informed consent.
- Voluntary participation.
- Withdrawal.
- Privacy.
- Confidentiality.
- Anonymity or pseudonymity.
- Potential harm.
- Sensitive topics.
- Vulnerable populations.
- Researcher safety.
- Compensation.
- Data access.
- Conflicts of interest.
Do not state that a study is “ethical” simply because risk appears low. Explain the safeguards.
Data management
A data-management section may cover:
- Data types and formats.
- Collection and naming conventions.
- Secure storage.
- Access permissions.
- Backup.
- De-identification.
- Metadata.
- Retention period.
- Destruction.
- Sharing.
- Archiving.
- Legal or contractual restrictions.
The level of detail should reflect the proposal type and institutional requirements.
11. Write the Title and Summary
The title and summary appear first but are often easier to finalize after the main proposal has been drafted.
Writing the title
A good title is:
- Specific.
- Informative.
- Concise.
- Consistent with the actual design.
- Free from claims that the study cannot establish.
Weak title:
Social Media and Students
Stronger title:
Association Between Night-Time Social Media Use and Self-Reported Sleep Quality Among First-Year University Students
The second title identifies the variables, population and non-causal design.
Writing the summary
A proposal summary should usually explain:
- The problem.
- The objective.
- The approach.
- The expected output or contribution.
- The requested support or decision.
Example:
First-year students often receive detailed feedback only after submitting their final research proposals, limiting opportunities for improvement during drafting. This study will evaluate whether two structured peer-feedback sessions improve proposal quality. Two seminar groups will participate in a quasi-experimental mixed-methods study using proposal-rubric scores, student questionnaires and short interviews. The project will generate evidence about the effectiveness and acceptability of structured peer review and produce an adaptable teaching checklist.
Do not introduce major information in the summary that does not appear in the full proposal.
12. Revise From the Reviewer’s Perspective
Revision should test reasoning, not only grammar.
Ask:
- Is the requested decision clear?
- Is the problem supported?
- Is the proposed response proportionate to the problem?
- Does every objective have a method?
- Can each method produce the required evidence?
- Are the scope and schedule realistic?
- Is every cost justified?
- Are risks and limitations acknowledged?
- Are important terms defined?
- Can a non-specialist understand the main argument?
- Does the proposal follow every instruction?
Seek feedback from at least one reader who understands the subject and one reader who can test clarity. A knowledgeable reviewer may identify methodological problems, while a less specialized reader may expose unexplained assumptions.
Standard Proposal Structure
Not every proposal needs every section, but the following structure can be adapted to most contexts.
| Section | Main purpose | Question answered |
|---|---|---|
| Title page | Identify the proposal and writer | What is this document? |
| Executive summary or abstract | Summarize the case | What is proposed and why? |
| Introduction | Establish context and purpose | What should the reader understand first? |
| Problem or need statement | Define the issue | What needs attention? |
| Background or evidence | Support the rationale | What evidence establishes the need? |
| Aim and objectives | Define intended achievements | What will the work accomplish? |
| Proposed approach or methodology | Explain the work | How will the objectives be achieved? |
| Scope and deliverables | Define boundaries and outputs | What is and is not included? |
| Team and responsibilities | Establish capability | Who will do the work? |
| Timeline | Sequence the activities | When will each stage occur? |
| Budget and resources | Explain requirements | What will the plan cost? |
| Risk and ethics | Demonstrate responsibility | What could go wrong, and how will it be managed? |
| Evaluation | Define success | How will results be assessed? |
| Conclusion or request | Reinforce the decision | What should the reader approve? |
| References | Document supporting sources | Which evidence was used? |
| Appendices | Supply necessary detail | What supplementary information is needed? |
Short proposals may combine several sections. Long funding applications may separate them into multiple forms and attachments.
How to Write an Academic Research Proposal
A research proposal explains what you intend to investigate, why the investigation is needed and how it will be conducted. It should demonstrate relevance, knowledge of the field, methodological justification and feasibility.
Title
The title should indicate the central topic, key concepts or variables, population and context when appropriate.
Avoid titles that are:
- Too broad.
- Written as unsupported conclusions.
- Filled with abbreviations.
- More ambitious than the proposed study.
- Inconsistent with the design.
Abstract or Proposal Summary
The abstract is a concise overview of the proposed research. Include:
- Context.
- Problem.
- Aim.
- Design.
- Participants, cases or data.
- Main analysis.
- Expected contribution.
Because no study has yet been completed, do not report invented results. Use future-oriented language such as “the study will examine” and carefully qualified language such as “the findings may inform.”
Introduction and Background
The introduction should move from the broader topic to the specific study.
A useful sequence is:
- Introduce the field or context.
- Establish the importance of the issue.
- Summarize the relevant state of knowledge.
- Identify the unresolved problem.
- State what the proposed study will do.
- Explain why the study is worthwhile.
The introduction should not become a long general history of the topic. Include only background that helps readers understand the problem and rationale.
Problem Statement
The research problem is the specific uncertainty, inconsistency, practical difficulty or knowledge gap the study will address.
A strong problem statement distinguishes among:
- A broad topic.
- A practical problem.
- A researchable problem.
- A proposed research response.
For example, “student retention” is a topic. “A high proportion of first-year online students leave before completing the first semester” is a practical problem. “Limited evidence exists about how early academic-support use is associated with withdrawal in this programme” is a research problem.
Literature Review
The literature review should not be a list of article summaries. It should synthesize evidence and build the case for the study.
Organize it by:
- Themes.
- Theories.
- Methods.
- Findings.
- Populations.
- Historical developments.
- Debates or contradictions.
A critical literature review asks:
- Where do studies agree?
- Where do they disagree?
- What methods have been used?
- What limitations recur?
- Which populations or contexts are missing?
- Which concepts require clarification?
- How will the proposed study extend, test or challenge existing knowledge?
End the review by making the research gap and the proposed contribution explicit.
Research Gap
A research gap is not simply a topic that has received little attention. It is a defensible limitation in current knowledge that the proposed study can address.
Common gap types include:
- Evidence gap: insufficient evidence about a relationship or outcome.
- Population gap: limited research involving a particular group.
- Context gap: findings have not been examined in a relevant location or setting.
- Methodological gap: existing studies rely on methods that leave important questions unresolved.
- Theoretical gap: an established theory has not explained a phenomenon adequately.
- Contradiction gap: findings are inconsistent.
- Implementation gap: an effective intervention has not been translated into practice successfully.
The gap should be narrow enough for the proposed research to address realistically.
Research Aim, Objectives and Questions
The aim, objectives and questions should describe the same project at different levels.
- The aim states the overall purpose.
- The objectives specify what the researcher will do.
- The research questions state what the study seeks to answer.
- The hypotheses, when appropriate, state testable expectations.
Example:
Aim:
To examine the relationship between structured peer feedback and undergraduate research-proposal quality.
Objective:
To compare proposal-rubric scores before and after structured peer-feedback sessions.
Research question:
How do proposal-rubric scores change after students participate in two structured peer-feedback sessions?
Hypothesis:
Students’ mean proposal-rubric scores will be higher after the peer-feedback sessions than before them.
Do not include a hypothesis automatically. Exploratory qualitative studies commonly use open research questions rather than predictive hypotheses.
Conceptual or Theoretical Framework
A theoretical framework uses an established theory to explain the phenomenon or guide the study. A conceptual framework organizes the key concepts and proposed relationships relevant to the project.
Explain:
- Which framework is used.
- Why it is appropriate.
- Which concepts are central.
- How it shapes the questions, data collection or interpretation.
- Where its limitations lie.
Do not add a theory merely to make the proposal sound academic. It should influence the actual design.
Methodology
Research approach and design
Identify whether the research is:
- Quantitative.
- Qualitative.
- Mixed methods.
- Experimental.
- Quasi-experimental.
- Correlational.
- Descriptive.
- Exploratory.
- Explanatory.
- Case-study based.
- Ethnographic.
- Historical.
- Practice based.
- Based on secondary data.
Explain why the design is appropriate for the question.
Setting and population
Define:
- Where the research will occur.
- Who or what the research concerns.
- Relevant inclusion and exclusion criteria.
- The period covered.
- The unit of analysis.
Avoid using “population” and “sample” interchangeably.
Sampling
Explain:
- Sampling frame.
- Sampling method.
- Intended sample size.
- Recruitment procedure.
- Inclusion and exclusion criteria.
- Expected nonresponse or attrition.
- Sample-size justification where relevant.
Probability sampling may be suitable when statistical generalization is important and a sampling frame exists. Purposive sampling may be suitable when the study requires information-rich cases with particular characteristics. The choice should follow the research objective.
Data collection
Describe:
- Instruments or data sources.
- How they will be developed or selected.
- Pilot testing.
- Administration procedures.
- Duration.
- Recording.
- Quality checks.
- Researcher training.
Attach lengthy questionnaires, interview guides or observation tools as appendices when permitted.
Measurement
For quantitative research, define the variables and how they will be measured.
For qualitative research, explain the central concepts, experiences or processes being explored without forcing them into inappropriate numerical variables.
Discuss the quality of existing scales or instruments and explain any adaptation.
Data analysis
Specify the planned analysis before data are collected.
Quantitative examples include:
- Descriptive statistics.
- Confidence intervals.
- Correlation.
- Regression.
- t tests.
- Analysis of variance.
- Nonparametric tests.
- Multilevel modelling.
- Time-series analysis.
Qualitative examples include:
- Thematic analysis.
- Content analysis.
- Grounded-theory coding.
- Narrative analysis.
- Discourse analysis.
- Framework analysis.
Mixed-methods proposals should explain where the quantitative and qualitative components are integrated.
Avoid listing every possible technique. Select analyses that answer the stated questions.
Research quality
Quantitative proposals may discuss:
- Reliability.
- Construct validity.
- Internal validity.
- External validity.
- Statistical power.
- Missing data.
- Bias.
- Confounding.
Qualitative proposals may discuss:
- Credibility.
- Dependability.
- Confirmability.
- Reflexivity.
- Transferability.
- Triangulation.
- Audit trail.
- Negative-case analysis.
Use the quality criteria appropriate to the research tradition rather than applying them mechanically.
Ethical Considerations
State whether formal approval will be required and identify the relevant committee or process.
Explain:
- Consent.
- Recruitment.
- Participant information.
- Withdrawal.
- Data protection.
- Potential distress or harm.
- Safeguarding.
- Incentives.
- Deception, when applicable.
- Community or cultural considerations.
- Researcher conflicts.
- Dissemination of sensitive findings.
Ethical planning should be integrated into the method rather than added as a final paragraph.
Data-Management Plan
Describe how data will be handled throughout the research lifecycle.
Include:
- Data types.
- File formats.
- Storage location.
- Encryption.
- Access permissions.
- Backup.
- File naming and version control.
- De-identification.
- Retention.
- Destruction.
- Sharing.
- Archiving.
- Metadata and documentation.
A plan to share data should not override privacy, consent, legal, contractual or community obligations.
Timeline and Work Plan
A research-proposal timeline should show that the project can be completed within the degree or funding period.
Example:
| Stage | Months |
|---|---|
| Refine literature review and instruments | 1–2 |
| Submit ethics application | 2 |
| Pilot instruments | 3 |
| Recruit participants | 3–4 |
| Collect data | 4–6 |
| Clean and organize data | 6–7 |
| Analyze data | 7–9 |
| Interpret findings | 9–10 |
| Draft chapters or report | 10–12 |
| Revise and submit | 12–14 |
The exact schedule depends on project complexity. Include realistic approval and revision time.
Budget and Resources
Student proposals may only need to identify required resources. Funded proposals may require detailed cost categories and justifications.
Possible items include:
- Research-assistant time.
- Participant compensation.
- Travel.
- Fieldwork.
- Laboratory supplies.
- Software.
- Equipment.
- Transcription.
- Translation.
- Data access.
- Open-access publication.
- Workshops.
- Community dissemination.
Explain institutional resources that are already available, such as laboratories, databases, software licences, specialist supervision or secure storage.
Expected Contribution and Significance
Explain how the study may contribute to:
- Theory.
- Evidence.
- Methodology.
- Policy.
- Professional practice.
- Education.
- Technology.
- Community understanding.
- Future research.
Separate realistic direct contributions from speculative long-term impacts.
Weak:
This research will transform higher education worldwide.
Stronger:
The study will provide institution-specific evidence about the feasibility and perceived usefulness of structured peer feedback. Its findings may inform the design of a larger multi-institutional evaluation.
Limitations and Risks
A proposal should not pretend that the planned research is perfect.
Anticipated limitations might include:
- Small sample.
- Single-site design.
- Self-reported measures.
- Limited follow-up period.
- Selection bias.
- Restricted access to records.
- Researcher positionality.
- Language limitations.
- Incomplete historical data.
Explain which limitations can be reduced and which will remain when interpreting the results.
References and Appendices
Include every source cited in the proposal using the required citation style.
Appendices may contain:
- Questionnaire.
- Interview guide.
- Participant-information sheet.
- Consent form.
- Recruitment material.
- Detailed timeline.
- Budget.
- Risk register.
- Conceptual model.
- Technical specification.
- Letters of support.
Do not use appendices to evade the main word limit or hide information that reviewers need to understand the core argument.
How Requirements Differ by Discipline
| Discipline or approach | Typical emphasis |
|---|---|
| Experimental STEM | Hypotheses, experimental design, controls, technical feasibility, preliminary evidence, reproducibility and risk |
| Quantitative social science | Theory, measurement, sampling, statistical analysis, bias and generalizability |
| Qualitative social science | Context, participant selection, access, reflexivity, interpretation, ethical relationships and rigor |
| Humanities | Primary sources, archives, interpretive framework, scholarly intervention, languages and chapter logic |
| Health research | Clinical significance, participant protection, protocol, sample size, safety, data monitoring and implementation |
| Computer science | Technical problem, system design, datasets, benchmarks, evaluation metrics, reproducibility and computational resources |
| Education | Learning context, participants, intervention, assessment, institutional access and practical implications |
| Practice-based or artistic research | Creative practice, research question, reflective documentation, artefact or performance, context and evaluative framework |
Always check disciplinary examples approved by the relevant department or funding programme.
How Requirements Differ by Academic Level
Undergraduate proposal
An undergraduate proposal usually demonstrates that the student can define a manageable question, identify relevant literature, choose a basic method and complete the work within a course schedule.
The project should be narrow. Originality may come from applying an established approach to a particular case rather than generating an entirely new theory.
Master’s proposal
A master’s proposal normally requires a stronger critical review, clearer methodological justification and greater independence. It should demonstrate engagement with a specific research gap while remaining feasible within the degree period.
Doctoral proposal
A doctoral proposal must make a credible case for an original contribution. Reviewers may also assess:
- Fit with the department.
- Availability of supervision.
- Access to facilities or field sites.
- Research training needs.
- Scope for a thesis-length contribution.
- Feasibility within the registration period.
The proposal is a starting plan, not a contract guaranteeing that every question or method will remain unchanged.
Research-grant proposal
A grant proposal must align closely with the funding opportunity. In addition to academic merit, reviewers may assess:
- Significance.
- Innovation.
- Impact.
- Team expertise.
- Project management.
- Risk.
- Budget.
- Value for money.
- Data management.
- Research environment.
- Stakeholder engagement.
- Dissemination.
Generic grant proposals are rarely competitive because each funder defines its own priorities and review criteria.
Worked Academic Proposal Example
The following example is hypothetical. It demonstrates alignment rather than reporting a completed study.
Proposed title
Effect of Structured Peer Feedback on the Quality of First-Year Undergraduate Research Proposals: A Mixed-Methods Pilot Study
Background and problem
First-year students in the selected programme prepare a short research proposal as their final assessment. Most formal feedback is provided after submission, when students can no longer revise the assessed work. Although peer feedback could provide earlier support, the programme does not currently use a standardized peer-review process. Evidence is needed about whether such a process is feasible, useful and associated with measurable improvement in proposal quality.
Aim
To evaluate the feasibility and potential educational value of a structured peer-feedback process for first-year research proposals.
Research questions
- How do students’ proposal-rubric scores change after two structured peer-feedback sessions?
- How do students describe the usefulness and challenges of the feedback process?
- Is the process feasible for tutors to deliver within existing seminar time?
Design
A mixed-methods pilot study will combine a single-group pretest–posttest comparison with student questionnaires, tutor implementation records and a small number of semi-structured interviews.
Participants
Students enrolled in two first-year research-methods seminar groups will be invited to participate. Participation in the research component will be voluntary and will not affect course grades.
Data collection
- Draft proposals will be assessed before the intervention using a standardized rubric.
- Students will complete two peer-feedback sessions using an instructor-developed checklist.
- Revised proposals will be assessed using the same rubric.
- An anonymous questionnaire will examine perceived usefulness and difficulties.
- A purposive subsample will be invited to short interviews.
- Tutors will record preparation and delivery time.
Analysis
Pre-intervention and post-intervention rubric scores will be summarized and compared using a paired analysis appropriate to the score distribution. Questionnaire responses will be summarized descriptively. Interview data will be analyzed thematically. The findings will be integrated when assessing feasibility and potential effectiveness.
Ethics
Students will receive study information and provide consent. Research participation will be separated from normal assessment. Proposal files used for research will be coded, stored securely and accessed only by the approved research team. Tutors responsible for grading will not receive identifiable questionnaire or interview responses.
Limitations
The study will involve a small, non-random sample from one programme. Score changes cannot establish that peer feedback alone caused improvement because students may also revise their work through independent study or tutor guidance. The study is therefore framed as a pilot rather than a definitive effectiveness trial.
Expected contribution
The project will determine whether the intervention and data-collection procedures are workable and will provide preliminary evidence to guide a larger controlled evaluation.
This example is coherent because the problem, questions, methods, ethics, analysis and claims are aligned.
Copyable Proposal Template
Title page
Proposal title:
Writer or research team:
Institution or organization:
Recipient:
Date:
Version:
Executive summary or abstract
Briefly state:
- The problem or need.
- The main objective.
- The proposed approach.
- The expected output or contribution.
- The support or decision requested.
1. Introduction
Introduce the topic, context and purpose of the proposal.
2. Problem or need statement
Define the specific problem, evidence, affected group and consequences.
3. Background and rationale
Summarize relevant evidence, previous work and the gap the proposal addresses.
4. Aim and objectives
Aim:
[State the overall purpose.]
Objectives:
- [Objective one]
- [Objective two]
- [Objective three]
5. Research questions or intended outcomes
[List the questions, hypotheses or project outcomes.]
6. Proposed approach or methodology
Explain:
- Design or strategy.
- Setting.
- Participants, users, cases or data.
- Sampling or selection.
- Activities or data collection.
- Analysis or evaluation.
- Quality-control procedures.
7. Scope and deliverables
Included:
[Define included work.]
Excluded:
[Define boundaries.]
Deliverables:
[List the expected outputs.]
8. Ethics, risk and data management
Describe ethical safeguards, major risks, mitigation and data-handling procedures.
9. Team and responsibilities
| Person or role | Responsibility | Relevant capability |
|---|---|---|
10. Timeline
| Activity | Start | End | Responsible person | Output |
|---|---|---|---|---|
11. Budget and resources
| Item | Quantity | Unit cost | Total | Justification |
|---|---|---|---|---|
12. Evaluation and success criteria
Explain what will be measured, how it will be measured and what will indicate successful completion.
13. Expected contribution or benefit
State the likely academic, practical, organizational or social value.
14. Limitations
Identify important constraints and explain how they affect the proposal.
15. Conclusion and requested decision
Restate the value and feasibility of the plan and specify the approval, funding or action requested.
References
[List every cited source in the required style.]
Appendices
[List essential supporting documents.]
How to Write a Proposal Introduction
A proposal introduction should identify the context, problem and purpose quickly. It should answer the reader’s initial questions without delaying the main argument.
A useful introduction pattern is:
- Establish the context.
- Identify the specific issue.
- Explain why it matters.
- State the proposed response.
- Preview the proposal.
Example:
Universities increasingly expect undergraduate students to design independent research projects, yet many students encounter difficulty translating a broad topic into a feasible proposal. In the selected programme, proposal feedback is usually provided only after final submission. This project proposes a structured peer-feedback process that allows students to review and revise their work during development. The study will evaluate the process through proposal-rubric scores, student feedback and tutor implementation records.
Avoid beginning with a dictionary definition, an unsupported global claim or several paragraphs of remote historical background.
How to End a Proposal
A proposal conclusion should not introduce a new method, cost or objective. It should bring the argument together and make the requested decision clear.
Include:
- The central problem.
- The proposed response.
- The main value.
- Evidence of feasibility.
- The requested approval or action.
Example:
The proposed pilot addresses the current absence of formative, structured feedback during first-year proposal development. Its limited scope, use of existing seminar sessions and mixed-methods evaluation make it feasible within one semester. Approval is requested to conduct the study following institutional ethical review and to use the findings when deciding whether a larger evaluation is justified.
Advantages of Writing a Proposal
A well-designed proposal can:
- Clarify an idea before resources are committed.
- Reveal weaknesses in scope or methodology.
- Align team members and stakeholders.
- Establish responsibilities and expectations.
- Support ethical and regulatory review.
- Estimate time and cost.
- Create criteria for evaluating progress.
- Enable comparison among competing ideas.
- Provide a foundation for a project plan or research protocol.
The writing process itself may improve the project because it forces assumptions to become explicit.
Limitations of Proposals
A proposal also has limitations:
- It describes expected rather than observed results.
- Early assumptions may later change.
- Strict templates can oversimplify complex research.
- Review decisions may be influenced by disciplinary preferences or available resources.
- Detailed preparation can consume substantial time.
- Writers may overpromise to make a proposal appear competitive.
- A successful proposal does not guarantee successful implementation.
- A rejected proposal is not necessarily evidence that the underlying idea has no value.
Treat the approved proposal as an accountable plan while retaining justified flexibility when evidence or circumstances change.
Digital Tools for Proposal Writing
Literature-search tools
Academic databases and discovery services help identify relevant evidence. Select databases appropriate to the discipline and document important search terms and filters.
Reference managers
Tools such as Zotero, EndNote and Mendeley can:
- Store sources.
- Attach files.
- Organize reading.
- Insert citations.
- Generate reference lists.
- Support collaborative libraries.
Reference-manager output should still be checked for incorrect capitalization, missing fields, duplicate entries and inconsistent metadata.
Planning tools
Project-management or spreadsheet tools can help create:
- Task lists.
- Gantt charts.
- Dependency maps.
- Budgets.
- Risk registers.
- Responsibility matrices.
- Submission checklists.
Use tools that simplify the process rather than adding unnecessary administration.
Analysis and sample-planning tools
Depending on the proposal, researchers may use statistical software, qualitative-analysis software, power-analysis tools, survey platforms, laboratory software or programming languages.
Name software only when it forms a meaningful part of the method. The proposal should explain the analytical procedure, not merely list product names.
Collaborative writing and version control
Cloud documents can support comments and simultaneous editing. More technical projects may use formal version-control systems.
Establish:
- File-naming conventions.
- Version ownership.
- Approval procedures.
- Comment resolution.
- Secure access.
- Backup.
- A final authoritative copy.
Can Artificial Intelligence Be Used to Write a Proposal?
AI tools may assist with brainstorming, outlining, language editing, question generation, formatting or identifying areas that require clarification. They should not replace scholarly judgment, source verification, methodological design or responsibility for the final document.
Responsible use requires the writer to:
- Follow institutional, course, publisher and funder policies.
- Verify every factual claim and reference.
- Read the original sources.
- Avoid entering confidential, proprietary, identifiable or unpublished sensitive material into tools without appropriate safeguards.
- Check for fabricated citations and distorted summaries.
- retain responsibility for research design and interpretation.
- disclose material AI assistance when required.
- preserve records when institutional policy requires them.
- ensure that submitted writing represents the author’s genuine understanding.
AI-generated text can sound confident while containing methodological contradictions, false references or unsuitable recommendations. It should be treated as unverified assistance rather than authoritative evidence.
Common Proposal-Writing Mistakes
| Mistake | Why it weakens the proposal | Better approach |
|---|---|---|
| Ignoring instructions | May make the submission noncompliant | Build a requirement checklist first |
| Starting with a broad topic | Leaves the actual problem unclear | Define a specific, researchable or actionable problem |
| Writing for oneself | Assumes knowledge the reviewer may not have | Explain context and necessary terminology |
| Listing literature without synthesis | Does not establish a gap | Compare findings, methods and limitations |
| Claiming that no research exists | Usually difficult to prove | Define the precise evidence, context or method gap |
| Using vague objectives | Makes evaluation difficult | Use specific action verbs and realistic outputs |
| Naming a method without justification | Does not show methodological reasoning | Explain why it answers the question |
| Misaligning questions and analysis | Produces evidence that cannot answer the question | Map every question to data and analysis |
| Overpromising impact | Reduces credibility | Separate direct outcomes from possible longer-term impact |
| Underestimating time | Makes the plan appear unrealistic | Include approvals, recruitment, checking and revision |
| Providing unexplained costs | Prevents value assessment | Link every cost to an activity |
| Hiding limitations | Suggests weak critical judgment | Acknowledge and manage limitations |
| Adding ethics as an afterthought | Separates safeguards from the design | Integrate ethics into recruitment, collection and storage |
| Inventing expected findings | Confuses a proposal with a completed report | State expected contributions without fabricating results |
| Using unsupported AI-generated references | Damages accuracy and trust | Verify references against original publications |
| Editing only grammar | Leaves reasoning errors untouched | Review logic, alignment, compliance and feasibility |
Final Proposal Checklist
Requirements
- Have all instructions been followed?
- Are all required headings present?
- Is the document within the word or page limit?
- Are the correct forms and appendices included?
- Is the submission version clearly identified?
Problem and rationale
- Is the problem specific?
- Is it supported by relevant evidence?
- Is the gap clear?
- Does the rationale explain why the work is needed?
Objectives and alignment
- Is the aim concise?
- Are the objectives achievable?
- Do the questions match the objectives?
- Does each objective have a corresponding method?
- Do the methods produce evidence relevant to the questions?
Feasibility
- Is the scope realistic?
- Is access to participants, data or facilities credible?
- Is the timeline achievable?
- Are responsibilities clear?
- Is the budget justified?
Research quality
- Is the design appropriate?
- Are sampling and recruitment explained?
- Are measures or data sources suitable?
- Is the analysis specified?
- Are validity, rigor, bias or reflexivity addressed appropriately?
Ethics and data
- Are participant risks identified?
- Are consent and confidentiality explained?
- Is data storage secure?
- Are retention and sharing plans appropriate?
- Are approvals identified?
Communication
- Can a non-specialist understand the main proposal?
- Are technical terms defined?
- Are paragraphs focused?
- Do tables and figures add information?
- Are citations and references accurate?
- Is the requested decision explicit?
Conclusion
Writing a strong proposal requires more than placing an idea into a standard template. The proposal must connect a clearly defined problem with evidence, objectives, an appropriate method, realistic resources, ethical safeguards and measurable criteria for success.
Begin with the instructions and the reader’s decision. Then test the alignment of every section. A proposal becomes persuasive when reviewers can see not only that the idea is worthwhile, but also that the writer has developed a credible plan for carrying it out.
