Reading path: Coastal field methods →
Pause without losing your place
An unexpected event can be scientifically interesting and still interrupt a routine measurement. Before attending to it, mark the current step and time in the notebook. A short pointer such as “routine sequence paused after station 2; event note E1” makes it easier to resume without skipping or duplicating work.
If the event requires immediate attention for safety, put safety first and reconstruct the sequence only when conditions permit. A notebook is useful when it records what happened, including interruptions, rather than implying a perfectly uninterrupted visit.
Give the event its own record
Use a separate event entry with a clear identifier, time, location, and context. Describe what was directly observed, what changed, and how long it lasted if known. Distinguish an estimate from an instrument reading and avoid guessing at causes before there is evidence.
For example: “E1, 10:18, west edge of pool. A wave overtopped the rock lip; water entered the marked quadrat and moved loose algae for roughly 20 seconds. Routine temperature measurement paused; no reading taken during surge.” This captures the relevant conditions without turning the event into an unsupported explanation.
Resume the planned measurements
After the event, return to the sequence marker and state where work resumed. If a planned reading was delayed or could not be made, record that explicitly instead of inserting a later value as if it were taken on schedule. A later measurement may be useful, but its time and circumstances should remain distinct.
A continuation could read: “Resumed at 10:21 with station 3; station 2 temperature taken at 10:22 after water settled, 12.4 °C.” This indicates that the routine sequence changed and allows later analysis to account for the delay.
Connect event and routine records
If the event affected nearby observations, link the event code to those entries. For example, note that a photograph was taken during E1 or that a transect segment was disturbed. Keep the regular data fields intact and add the event reference alongside them so the exception does not disappear inside a routine table.
A clear interruption record protects both parts of the visit: the planned observations and the unexpected occurrence. Later readers can decide whether the event changes how a measurement should be interpreted because the timing and context were preserved.
Have a correction or a source to suggest? Send a note →