Playbook: Sample Use Case

Certification Data

Many organizations collect and use Your Data in order to gain a certification, qualify for a permit or special designation, or support an audit. This example highlights an agricultural data use case that parallels similar efforts in other sectors.

icon: 2 people in an interview

What do we want to do?

We want to help agricultural producersfarmers and rancherscollect, organize, and present the necessary information to obtain certifications that can enhance their income, and permits which allow ongoing operation.

Who are the data stakeholders?

  • We, the primary data collectors, are agricultural cooperatives, extension agents, local businesses, and nonprofits that advise and support these producers.
  • The primary data collectors may also be organizations that provide infrastructure to hold data, and services to complete the forms and reports required for agricultural certifications and licensing.
  • The data is collected from the producers and coops, employees and workers, as well as their advisors and agents.
  • Downstream users of the data may include the certifying or licensing agencies and organizations, supply chain intermediaries, or consumers. Regulators and policymakers considering standards and adoption levels, and researchers seeking to understand practices and outcomes, may also use this data.

What types of data do we use?

  • We mainly collect and use agricultural data, including inputs such as seed, fertilizer, or water, and practices, such as tillage, planting, weed and pest eradication, harvesting, or herd movement.
  • Data may also include data about workers, and financial data related to farm or ranch business and operations.
  • Data may be collected verbally in an interview, gathered manually via pen and paper, captured in a mobile application, or submitted online.

What benefits, challenges, or risks do we encounter?

  • This data provides documentation that is necessary to maintain operational licenses, and may provide beneficial opportunities for government incentives and market premiums.
  • Agricultural data can be challenging to capture. It can be time-consuming to gather, and its benefits may be uncertain or take a long time to be realized. Producers often lack the time or resources needed to provide the data, and may distrust the certification systems themselves.
  • The data can hold risk for both producers and their workers. Data may be used against them if it is inconsistent, to target them by competitors or corporate interests, or it can create future liabilities, such as if a fertilizer that was considered best practice at the time of application is later determined to be damaging or even dangerous.

Is this use case appropriate for BD4D?

  • Yes. Collectors and producers alike should be able to trust that collected data will be used only for its intended purpose: for the primary benefit of the producers.
  • Uses such as contributing to research efforts or policymaking can similarly advance the interests and opportunities of producers. Adopting BD4D provides a path to evaluate an organization’s data practices and stewardship, especially where sensitive data is involved.
  • Adopting the BD4D Standard changes the status quo. Without it, data gathered for this use case may include Your Data that is not required for certification, might be used for other purposes, or might be shared or stored beyond a reasonable time period—all without the data stakeholders’ knowledge or ability to request deletion or transfer.

7. Binding

Impact Data