Skip to content

Monitor · over time

Follow every financed plot, week after week.

Monitor compares each plot with its own history and with its neighbours. Persistent gaps rise to a portfolio view, with the real coverage of each source and a human review before any alert.

Data shown on this site is demo data. Nothing is presented as monitored in real time.

Monitor · season series
Demo
0.20.40.60.8W1W8W15W22W29Today
Plot (simulated index)Three-season median and envelope

Gap to median

−0.19

Decline since week 15, consistent with water stress. Watch proposed; local rainfall to check.

Source coverage across 8 plots

  • Geometry8/8
  • Satellite8/8
  • Vegetation index8/8
  • Field agents6/8
  • IoT stations3/8
  • Drone1/8

Index computed from visible bands (simulation), not a measured NDVI. IoT stations and drone: as available, never systematic.

01 /Who it is for

For following a portfolio after the decision.

For institutions that want to keep reading financed or insured plots without multiplying visits.

  • 01

    Portfolio monitoring

    See which plots drift from their usual path, and since when.

    Banks and MFIs

  • 02

    Season monitoring

    Compare an area with its history as the season unfolds.

    Insurers

  • 03

    Basin monitoring

    Anticipate gaps across a network of farmers or cooperatives.

    Programmes and agribusiness

02 /Inputs and deliverables

Series over time, gaps explained.

Monitor does not just draw a curve: it states the gap, how long it has lasted and which sources it rests on.

What is monitored

  • Geometries of the portfolio’s plots
  • Satellite passes and vegetation indices
  • The same period across several seasons
  • Field agent observations and visits
  • Weather stations and drone missions, when available

What is delivered

  • Portfolio view

    Plots by status, with the date of the last usable signal.

  • Gaps and watches

    Each gap with its duration, size and the suggested explanation.

  • Source coverage

    What is observed, how often, and what is not.

  • Periodic reports

    A summary for committees or monitoring teams, at an agreed frequency.

03 /Before an alert

An alert has to be earned. Three filters before it goes out.

A monitored portfolio must not turn into a stream of false alarms.

  • 01

    Persistent gap

    One pass is not enough: the gap must last across several observations.

  • 02

    Compared context

    The plot is compared with its history and its neighbours to rule out an area effect.

  • 03

    Human review

    An analyst validates the alert and proposes the action: document, call or visit.

04 /Roles and limits

Monitor and flag. Not decide for you.

Monitor produces signals and reports. The measures to take remain yours.

What Wakama does

  • Follow plots over time
  • Compare with history and neighbours
  • Flag persistent gaps after review
  • Document each signal and its sources

What your institution keeps

  • The choice of follow-up actions
  • The relationship with the borrower or policyholder
  • Restructuring or recovery decisions
  • The portfolio risk policy

Limits and dependencies

  • No real-time monitoring claimed: frequency follows satellite passes
  • Cloud cover can delay a reading
  • API and integrations to be confirmed case by case
  • Stations and drones not available in every area

05 /Getting started

Start with a sample of plots.

Delivery formats (reports, dashboard, exports) are scoped to your needs and to what is available in your area.

  1. 1Meeting

    Demo

    Walk through a fictitious season and its gaps, plot by plot.

  2. 2Deliverables

    Monitored sample

    Follow a sample of plots over a set period, with reports.

  3. 3Tailored

    Portfolio

    Extend monitoring to the portfolio, with an agreed frequency and thresholds.

Next step

Let’s talk about how you follow your plots today.

A short meeting to understand your portfolio, see a demo season and identify what can be monitored in your areas.