How to Cite a Book in APA, MLA and Chicago
How to cite a book in APA 7th, MLA 9th and Chicago 17th, with reference and in-text examples for one or two authors, editions, translations and chapters.
Last updated 10 min read
Key takeaways
A research proposal describes a project you have not done yet and makes the case for doing it. Students write them for a dissertation or thesis, for a capstone or independent study, and when applying to some graduate programs; researchers write them to win funding. The reader changes, but the questions they bring stay the same: is this question worth answering, can it be answered, is the plan realistic, and can this person carry it out?
That makes a proposal an argument, not an overview of a topic. A strong one is specific where weak ones are vague: it names the sources or participants, the method of analysis and the weeks each stage will take. It is also honest about what it cannot know. Nobody expects you to predict your findings, and a proposal that announces them reads as if the conclusion came first and the research second.
Approval does not freeze the project. Questions sharpen and plans shift once the work begins. A clear proposal makes those changes easier to explain, because you and your supervisor can see exactly what moved and why.
Most proposals use some version of the sections in the table below, though names and order vary. Where your guidelines differ, follow them exactly: a reviewer working through a stack of proposals looks for their own headings in their own order. Some guidelines also ask for an abstract, a budget or a statement of expected outcomes, which should describe what the project will contribute, not what it will prove.
| Section | Question it answers | What to include |
|---|---|---|
| Title | What is this project about? | A specific title that names the topic and, where possible, the setting or approach |
| Introduction and background | Why does this matter? | The context, the problem and a brief case for studying it now |
| Research question and aims | What exactly will you find out? | One main question, any sub-questions, and the aims and objectives that follow |
| Literature review | What is known, and what is missing? | The key debates and findings, ending at the gap your project addresses |
| Methodology | How will you answer the question? | Design, sources or participants, data collection and analysis, and why each fits |
| Ethics and limitations | What could go wrong? | Consent, data storage, approvals needed, and the limits of your design |
| Timeline and resources | Can it be done in the time available? | Dated phases, plus any access, equipment, travel or costs |
| References | What does your case rest on? | Every source cited, in the required style |
Start with the guidelines, not a blank page. Note the word count, required headings, citation style, deadline and the criteria the proposal will be judged on. If you are applying to a graduate program or approaching a possible supervisor, read what their research covers too; a proposal that fits a department's strengths is easier to support.
Then check that you have the two things no proposal can do without. The first is a focused research question, one sentence you could defend; the guide to writing a good research question shows how to get there. The second is a reason the question is still open: a gap, a disagreement or an untested setting in existing work. The limitations and future-research paragraphs of recent studies are the usual place to spot one, and the guide to reading a research paper quickly and properly shows how to get to them without reading every paper front to back.
If you cannot state either yet, read more before drafting. A proposal written around a vague question ends up with vague methods, and polishing the prose later will not fix that.
You do not have to write the sections in the order they appear. This sequence starts with the parts that define the project and leaves the framing until last, when you know exactly what you are framing:
Four sections carry most of the weight. Here is what a reviewer looks for in each.
Open with the problem, not the history of the field. In a paragraph or two, set out the context, state the issue and explain why it matters, then lead the reader to your question. By the end of the first page, a reviewer should know exactly what you plan to study.
This is not a full literature review. It is a selective account of the main positions and findings, organized by theme, that ends at the gap your project fills. Cite the key works, show you know where the debate stands, and stop once your question looks necessary.
Be concrete: what data, from whom or where, collected how and analyzed how. Justify each choice, such as why interviews rather than a survey, or why this archive rather than another. Write in the future tense, name the main limitation of your design and say how you will reduce it. The guide to writing a methodology section covers this in more depth.
Break the work into phases, such as ethics approval, data collection, analysis and writing, each with dates. Leave room for delays you cannot predict, especially wherever you depend on other people: interviewees, archives or approval committees.
Aims and objectives confuse many students, so here is a short worked example built around a hypothetical project on community gardens. The aim states the overall purpose. The objectives are the concrete steps that achieve it, and each one should be something you can visibly finish.
As you read it, notice that every objective implies a method and a block of time in the timeline: gathering documents, interviewing coordinators, comparing the two. If an objective maps to nothing in your methods, either the methods are missing something or the objective does not belong. Notice too that the project claims to explain one city, not every city:
The literature review is often the slowest part of a proposal, and Cavua's Work space is built for that stage. Upload your key papers as PDFs or Word files and ask across several at once where they agree, where they disagree and what none of them examines. Answers point to the page, so you can check each claim before it goes into your review, and you can export a session to keep a record of what you found.
Before you meet your supervisor, rehearse: video or voice call the tutor about your documents and explain your question, method and gap out loud, or use โQuiz meโ to check you know your key sources. Your plan sets how much of each you can use, and the pricing page states each plan's allowance.
Before you submit, check your draft for these problems. Each one makes a reviewer doubt either the question or the plan:
How to cite a book in APA 7th, MLA 9th and Chicago 17th, with reference and in-text examples for one or two authors, editions, translations and chapters.
How to cite a website in APA 7th, MLA 9th and Chicago 17th, with patterns for pages with no author or no date, organizations as authors and pages that change.
Research paper structure explained: what goes in each IMRaD section, the tense and length conventions, the order to write it in, and when not to use IMRaD.
Chicago citation in the 17th edition: how footnotes and shortened notes work, author-date in-text citations, and bibliography examples for books and articles.
Learn how to paraphrase a source properly: a five-step method, a worked before-and-after example, citation formats, and the mistakes that count as plagiarism.
Learn how to write an abstract step by step: what to include, how long it should be, a move-by-move template, an annotated example and the mistakes to avoid.
It depends on the purpose and the guidelines. A proposal for a course project or undergraduate dissertation may run to a few pages, while proposals for doctoral programs and research funding are usually much longer and more detailed. Always follow the stated word count, and if none is given, ask; going far over or under suggests you have not read the brief.
Most include a title, an introduction with background, the research question and aims, a short literature review, the methodology, ethics and limitations, a timeline and references. Some also require an abstract, a budget or a statement of expected outcomes. Use the headings and order your guidelines specify, since reviewers look for them.
Use the future tense for the work you plan to do, as in this study will interview or the analysis will compare. Use the present tense for what existing research shows and what your proposal argues, and the past tense for anything already done, such as a pilot study. Keep tenses consistent within each section.
An aim is the broad purpose of your project, usually a sentence or two describing what you want to understand or achieve. Objectives are the specific steps that will achieve the aim, such as collecting particular documents or interviewing a defined group. Each objective should be something you can clearly complete, and each should connect to your methods.
A research proposal describes a project before it happens and argues that it is worth doing and feasible. A research paper reports a project after it is done, with results and conclusions. Proposals are written mostly in the future tense and end with a plan; papers are written mostly in the past tense and end with findings.
Usually yes, within reason. Research questions often sharpen once you start reading and collecting data, and supervisors expect some change. Discuss significant changes before making them, and keep a note of what changed and why. If the change affects human participants, you may need to update your ethics approval before you continue.
Every Cavua course comes with a 24/7 tutor you can video call, speak to or chat with โ on the material you are actually studying.