Margin Evidence
Research Notes

How to Keep a Source Log for Personal Research

Margin Evidence · Updated 2026-07-19 · 4 min read
How to Keep a Source Log for Personal Research
In briefKeep a source log by creating one retrievable record per source when you first consult it. Record author or organization, title, publisher or collection, dates, stable identifier or URL, access date, exact page or section, relevance, limitations, verification status, and next check. Mark quotations, paraphrases, and your own ideas separately, then place source IDs beside working claims with a note explaining what each source supports. Preserve versions, corrections, access restrictions, and privacy limits, and test whether another authorized reader can retrieve the cited passage.
Contents

Give every source one retrievable record

A source log is a running list of what you consulted, where it can be found, what it contributed, and what limits apply. Create the record when you open the source, not three days later when twelve browser tabs have formed a small, ungovernable republic.

The research notes section starts with retrieval because a claim you cannot trace is difficult to verify, quote, update, or correct.

Use fields that answer future questions

For each source, record:

Use the citation style required by the eventual recipient, but keep richer working details even when the final style omits them. A short bibliography entry may not remember which paragraph supported which sentence.

Separate quotation, paraphrase, and your idea

Mark verbatim language with quotation marks immediately and record its exact location. Keep excerpts short and necessary; note omissions and surrounding context. A paraphrase restates the source's meaning in your own structure and language while still requiring attribution. A personal thought or synthesis should be labeled as yours.

Do not paste source language into a general note field and plan to “sort it out later.” Later has an established interest in plausible deniability and poor punctuation.

When copyright, confidentiality, participant consent, or database terms restrict copying, record only what you are permitted to keep. Store sensitive material in an appropriate authorized system, not an ordinary personal worksheet.

In the working draft, add the source ID beside every checkable claim. One paragraph may need several IDs when it combines different evidence. Conversely, one source can support several claims without becoming permission to cite it for everything near the subject.

Write a brief support note: “S014, table 2, reports annual total for 2024,” or “S022, methods section, defines inclusion criteria.” This makes the relationship inspectable. A URL alone says where you went, not what you found there.

The observation-inference guide helps distinguish what a source reports from what you conclude; thinking tools covers uncertainty labels.

Record source quality without one magic score

Evaluate authority for the particular claim. A regulator may be primary for its rule, a manufacturer for its current manual, and a research paper for its own methods and results. None becomes universally authoritative on every adjacent question.

Note whether the source is primary or secondary, current enough, transparent about methods, complete enough for the claim, and independent of a relevant conflict. Save corrections, retractions, version history, and competing evidence. Do not compress those judgments into a mysterious “8/10 reliable” unless a defined project method genuinely uses that scale.

Keep dates and versions visible

Online pages, datasets, manuals, and policies can change. Record access dates and version identifiers. When appropriate and permitted, preserve an authorized snapshot or archived reference without bypassing access controls. For a live page, revisit before publication or an important decision.

If two versions differ, do not silently overwrite the old note. Record what changed and which version supports the current claim. A clean history is especially valuable when a source later corrects itself.

Run a retrieval test

Once the log contains ten sources, ask someone authorized—or future-you on a fresh morning—to locate three exact supporting passages using only the records. Fix every ambiguity the test reveals. Add controlled tags only after real retrieval needs appear.

Finally, back up the log according to the project's sensitivity and retention rules. The best source system is not the prettiest database; it is the one that lets a careful reader travel from sentence to evidence without packing emergency snacks.

FAQ

What is the difference between a source log and bibliography?

A bibliography lists sources in a citation format for readers. A working source log usually contains more: access dates, exact passages, relevance notes, claim links, version information, limitations, permissions, and verification tasks. The bibliography may be generated from the log, but it rarely preserves every decision needed to retrace research. Follow the required final citation style while keeping richer private working records.

Should I copy quotations into a source log?

Only when permitted and useful. Mark verbatim text immediately with quotation marks and an exact page, section, paragraph, or timestamp, and preserve enough context to avoid distortion. Keep excerpts no longer than needed and observe copyright, database, confidentiality, and consent limits. When copying is restricted or sensitive, store an authorized locator and summary instead in the system approved for the project.

How do I track a webpage that might change?

Record the page title, responsible organization, URL, publication or update date when given, access date, and the exact section used. Save a version identifier or authorized snapshot when appropriate and permitted. Recheck the live page before an important decision or publication. If content changes, preserve the earlier record and note the difference rather than silently replacing the evidence trail.

Can one source support several claims?

Yes, when the source actually addresses each claim. Link every working claim to the relevant source ID and location, with a short note about the support. Do not cite a source for nearby assertions it never makes. Conversely, a complex paragraph may need several sources. Claim-level links make it easier to update one fact without rebuilding the entire project from memory.

How should I rate source reliability?

Evaluate fitness for the specific claim rather than assigning one universal score. Consider whether the source is primary for that fact, current enough, transparent about method, complete enough, independent where needed, and subject to corrections or conflicts. Record the reasons and limitations in words. A regulator, manufacturer, witness, paper, and review can each be authoritative for different questions without becoming equally reliable for all.