A farmer can only decide whether Thursday is safe after a spray when the product, dose, application time, and reviewed re-entry interval are known. A vague warning cannot tell a family when it can return to the farm without risking exposure.
At 6:40 on Wednesday morning, Adwoa, an illustrative cocoa farmer, stands at the edge of her plot with her hoe against one shoulder and her daughter’s lunch wrapped in cloth. A neighbour sprayed part of the farm the previous afternoon. Now rain has passed, pods still need checking, and Thursday is the next day Adwoa can spare for work there.
She has heard the familiar advice: wait before going back.
But wait how long?
If she returns too early, she could enter a recently treated area without knowing the safety interval. If she waits longer than necessary, a disease problem can spread while she stays away. The possible bad ending sits plainly in front of her: exposure for the people working the plot, or a harvest problem left unattended because nobody could give a date.
A warning is not a calendar
“Be careful after spraying” may sound responsible, but it leaves the hardest part with the farmer. Adwoa still has to decide whether Thursday morning is safe, whether only the sprayed rows should be avoided, and whether rain changed what she needs to do next.
That decision depends on details that cannot be guessed from a voice note:
- The exact product used.
- The label instructions for that product.
- The application time and conditions.
- The verified re-entry interval.
- Whether the farmer means returning to inspect, weed, harvest, or spray again.
A pesticide name may be uncertain in spoken Twi. A farmer may use a brand name, an English term, or a local description. One missing word can change the answer from “stay out until the stated interval has passed” to “ask the extension officer before entering.”
This is why an answer needs to be tied to reviewed guidance, not generated from a general conversation. AgriVoice is designed to select from reviewed content in response to a farmer’s question. When the necessary information is missing or uncertain, the right response is an escalation to a named person, not a confident instruction.
The three chemical guidance blocks still being withheld in AgriVoice show why that boundary matters. They need an agronomist to verify dosage, re-entry, and pre-harvest intervals before they can be spoken as advice. Until then, refusal protects the farmer better than a smooth-sounding answer. [Kwaku’s missing pesticide interval]( /blog/kwaku-s-missing-pesticide-interval-a-safe-farm-decision-must-wait-e92220b6/) is the same problem in practical terms: a safe decision sometimes has to wait for confirmed information.
Reviewed Twi carries the meaning farmers need
A calendar answer only helps if the farmer understands it the first time. That means the guidance must be reviewed in speakable Asante Twi by someone who understands farming vocabulary, while retaining English terms farmers commonly use, such as a familiar product category or COCOBOD.
Machine translation has already shown why this work cannot be treated as a finishing touch. In an earlier test, the Twi word for cocoa was translated as “chicken.” The sentence may still sound fluent. It would still be wrong.
For pesticide guidance, the risk is greater. A translated instruction can lose the distinction between a product name, an action, a time period, and a condition for escalation. A farmer who asks, “Can I return on Thursday?” needs a response that makes the next step clear in the language they use at the farm:
- Which details to check before entering.
- What cannot be confirmed from the question.
- Who will receive the escalation.
- What to do while waiting for that answer.
Ghana’s nationwide spraying and fertilizer distribution makes that clarity especially useful. With community allocation led by extension staff and traditional leaders, inspected agrochemicals, protective equipment, and risk-prioritized spraying, farmers may hear several instructions through several people. A clear, reviewed voice response can help preserve the exact safety step instead of reducing it to “come back later.”
The safe answer may be an escalation
On Wednesday evening, Adwoa records a Twi voice note. She remembers the colour of the container but cannot name the product. She also does not know when the spraying ended.
The system should not convert that uncertainty into a Thursday approval. It should explain that the interval cannot be confirmed from the information provided and send the question to the named extension officer. That is the turn in the story: uncertainty becomes a specific next action, with an accountable person attached.
A good escalation path matters as much as a good answer. The active AgriVoice pilot requires a cocoa-sector partner to name the extension officer who receives these cases. It also measures whether escalations are resolved in less than one working day. A farmer should know that their voice note went somewhere, and that someone is responsible for the reply.
By Thursday, Adwoa has a clearer boundary. She knows whether to stay out, which detail still needs confirmation, and who can give it. Her hoe remains by the door until the safe return time is confirmed. That is a small change in a morning routine, but it is the difference between acting on a calendar date and acting on a guess.
Build advice around the decision a farmer must make
For cocoa-sector partners, the practical work starts before any pilot message is sent. Review each Twi block. Confirm pesticide dosage, re-entry, and pre-harvest intervals with a Ghanaian agronomist. Test farmer voice notes that include uncertain product names and code-switched language. Name the person who will handle cases that cannot be answered safely.
Then measure what happens in the field: whether farmers understand the spoken response, whether the system answers or escalates correctly, and whether the human follow-up arrives in time to support a real farm decision.
Thursday should never be an assumption.
Comments
No comments yet.