Literature Review Template — Academic Writing Template

How to Use a Literature Review Template: From Sources to Synthesis

A literature review template can tell you where the introduction goes, how many thematic sections to plan for, and where the reference list belongs. What it cannot do is write the review for you. The gap between a filled-in outline and a literature review that actually earns a strong grade or gets past peer review is almost always the same gap: knowing how to move from a pile of PDFs to a set of themes, and from a set of themes to sentences that synthesize rather than summarize. This guide walks through that process in detail — how to search for sources without missing the important ones, how to screen out the ones that don't belong, how to read and take notes efficiently, how to spot the themes hiding across dozens of papers, and how to write paragraphs that sound like a researcher thinking, not a bibliography read aloud. If you haven't already grabbed the outline itself, the literature review template pairs directly with everything below — use the template for structure and this guide for the thinking that fills it.

Most students and early-career researchers don't struggle with the literature review because they lack sources. They struggle because they never learned a repeatable process for turning forty or fifty sources into a coherent argument about the state of a field. That process has distinct stages, and skipping any one of them shows up later as a weak, listy, hard-to-follow chapter. Search badly and you'll miss the papers a reader expects to see cited. Screen carelessly and you'll end up defending irrelevant sources in your introduction section. Take notes without structure and you'll spend twice as long re-reading papers you've already read once. Skip synthesis and your literature review becomes an annotated bibliography with paragraph breaks. Each section below tackles one of these stages on its own, with concrete techniques and examples you can apply immediately, whether you're working from a free literature review template for a course paper or writing the full literature review chapter of a thesis.

1. Define Your Review Question Before You Search Anything

The single biggest time-waster in literature review writing is starting to search before you've pinned down exactly what question the review answers. A literature review is not "everything written about topic X." It's an argument about what is known, what is contested, and what is missing, organized around a specific question or set of questions. Without that question written down in one or two sentences, your search terms drift, your inclusion criteria stay fuzzy, and you end up hoarding sources you'll never actually use.

Write your review question the way you would write a research question, even if the literature review isn't attached to your own empirical study. Something like "How do remote work arrangements affect employee reported job satisfaction across different organizational sizes?" is searchable and boundable. Something like "What research exists on remote work?" is not — it will return tens of thousands of results and give you no basis for deciding what to leave out. If your literature review sits inside a thesis or dissertation, this question should map onto (though not be identical to) your overall research question, and it's worth revisiting the thesis template for how the literature review chapter is expected to connect to your methodology and results chapters later on.

Once you have a working question, break it into its component concepts. That remote-work example splits into at least three concepts: remote or flexible work arrangements, job satisfaction (or a related construct like engagement or burnout), and organizational size or context. Each concept becomes a set of search terms in the next stage. This decomposition is also what keeps a thematic literature review thematic — your themes in the final draft will often trace back to these component concepts, refined by what you actually find in the literature.

2. Build a Systematic Search Strategy

A systematic search strategy is what separates a literature review that a reader trusts from one where they wonder what you missed. The goal isn't to read everything that exists — that's impossible and not the point — it's to be able to say, credibly, that you searched in a way that would have found the important, relevant work if it exists.

Start by choosing your databases deliberately rather than defaulting to a general web search. Google Scholar is a reasonable starting point for casting a wide net and for tracking citation counts, but it shouldn't be your only source — it indexes inconsistently and doesn't let you build the kind of precise, replicable search string that discipline-specific databases do. If you're in health, medicine, or life sciences, PubMed gives you controlled vocabulary (MeSH terms) that dramatically improves precision over free-text search. Most other disciplines have an equivalent — PsycINFO for psychology, ERIC for education, Web of Science and Scopus for cross-disciplinary coverage, IEEE Xplore for engineering and computer science. Ask a librarian which databases are considered authoritative in your field if you're not sure; this is one of the few points in the process where five minutes of expert advice saves hours of rework.

For each core concept you identified in the previous step, list synonyms and related terms, then combine them with Boolean operators. A basic search string for the remote-work example might look like: (“remote work” OR “telecommuting” OR “telework” OR “work from home”) AND (“job satisfaction” OR “employee engagement” OR “burnout”) AND (“organi?ational size” OR “firm size” OR SME). Note the truncation and wildcard handling (organi?ational catches both British and American spelling) — small details like this are exactly what separates a search that finds twelve papers from one that finds sixty.

