NCGS-M010 — Household benefit survey

Pre-release. This site describes standard version 0.7.0-dev, which is in development and may change before version 1.0.0.

A structured survey of the owner at a household stand, taken on a monitoring visit at T2 or later that observed a living tree there, after KIA-Adapt’s A4 questionnaire: per living fruit tree whether it bore fruit in the recent season, and for the household whether fruit was shared or sold, the months with fruit and the people the trees benefit; reported as counts of trees and of households, never as a person’s answers.

underlying principles and assumptions

The household is a site type plus the owner role, never a person (ADR-0007); the survey’s answers are counts and yes-or-no values on the household survey record; a living tree is confirmed by the visit’s observation, not by the answer alone; the survey rides on a monitoring visit, so its horizon and its trees are the visit’s (ADR-0010).

methods and procedures

On a monitoring visit at a household stand at T2 or later, the fieldworker first observes the trees as the census does; if at least one tree is alive, they ask the owner, for each living fruit tree observed, whether it bore fruit in the recent season, and for the household whether fruit was shared or sold, in how many months of the past year it had fruit, and how many of its people benefit; the household survey record carries the answers, the visit and the owner’s agent identifier, no names.

data requirements and inputs

A household survey record (dataRequirements/household-shapes.ttl) for the visit; the monitoring visit record at the stand with its tree observations; the stand registered as a household-stand site; the owner enrolled in the owner role; the consignments and planting records that put the trees there. A design applying it declares an instrument whose mapping captures the household survey; the standard’s own form is household-survey-ui-shapes.ttl, and an implementer’s instrument built from it supplies the mapping.

calculation and transformation rules

Both counts take only surveys on a visit that declares T3 or a later horizon, the earliest horizon of both indicators: a survey at T2 is a valid record whose answers enter neither count. Trees bearing fruit = count of fruiting answers whose tree is a fruit-tree individual observed alive on the visit and whose bearingFruit is true. Households sharing or selling fruit = count of household-stand sites whose survey for the visit has fruitShared or fruitSold true. Months with fruit and people benefiting are recorded per household and reported alongside, not counted. Each rolls up by summing over stands; a stand with no survey at the horizon is not surveyed, never counted as a no. A corrected survey restates the first (ADR-0018) and only the latest counts.

outputs and units of measure

Trees bearing fruit in the recent season (count, NUM) by horizon, species, site and census place; households sharing or selling fruit (count, NUM) by horizon and census place.

validation and verification approach

Validation: a design applying NCGS-M010 includes household stands in a stratum the monitoring plan reaches at T2 or later and declares an instrument that captures the household survey; the survey enters the design’s validation sample. Verification: a reviewer meeting the KSR requirement in community engagement and education and in field survey and data capture, who is not the interviewer, checks with the visit’s verification that each survey is at a household stand on a visit at T2 or later, that the respondent is the enrolled owner, that every fruit tree answered for was observed alive on the same visit, and that the answers are counts and yes-or-no values only. A survey whose visit is not approved enters no count.

limitations and applicability boundaries

Self-reported fruiting, sharing and selling; a season’s yield is not a harvest weight and a sale is not an income. Defined for household stands only. A tree that bore fruit but died before the visit is not counted. The answers are the owner’s, on one day.

rationale

The food and local-economy domains need figures a household component can evidence; asking the owner on the visit that already confirms the trees keeps the answers tied to trees the standard has observed, and counting households rather than people keeps personal data out of the graph.

Applicability

  • NCGS-M010 applies only to a visit at a household stand.
  • NCGS-M010 applies only to a visit that carries a household survey record: the survey is the methodology’s record.
  • NCGS-M010 applies only to a visit that declares T2 or a later horizon.

Indicators it serves

Activity types

  • Monitoring visit

Knowledge domains a reviewer needs

  • Community engagement and environmental education
  • Field survey and data capture

Variables

Variable Role Unit Description
Households sharing or selling fruit (|H_f|) DerivedOutput NUM |H_f| = count of stands with fs or fd true, on surveys whose visit declares T3 or later.
Trees bearing fruit (|F|) DerivedOutput NUM |F| = count of living fruit-tree individuals at the stand with bf_i true, on surveys whose visit declares T3 or later.
Fruit shared (fs) MeasuredInput UNITLESS
Fruit sold (fd) MeasuredInput UNITLESS
Months with fruit (m_h) MeasuredInput NUM Months in the past year in which the household had fruit from the programme’s trees, 0 to 12; reported alongside, not counted.
People benefiting (p_h) MeasuredInput NUM People in the household who benefit from the programme’s trees, one count; reported alongside, not counted.
Tree at the stand alive (a_i) MeasuredInput UNITLESS
Tree bore fruit in the recent season (bf_i) MeasuredInput UNITLESS

Monitoring requirements

  • NCGS-M010 monitoring requirement: the survey with the visit at T2 or later: A household survey record with every monitoring visit at a household stand from T2 that observed a living tree, under a design applying NCGS-M010.

This page explains the standard and does not decide conformance: only the released corpus does. It describes methodologies/methodologies.ttl, methodologies/applicability-shapes.ttl, methodologies/variable-registry.ttl at standard version 0.7.0-dev.