Projects & Partnerships — Activation Requirements
Eligibility criteria, required data points and protocol commitments for a negotiated project tier, including the standard for digital Monitoring, Reporting and Verification (dMRV) projects
Negotiated Project Tier
Full Enterprise-level access for the agreed project period plus a 90-day grace period, activated with a unique project code and invoiced directly. The criteria below are the template minimums; any of them may be negotiated and recorded in the agreement summary.
| Criterion | Minimum requirement | Evidence required |
|---|---|---|
| Land ownership | Minimum 10 acres (4 ha) under secure tenure: freehold title, registered lease of 5 years or longer, or a documented family/community land agreement. | Title deed, lease agreement or signed community land agreement, plus GPS-mapped boundaries for at least 80% of the project area. |
| Production experience | At least 3 years of verifiable commercial production in the target commodity; 5 years or more for multi-zone or multi-commodity projects. | Harvest and sales records, cooperative membership history or audited farm accounts. |
| Water & irrigation | A functional water source covering at least 60% of the project area, with storage of 2,000 m³ per 10 acres or a borehole yield of 5 m³/hour. | Water use permit or borehole log, pump and storage specifications, photographs of installed infrastructure. |
| Field & spatial data | Every project field registered with mapped boundaries, reported acreage and the verification status recorded in the platform. | Field records with GPS polygons and size verification results. |
| Member data & consent | Data-sharing consent captured for every member farmer or outgrower included in the project. | Signed consent records held against each farmer profile. |
| Governance & contacts | A named project lead and a second contact, an agreed payment structure, and a documented milestone schedule for the project period. | Completed project details form with both contacts and the signed agreement summary. |
Project name
Negotiated title used on the project code and invoices
Purpose of the project
Development objective the tier is granted for
Agreement summary
Scope, deliverables and obligations of both parties
Payment structure
Milestones, instalments and amounts
Payment reference IDs
Transaction detail or reference numbers for each instalment
Mode of payment
Bank transfer, mobile money, cheque, cash or other
Project lead
Name, email and phone of the accountable lead
Second contact
Name, email and phone of the backup contact
Expected payment date
Date payment is expected; access is locked if no payment details are logged by then
Project period
Start date, end date and the 90-day grace period that follows
- Submit monthly field, harvest and offtake data through the workspace, including expected yields before each harvest.
- Maintain quality grading at the agreed standard: Grade A and Grade B accepted, Grade C rejected at intake.
- Keep the member directory and consent records current for every farmer participating in the project.
- Allow pre-harvest inspection by the offtaker and project partners on the scheduled date each season.
- Keep at least one named project lead and one second contact reachable for the duration of the project.
- Log payment details before the expected payment date so the tier is not suspended.
dMRV Project Standard
For digital Monitoring, Reporting and Verification projects. These requirements sit on top of the general requirements above and are agreed with the research institution at co-design, before fieldwork begins.
| Criterion | Minimum standard | Evidence required |
|---|---|---|
| Operational dMRV platform | A farm-management or MRV platform in live production for at least 12 months, at technology readiness level 6 or above. Concept notes, prototypes and spreadsheets do not qualify. | Platform address, go-live date, workspace and user counts, and a read-only demo account for review. |
| Smallholder & cooperative reach | Registered smallholder producers and cooperatives in at least one project country, with a field network able to reach them in person. | Member register extract, cooperative agreements and a country / district coverage list. |
| GPS-mapped field records | GPS-mapped plot boundaries and reported acreage for every field in the pilot, each field carrying a recorded size-verification status. | Field polygon export, acreage reconciliation and the verification log. |
| Trained field officer network | A named and trained extension or field officer network under supervision by an agricultural team, able to capture structured data and re-visit plots on schedule. | Officer roster with training dates, areas of coverage and the supervision structure. |
| Auditable records & transaction trails | Dated field activity records, input and production data, cost per acre and transactional trails that an independent reviewer can trace and reconcile. | Sample audit extract showing timestamps, user attribution and change history. |
| Independent verification sources | At least two independent sources available to cross-check reported data — for example satellite or GPS boundary checks and cooperative or warehouse records. | Verification matrix naming each source and the indicator it checks. |
| Data governance readiness | Consent capture, lawful basis, anonymisation, storage and retention arrangements documented and ready to be written into the project protocol. | Consent instrument, data protection policy, retention schedule and ethics / IRB reference. |
| Institutional contracting capacity | Capacity to execute a written agreement with the contracting research institution before work commences, with a named lead and a second contact. | Signatory details, contracting route and both contacts. |
Research institution & protocol reference
Contracting institution, protocol / ethics reference number and version
dMRV framework scope
Indicators, sampling protocols and data flows agreed at the co-design stage
Indicator set
Every monitored indicator with its unit, measurement frequency and responsible party
Sampling protocol
Sample size, stratification, plot selection method and re-visit cadence
Data flow map
Where each data point is captured, by whom, in which system, and where it lands
Verification plan
Independent source per indicator, accepted tolerance and escalation when a discrepancy is found
Reporting cadence & format
Baseline, mid-line and end-line reporting dates, with the agreed narrative and machine-readable format
Field sites & locations
Project countries, districts, participating cooperatives and the operating field hub used as a pilot site
Consent & lawful basis
Consent instrument, lawful basis, withdrawal route and data subject contact
Storage, retention & access
Hosting location, retention period, deletion trigger and who may access raw data
Pilot budget lines
Travel and fieldwork costs plus the agreed modest remuneration for the partner's contribution
Written agreement reference
Executed agreement between the research institution and the dMRV partner, dated before work commences
Publication & authorship position
Anonymisation rule for published outputs and the authorship / acknowledgement arrangement
Lead & second contact
Named accountable lead and backup, each with email and phone
- Co-design the dMRV framework with the research team: definitions, indicators, sampling protocols and data flows appropriate to smallholder production systems.
- Capture field-level data on the ground using the platform and the trained field officer network, under direct supervision by the partner's agricultural team.
- Verify reported data against independent sources: GPS-verified plot boundaries, dated field activity records and cross-checks with cooperative records.
- Deliver structured dMRV reports at the agreed intervals, in a format usable for both academic analysis and programme reporting.
- Contribute to the interpretation of findings and to the drafting of project outputs, including joint publications where appropriate.
- Take part in pilot workshops and fieldwork for the duration of the pilot period.
- Provide access to the named operating field hub as a pilot site, with irrigation, diversified crops and livestock, and records held across several seasons.
- Capture informed consent before any farm-level data is collected, and honour withdrawal requests within the agreed window.
- Flag any protocol deviation, data gap or verification discrepancy to the research team within the agreed reporting interval.
- Travel expenses and a modest remuneration for the partner's contribution are provided by the contracting research institution.
- The specific terms are set out in a written agreement executed before work commences; nothing in this requirements set is a signed contract.
- The pilot period, delivery milestones and reporting dates are fixed in that agreement and mirrored in the project activation record.
- Payment reference IDs are logged against the project before each expected payment date, or access is locked until they are.
- Informed consent is captured and recorded for every farm, plot and respondent before collection begins.
- The lawful basis for processing is identified and documented in the project protocol.
- Published outputs are anonymised: no farm, cooperative or respondent is identifiable in any publication.
- Storage location, access control and retention period are agreed in the protocol, with deletion at the end of the retention period.
- Data sharing is limited to the named research team and the purposes in the protocol; onward sharing requires written approval.
- Ethics or IRB approval is referenced in the protocol before fieldwork starts.
How to activate the tier
Submit the activation request from the Subscription page with the project code issued to you, including both contacts, the payment structure and the project period. The tier activates immediately and the subscription end date is set to the project end date plus 90 days.