A workable search strategy checklist looks like this:

• Write out each core concept from your review question separately.
• List at least three synonyms or related terms per concept, including discipline-specific jargon and older terminology that may appear in earlier papers.
• Combine concepts with AND, and synonyms within a concept with OR.
• Decide on a publication date range and justify it (e.g., "past 10 years" is defensible for a fast-moving field; older foundational work may deserve an exception).
• Decide which databases you'll search and search each one with the same string, adapting syntax as needed.
• Record the exact search string, database, date searched, and number of results for every search — you'll need this for a methods note even in a non-systematic thematic review, and it's essential if your review needs to meet PRISMA-style reporting standards.
• Run a citation search on your two or three most important papers (who cited them, and what did they cite) to catch anything your keyword search missed.

Keeping a simple search log — a spreadsheet with columns for database, search string, date, and results count — takes minutes to set up and saves you from the common disaster of not being able to remember or reconstruct how you found your sources when a supervisor or reviewer asks.

3. Set Inclusion and Exclusion Criteria Before You Screen

Screening without predefined criteria is how literature reviews end up bloated with tangentially related sources or, worse, missing sources that clearly should have been included. Set your inclusion and exclusion criteria before you start reading abstracts, not while you're reading them — deciding in the moment, paper by paper, is exactly how bias creeps in (you keep the papers that agree with your hunch and quietly drop the ones that don't).

Typical inclusion criteria cover: publication date range, language, study type (empirical studies only, or do you also want theoretical/conceptual papers and reviews), population or context (does the paper need to be about a specific industry, age group, or geography), and relevance to at least one of your core concepts. Exclusion criteria are the mirror image, plus practical ones — no full text available, duplicate of a source already included, or a paper that only mentions your topic in passing rather than examining it substantively.

A three-pass screening process works well for most literature reviews:

1. Title screen. Skim titles from your search results and eliminate anything obviously irrelevant. Be generous here — when in doubt, keep it for the next pass.
2. Abstract screen. Read the abstract of everything that survived the title pass and apply your inclusion/exclusion criteria more rigorously. Keep a short note on why you excluded anything borderline, in case you need to justify the decision later.
3. Full-text screen. For everything that survives, read enough of the full text to confirm it genuinely fits — sometimes an abstract oversells what a paper actually delivers, or the methodology turns out to be too weak to cite as evidence for a claim.

This staged approach, borrowed from systematic review methodology, scales down perfectly well for a narrative or thematic literature review that doesn't need full PRISMA reporting. You don't need a flow diagram with exact numbers at every stage unless your program or journal requires one, but doing the screening in stages — rather than deciding in one pass — measurably improves the quality and defensibility of your final source list. If your review needs to describe its methodology formally, the research methodology template has a structure for reporting exactly this kind of search-and-screen process.

4. Read Efficiently and Take Structured Notes

Once you have a screened set of sources — for a typical course-length literature review, somewhere between fifteen and thirty is common; for a thesis chapter, forty to eighty is not unusual — the next failure point is reading inefficiently. Reading every paper cover to cover, in the order you happen to have downloaded them, without a consistent note-taking structure, is the single biggest time sink in the entire process, and it produces notes that are useless for synthesis because they're organized by source rather than by idea.

Read strategically instead of linearly. For most academic papers, the abstract, introduction, and conclusion tell you 70–80% of what you need for a literature review — you're extracting the paper's claims, findings, and stated limitations, not evaluating its raw data. Read the methodology section closely only when you need to judge the strength of a claim (sample size, study design, measurement approach) or when methodology itself is part of what you're comparing across sources. Skim results sections for the specific findings relevant to your review question rather than reading every reported statistic.

Take notes in a structured format from the first paper onward — retrofitting structure onto forty papers' worth of freeform notes later is miserable. A simple synthesis matrix works well: one row per source, and columns for citation, sample/context, key findings, methodology, relevant themes, and a "my take" column for your own critical reaction. Building this in a spreadsheet means that by the time you've read your last source, you can sort or filter by the theme column and instantly see which sources cluster together — which is exactly the input the next stage of the process needs. This is also precisely the kind of scaffolding that WritingBuddy's source import and thematic clustering tools are built to speed up: importing your PDFs and letting the software surface candidate themes across sources gives you a first draft of that matrix in minutes rather than hours, though you should still read closely enough to verify what it surfaces.

