1. Read a weather alert at the right level
The Thai Meteorological Department's 06:00 bulletin on 31 August 2026 reported increasing rain, heavy rain in some areas and very heavy rain in selected areas, warning of accumulated-rain, flash-flood and runoff risks. Its 30 August–2 September outlook maintained the heavy-to-very-heavy rain caution.
This is a preparedness trigger and a guide to where inspection may be needed. It does not identify which orchard has standing water, which tree has symptoms, which fruit cohort was affected or when a lot can be released. Quality decisions therefore need plot- and lot-level evidence after the alert.
2. Alert, impact and diagnosis are different evidence layers
An Alert signals risk before or during an event. Impact is what is actually observed in access routes, drainage, soil, trees or blocks. Diagnosis assigns a cause using sufficient evidence and qualified judgement.
A 4 August 2026 follow-up in Mae La Noi after flooding found most durian trees in good condition, some yellowing leaves and drainage channels already made by the grower. The example shows why an affected-area label does not mean every tree has the same outcome.

3. The six-layer Weather Event Evidence Record
The record should let a reviewer trace a lot back to the warning, orchard condition, checks and decision rationale, using the organisation's and relevant authority's procedures.
- Alert Context — issuing source, date and time, affected area, forecast window and recipient
- Orchard Impact — orchard, block, inspection map, access, drainage, soil, trees and time-stamped images
- Tree & Fruit Check — observed symptoms, samples or checks, inspector and questions escalated for expert review
- Action Log — action, operator, time and rationale, without recalling product names or rates from memory
- Decision — Hold, Recheck or Release, authorised person, conditions and supporting evidence
- Lot Handover — harvest or intake lot, documented quantity, time and exceptions requiring follow-up
4. When to Hold and when to escalate
Hold does not mean that fruit has failed. It means the evidence is not yet sufficient for a decision. A workable procedure identifies who can stop work, what must be rechecked and how material from an undecided block is kept separate.
DOAE's durian root-and-collar-rot guidance distinguishes symptoms across roots, trunk, leaves and fruit, and notes that some leaf symptoms are found more often after consecutive days of heavy rain. Record and escalate abnormalities for proper diagnosis rather than choosing a treatment or product from this summary.
5. Link the orchard record to harvest and packhouse intake
When fruit moves into harvest or packhouse intake, the event record should travel with orchard and block identity, harvest date and intake lot. The receiving party can then see which Hold was closed, which condition still needs checking and who authorised the decision.
A photo without a plot code or timestamp is weak evidence. So is a note saying only ‘heavy rain’ without the issuing source or inspection point. Credibility comes from connecting identity, event, inspection, decision and handover.
6. Claims boundary
This article provides an evidence-management framework. It does not prescribe rainfall thresholds, harvest waiting periods, diagnosis or pesticide use. Actual decisions must follow official requirements, registered labels, qualified advice and orchard context.
The sources do not establish that Siam Diamond or any partner orchard was affected, used a particular intervention or released a lot. Hold/Recheck/Release are evidence states here, not quality or safety certifications.


