The Literature Review in a PhD Dissertation Proposal: What It Must Argue, Not Just Summarize
Your proposal literature review is a case for the project, not a summary of the field. This guide explains how to prove a gap exists, which literatures to include, why organizing by source fails, and how to connect every claim to your research questions and methods.

The Literature Review in a PhD Dissertation Proposal: What It Must Argue, Not Just Summarize phd dissertation proposal literature review
The literature review in a PhD proposal must argue for the necessity of your project by establishing a real, significant gap and positioning your work relative to existing approaches. It should be selective and focused, organized by argument rather than source, and explicitly connected to your research questions and methods.
You have a folder of 80 PDFs and a blank document titled 'Chapter 2.' The proposal deadline is in six weeks. You know the literature review needs to show you have read the field, but the advice you keep hearing, 'be comprehensive,' 'cover everything', makes the task feel impossible. This guide treats the literature review as an argument, not an archive. It explains what the review must accomplish at the proposal stage, how to prove a gap exists, which literatures to include (and which to cut), why organizing by source fails, how long it should be, and how to connect every claim to your research questions and methods. A committee should read your review as a case for your project, not as a test of your endurance.
What job does the literature review do in a proposal that it does not do in the final dissertation?
In the final dissertation, the literature review is a comprehensive foundation. It demonstrates mastery of the field, situates your findings, and acknowledges the many strands of work that inform your study. In the proposal, the review has a narrower, more argumentative job: it must justify why the dissertation should be written at all. The proposal review is a case for the project, not a summary of the field.
A committee reading your proposal is asking three questions: Is there a gap? Does it matter? Can this candidate fill it? The literature review is where you answer those questions. It must show that the gap is real, that it is significant enough to warrant a multi-year project, and that your approach is plausible. The final dissertation review can be expansive; the proposal review must be persuasive.
Consider the difference in audience and purpose. The final dissertation is read by examiners who want to see that you know the field and that your contribution is original. The proposal is read by a committee that wants to see that you have a viable project. They are not looking for an exhaustive summary; they are looking for evidence that you can identify a problem, define its boundaries, and design a study to address it. The literature review in the proposal is thus a strategic document. It selects from the literature to build an argument, not to display erudition.
This means the proposal review will necessarily be incomplete. It will omit many worthy works. That is not a flaw; it is a feature. The review must be focused enough to make the gap visible. If you try to cover everything, the gap gets buried under a pile of citations. The committee will not be able to see what is missing because they are distracted by what is present.
Another difference is the treatment of method. In the final dissertation, the literature review often includes methodological debates that inform your design. In the proposal, you have a separate methods section, so the literature review should only cover methodological literature insofar as it establishes the gap or justifies your approach. You do not need to review every possible method; you need to show that the methods you propose are appropriate and that no existing study has used them to address your gap.
Finally, the proposal review must anticipate the committee's objections. In the final dissertation, you can respond to objections in the discussion. In the proposal, you must preempt them. The most common objection is 'this gap is already addressed by X.' Your review must show that you know X and that X does not fully address the gap. This requires a careful, critical engagement with the closest prior work, not a dismissive footnote.
How does the review prove a gap exists rather than merely asserting one?
Asserting a gap is easy: 'No study has examined X.' Proving it is harder. The committee will not take your word for it; they will check. They will think of studies you missed. They will point to work in adjacent fields. They will ask whether the gap is real or just a product of your search strategy.
To prove a gap, you need to do three things: define the gap precisely, show what has been done, and explain why what has been done does not close it. The first step is definitional. A gap is not 'no one has studied X.' A gap is a specific unanswered question or unresolved contradiction. For example, 'No one has studied how remote workers in small firms negotiate boundaries between work and home' is a topic, not a gap. A gap would be: 'Existing studies of remote work boundaries focus on large corporations and assume stable home environments; we do not know how workers in small firms, where roles are less defined, manage boundaries when home and work are physically proximate.' That is a gap you can argue.
The second step is to demonstrate what has been done. This is where the review becomes selective but thorough. You must cover the major studies that address your topic, including those that come closest to your gap. You need to show that you know the landscape. But you do not need to cover everything; you need to cover what matters for the gap. If you are studying remote work in small firms, you need to review the literature on remote work boundaries, but you can be selective about the literature on small firms in general. You need to show that the intersection of these literatures leaves a hole.
The third step is to explain why the existing work does not close the gap. This is the critical part. You cannot simply say 'no one has looked at small firms.' You must explain why the existing studies, which might include small firms tangentially, do not answer your question. Perhaps they treat small firms as a homogeneous category, or they focus on managerial perspectives rather than worker perspectives, or they use methods that cannot capture boundary negotiation. You need to engage with the closest work and show its limitations.
A useful technique is to build a table or matrix in your mind (and perhaps in an appendix) that lists the key studies and their dimensions: population, context, method, findings. Then you can see where the holes are. But in the review itself, you should not present a table; you should present an argument. The argument might go: 'Studies A and B examined boundary management in large firms and found X. Studies C and D extended this to small firms but focused on formal policies. Neither stream captures the informal, relational aspects of boundary management that are likely to be salient in small firms where formal policies are absent.' This shows that you know the work and that the gap is a logical extension, not a random omission.
Proving a gap also requires showing that it is significant. Significance can come from theoretical importance (the gap challenges a core assumption), practical importance (the gap affects a large population or has policy implications), or methodological importance (the gap requires a new approach). You should articulate why filling this gap matters. If you cannot explain why anyone should care, the committee will wonder why they should approve the project.
Finally, you must anticipate the objection that the gap is already addressed. This means you need to search for the study that might fill your gap and show that it does not. Sometimes this means engaging with work outside your immediate field. For example, if you are in education and studying remote work, you might need to look at management literature. The committee will respect you for it.
Which literatures belong in the review, and which should be left out?
Scope boundaries are essential. A common failure mode is the kitchen-sink review: everything remotely related gets included. This dilutes the argument and signals that you cannot prioritize. The proposal review should include only those literatures that are necessary to establish the gap and justify your approach. There are three categories of literature that belong: the literature that defines the problem, the literature that has attempted to solve it, and the literature that informs your method.
The first category is the literature that defines the problem. This is the work that establishes the phenomenon you are studying. If you are studying remote work boundary management, this includes the classic studies of boundary theory, work-family conflict, and remote work. You need to show that you understand the core concepts and debates. But you do not need to review every study of remote work; you need to review the ones that set up the gap.
The second category is the literature that has attempted to solve the problem. This is the work that comes closest to your gap. You need to review it critically to show why it falls short. This is where you demonstrate your knowledge of the field's central debates. You should not just cite the consensus; you should show where scholars disagree. For example, some studies might argue that boundary management is a matter of individual preference, while others argue it is shaped by organizational norms. Your gap might emerge from this debate: if the debate has only been examined in large firms, then small firms are an important test case.
The third category is the literature that informs your method. If you are using a particular qualitative approach or a specific survey instrument, you need to cite the methodological literature that justifies it. But again, be selective. You do not need to review all of qualitative methodology; you need to cite the key works that support your choices.
What should be left out? Literature that is only tangentially related. Literature that is outdated, unless it is foundational. Literature that is in a different field and does not speak to your gap. Literature that you find interesting but that does not serve the argument. This last one is the hardest to cut. You may have read a fascinating study that you want to include, but if it does not help establish the gap or justify the project, it belongs in a footnote at most.
Another way to think about scope is to define your boundaries explicitly. In the review, you can state: 'This review focuses on studies of boundary management in organizational contexts. It does not review the literature on personality traits that influence boundary preferences, except where those traits interact with organizational context.' This shows the committee that you have made deliberate choices. It also protects you from criticism that you missed something: you can say it was outside your scope.
But be careful: excluding a literature that the committee thinks is essential is risky. You need to justify your exclusions. If you are excluding a literature, explain why it is not relevant to your gap. For example: 'Studies of boundary management in home-based businesses are not reviewed here because they typically involve owners who have control over their schedules, whereas this study focuses on employees in small firms.' That is a defensible boundary.
Why summarizing sources in order fails, and what to organize around instead
The annotated bibliography trap is the most common failure in proposal literature reviews. It happens when you organize the review source by source: 'Smith (2010) found X. Jones (2012) found Y. Lee (2015) found Z.' This is not a review; it is a list. It fails because it does not build an argument. The reader cannot see the gap because they are lost in the details of individual studies. It also signals that you have not synthesized the material.
The alternative is to organize around arguments, themes, or debates. Instead of 'Smith found X,' you write: 'One stream of research argues that boundary management is primarily an individual cognitive process (Smith, 2010; Lee, 2015). Another stream emphasizes organizational norms and structures (Jones, 2012; Patel, 2018). These streams have rarely been integrated, and when they have, the focus has been on large firms.' This shows that you understand the relationships between studies and that you can identify patterns.
Organizing by argument does not mean ignoring individual studies. You still cite them, but you use them as evidence for a point. You group them by what they claim or assume. You compare and contrast them. You show how they build on or contradict each other. This is synthesis.
There are several ways to structure a synthesis. You can organize by theoretical perspective (e.g., functionalist vs. interpretive). You can organize by methodological approach (e.g., quantitative vs. qualitative). You can organize by population or context (e.g., large firms vs. small firms). You can organize by chronology, but only if the field has genuinely evolved in a way that matters for your gap. Often, chronology is the least useful because it does not reveal the conceptual structure.
The best structure depends on your gap. If your gap is about a missing context, organize by context. If your gap is about an unresolved debate, organize by the debate. If your gap is about a methodological limitation, organize by method. The structure should make the gap obvious.
A useful technique is to write a paragraph that begins with a claim, then supports it with multiple citations. For example: 'Studies of boundary management in small firms have largely relied on owner-manager accounts (e.g., Smith, 2010; Jones, 2012). This has produced a top-down view of how boundaries are managed, but it has left the employee perspective largely unexplored.' This paragraph makes a claim (small firm studies rely on owner-manager accounts), supports it with citations, and points to the gap (employee perspective). That is synthesis.
Another technique is to use a matrix or table in your own notes to map studies against dimensions, then write from the matrix. But do not put the matrix in the proposal unless it is genuinely helpful. The proposal should be prose that argues.
How long and how exhaustive should the proposal's literature review be?
There is no universal word count, but there is a principle: the review should be proportionate to the proposal stage. It is indicative, not exhaustive. It should be long enough to establish the gap and demonstrate command of the field, but not so long that it becomes a draft chapter. In many programs, the literature review in a proposal is 15-30 pages double-spaced, or 3,000-6,000 words. But these are rough guidelines. The key is that it should be focused.
Exhaustiveness is a trap. You cannot read everything, and you should not try. The proposal is a plan; the final dissertation will have a more comprehensive review. The proposal review should cover the key works that define the gap and the closest attempts to address it. It should also show that you know the major debates. But it does not need to cover every study ever conducted.
A good rule of thumb is that the review should be as long as necessary to make the argument and no longer. If you can make the argument in 10 pages, do not pad it to 30. Padding dilutes the argument and signals insecurity. The committee will appreciate concision.
However, being too short can also be a problem. If the review is only 5 pages, the committee may doubt that you have a command of the field. The review needs to demonstrate that you have done the reading. This means citing a sufficient number of works, but again, quality over quantity. A well-chosen set of 50-80 references is often enough for a proposal, depending on the field.
Another consideration is the balance between breadth and depth. You need to show breadth (you know the major streams) and depth (you understand the key studies in detail). A common mistake is to cite many studies superficially. Better to engage deeply with a few key studies and show how they relate to your gap.
The review should also be proportionate to the scope of the project. A PhD dissertation is a multi-year project, so the gap should be significant enough to warrant that time. But the review does not need to prove that the gap is so huge that it will take five years to fill. It needs to show that the gap is real and that the project is feasible.
Finally, remember that the proposal is a genre with its own conventions. In some fields, the literature review is integrated into the introduction; in others, it is a separate chapter. Follow the conventions of your field, but always prioritize the argument.
How should the review connect to the research questions and methods that follow it?
The literature review does not stand alone. It must connect forward to the research questions and methods. Every gap you identify should map to a research question, and every research question should have a method that can answer it. This mapping is important for the proposal's coherence.
A common failure is a disconnect between the review and the rest of the proposal. The review identifies a gap, but the research questions do not address it. Or the methods are not suited to answering the questions. The committee will notice this. They will ask: 'You said the gap is X, but your questions are about Y. Why?'
To avoid this, you should design the review and the research questions together. As you write the review, you should be thinking: What question does this gap imply? What method would answer that question? Then, when you write the research questions, you can refer back to the gap: 'As established in the literature review, there is a gap in understanding how employees in small firms negotiate boundaries. This study addresses that gap by asking: How do employees in small firms describe their boundary management strategies?'
The methods section should then justify why your chosen methods are appropriate for answering those questions. If you are using interviews, explain why interviews are suited to exploring boundary management strategies. If you are using surveys, explain why a survey can capture the relevant dimensions. The methods should also address the limitations of prior work: if prior work used only owner-manager accounts, your method of interviewing employees directly addresses that limitation.
The connection should be explicit. You can use signposting: 'This gap leads to the first research question...' or 'To answer this question, the study will use...' This helps the reader see the logic.
Another way to ensure connection is to create a table that maps gaps to questions to methods. This table can be in the proposal or in your notes. It forces you to be consistent.
Finally, the review should also connect to the significance section. If you argue that the gap is significant because it affects a large population, your methods should be able to speak to that population. If you argue that the gap is theoretically important, your methods should be able to test or explore the theory.
The literature review in a proposal is an argumentative document. It must establish a gap, prove it is real and significant, position your project relative to existing work, define scope boundaries, demonstrate command of debates, avoid the annotated bibliography trap, be proportionate, and connect forward. When done well, it turns a pile of PDFs into a compelling case for your project.
Frequently Asked Questions
How is the literature review in a proposal different from the one in the final dissertation?
The proposal review argues for the project's necessity by establishing a gap, while the final dissertation review provides a comprehensive foundation for the findings. The proposal review is selective and strategic; the final review is more exhaustive.
How do I prove a gap exists rather than just asserting it?
Define the gap precisely, show what has been done in the closest studies, and explain why those studies do not close it. Engage critically with the nearest work and anticipate the objection that the gap is already addressed.
Which literatures should I include in the proposal review?
Include only the literatures that define the problem, have attempted to solve it, or inform your method. Exclude tangentially related work and justify your exclusions explicitly.
Why is organizing by source a problem?
Organizing by source produces a list, not an argument. It hides the gap and shows a lack of synthesis. Organize by themes, debates, or arguments instead, using sources as evidence for your claims.
How long should the literature review be?
It should be proportionate to the proposal stage: indicative and focused, not exhaustive. Aim for 15-30 pages or 3,000-6,000 words, but prioritize clarity of argument over length.
How does the review connect to the research questions and methods?
Every gap should map to a research question, and every question should have a method that can answer it. Make these connections explicit with signposting and ensure methods address the limitations of prior work.
The notes on PhD Admission Requirements: Committees cover the next question, so this page does not repeat them.