Whatever tool you use, capture direct quotes sparingly and always with page numbers — you'll want a small number of precise quotes for concepts that are hard to paraphrase without losing meaning, but a literature review that's mostly stitched-together quotations reads as unprocessed. Paraphrase the rest in your own words as you take notes, not later; this forces you to actually understand the claim rather than just relocating text, and it's also the best defense against accidental plagiarism, since you're not staring at someone else's sentence structure while trying to write your own.

5. Identify Recurring Themes Across Sources

This is the stage where a thematic literature review structure actually takes shape, and it's also where the process feels the least linear. You're looking for the two or three (occasionally four) recurring ideas, debates, or dimensions that organize the field, and you're finding them inductively — from the actual content of your sources — rather than deciding on themes in advance and forcing sources into them.

A practical technique is open coding, borrowed from qualitative research methods. Go through your synthesis matrix or your notes and, for every distinct claim or finding, jot a short code — a two-to-four-word label — describing what it's about. Don't worry about consistency on the first pass; you'll have codes like "manager support," "tech access barriers," "isolation/loneliness," "productivity metrics," "policy variation by country." Once you've coded everything, group similar codes together. "Manager support" and "team communication norms" might collapse into a broader theme like organizational culture factors. "Tech access barriers" and "home workspace quality" might collapse into physical/material conditions. What started as a dozen scattered codes usually collapses into three to five genuine themes once you look for the underlying pattern.

A theme, for literature review purposes, is not a topic — it's a claim or a tension that multiple sources speak to, even if they don't agree. "Remote work and job satisfaction" is a topic. "The relationship between remote work and job satisfaction depends heavily on whether the arrangement was chosen or mandated" is a theme, because it's a specific, arguable claim that different sources provide evidence for, against, or with nuance about. If you can't state your theme as a sentence with a subject and a claim, it's probably still a topic, and you need to keep digging into your notes to find the actual pattern.

Expect this stage to take real iteration. It's common to draft three themes, start writing, realize halfway through that two of your themes are actually different facets of the same underlying issue, and have to re-sort your sources. That's normal and even a sign you're synthesizing rather than just filing sources into predetermined boxes — treat your first thematic breakdown as a hypothesis to test against the material, not a final answer.

6. Summarizing vs. Synthesizing: The Skill That Actually Matters

If there is one skill that separates a strong literature review from a weak one, it's this. Summarizing means reporting what one source said. Synthesizing means combining what multiple sources say to make a point that no single source made on its own. A literature review built entirely from summary reads as a list — "Smith found X. Jones found Y. Lee found Z." — even when it's organized under thematic headings, because the organizational structure is cosmetic if the sentences themselves never compare, contrast, or combine sources.

Here's what pure summary looks like, paragraph by paragraph, source by source (names and findings below are illustrative, not real citations):

Before (summary, source-by-source): "One study examined remote workers in the technology sector and found that job satisfaction increased after the shift to remote work, attributing this to reduced commute time. Another study looked at remote work in financial services and found no significant change in job satisfaction, though employees reported higher stress. A third study surveyed workers across multiple industries and found that satisfaction outcomes varied depending on whether remote work was voluntary or mandated by the employer."

Notice what's wrong even though every sentence is accurate: each source gets its own island. The reader has to do the comparative work themselves — is the tech-sector finding an outlier, or does it fit a pattern? The paragraph reports three findings but makes zero arguments.

After (synthesis, organized around the underlying pattern): "Findings on remote work and job satisfaction are inconsistent across industries, but a closer look suggests the inconsistency itself is meaningful rather than contradictory: outcomes cluster less by sector and more by whether the remote arrangement was chosen or imposed. Increases in satisfaction, such as those linked to reduced commute time in technology-sector samples, tend to appear where employees opted into remote work, while sectors where the shift was mandated — financial services, for instance — show flat satisfaction alongside elevated stress. This pattern is consistent with research spanning multiple industries showing that autonomy over the decision to work remotely, more than the remote arrangement itself, predicts whether satisfaction rises or stays flat. Taken together, these findings suggest that studies treating remote work as a single uniform condition may be obscuring a more important variable: employee choice."

