Skip to main content
The LIP Producer Survey is a quantitative tool developed to systematically capture the indicators needed for a Living Income Price analysis. This survey is designed for in-person interviews, allowing direct engagement with respondents. This format facilitates the collection of accurate and detailed information. The survey’s structure is flexible and tailored to meet the specific needs of a LIP study while adaptable to the contexts of different crops and countries.

Content of the survey

The LIP Producer Survey is composed of 10 sections, each focusing on key areas relevant to the LIP analysis:
  1. Introduction and consent: Questions to introduce the survey and obtain consent from participants.
  2. Household demographics: Questions on the farmer’s background, including age, gender, education, and household composition. This section is primarily used for data disaggregation.
  3. Farm characteristics: Information about the farm, such as its size, location, and the variety of the focus crop.
  4. Revenue from the focus crop: Questions on the quantity produced and sold, price, types of buyers, and revenue from the previous season.
  5. Production cost: Information on input costs, asset costs, labor, etc.
  6. Income from other crops: Questions on the quantity produced and sold, prices from other crops and the different types of other crops.
  7. Income from livestock: Questions on the types of livestock, the revenue from livestock, the related labour and other costs.
  8. Income from off-farm labour and other income: Assess all other income sources and their related income.
  9. Access to finance and related costs: Information about access to finance, including sources of loans.
  10. Cooperative Membership: Questions about membership in agricultural cooperatives, its benefits, and certification.
The primary goal of this survey is to accurately measure the Living Income Price (LIP). The details of how different questions contribute to this LIP are outlined in the calculation sheet.

How to use the Survey Builder

A Survey Builder tool has been developed to facilitate the design of the survey, ensuring consistency across different cases while allowing customisation to specific contexts. To begin, open the survey builder by making a copy of the template through this link. The survey layout is designed for direct upload into KoBoToolbox, a widely recognised platform for digital survey development. This format offers flexibility and adaptability, ensuring that the survey can be tailored to the unique needs of each context. The workbook consists of the following tabs:
  • Contextualisation sheet
  • Survey (for KoboToolbox upload)
  • Choices (for KoboToolbox upload)
  • Settings (for KoboToolbox upload)

KoboToolbox Survey, choices, and settings templates

The Survey Worksheet contains the full list of questions and their details, defining how they will appear and function in the KoBoCollect app or other compatible data collection platforms. This sheet should not be modified, as it is automatically contextualised based on the selections made in the Contextualisation Sheet. The main columns of the survey worksheet are: The Choices Worksheet defines the options for multiple-choice questions. Each row represents a single choice, and these are grouped by list_name, linking them to the relevant question in the Survey Worksheet. It contains 3 main columns: While optional, the Settings Worksheet is highly recommended to ensure proper metadata management for the survey. At a minimum, you should specify the form_title and form_id, which are essential for organising and identifying your survey. The form_id defaults to the date, but it can be customised if needed. For more information on using KoBoToolbox’s XLSForm format, please refer to https://xlsform.org/en/

Manual adjustments

After making a copy of the survey and filling out the contextualisation sheet, there are a few leftover tasks that cannot be automated. These can be found under the manual checklist part of the contextualisation form and are mainly related to the choices sheet. The lists that require attention are in red. You will need to manually fill in the names of the enumerators that are being sent to the field and the location names for every administrative level. It is only necessary to fill in the names of localities where the data collection is taking place as these will be used to record the location of the farmer. Make sure that the list_name is exactly the same for all options and that the name column contains only unique values. Example: Data collection in Sierra Leone in 3 districts. The second adjustment is related to the crop harvests and seasons. When we ask farmers about their production quantities and cost, we allow them to choose the time period for which they want to report. In practice, some farmers may choose to report their quantities and cost for the main and the off season separately. Some may have only had one productive season. Some may know their cost values but only per the whole year. The survey is currently designed to let farmers answer for the last 12 months, season 1 or season 2. That is determined by this list in the choices sheet: However, that might not be optimal for every focus crop. In some scenarios the seasons also have distinct local names. For example, in the context of coffee in Uganda this could be the Main crop and the Fly Crop. Labels with an * can be replaced by these local names to facilitate better understanding between enumerators and respondents. If you think farmers might prefer reporting by four seasons instead of two feel free to adjust the list: *to be replaced by more distinctive/local names
It is important to choose the option that will feel the most natural to farmers to get more accurate and reliable information.
Lastly, the manual checklist also includes a list of tasks for the contextualisation sheet that ensure the automatic adjustments to the survey work as intended. In case you do not require the Spanish translation of the survey, delete the following columns from the survey sheet:
  • label::Spanish, hint::Spanish, constraint message::Spanish