How can field notes show uncertainty without becoming vague?

Name the uncertain part

Uncertainty is useful when it is attached to a particular feature. Instead of writing “maybe a hydroid,” note what is known and what is unresolved: “branched colony attached to kelp; tentacles not resolved; hydrozoan identification provisional.” This separates the observation from the taxonomic interpretation.

The same approach works for counts, measurements, and behavior. “About 20 individuals, lower edge partly hidden” is clearer than “somewhere around 20.” A range can be useful when it reflects the visible evidence; explain what prevented an exact count rather than presenting false precision.

Show the evidence behind the note

Record the visible traits, viewing conditions, and method that support the tentative conclusion. A photograph may show colony shape but not its finer structures. A current may obscure the subject, or lighting may change apparent color. These constraints help a later reader understand why confidence is limited.

For example: “Likely pteropod based on shell outline and swimming posture; viewed briefly through rippled surface, shell opening not visible; image CW03_022 blurred.” This does not claim a definitive identification. It preserves the basis for the tentative label and the missing evidence.

State what would help

A useful uncertainty note identifies a next observation that could distinguish possibilities: a closer side view, a scale reference, a clearer image of a particular structure, or repeated measurements under steadier conditions. Phrase this as a need, not a promise that the evidence will be obtained.

If two interpretations remain plausible, list them and the feature that would separate them. For instance, “thin strands may be tentacles or attached algae; inspect a close view of their attachment.” This gives a future observer a focused task instead of leaving an open-ended doubt.

Keep confidence separate from the record

Use a consistent confidence label if a project needs one, and define what each label means. A word such as “probable” should have a shared meaning across observers; otherwise it can sound more certain than intended. Keep the underlying description even when using a confidence code.

Specific uncertainty makes notes more useful, not less. It tells readers where the evidence ends, preserves what was actually seen, and points toward a practical way to learn more.

Have a correction or a source to suggest? Send a note →