The second version does several things the first doesn't. It opens with a claim (the inconsistency is meaningful, not noise), it uses the sources as evidence for that claim rather than as the organizing units of the paragraph, it explicitly names the variable that reconciles the seemingly conflicting findings, and it ends with an interpretive statement that goes slightly beyond what any single source said. That last move — the small inferential step that connects sources to say something none of them said individually — is synthesis. It's also, not coincidentally, one of the hardest things to produce with a template alone, and it's the specific gap that AI-assisted synthesis drafting tools like the ones in WritingBuddy are designed to help close: surfacing the cross-source pattern from your notes so you're editing and verifying an argument instead of assembling one sentence at a time from scratch. Whatever tool or process gets you there, the test is always the same — read your paragraph and ask whether it could have been written by someone who'd only read one of your sources. If yes, it's summary. If it needed all of them, it's synthesis.

7. Build a Conceptual or Theoretical Framework From Your Themes

Once your themes are stable, many literature reviews benefit from an explicit conceptual or theoretical framework section — a literature review template's "conceptual framework" section is marked optional for good reason, since not every review needs one, but it's worth understanding when it earns its place and how to build it well rather than skipping it by default.

A theoretical framework applies an existing, named theory (say, self-determination theory, or a specific organizational behavior model) to organize and interpret your themes. Use this when your field has an established theory that plausibly explains the pattern you've found across sources, and when connecting your review to that theory will help a reader situate your work within a larger scholarly conversation. A conceptual framework, by contrast, is something you build yourself, inductively, out of the relationships between your own themes — it's appropriate when no single existing theory quite captures what your sources collectively show, or when your review deliberately synthesizes across theoretical traditions that don't share a common framework.

To build a conceptual framework from your themes, start by drawing the relationships between them, literally with a diagram if that helps. Is one theme a precondition for another? Do two themes represent competing explanations for the same outcome? Does one theme moderate the strength of another? In the remote-work example, "employee choice/autonomy" might function as a moderating variable that determines whether "physical/material conditions" translate into satisfaction gains or losses. Naming these relationships explicitly, and giving each construct a clear, consistent label, is what turns three unconnected thematic sections into a framework a reader can hold in their head and, ideally, apply themselves.

Keep the framework visual and simple where you can — a basic box-and-arrow diagram often communicates a conceptual model faster than a paragraph of prose, and pairing the diagram with a short explanatory paragraph covers both readers who think visually and those who want the argument spelled out in text. Resist the temptation to make the framework more elaborate than your evidence supports; a framework with two well-supported relationships is more credible than one with six relationships, half of which are speculative extensions past what your sources actually show.

8. Write Topic Sentences That Signal Synthesis

The topic sentence of each paragraph is doing more structural work in a literature review than in almost any other kind of academic writing, because it's the sentence that tells the reader whether what follows is going to be a list or an argument. A weak topic sentence announces a source: "Smith (2019) studied the effects of remote work on productivity." A strong topic sentence announces a claim about the field: "The relationship between remote work and productivity appears to depend more on task type than has generally been assumed."

Notice that the strong version doesn't mention a specific source at all — it makes a claim, and the sources that follow in the paragraph serve as evidence for that claim. This is a useful diagnostic: if you can't write a topic sentence for a paragraph without naming a specific author, you probably haven't found the synthesis point yet, and it's worth going back to your theme notes and asking what claim this cluster of sources is actually collectively supporting or contesting.

A few reliable topic-sentence patterns for signaling synthesis:

• Convergence: "Multiple lines of evidence point toward..." or "Despite differences in method and sample, studies consistently find..."
• Divergence or debate: "Findings on [topic] diverge sharply depending on..." or "There is little consensus on whether..."
• Evolution over time: "Early research framed [topic] primarily in terms of X, but more recent work has shifted toward..."
• Gap-oriented: "While [aspect A] has received substantial attention, [aspect B] remains comparatively unexamined."
• Conditional/moderator: "The effect of [variable] on [outcome] appears to hold only under certain conditions, namely..."

Each of these forces the sentence to make a claim about the literature as a body, which is exactly the orientation a thematic literature review needs at the start of every paragraph, not just at the start of every section. Once you have a strong topic sentence, the rest of the paragraph's job is to support, complicate, or qualify that claim using your sources as evidence — which naturally pulls you away from summary and toward synthesis, because the sources are now serving the sentence rather than the sentence serving as a label for the sources.

9. Identify and Articulate Genuine Research Gaps

