Return to Editorial

The Difference Between Having Evidence and Being Able to Use It

Most producers have more evidence about their products than they realise. The problem is that it exists in fragments.

March 20264 min readBy Hedamo
Filing folders and documents on a shelf in a neutral office setting

When producers say they have a documentation problem, they usually mean one of two things.

The first is a genuine absence of evidence: they have never tested their product, have no records of their production process, hold no certifications, and have not systematically documented what they do. This is a real documentation problem, and it requires investment to address.

The second is something different and considerably more common: they have evidence, in abundance, but it is not organised in a way that can be used.

The Scattered Evidence Problem

A typical small or mid-sized food producer, when asked to describe what documentation they have, will produce a collection something like this: a certificate from a domestic food safety body, several years old. A laboratory analysis from when they entered a regional market. A letter of appreciation from a long-standing buyer. Photographs of the harvest and production process from last season. A product specification sheet written for a trade show, in the domestic language. Records of their supplier relationships, kept in a spreadsheet. Notes on their production methods, never formally written up. A certificate that may or may not be current.

None of these individually are sufficient for a buyer due diligence process, or a procurement qualification, or an institutional partner assessment. Together – assembled, structured, and presented coherently – they constitute a significant body of evidence about the product and the producer.

The problem is not the absence of evidence. The problem is that the evidence exists in fragments: different formats, different languages, different levels of formality, produced at different times for different purposes, held in different places, with no shared structure and no single version of what the product is.

Why Fragments Cannot Be Used

A buyer evaluating a new supplier needs to form a view of the product and the producer within a limited time, using the materials they have been given. If those materials require the buyer to assemble a coherent picture from disconnected fragments – to infer from the combination of an old certificate, a technical sheet in a foreign language, and some photographs what the product's attributes actually are – most buyers will not do it.

Not because they are lazy. Because they have other suppliers who make the evaluation easy.

Fragments impose a cost on the buyer. That cost is the work of interpretation – of assembling a scattered set of materials into a coherent picture. Buyers who bear that cost do so for suppliers they have a compelling reason to pursue. For first introductions, where no relationship has yet developed, that cost is a reason to move on.

The evidence is there. The architecture to hold it is not.

What Assembling Evidence Requires

Turning scattered evidence into usable documentation requires two things.

First, a structure: a consistent framework for organising product information that covers the categories a buyer, regulator, or institution is likely to ask about. Origin. Production practices. Composition. Existing certifications. Health-relevant attributes. Gaps – where information is not yet available.

Second, a process: a disciplined approach to populating that structure, updating it as the product and producer's circumstances change, and maintaining it as the authoritative source for all external communications about the product.

This is not a large technical undertaking. For most producers, the raw material – the evidence – already exists. What is missing is the assembly. Putting the fragments into a structure that can be read by someone who has no prior knowledge of the producer takes time and care, but it does not usually require generating evidence that does not exist.

Most producers are closer to having usable documentation than they realise. The gap is not what they know or what they have. It is whether what they know and have is held in a form that someone else can read.

Hedamo Logo
US Office

9100 Wilshire Blvd, Ste # 333, #189 Beverly Hills, California 90212 USA.

India Office

T-Hub, Hyderabad, Telangana 500081, INDIA

+1 424 400 8899+91 96147 09999outreach@hedamo.com
Β© 2026 Hedamo | An Altibbe Inc. Ecosystem

Hedamo is a disclosure system. All reports are based on producer-declared information. Hedamo structures and presents disclosures but does not verify, certify, or approve products. Interpretation remains with stakeholders.

The Difference Between Having Evidence and Being Able to Use It | Hedamo