Why a search log is worth keeping
A search can feel productive in the moment and become hard to reconstruct a week later. You may remember finding a promising article but not which database led you to it. Or you may repeat a query without realizing that you already tried it with different filters. A search log gives you a record of your route through a topic, not just a list of the sources you decided to keep.
This is especially useful when a question changes as you learn. Suppose you begin with “Do urban trees reduce heat?” and discover that the answer depends on what you mean by heat: air temperature, surface temperature, or people’s exposure while walking. Your log can show how that discovery changed your search terms. It can also help you explain your approach to a classmate or colleague without pretending that your first query found everything.
Record enough to retrace each search
Use a spreadsheet, document, or notebook—whichever you will actually update. Give each search attempt its own row or short entry. Record the date, the place you searched, the exact query you entered, and any important limits, such as publication period, language, or document type. If a search tool automatically changes your query or sorts results in a particular way, note that when it matters. These details let you repeat a search and understand why two similar attempts produced different results.
Add a brief outcome rather than trying to copy the entire results page. For example: “Found several papers about surface temperature; few address pedestrians” is more useful than “good results.” Save the title or stable identifier of a promising item, plus a note about why it caught your attention. A search log is not a finished bibliography: its job is to preserve your decisions, including searches that were unhelpful. A simple entry might read: “Library database; ‘street trees’ AND ‘pedestrian heat’; limited to journal articles; found a useful term, ‘thermal comfort’; next: search that term without the street-tree limit.”
Log your choices while they are fresh
You do not need to pause after every click. Make an entry when you change a query, switch platforms, apply a meaningful filter, or follow a new line of inquiry. If you try several small variations quickly, group them only if you can still tell what you tried. Writing down the exact words matters: “urban trees heat” and “tree canopy thermal comfort” may lead you toward different kinds of material, even though both relate to the same question.
Keep observations separate from judgments. “First page mostly covers planting costs” describes what you saw; “not relevant” leaves you less to work with later. If you decide not to use a source, record the reason in a few words: wrong location, unclear method, or a focus on a different outcome. That note can prevent you from reopening the same item repeatedly, while leaving room to reconsider it if your question changes.
Use the log to plan the next search
After a search session, scan your entries for repeated patterns. Are several queries returning the same sources? You may need a different database, a broader concept, or an alternative term. Are you finding broad overviews but no studies that address your specific setting? Try combining the core concept with a location, population, or method. Are the most promising sources using language you did not expect? Borrow their terminology for the next round of searching.
For the urban-tree question, a log might show that searches for “heat reduction” mostly led to discussions of surface temperature, while “thermal comfort” brought up work focused on people’s experience outdoors. Neither path is automatically better. The choice depends on the question you now want to answer. Note that decision in the log, then write the next query as a test: “Does adding ‘walking’ help locate sources about pedestrian exposure?” Recording the reason for a query makes its results easier to interpret.
Keep the system small and reviewable
A useful log can have just six fields: date, search location, exact query, limits, outcome, and next step. Add fields only when they solve a real problem. If you work with others, agree on how to name databases and record filters so entries are understandable across the group. If your project lasts a while, put the research question and the date of its latest revision at the top of the log. That context helps you see which older searches may need another look.
Before you stop, spend a few minutes marking what to revisit: a promising item, an unfamiliar term, or a query worth trying in another tool. When you return, start with those notes rather than reconstructing your train of thought. The aim is not a perfect account of every result. It is a reliable record of what you tried, what you learned, and why your next search should be different.