A research gap is not simply "not much has been written on this." That framing is weak because it doesn't explain why the gap matters or why anyone should care that it exists. A genuine, well-articulated research gap explains what the field currently assumes or has established, and then explains specifically what remains unknown, unexamined, or poorly resolved as a consequence — and, ideally, why that unresolved piece matters for theory or practice.

There are a few recognizable categories of gap, and knowing them helps you look for the right kind rather than settling for the first thin spot you notice:

• Population gap: the phenomenon has been studied extensively in one population or context but not extended to another where there's reason to think findings might differ (e.g., extensively studied among knowledge workers but rarely among frontline or shift-based employees).
• Methodological gap: the topic has been studied, but almost entirely with one method (say, cross-sectional surveys), leaving causal or longitudinal questions unanswered.
• Contradiction gap: studies disagree, and no one has systematically investigated why, or under what conditions each finding holds.
• Conceptual gap: a construct is used inconsistently across studies, or two related concepts have never been examined together despite an obvious theoretical connection.
• Evolving-context gap: conditions have changed (new technology, new policy, a shifted labor market) since the bulk of existing research was conducted, so older findings may no longer generalize.

Writing the gap well means naming which of these categories applies and connecting it explicitly to what your own project (if the literature review sits inside a larger study) intends to do about it. A weak gap statement reads: "Not much research has looked at remote work and small teams." A stronger one reads: "Existing research on remote work and job satisfaction draws almost entirely on samples from large firms with over 500 employees; because small teams operate with different management structures and less formalized communication infrastructure, it remains unclear whether the moderating role of employee choice identified in large-firm samples holds in smaller organizations." The second version names the gap category (population gap), explains the mechanism that makes the gap matter (different management structures), and ties it back to a specific finding from earlier in the review (the choice/autonomy moderator), which is exactly the kind of connective tissue that makes a literature review feel like a single argument rather than three separate sections stapled together.

10. Common Structural Mistakes That Sink a Literature Review

A few mistakes show up so often that it's worth naming them directly so you can check your own draft against the list.

The source-by-source "list" review is the most common failure mode, and it usually happens for a structural reason, not a laziness reason: writers organize their notes by source (one document or one note-card per paper) and then write the review in the same order they took notes, which produces a paragraph per source almost by default. The fix is upstream of the writing — organize your notes by theme before you start drafting (the synthesis matrix from section 4 exists precisely to make this possible), so that when you sit down to write a section, you're looking at five sources that all bear on one claim rather than reading through your notes chronologically.

Weak or missing transitions between paragraphs and sections is the second most common issue. A reader should never have to guess why paragraph four follows paragraph three. If your themes genuinely relate to each other — and they should, since you built them from the same body of literature — say so explicitly at section boundaries: "Having established that autonomy moderates the relationship between remote work and satisfaction, a related question is whether this moderating effect operates differently across organizational sizes." That single sentence does the work of telling the reader the logical connective tissue between two thematic sections, and it costs almost nothing to add once you know to look for the gap.

A missing critical voice is the third recurring problem, especially in reviews written under time pressure. It's not enough to report that sources exist and what they found; a strong literature review evaluates them — noting where a study's sample size limits how far its findings generalize, where a measurement approach might not capture the construct it claims to, or where a widely cited finding hasn't actually been replicated. This doesn't require being harsh or contrarian for its own sake; it requires treating sources as claims with varying levels of support rather than as equally weighted facts. A sentence like "though frequently cited, this finding rests on a single small-sample study and has not been replicated in larger or more diverse populations" is doing real critical work that a purely descriptive sentence never does.

A fourth mistake worth flagging: introductions and conclusions that don't match the body. It's common to draft the introduction before fully knowing what themes will emerge, and then never revise it to reflect what the review actually ended up arguing. Always do a final pass checking that your introduction previews the actual themes in your actual order, and that your conclusion doesn't introduce a claim or gap that was never discussed in the body — both are surprisingly easy to miss when you're deep in the sentence-level work of the middle sections.

11. Revising Your Draft: From First Draft to Polished Review

Revision for a literature review benefits from a specific sequence, because trying to fix organization, argument, and sentence-level clarity all in one pass is inefficient — you'll polish sentences you end up cutting when you reorganize later.

