Record the question behind the action
A useful notebook explains why an action was taken as well as what happened. Date the entry, identify the question and state the intended purpose of the activity. Separate a plan from an observation and an observation from an interpretation. This prevents a later reader, including your future self, from assuming that an expectation was a result. Use the format required by your institution or project, especially where formal laboratory records or approved research systems apply.
Make versions identifiable
Give files and materials stable identifiers and record which version an entry refers to. If a dataset changes, note the change and preserve the appropriate authorised record of the earlier state. For computational work, record the relevant code version and processing steps. Do not put passwords or confidential personal data into an ordinary notebook. The record should make the work traceable while respecting the project’s access rules, consent conditions and data-management arrangements.
Write down the abandoned branch
A failed attempt may explain why the final method looks the way it does. Describe what you tried, what problem arose and what evidence justified changing direction. Avoid rewriting the history so that the successful route appears inevitable. In a hypothetical document-analysis project, an initial coding category might be too broad to distinguish cases. Recording that problem and the revised definition makes the later analysis easier to examine than a notebook containing only the final categories.
Separate evidence from confidence
Use explicit labels for unresolved questions, missing information and provisional interpretations. A confident tone cannot replace a measurement or source. If you notice an error, correct it through the approved process while preserving a clear account of what changed. Ask a supervisor how your field expects corrections, retention and sharing to be handled. Different projects can require different records, and this general workflow does not replace a research protocol or formal compliance requirements.
Run a handover check
Choose one entry and imagine giving it to an authorised colleague unfamiliar with that day’s work. Could they identify the material, understand the decision and locate the next step? If not, add the missing context. At the end of each work period, record the remaining question and the intended next action. The objective is not a beautiful diary. It is an honest, navigable account that supports explanation, review and responsible continuity within the project’s rules.
A practical exercise
Select a small completed activity and reconstruct its record using only material you are authorised to access. Label anything reconstructed from memory so that it is not mistaken for a contemporaneous note. Identify the input, version, action, observation, interpretation and next step. Then ask whether an authorised reader could understand why you chose that action. If the answer depends on context stored only in your memory, add an explanation. This exercise is about improving the record; do not alter an official research record outside the project’s correction procedures.
