How to Build Flashcards from Your Reading
How to build flashcards from your reading — a practical guide for students who want to convert reading notes into high-quality flashcards that actually
Student & Academic
How to keep a digital lab notebook — a practical guide for students and researchers in science, engineering, and social science labs who want a
A lab notebook is not a record-keeping formality. It is the primary document that makes research reproducible — by you, by your lab, and by the field.
The reproducibility crisis in science — documented by Ioannidis (2005) in PLOS Medicine, and later by the Open Science Collaboration's 2015 replication study in Science that found only 36-39% of psychology study results replicated at comparable effect sizes — has roots in inadequate documentation as much as in statistical practices. When results cannot be reproduced, the first question is whether the original procedure was recorded precisely enough for reproduction to be possible.
Beyond reproducibility, lab notebooks serve practical purposes that researchers discover when they need them:
Returning to old work: Two months after running an experiment, you cannot remember the exact concentration you used, which column you ran on which sample, or why you made a procedural decision. The notebook is the only reliable record.
Handing off to others: When a new lab member joins or takes over a project, the notebook is the documentation that prevents them from rediscovering your errors.
Intellectual property: In industry and in patent disputes, a contemporaneously dated lab notebook is evidence of who discovered what, when. Many institutions and companies specify notebook requirements in their policies for exactly this reason.
Writing up: When you write a methods section six months after the experiment, you're working from the notebook. A sparse notebook produces a sparse methods section that reviewers will flag as insufficient.
The question is not whether to keep a lab notebook. The question is how to keep one that's actually useful.
Traditional paper lab notebooks — bound, paginated, dated in ink — have one advantage that digital systems don't fully replicate: they are tamper-evident and legally defensible as-is. Regulators, patent attorneys, and IRBs have decades of established practice for paper notebooks.
Digital lab notebooks offer advantages that paper can't match:
For most student and academic research labs, digital notebooks are now the standard practice. The choice is which digital system, and how to use it consistently.
There is no single right tool. The right choice depends on your lab's scale, compliance requirements, and existing infrastructure.
Purpose-built Electronic Lab Notebooks (ELNs):
General tools adapted for lab use:
For regulated environments (FDA-regulated labs, clinical research): If your lab is subject to FDA 21 CFR Part 11 (electronic records and signatures regulations) or equivalent, you need an ELN with a validated audit trail, access controls, and e-signature support. This rules out general-purpose tools. Check with your lab manager or compliance officer before selecting a system.
For most graduate students and academic research labs without regulatory requirements: Benchling (life sciences), eLabFTW (physical or mixed sciences), or Notion (flexible/multi-discipline) covers the majority of use cases.
The fundamental rule of lab notebook entries is that another competent researcher who reads your entry should be able to reproduce what you did without asking you any questions.
Every experimental entry should contain:
Header:
Objective: One to two sentences stating what this experiment is trying to determine or demonstrate. Not "ran PCR" but "testing whether primer pair JR-01/JR-02 amplifies the BRCA1 exon 11 insert from the pUC19 construct created on [date]."
Materials: Specific reagents (with lot numbers and concentrations where relevant), equipment (model numbers for instruments), software (name and version). Lot numbers matter because reagent quality varies; equipment model numbers matter because different instruments produce different results; software versions matter because algorithms change.
Protocol:
Raw data:
Analysis:
Results:
Conclusions and next steps:
Entry closure:
Recording the intended protocol instead of what you actually did: The most common lab notebook error. You planned to incubate for 2 hours and incubated for 2.5 hours. The notebook should say 2.5 hours, with a note explaining why. Recording the planned protocol as the executed one means your records don't describe your experiment.
Not recording failures: A failed experiment with a recorded reason ("agarose gel showed no bands — primers did not anneal at 60°C; will try gradient PCR") is scientifically useful. A failed experiment with no record — because you planned to "redo it properly" before documenting — is lost data. Record what happened, even when it didn't work.
Vague descriptions that don't specify parameters: "Incubated at room temperature" — what temperature is room temperature? "Added a small amount of ethanol" — how much? "Ran the standard protocol" — which version? Parameters that seem obvious when you run the experiment become ambiguous months later.
Not attaching raw data at entry time: If you plan to "attach the gel image later," you will often not. Attach it when you upload it from the imaging system, while you're still at the computer.
Editing past entries without audit trail: In a paper notebook, corrections are a single strikethrough — the original is still visible. In a digital notebook, deleting and rewriting loses the original. Use the amendment or versioning system your ELN provides; for general tools, add a clearly dated amendment note below the original entry rather than editing it.
A lab notebook structure that works for most research projects:
DIGITAL LAB NOTEBOOK STRUCTURE
Top level:
Project A
Protocols (the SOPs and standard methods you follow, not individual experiments)
Reagent log (running record of reagent preparation, lot numbers, dates)
Experiments
Exp-001 — [Brief description] — [Date]
Exp-002 — [Brief description] — [Date]
...
Data archive (links to or copies of the raw data files for this project)
Meeting notes (lab meeting, supervisor meeting notes relevant to this project)
Project B
[Same structure]
Lab inventory (shared: reagent stocks, equipment logs, calibration records)
The experiment numbering system varies by lab. Common approaches: sequential by project (Exp-001, Exp-002), by date (20261015-PCR-01), or by researcher initials (JR-2026-001). Pick one and use it consistently. The numbering is how you cross-reference: "see Exp-014 for gel image from original construct."
Setup: Marcus is a first-year PhD student in a biochemistry lab. The lab uses Benchling. He's been assigned to characterize a novel enzyme variant.
Week 1 — Setup: Lab manager gives Marcus access to the lab's Benchling account. He creates his project ("Enzyme Variant Characterization — MarcusR") and a Protocols folder. He copies the lab's standard SOP for protein purification into his Protocols folder and notes the version number and date.
Week 2 — First experiment (SDS-PAGE to confirm protein purity):
He creates Exp-001. Objective: "Confirm that the purified Enzyme X variant (batch 2026-10-12) is > 90% pure by SDS-PAGE." He records: reagent lot numbers for the gel components and loading buffer; the instrument model; the protocol (Benchling link to the SOP plus the two deviations — used 8% gel instead of 10% because the protein's predicted MW is 95 kDa, and ran 45 minutes instead of the standard 40 because of a power fluctuation). He attaches the gel image. He records that the result showed one major band at ~95 kDa with faint secondary bands — estimates 85-88% purity by densitometry. Conclusion: meets minimum threshold for next assay but marginally; notes that repeat purification may be needed if activity assay results are inconsistent.
Week 6: Marcus's supervisor asks about the purity of the batch used in the kinetics assay from three weeks ago. Marcus searches Benchling for "Enzyme X batch 2026-10-12" — two entries come up: Exp-001 (purity confirmation) and Exp-007 (kinetics assay). He can answer the question in 90 seconds. Without the notebook, this would have required reconstructing the experiment from memory.
A digital lab notebook done well is the infrastructure that makes your research reproducible, your methods section writable, and your past experiments accessible. The setup investment — choosing the right tool, establishing a consistent entry structure, building the habit of recording what actually happened rather than what was planned — pays out every time you return to old work, hand something off to a new lab member, or sit down to write up results. The cost of poor documentation is invisible at entry time and obvious six months later. The cost of thorough documentation at entry time is ten extra minutes per experiment, permanently.
See also: AI Knowledge Management in 2025.
More WebSnips articles that pair well with this topic.
How to build flashcards from your reading — a practical guide for students who want to convert reading notes into high-quality flashcards that actually
How to organize PDFs for research — a practical guide for students and researchers who want a systematic, searchable, and durable PDF organization system
How to prepare a conference presentation from notes — a practical guide for students and early-career researchers who want to transform their research
How to read faster without losing comprehension — a practical guide for students who have more assigned reading than they can finish, and want to increase
How to write a dissertation literature chapter — a practical guide for PhD students and graduate researchers who want to write a literature chapter that
How to avoid plagiarism with good note-taking — a practical guide for students who want a note-taking system that clearly distinguishes quotes from