- Keep individual board histories visible; an average can hide a different trajectory.
- Compare readings only with their method, location, conditions and time recorded.
- No measured values or readiness thresholds are implied by these hypothetical trends.
An unusual observation is a question
A value that differs from nearby observations deserves context before interpretation. Check its board identity, location, method, settings, and notes. Electronic moisture observations can be affected by species, temperature, treatments, moisture distribution, and technique. That means a surprising number should neither be dismissed automatically nor treated as a complete diagnosis of the material.
Repeat with a documented purpose
Review the instrument instructions and confirm the recorded setup before obtaining follow-up observations. State what the follow-up is checking, such as a suspected setting error or a different accessible position. Preserve the original entry and attach the explanation. If a value is excluded from a calculation because it is invalid, retain the reason visibly rather than silently deleting it from the history.
Do not combine unlike groups by accident
Separate bundles with different identities, products, delivery events, or storage histories when those distinctions matter to the question. A single average across them can obscure the very difference you need to investigate. Keep the grouped summaries and individual records accessible. This is a proposed organization method, not a claim that a particular grouping guarantees representative sampling.
- Retain supplier and bundle identifiers.
- Show the count and positions within each group.
- Mark wetting and storage changes by affected group.
- Keep follow-up observations linked to the original entry.
Avoid unsupported thresholds
This guide does not set a universal acceptable spread or a number that automatically makes a board an outlier. A project specification may define requirements, but it needs its source and scope attached. Where none exists, report the difference plainly and obtain the appropriate review. Describing uncertainty accurately is more useful than creating a pass/fail rule that the measurement procedure does not support.
Hypothetical mixed delivery with one unusual position
Bundles D and E share an order but were stored in different locations. One observation on E differs from the others. The log keeps D and E separate, reviews E's recorded settings, and adds a labeled follow-up. It does not drop the observation to improve the combined average or assume that every board in E has the same condition.
Common questions
Can I delete an obvious entry mistake?
Correct it transparently. Keep a correction note or history showing what changed and why, especially if the value appeared in an earlier report.
What spread is acceptable within a bundle?
Use a documented applicable requirement if one exists. This workflow supplies no universal spread threshold or automatic acceptance decision.
Evidence & limits
Reviewed September 13, 2026. Sources support their stated technical principles; this site's workflows and hypothetical examples are not product tests, supplier approvals or independently reviewed project records.