Making the Search Visible: A Defensible Record of Database Queries for Your Methods Chapter

A literature search can feel like a private conversation between you and a database. You type a string, scan titles, follow a citation, refine a filter, and move on. By the time you write your methods chapter, the route may be difficult to recall. That is not a failure of memory; it is a predictable consequence of iterative research. A simple search log protects against that gap. It makes the process visible, not to create extra bureaucracy, but to give your reader a clear account of how you reached the evidence you use.

Why a search record belongs in the methods chapter

In a UK dissertation, the methods chapter is expected to explain not only what you did but why your choices were reasonable. For a literature-based study, that includes the search strategy. Which databases did you use? Which terms did you combine? Which date limits or language filters did you apply? Which results did you exclude, and on what basis? Without a record, these details are often reconstructed late in the process. Reconstruction is not dishonest in itself, but it can drift into post-hoc rationalisation: a tidy story told after the fact rather than an accurate description of the work.

A search log offers a more defensible alternative. It does not need to capture every click. It needs to capture the decisions that shaped your evidence base. That distinction matters. The aim is transparency, not surveillance of your own study habits.

What to record without turning it into a burden

A useful log is short enough to maintain and specific enough to explain. For each substantial search session, record the date, the database or platform, the search string as entered, and any limits applied. Note the number of results if the platform displays it, and write one or two lines on what you did next: which records you screened, which you excluded, and why. Dead ends deserve a place too. A search that produced nothing relevant is still part of the method, and it can help explain why you narrowed or widened your terms.

Inclusion and exclusion decisions should be recorded in plain language. For example: excluded because the study focused on secondary education rather than higher education; excluded because the publication date fell outside the chosen period; excluded because the abstract indicated a different methodological focus. You do not need to justify every individual record. You do need a consistent rationale that a reader could follow.

A minimal template you can keep open

A simple document or spreadsheet is sufficient. Consider columns for date, database, search string, limits, results, screening notes and follow-up actions. If a table feels cumbersome, a dated running note works equally well. The key is to update it while the search is fresh, not to create an elaborate system you will abandon after a week.

It is also worth keeping a separate note of sources found through citation chasing or recommended reading. These routes are legitimate parts of a literature search, but they are not database queries. Recording them separately prevents the methods chapter from implying that every source emerged from a single systematic string.

From notes to a short methods paragraph

When you draft the methods chapter, resist the temptation to reproduce the log in full. Use it to write a concise paragraph that explains your approach. You might describe the databases consulted, the core search concepts and how they were combined, the limits applied, and the screening criteria used to decide which records merited closer reading. Mention that the search was iterative and that terms were refined in response to initial results. That is usually more accurate than presenting a fixed strategy that was never actually fixed.

A defensible paragraph does not need to claim exhaustiveness. It needs to be honest about scope. If you searched three databases and followed up on key citations, say so. If you restricted the search to a particular date range, explain why. If you excluded grey literature, acknowledge the decision and its implications. This is not an admission of weakness; it is a mark of methodological awareness.

The appendix entry: enough, not everything

Some programmes expect a search log or search strategy table in an appendix. Even where it is optional, a tidy appendix entry can strengthen the methods chapter. Include the final search strings, the databases used, the date of the search and the main limits. A short table of inclusion and exclusion criteria is often more useful than a long list of every record screened. The appendix should support the chapter, not overwhelm it.

Before submitting, check that the appendix and the methods paragraph tell the same story. Inconsistencies—such as a date range in the appendix that differs from the one described in the chapter—are easily avoided by working from the same log.

Ethical transparency and the temptation to tidy up

There is a subtle ethical point here. A search log is not a performance of rigour. It is a record of what you actually did. If your search evolved, say so. If you missed a database that might have been relevant, you can acknowledge the limitation rather than pretending the strategy was complete from the beginning. Transparency about the process is more credible than a flawless narrative that cannot be substantiated.

This also protects you if questions arise later. A supervisor, examiner or ethics reviewer may ask how you identified your sources. A dated log gives you a calm, factual answer. It turns a memory test into a matter of record.

A routine for the final months

As you move from searching to writing, set aside twenty minutes to review your log. Check that the key searches are recorded, that exclusion decisions are legible, and that the methods paragraph reflects the log rather than an idealised version of it. Then close the document and return to the chapter. The log has done its work: it has made your search visible, and your methods chapter more defensible.