How to Keep Repeat Site Observations Together in a Modular Field Notebook

What “together” should mean in a notebook

A useful record has two ways in: the order events happened and the place they happened. Keep the original entries in date order, so each visit remains a readable account of that day. Add a location index that points back to those entries, so you can find every visit to a particular site. This is a practical design choice: the National Park Service describes field notebooks as portable, customizable records of field days, while Parks Canada recommends a table of contents and, for larger projects, an index. National Park Service: Field Notes and Parks Canada: Field notes

This approach fits a modular notebook because the basic unit is a dated visit, not a preassigned page for each place. One location can have many visits; a single outing can also include several locations. Page references connect the two without rearranging or removing pages.

Set up a small site key before the first visit

Choose short codes that are easy to distinguish and write consistently. For example, use “POND-N” for the north pond path and “GATE-2” for a second gate. Write a small site key inside the cover or on the first page: code, plain-language name, and a brief locator such as “north pond path, bench beside the footbridge.” If the location is broad, add a sketch or recognizable landmarks. A code is only useful when you can still tell where it points.

Number the pages if the notebook does not already do so. If you use a notebook with fixed page numbers, leave several pages at the front for the index; if you prefer not to reserve space, start the index at the back and let it grow toward the middle. Keep the main observations in chronological order either way. Parks Canada’s guidance supports using headings and organizational elements, with a contents page and an index when the record grows; the exact format can be adapted to the task. Parks Canada: Field notes

Start every visit with the same compact header

At the top of each new visit, record the date, start time, site code and name, and the reason for the visit if that will help you interpret the notes later. Add conditions that matter to what you are observing: for example, rain, wind, cloud cover, recent maintenance, or whether the path is muddy. The Cornell Lab’s field notebook guidance recommends starting a trip with date, time, place, and weather. Cornell Lab of Ornithology: Take Note! Tips for Keeping a Field Notebook

A reusable header might look like this: “2026-10-09 | 08:20 | POND-N — north pond footbridge | overcast, light wind | checking waterline and fallen branches.” Use the detail that will help you understand or repeat the observation, rather than filling boxes mechanically. If you move to another site, begin a new visit block with its own location header. That makes it clear which observations belong to which place.

Record observations as separate, findable blocks

Under the header, give each observation a time or sequence marker and a concise description. Separate what you directly noticed from your interpretation. For example: “08:27 — Water reaches the lower stone on the east bank; the stone was dry on the last visit” records a comparison and its location. “Water level is unusually high” is an interpretation; keep it, if useful, but label it as one and note what you used to judge it. Add a sketch, simple measurement, or landmark reference when words alone may be ambiguous.

If you return to the same place several times in a day, mark each check with its time. If you visit more than one place, do not rely on a heading several pages earlier: repeat the site code on each page or continuation. The aim is for a page viewed on its own to retain enough context to identify the visit. This is especially helpful when pages contain sketches, loose measurements, or short notes that may be hard to connect to the entry before them.

Build the location index as you go

When a visit begins, note its page number in the index, then add the visit date. Keep one line per visit or a compact list under each site code. For example:

Site: POND-N; Location description: North pond footbridge; Visit references: 12 — 2026-10-09; 19 — 2026-10-16

Site: GATE-2; Location description: Second gate, west path; Visit references: 13 — 2026-10-09

At the end of a field session, check that each new visit has a page reference and that any continuation pages carry the same code. Once a site has several entries, the index can point to a range only when the range contains visits to that site alone; otherwise list the individual pages. A few extra entries are easier to use than a reference that sends you to unrelated notes.

Compare visits without rewriting the record

To review a site over time, use the index to open each referenced entry and compare like with like. Check whether the observation point, method, and timing stayed similar. If they changed, record that difference rather than presenting the notes as a direct comparison. A changed viewpoint, new obstruction, different tool, or missed visit can explain why two descriptions are not equivalent.

For instance, a weekly check of a garden bed could use the same corner marker and note the date, approximate time, recent rain if known, and visible changes. A return visit could then refer to the earlier page: “See p. 12; today the soil surface is dry, earlier entry noted damp soil.” This does not establish why the condition changed, but it preserves the sequence and gives you a clear starting point for another check. That distinction between observation and explanation is a useful safeguard against turning a notebook into a record of assumptions.

Keep the system workable as the notebook grows

Review the index occasionally, not after every sentence. At the close of a session, confirm page references, clarify abbreviations that may be unclear later, and add missing context while the visit is still fresh. Parks Canada recommends that headings and organizational elements make field records readable, and its manual notes that related project records should be referenced in the field notebook. For an everyday notebook, that can mean adding a page number for a map, checklist, or photo note rather than copying the same material repeatedly. Parks Canada: Field notes

Keep the code list short. If a place name changes or you split one broad site into two smaller observation points, record the change in the site key and note the date you began using the new code. Avoid silently reusing an old code for a different location. If conditions are wet, choose a writing tool and paper suited to them; the notebook manufacturer Rite in the Rain says pencils and its all-weather pens can be used on its paper in wet conditions, while standard ballpoint pens may have trouble when the paper is wet. Rite in the Rain: FAQs

A quick end-of-visit check

Before closing the notebook, ask: Can I tell when and where this visit happened? Are multiple locations separated clearly? Do the observations point to the relevant site and page? Can I distinguish what I saw from what I inferred? Did I add the new page to the location index? If any answer is no, add a brief correction or note while the details are still available.

The result is a straightforward system: chronological pages preserve the story of each outing, repeated site codes group entries by place, and the index supplies the route between them. It stays useful whether you revisit one location occasionally or rotate among several, and it scales by adding entries rather than redesigning the notebook.

Sources

Keep exploring this topic