Filovara
EN
WorkspaceScreen a plot free
GuidesEvidence concept

How to interpret WHISP indicators without overstating the result

Read source-level WHISP indicators, distinguish observations from decisions, and document uncertainty before using a result in EUDR review.

A WHISP response is useful because it preserves several geospatial observations rather than collapsing them into an unexplained pass or fail. Reviewers should read indicator provenance, classes, timing, coverage, and unavailable values before connecting the response to supplier evidence and an accountable business decision.

A practical preparation workflow

  1. 1

    Confirm that the result belongs to the expected plot geometry and WHISP execution.

  2. 2

    Review every relevant indicator with its source, class, version, and limitation.

  3. 3

    Record whether the response supports review, needs more evidence, or cannot be relied on.

Do not turn many indicators into one unexplained score

Different datasets answer different questions and can cover different dates or land-change classes. Keep the individual observations visible so reviewers can see agreement, conflict, and missing coverage.

Separate three layers of meaning

The response contains technical observations. A reviewer interprets those observations beside supplier and production evidence. The responsible business then records the decision for the specific case. Keeping these layers separate prevents software output from appearing legally authoritative.

  • Observation: what a named dataset returned for the submitted area.
  • Interpretation: how a reviewer understands that result and its limits.
  • Decision: what the responsible business does next and why.

Treat missing and unavailable results as information

A missing indicator, service failure, or coverage limitation is not a green result. Record it explicitly, decide whether another source or supplier document is needed, and rerun only as a new version.

What to check

  • Exact plot and evidence hash used for the response
  • Indicator source, class, value, and unit
  • Dataset timing, coverage, and unavailable values
  • Documented interpretation, owner, and next action
Keep this limitation visible

An indicator can be technically accurate for its dataset and still be insufficient for a legal or commercial conclusion about the plot, shipment, or product.

Questions teams ask

Is a low or clear indicator enough to close the review?

Not by itself. Confirm plot identity, dataset scope, relevant dates, supplier evidence, and the business’s due-diligence standard.

What if two indicators disagree?

Preserve both sources, investigate their date and classification differences, and document which additional evidence or expert review is required.

Can a reviewer edit the WHISP response?

No. Preserve the response as evidence. Add interpretation and decisions as separate records so the original technical output remains reproducible.