Reading path: Coastal field methods →
Mark the change when it happens
Record a method change on the date it begins, before the new approach becomes routine. State what changed in concrete terms: search duration, area boundary, sampling depth, equipment, observer position, or the rule for counting an organism. “Survey updated” is too vague to help someone interpret the next record. If possible, keep the previous method description nearby or refer to its page number. A reader should be able to identify where one procedure ends and another begins without guessing from a sudden change in the results.
Explain why the procedure changed
Give the practical reason without turning it into an unsupported claim about the data. Perhaps a marker washed away, glare made one viewing angle unusable, or the team added a fixed search duration to improve consistency. Note the circumstance and the decision. For example: “Beginning 14 May, search each marked pool for eight minutes because visits varied in effort; earlier records have no timed duration.” That explanation identifies the purpose and, just as importantly, tells a future analyst which earlier records lack the new information.
Flag the comparison boundary
Changes can alter what gets detected, even when the underlying community has not changed. A larger area, longer search, magnifying lens, or different observer may produce different counts. Mark which visits used the earlier method and which used the revised one. If old and new records can be compared only for a shared subset, define that subset. For instance, counts from the same marked rock face might remain comparable even if the surrounding search area expanded. Avoid presenting the whole series as one uniform run when its methods differ.
Preserve both versions in the record
Keep the original observations and method notes intact, then add the new procedure as a dated entry or versioned protocol. If you test both methods on the same visit, record the results separately and describe the order, areas, and effort. Such a comparison can reveal whether the procedure itself changes what is recorded, though it does not automatically resolve every source of variation. When a change was made accidentally and discovered later, document when it was noticed and which entries may be affected. A clear change log gives future readers a way to interpret the transition rather than mistaking it for an ecological event.
Have a correction or a source to suggest? Send a note →