Research Proposal and Scope Development

What should a research proposal contain?

An understanding section restating the decision and question; objectives; the approach written so a non-researcher can see why it answers the question; scope in three parts, including exclusions; deliverables with revision rounds and acceptance criteria; a timeline showing both parties' obligations; an assumptions register; a plain statement of what the study will not answer; scope options; and governance covering data protection, ethics, AI involvement and named accountability.

How do I explain a research method to someone who is not a researcher?

Write three linked statements per objective: what we will do, what that produces, and why that answers your question. The third is usually missing and is the only one they can evaluate. Never let a method term appear without its purpose in the same sentence, and move technical specification to an appendix where the technical reader will find it.

How do I stop scope creep on research projects?

Write the exclusions down before the work starts, resolve the boundary cases explicitly, and keep an assumptions register with consequences. Then a mid-project addition becomes a factual conversation ("this rests on assumption four, which has not held") rather than a negotiation about goodwill. Deliverable ambiguity is the other main source: specify length, audience, revision rounds and an acceptance criterion.

What should be in the out-of-scope list?

The things a client will reasonably assume are included: additional markets or languages, re-cuts of the data for another audience, extra presentations, raw data and transcripts, translation of deliverables, workshops, and further analysis after delivery. A list long enough to feel slightly uncomfortable is about right, because every omitted item is a conversation that will otherwise happen under time pressure.

Should I tell a client what the research will not answer?

Yes, in the proposal, near the front, in plain language. The commercial argument is stronger than the ethical one: a study is judged against what its audience assumed it covered, and a list they read before buying is the cheapest possible protection against a disappointed client.

How do I turn down a research brief without losing the client?

State what was asked, why it will not answer the question in one or two sentences of followable reasoning, what would answer it, and what that costs in scope terms. Give them something useful even if they go elsewhere, and make sure it does not read as a bid for more budget. A specific, useful decline is remembered favourably.

What is the difference between a research plan and a research proposal?

The plan is internal: activities, dependencies, owners, risks and the honest timeline the team will work to. The proposal is the external offer: the approach explained to a buyer, the scope and exclusions, the assumptions, the deliverables and the commitment. Build them in that order, and where they conflict, the internal plan is the truth.

How should I present options when the budget will not cover what is needed?

As options answering different questions, not as good, better and best. Propose what the question needs first, then show the narrowing and what it removes from the answer. That order makes the compromise legible and it survives the moment when the study is judged. The alternative, quietly buying the same scope with less sample or less analysis, is negotiating quality invisibly.