Before You Submit: A Practical Checklist for Research Proposals

A strong research proposal does not need to be perfect. It does, however, need to be coherent.

Before a supervisor, funder, ethics committee, or institutional reviewer gets into the finer details, they are usually asking a few basic questions: What is the problem? Why does it matter? What exactly will be done? Are the methods defensible? Is the work feasible? Are participants protected?

Many proposals struggle not because the idea is weak, but because the proposal does not make the idea easy to understand. The good news is that many of these issues can be caught before submission.

Here is a practical checklist to use before sending your proposal out.

1. Is the research problem clear?

Your proposal should not make the reader search for the problem. Within the first few paragraphs, it should be clear what issue you are addressing, who is affected, and why the issue matters.

A common mistake is writing a long background section that gives context but never lands the point. Background is useful, but it should lead the reader toward a specific problem, not wander through everything ever written on the topic.

A useful test is this: after reading the introduction, can someone explain your study problem in one sentence? If not, the framing needs work.

2. Do the objectives match the research question?

Your research question and objectives should speak to each other. If the question is about experiences, the objectives should not suddenly focus only on prevalence. If the aim is to assess implementation, the objectives should not read like a clinical effectiveness trial unless that is truly the design.

Each objective should be specific, answerable, and linked to a method. Avoid objectives that are too broad, such as "to assess factors associated with health service use," without defining which factors, which service, which population, and which context.

A good objective gives the methods section something to do.

3. Is the methodology defensible?

The methods section should explain how the study will answer the research question. It should not simply list techniques.

Check whether you have clearly described the study design, setting, population, eligibility criteria, sampling approach, sample size or justification, data collection procedures, variables or topics of interest, and analysis plan.

For quantitative studies, reviewers will look for clarity on sample size, measurement, variables, and analysis. For qualitative studies, they will expect a clear rationale for participant selection, data collection methods, depth, variation, and analytic approach. For mixed-methods studies, they will want to understand how the qualitative and quantitative components relate to each other.

The key question is: if someone followed your methods section, could they conduct the study as intended?

4. Are the ethics documents consistent?

Ethics submissions often get delayed because the documents do not match. The protocol says one thing, the consent form says another, and the data collection tool quietly introduces a third version of the study.

Before submission, check consistency across the protocol, consent forms, assent forms where applicable, recruitment materials, data collection tools, letters of support, and any institutional documents.

Pay close attention to study procedures, risks, benefits, confidentiality, voluntary participation, compensation or reimbursement, data storage, and who will access the data.

Small inconsistencies can trigger avoidable revisions. Ethics committees are not being dramatic; they are checking whether participants will be clearly informed and protected.

5. Does the budget match the work?

A budget should reflect the actual scope of the study. If you propose fieldwork in multiple sites, the budget should show how travel, supervision, data collection, training, communication, transcription, translation, data management, and dissemination will be handled.

A weak budget can make a strong proposal look unrealistic. A bloated budget can make it look careless. The goal is not to make the budget small; it is to make it believable.

Every major activity in the workplan should have a budget implication, and every major budget line should be traceable to the workplan.

6. Is the timeline realistic?

Research timelines often look brave on paper and brutal in practice. Build in time for approvals, tool refinement, recruitment delays, fieldwork supervision, data cleaning, transcription, analysis, writing, and revision.

If your timeline assumes everything will go right, it is probably wrong.

A good timeline is not slow. It is honest.

7. Are all attachments ready?

Before submission, confirm that all required attachments are included and properly named. These may include the protocol, consent forms, tools, CVs, letters of support, administrative approvals, budget, workplan, recruitment materials, and any funder- or REC-specific forms.

Missing attachments are one of the easiest ways to delay review.

Final check

Before submitting, ask yourself one simple question:

Can a reviewer understand what we want to do, why it matters, how we will do it, and whether it is feasible and ethical?

If the answer is yes, the proposal is closer to submission-ready.

If the answer is no, do not panic. That is exactly what revision is for. Better to fix the gaps before submission than to meet them again in a reviewer's comment letter, where they arrive wearing shoes.