Do a structural pass first, before touching individual sentences. Read only your topic sentences, one after another, skipping the body of every paragraph. This quickly reveals whether your themes are actually distinct (if two topic sentences make almost the same claim, you likely have overlapping themes that should merge) and whether the order makes sense (does theme two logically need theme one established first, or could they swap without loss). This is also the fastest way to catch the source-by-source list problem from the previous section — if your topic sentences name authors rather than claims, you'll see it immediately in this pass.

Do an argument pass second. For each section, ask: what is this section's one main claim, and does every paragraph in it either support, complicate, or qualify that claim? Cut or relocate anything that doesn't. This is also the point to check your critical voice — mark any paragraph that's pure summary with no evaluative sentence, and either add one or fold that source into a paragraph where it can serve as evidence for someone else's point.

Do a transitions pass third, reading the review straight through and marking every place where you had to pause to figure out why the next sentence or paragraph followed. Add explicit connective sentences at those points rather than relying on headings alone to do that work — headings organize a document for skimming, but transitions are what make it readable start to finish.

Finally, do a citation and formatting pass. Check that every claim attributed to a source is actually supported by that source (a surprisingly common error after multiple rounds of paraphrasing is drift, where a claim gets slightly stronger or more general each time it's rephrased, until it no longer matches what the source actually said). Confirm your citation style is applied consistently — the APA citation guide and Harvard citation guide are worth bookmarking if you're switching between styles for different courses or submissions, since small formatting inconsistencies are exactly the kind of thing reviewers and graders notice even when they don't affect the argument.

It's worth reading your draft aloud, or having it read aloud, at least once during this process — awkward synthesis sentences (the ones trying to hold together three sources' worth of nuance in a single overloaded clause) are much easier to hear than to see, and hearing where you stumble usually tells you exactly where a sentence needs to be split or restructured.

12. Putting It All Together With a Literature Review Template

A literature review template earns its keep once you've done the work described above — it's the container that keeps your introduction, thematic sections, gap statement, optional framework, and conclusion in the order a reader expects, so that the argument you've built through searching, screening, coding, and synthesizing has a clear place to live. Used the other way around — filled in before the thinking is done — a template just produces headers with summary paragraphs underneath them, which is why the process matters more than the outline, even though both matter.

If you're assembling a literature review as part of a larger project, it's worth looking at how the review connects outward: to your methodology chapter if you're pulling from the research methodology template, to your full thesis structure if you're using the thesis template, and to discipline-specific expectations if you're writing for a field with its own norms, which the researcher-focused and graduate-student-focused resources cover in more depth than a single template page can. If literature reviews are a recurring part of your workflow rather than a one-time assignment, it's also worth reading through the dedicated literature review writing page to see how source import, thematic clustering, and synthesis drafting fit together across an entire project rather than a single chapter.

For anyone assembling their reading list and pulling quotes across many sources, keeping your reference metadata clean from the start avoids a painful cleanup pass later — a tool like Crossref is a reliable way to verify DOIs and publication details when your notes have drifted from the original citation, and the Purdue OWL remains one of the most dependable free references for citation mechanics and general academic writing conventions across styles. None of these external tools replace the thinking this guide walks through, but they remove friction from the parts of the process — formatting, verification, source tracking — that shouldn't be where your time goes when the real work is building an argument out of what the literature actually shows.

Ultimately, the fastest way to get from a blank template to a finished thematic literature review is to treat the stages in this guide as sequential, not optional: define your question, search systematically, screen against real criteria, take structured notes, code for themes, write synthesis instead of summary, build a framework only if it earns its place, write topic sentences that make claims, name your gaps precisely, watch for the structural mistakes that give away a rushed draft, and revise in passes rather than all at once. Whether you do the source management and drafting by hand or use a free literature review template with AI-assisted source synthesis, like WritingBuddy provides, the underlying skill is the same, and it's the skill that a template alone can never substitute for: reading widely, thinking comparatively, and writing sentences that could only have been written by someone who read everything, not just one thing at a time. For more on how this fits into the wider academic writing process, the literature review guide, literature review writing tips, and common academic writing mistakes articles on the WritingBuddy blog cover related ground, and the FAQ page answers many of the logistical questions — word counts, formatting, timelines — that come up once the writing itself is underway. If you're comparing tools for managing sources and drafting at scale, the WritingBuddy vs. SciSpace comparison and the pricing page lay out what's available beyond the free template, and the examples page shows finished literature reviews if you want to see the finished product these techniques are meant to produce before you start your own.