Keep the observation beside the explanation.

Record the question, method, measurements, and limitations in one Markdown note. Tables and equations help explain the work; source links let you return to the evidence.

Start a research note

Opens an editable template with illustrative data. Sign in for cloud sync; PDF export is included in Pro.

Keep the observation beside the calculation

Research note Ā· illustrative data

## Observations

| Trial | Time (s) |
| --- | ---: |
| 1 | 12 |
| 2 | 15 |
| 3 | 9 |

Rendered note

Observations

Trial Time (s)
1 12
2 15
3 9

Write down the measurements and units before interpreting the result. These are sample values, not study findings.

Record how you got the observation

Begin with a question and a method. Record the dataset version, units, date, and conditions that could change the interpretation. Keep direct observations separate from an explanation you have not yet tested.

The research notes template uses three explicitly illustrative timings to show the structure. Replace the sample values and method with your own. A useful note should make clear which observations came from your work and which are examples, estimates, or assumptions.

Show the calculation and its limits

Use a Markdown table for a small set of values and KaTeX for an equation. Inline notation uses $...$; a displayed equation uses a pair of $$ delimiters on separate lines. In the example, the mean is written as (12 + 15 + 9) / 3 = 12 seconds.

The editor renders the notation you provide. It does not run an analysis notebook, recompute the mean when a table cell changes, or validate a conclusion. Keep executable analysis and original data in the tools that produced them, and link to the relevant version from the note.

Add figures and traceable references

Place a figure close to the observation it supports. Image uploads let you insert a hosted image reference; give it useful alt text and add a caption in the surrounding text. For small charts, the Vega-Lite guide explains how to describe the figure as data and a chart specification.

Record sources with enough detail to find them again: title, author, URL or DOI, dataset version, and access date where appropriate. Markdown footnotes can hold additional context, but they are not automatic bibliography management. See the footnotes guide for supported syntax.

Return to the note and share a reviewed copy

Keep related notes in a workspace, with folders for the project or subject. Use version history to inspect saved earlier text when an interpretation changes. Its retention is limited, so retain important milestones and original data separately.

When the note is ready to share, export a PDF and check the figures, equations, and page breaks. Keep the Markdown source for the next revision. A public page is another option when the material is suitable for open access; review permissions and private information before publishing it.