Epinova Action Pilot in design

Turn priority lists into field plans teams can execute.

Epinova Action is being designed to translate priorities into microplans - who goes where, with what, and when - and to track field delivery against the plan in near real time.

The problem

The gap between plan and field is where impact is lost.

Microplans are still commonly built in spreadsheets and on paper maps. Teams are assigned without a clear view of distance, terrain or stock. Once activities begin, supervisors have limited visibility of what has actually been completed until reports arrive days or weeks later.

  • Microplanning is manual and slow to update
  • Team and commodity allocation rarely reflects real constraints
  • Supervisors lack timely visibility into field progress
  • Activity completion is difficult to verify

Product overview

From target areas to verified activities.

Action is designed to generate draft microplans from prioritized areas, available teams and commodities, then let supervisors adjust them. Field teams receive clear assignments; supervisors see planned versus completed activities on a live operations view.

Verification signals - such as location-stamped check-ins and supervisor confirmation - are planned to strengthen confidence in reported coverage.

Key capabilities

What it is designed to do

Pilot in design

Field microplanning

Draft plans by area, team and day from prioritized targets.

Pilot in design

Resource allocation

Matching commodities and staff to targets under stock constraints.

Planned

Team coordination

Assignments, schedules and supervisor workflows.

Planned

Routing

Suggested visit sequences accounting for distance and access.

Pilot in design

Operations dashboard

Planned vs completed activities by zone and team.

Planned

Activity verification

Location-aware check-ins and supervisor sign-off.

Interactive visualization

Explore Epinova Action

Illustrative operations view - fictional zones, teams and simulated progress.

Programme progress71%
Activities495/695
Field staff38
Zones6
Zone AZone BZone CZone DZone EZone F

Planned vs completed by zone

  • Zone A84%
  • Zone B62%
  • Zone C43%
  • Zone D94%
  • Zone E69%
  • Zone F55%

Resource availability

  • Zone ANets 72%Test kits 64%
  • Zone BNets 41%Test kits 58%
  • Zone CNets 66%Test kits 30%
  • Zone DNets 88%Test kits 81%
  • Zone ENets 55%Test kits 47%
  • Zone FNets 23%Test kits 52%

Task assignments

TeamTaskZoneStatus
Team 2Household net distributionZone BIn progress
Team 3Larval source surveyZone CDelayed - road access
Team 6Restock nets from central storeZone FRequested
Team 4Supervisor verification visitsZone DComplete

Illustrative operations view - fictional zones and teams, simulated progress.

Example workflow

How the work flows

  1. 01

    Plan

    Priority areas, teams and stock are combined into a draft microplan.

  2. 02

    Assign

    Supervisors adjust and publish assignments to field teams.

  3. 03

    Execute

    Teams record activities; progress updates the operations view.

  4. 04

    Verify

    Supervisors confirm completion and flag gaps for follow-up.

Inputs and outputs

What goes in, what comes out

Inputs

  • Priority areas from Epinova Prioritize
  • Team rosters and availability
  • Commodity stock levels
  • Settlement and road layers
  • Field activity records

Outputs

  • Microplans by zone and day
  • Team assignments
  • Planned vs completed tracking
  • Gap and follow-up lists

Intended users

Who it is for

Field supervisors

Practical plans that reflect real constraints.

Logistics officers

Visibility into stock against planned activity.

Programme managers

Timely confidence that work is being delivered.

Integrations

Works with the systems you already use

Integration scope is agreed with each partner; connectors marked “planned” are on the roadmap.

  • Mobile data collection tools (e.g. ODK-compatible forms, planned)
  • Logistics management systems (planned)
  • Spreadsheet import
  • Offline-tolerant field workflows (planned)

Responsible AI and data

Safeguards built in from the start

Low-bandwidth first

Designed for intermittent connectivity and lower-powered devices.

Minimal personal data

Field records focus on activities, not individuals, unless a programme requires otherwise under agreement.

Supervisor oversight

Automated plans are drafts for human review.

Shape the first Epinova Action pilot with us.

We are looking for programme partners to co-design field workflows.