Identify what the number describes
A number alone may leave the reader guessing whether it is a direct observation, a derived value, an estimate, or a target. The field definition should state what it represents and how it relates to the activity. Labels that appear obvious within one team can become ambiguous in a shared view.
The interface should preserve that meaning when the record is selected, compared, or exported. A useful review asks whether a person unfamiliar with the original conversation can explain what the value refers to and where it came from.
Make the unit explicit where it matters
A unit can belong to a field definition, an individual observation, or a method that governs a set of values. Whichever arrangement is chosen, the reader needs to understand it. Do not rely on a unit mentioned only in a distant note if values can be copied or viewed separately.
Conversions require an agreed rule and an appropriate basis. An interface should distinguish an original value from a transformed one and avoid suggesting that every quantity with a similar label can be meaningfully converted or compared.
Carry the relevant conditions
An observation may depend on a method version, setup, item revision, or other condition. The record model should identify which of those relationships matter to later interpretation. Capturing every possible detail is not the goal; preserving the distinctions needed for the research question is.
Comparison views need particular care. If a summary hides different conditions, the apparent difference between values can become misleading. A reader should be able to identify the condition or reach it without losing the comparison task.
Use an example to examine the handoff
Prepare a small synthetic record with its value, unit, origin, and conditions. Examine how it appears in entry, a compact table, an expanded record, and a proposed export. Check that the context remains attached to the right observation.
Where meaning is unresolved, record the question for the responsible domain owner. A prototype should not manufacture a scientific interpretation to make a screen look complete. The useful output is a clear information requirement and a visible account of what still needs agreement.
