document-a-lab-notebook-entry

# document-a-lab-notebook-entry Record what actually happened, including failures and deviations. ## When to use - Use for wet-lab, field, computational, prototyping, or analytical work under an approved protocol. - Do not erase, backdate, fabricate, or silently rewrite original observations. ## Procedure 1. Record date, time, author, project, experiment identifier, objective, hypothesis, and approved protocol version. 2. Identify samples, reagents, equipment, software, data, lot or version numbers, calibrations, and storage locations. 3. Describe the planned method or link to it, then record every actual step and parameter needed to reproduce the run. 4. Timestamp deviations, interruptions, environmental conditions, safety issues, and operator decisions as they occur. 5. Link immutable raw files, images, instrument outputs, code commits, checksums, and sample identifiers. 6. Separate observation from interpretation and mark unexpected or ambiguous results. 7. Record calculations with units and preserve the raw values behind summaries. 8. Sign or lock the entry through the approved system; append corrections with reason, author, and date. 9. State immediate disposition of samples, waste, data, incidents, and next actions. ## Worked example A reaction yields less product than expected. The entry records a temperature excursion and a different reagent lot instead of rewriting the protocol as if conditions were normal. Raw instrument files, calculation steps, and sample locations are linked, allowing the next experiment to test each explanation. ## Done - A timestamped lab notebook entry records protocol, materials, versions, actual procedure, deviations, observations, calculations, and sample disposition - Raw evidence links, identifiers, checksums, signatures, and append-only corrections are verified and retrievable