Avocados

1. Scope and Applicability

This PCR covers fresh, unprocessed avocados produced in managed perennial orchards and transferred at the farm gate. It includes orchard establishment, the non-bearing period, productive orchard management, harvest, and optional on-farm conditioning before hand-off. It applies to rainfed and irrigated orchards and to fruit sold for fresh consumption or further food processing without changing the farm-gate product identity. It excludes nursery operations, avocado oil, pulp, purée, frozen or dried avocado, prepared foods, off-farm transport, storage, retail, consumer use, and end-of-life packaging. Orchard establishment impacts shall be allocated to declared production years and disclosed rather than omitted.

2. Product Category Identity

Field	Value
canonical_pcr_id	pcr.agriculture-forestry-and-fishery-products.products-of-agriculture-horticulture-and-market-gardening.avocados
classification_refs	CPC 3.0: 01311 Avocados; mapping relation: exact
covered_products	fresh, unprocessed avocado fruit transferred at the farm gate, including fruit for fresh-market or processing destinations
excluded_products	nursery planting-stock production; avocado oil, pulp, purée, frozen or dried products; prepared foods; off-farm logistics and downstream use
representative_product	harvested avocado fruit, unprocessed, at farm gate
production_route	perennial orchard establishment, orchard management, harvest, and conditional farm-gate conditioning
market_state	fresh fruit at declared hand-off condition, with cultivar, maturity, quality grade, moisture or dry-matter convention, and conditioning status disclosed

3. Reference Flow

Field	Value
What	fresh, unprocessed avocado fruit at the farm gate
How much	1,000 kg as-received marketable avocado fruit
How well	harvested fruit meeting declared cultivar, maturity, quality grade, defect, and hand-off condition; no transformation into oil, pulp, purée, frozen, or dried product
How long or cycle	one declared production year within the orchard's productive life, with establishment impacts allocated across the declared orchard life
reference_flow_link	reference_product_at_declared_handoff

Field	Value
Reference amount	1000
Reference product flow	Fresh avocado fruit, production mix, at farm gate, unprocessed
Reference flow property	Mass 93a60a56-a3c8-11da-a746-0800200b9a66
Reference unit group	Units of mass 93a60a57-a4c8-11da-a746-0800200c9a66
Reference unit	kg
Required qualifiers	cultivar or cultivar group; production country, region, and climate; orchard age and productive status; crop year; orchard area; irrigation status and water source; maturity or dry-matter convention; accepted and rejected fruit basis; conditioning included or excluded

When constructing a foreground data package, the items listed in Required qualifiers must be declared in dataset metadata, process notes, reference flow comment, product description, or an equivalent data package field. Missing required qualifiers make the reference flow definition incomplete for that data package.

Each foreground dataset must explicitly select one actual route, declared gate, product state and output row. Reconcile the selected terminal route with reference_product_at_declared_handoff; normalize that handoff output to the reference quantity and retain preceding-stage outputs as measured transfers. Raw weighing, mass reconciliation and lot traceability requirements continue to apply.

The sole reference output is reference_product_at_declared_handoff, receiving the selected actual route product at the declared gate. Existing route-output ids identify the source and physical state; they are no longer individually fixed to the reference quantity.

4. Measurement and Unit Rules

rule_id	Applies to	Required property	Required unit	Rule
reference_mass_as_received	reference avocado output	Mass	kg	Report accepted fruit on the declared as-received hand-off basis. If dry matter, maturity, or defect adjustments are used, retain the measured basis and conversion before normalization.
orchard_life_allocation_basis	establishment and immature-orchard inputs	area, time, or mass activity property	ha, orchard-year, or kg fruit	Allocate establishment and non-bearing orchard inputs over the declared productive orchard life using the same orchard area, production years, and accepted fruit output basis; disclose exceptional replacement or abandonment.
area_to_reference_conversion	area-based orchard flows	activity-specific property	activity-specific unit	Divide orchard-year totals by accepted farm-gate fruit mass from the same orchard-year or declared multi-year average before scaling to 1,000 kg.
nutrient_product_and_basis	fertilizer or soil-amendment input	nutrient mass and product mass	kg product; kg N, kg P2O5, or kg K2O	Give every actual fertilizer or amendment product its own card, retaining physical product mass, formulation, nutrient composition and application records. Nutrient quantities are not additional inputs of the same product; collection or group identifiers cannot substitute for a concrete flow identity.

5. System Boundary

Boundary Abstraction

Field	Value
declared_starting_condition	orchard site before or at establishment, with planting material and purchased management inputs crossing the foreground boundary; existing land history and prior crop condition are disclosed
starting_condition_role	start of managed perennial avocado production and orchard asset accounting
product_classification_scope	fresh avocado fruit corresponding to CPC 3.0 code 01311
recursive_input_rule	avocado planting material and retained fruit are upstream inputs only when crossing the boundary; they must not be recursively represented as this same farm-gate fruit output
upstream_dataset_requirement	compatible upstream datasets for planting material, nutrient or soil-amendment products, crop protection, energy, irrigation supply, machinery services, packaging used before hand-off, and applicable waste treatment
disclosure	cultivar, orchard age, establishment year, productive life, replacement trees, orchard area, previous land use, soil and climate context, irrigation, nutrient basis, crop protection, yield, harvest losses, conditioning, co-products, and residue or waste destination

Boundary Rules

rule_id	Applies to	Rule	source_ids
boundary_orchard_establishment_to_farm_gate	all conforming datasets	Include site preparation, planting, orchard establishment, immature years, productive orchard management, harvest, and conditioning performed before the declared farm-gate hand-off.	fao-gap-framework-2003
boundary_perennial_orchard_disclosure	establishment and replacement trees	Include establishment and replacement-tree inputs only after assigning them to the declared orchard life or accepted fruit output basis; disclose the allocation horizon and non-bearing years. Include the attributable historical establishment, immature-phase and renewal contribution for the represented stand even when no new event occurs this year. The stated attribution records are required evidence, not a condition allowing omission: missing amounts, age/lifetime or output history remain an explicit completeness gap, never zero or an automatic exclusion. Retain the original events and apply the declared period/output method once; preserve any separately justified study exclusion.	fao-gap-framework-2003; iso-14067
boundary_direct_field_emissions	managed soil and crop residues	Include direct and indirect nutrient- and residue-related emissions using a geographically applicable method and the same activity data used for nutrient, irrigation, and residue accounting.	ipcc-2019-refinement; emep-eea-2023-guidebook
boundary_farm_gate_conditioning	optional conditioning	Include washing, sorting, grading, trimming, or short-term farm handling only when performed before hand-off and not already embedded in the harvest record; identify rejected fruit and destination.	fao-gap-framework-2003
boundary_post_farm_gate_exclusion	downstream activities	Exclude off-farm transport, storage, distribution, retail, consumer use, food processing, oil or purée manufacture, and packaging end-of-life unless the study explicitly extends beyond this PCR.

6. Process Inventory Structure

Process Map

process_id	process_name	inclusion	inclusion_condition	role	quantitative_reference
avocado_orchard_establishment_and_management	Avocado orchard establishment and management	required	always; include establishment and productive-year management with declared orchard-life allocation	managed perennial biological production and orchard asset formation	orchard area, orchard-years, establishment period, and annual accepted fruit output
avocado_harvest_and_farm_gate_handling	Avocado harvest and farm-gate handling	required	always	harvest capture, field handling, and farm-gate transfer	harvested, accepted, downgraded, and lost fruit mass for one production year
farm_gate_avocado_conditioning	Farm-gate avocado conditioning	conditional	washing, sorting, grading, trimming, or other conditioning occurs before hand-off and is not included in harvest records	prepare fruit for the declared hand-off state	incoming fruit mass and accepted conditioned fruit mass
declared_reference_handoff	Product Measurement at Declared Handoff	required		foreground	reference_product_at_declared_handoff

Process: Avocado orchard establishment and management (avocado_orchard_establishment_and_management)

Inputs

Product flows

Avocado planting material (avocado_planting_material_input)

Record nursery trees, grafted plants, or other planting material crossing into orchard establishment. Retained or self-propagated material must state its origin and allocation treatment.

• Selected flow: Avocado planting material for orchard establishment

• Flow property / unit: Mass or item count / kg or item

• Amount rule: measured planting-material quantity by orchard block and establishment year; retain count-to-mass conversion when used

• Value mode: Foreground record (foreground_record)

• Specificity: Site-specific (site_specific) Raw activity or stage basis: per orchard-year and converted to 1,000 kg accepted fruit.

• Normalization basis: per declared reference flow

• Basis kind: Crop cycle (crop_cycle)

• Evidence kind: Collected record (collected_record)

• Collection protocol: cp_orchard_establishment_records

• Sources:

• Range: Provisional establishment-planting screen

  • Range role: QA guardrail (qa_guardrail)
  • Lower: 100
  • Upper: 400
  • Unit: trees/ha
  • Basis: established orchard blocks; replace with nursery and planting records
  • Basis kind: Crop cycle (crop_cycle)
  • Evidence kind: Reasoned estimate (reasoned_estimate)

Urea fertilizer (avocado_orchard_establishment_and_management_agricultural_nutrient_inputs_urea)

Collection scope and applicability for avocado_orchard_establishment_and_management_agricultural_nutrient_inputs. The following concrete identities have separate cards and apply only when use or generation is evidenced inside the original process scope. They are not mandatory inputs or a default recipe. Document non-use; missing records are not zero. Add a separate concrete card for any other actual material instead of substituting one of these names or UUIDs. Preserve attribution and boundaries and avoid double counting components included in outsourced services.

Collect each fertilizer product separately. Preserve each actual product identity, quantity, formulation, nutrient composition, application event, and allocation; do not count a compound product more than once. Raw activity or stage basis: per orchard-year and converted to 1,000 kg accepted fruit.

Confirm identity, grade, state and unit from equipment, supplier and contemporaneous measurements; the product UUID does not establish actual use or upstream-provider compatibility. Count physical product mass once and retain moisture, N/P/K composition and application events; nutrient quantities are calculated attributes, not additional purchases of the same product. Give unlisted compound and organic fertilizers separate cards identified by formulation or feedstock.

• Selected flow: Urea 3f8850c0-f718-4c4b-8fcb-8fd42e03aa8e
• Flow property / unit: Mass / kg
• Amount rule: Collect raw quantities for this identity under cp_orchard_management_records and calculate the exchange per declared reference flow using the original attribution rules.
• Value mode: Foreground record (foreground_record)
• Specificity: Site-specific (site_specific)
• Normalization basis: per declared reference flow
• Basis kind: Reference flow (reference_flow)
• Evidence kind: Collected record (collected_record)
• Collection protocol: cp_orchard_management_records
• Sources: fao-fertilizer-identities

Use this product identity only when the actual formulation and grade are compatible. Retain supplier composition and mass records; do not substitute nutrient mass, dilute solution mass or service activity for the product mass. The UUID alone supplies neither a dose nor an emission factor.

Ammonium sulfate fertilizer (avocado_orchard_establishment_and_management_agricultural_nutrient_inputs_ammonium_sulfate)

Confirm identity, grade, state and unit from equipment, supplier and contemporaneous measurements; the product UUID does not establish actual use or upstream-provider compatibility. Count physical product mass once and retain moisture, N/P/K composition and application events; nutrient quantities are calculated attributes, not additional purchases of the same product. Give unlisted compound and organic fertilizers separate cards identified by formulation or feedstock.

• Selected flow: Ammonium sulfate 8c6f0cbb-16d7-4dc9-8d55-e8dea17d7faf
• Flow property / unit: Mass / kg
• Amount rule: Collect raw quantities for this identity under cp_orchard_management_records and calculate the exchange per declared reference flow using the original attribution rules.
• Value mode: Foreground record (foreground_record)
• Specificity: Site-specific (site_specific)
• Normalization basis: per declared reference flow
• Basis kind: Reference flow (reference_flow)
• Evidence kind: Collected record (collected_record)
• Collection protocol: cp_orchard_management_records
• Sources: fao-fertilizer-identities

Use this product identity only when the actual formulation and grade are compatible. Retain supplier composition and mass records; do not substitute nutrient mass, dilute solution mass or service activity for the product mass. The UUID alone supplies neither a dose nor an emission factor.

Triple superphosphate fertilizer (avocado_orchard_establishment_and_management_agricultural_nutrient_inputs_triple_superphosphate)

Confirm identity, grade, state and unit from equipment, supplier and contemporaneous measurements; the UUID remains unverified. Count physical product mass once and retain moisture, N/P/K composition and application events; nutrient quantities are calculated attributes, not additional purchases of the same product. Give unlisted compound and organic fertilizers separate cards identified by formulation or feedstock.

• Selected flow: Triple superphosphate fertilizer
• Flow property / unit: Mass / kg
• Amount rule: Collect raw quantities for this identity under cp_orchard_management_records and calculate the exchange per declared reference flow using the original attribution rules.
• Value mode: Foreground record (foreground_record)
• Specificity: Site-specific (site_specific)
• Normalization basis: per declared reference flow
• Basis kind: Reference flow (reference_flow)
• Evidence kind: Collected record (collected_record)
• Collection protocol: cp_orchard_management_records
• Sources: fao-fertilizer-identities

Potassium chloride fertilizer (avocado_orchard_establishment_and_management_agricultural_nutrient_inputs_potassium_chloride)

Confirm identity, grade, state and unit from equipment, supplier and contemporaneous measurements; the UUID remains unverified. Count physical product mass once and retain moisture, N/P/K composition and application events; nutrient quantities are calculated attributes, not additional purchases of the same product. Give unlisted compound and organic fertilizers separate cards identified by formulation or feedstock.

• Selected flow: Potassium chloride fertilizer
• Flow property / unit: Mass / kg
• Amount rule: Collect raw quantities for this identity under cp_orchard_management_records and calculate the exchange per declared reference flow using the original attribution rules.
• Value mode: Foreground record (foreground_record)
• Specificity: Site-specific (site_specific)
• Normalization basis: per declared reference flow
• Basis kind: Reference flow (reference_flow)
• Evidence kind: Collected record (collected_record)
• Collection protocol: cp_orchard_management_records
• Sources: fao-fertilizer-identities

Cattle manure applied as fertilizer (avocado_orchard_establishment_and_management_agricultural_nutrient_inputs_cattle_manure)

Confirm identity, grade, state and unit from equipment, supplier and contemporaneous measurements; the UUID remains unverified. Count physical product mass once and retain moisture, N/P/K composition and application events; nutrient quantities are calculated attributes, not additional purchases of the same product. Give unlisted compound and organic fertilizers separate cards identified by formulation or feedstock.

• Selected flow: Cattle manure applied as fertilizer
• Flow property / unit: Mass / kg
• Amount rule: Collect raw quantities for this identity under cp_orchard_management_records and calculate the exchange per declared reference flow using the original attribution rules.
• Value mode: Foreground record (foreground_record)
• Specificity: Site-specific (site_specific)
• Normalization basis: per declared reference flow
• Basis kind: Reference flow (reference_flow)
• Evidence kind: Collected record (collected_record)
• Collection protocol: cp_orchard_management_records
• Sources: fao-organic-nutrients

Composted plant residues applied to soil (avocado_orchard_establishment_and_management_agricultural_nutrient_inputs_plant_compost)

Confirm identity, grade, state and unit from equipment, supplier and contemporaneous measurements; the UUID remains unverified. Count physical product mass once and retain moisture, N/P/K composition and application events; nutrient quantities are calculated attributes, not additional purchases of the same product. Give unlisted compound and organic fertilizers separate cards identified by formulation or feedstock.

• Selected flow: Composted plant residues applied to soil
• Flow property / unit: Mass / kg
• Amount rule: Collect raw quantities for this identity under cp_orchard_management_records and calculate the exchange per declared reference flow using the original attribution rules.
• Value mode: Foreground record (foreground_record)
• Specificity: Site-specific (site_specific)
• Normalization basis: per declared reference flow
• Basis kind: Reference flow (reference_flow)
• Evidence kind: Collected record (collected_record)
• Collection protocol: cp_orchard_management_records
• Sources: fao-organic-nutrients

Irrigation water supplied (irrigation_water_input)

Record irrigation only when water is applied to the orchard. Rainfed production records zero applied irrigation with a documented water-balance or farm-management basis.

• Selected flow: Irrigation water supply

• Flow property / unit: Volume / m3

• Amount rule: metered or calculated irrigation volume by orchard block and production year

• Value mode: Foreground record (foreground_record)

• Specificity: Site-specific (site_specific) Raw activity or stage basis: per orchard-year and converted to 1,000 kg accepted fruit.

• Normalization basis: per declared reference flow

• Basis kind: Crop cycle (crop_cycle)

• Evidence kind: Collected record (collected_record)

• Collection protocol: cp_orchard_management_records

• Sources:

• Range: Provisional orchard irrigation screen

  • Range role: QA guardrail (qa_guardrail)
  • Lower: 0
  • Upper: 12,000
  • Unit: m3/ha/year
  • Basis: one production year; replace with metered records or a local water balance
  • Basis kind: Crop cycle (crop_cycle)
  • Evidence kind: Reasoned estimate (reasoned_estimate)

Electricity at the equipment supply point (orchard_energy_input_electricity)

Collection scope and applicability for orchard_energy_input. The following concrete identities have separate cards and apply only when use or generation is evidenced inside the original process scope. They are not mandatory inputs or a default recipe. Document non-use; missing records are not zero. Add a separate concrete card for any other actual material instead of substituting one of these names or UUIDs. Preserve attribution and boundaries and avoid double counting components included in outsourced services.

Record electricity, diesel, gasoline, or other purchased energy used for pumping, orchard operations, and contracted machinery when the service is not already represented by an upstream process. Raw activity or stage basis: per orchard-year and converted to 1,000 kg accepted fruit.

Confirm identity, grade, state and unit from equipment, supplier and contemporaneous measurements; the product UUID does not establish actual use or upstream-provider compatibility. Retain the electricity supply point, fuel grade, density and heating-value basis. Distinguish purchased heat from on-site fuel conversion without counting its input fuel again.

• Selected flow: Alternating current 455f0ef5-6118-4f2b-a3f5-1f75e0afe3ca
• Flow property / unit: Energy / kWh
• Amount rule: Collect raw quantities for this identity under cp_orchard_management_records and calculate the exchange per declared reference flow using the original attribution rules.
• Value mode: Foreground record (foreground_record)
• Specificity: Site-specific (site_specific)
• Normalization basis: per declared reference flow
• Basis kind: Reference flow (reference_flow)
• Evidence kind: Collected record (collected_record)
• Collection protocol: cp_orchard_management_records
• Sources: fao-agricultural-energy

This binding is alternating current at the use point with supply technology, voltage and provider unspecified. Confirm actual AC supply; DC requires a different identity. The database reference is 1 MJ: preserve meter kWh and convert once using 1 kWh = 3.6 MJ when linking reference quantities. Internal generation links to its foreground generator, without an additional purchased-electricity burden.

Diesel fuel supplied to equipment (orchard_energy_input_diesel)

Confirm identity, grade, state and unit from equipment, supplier and contemporaneous measurements; the product UUID does not establish actual use or upstream-provider compatibility. Retain the electricity supply point, fuel grade, density and heating-value basis. Distinguish purchased heat from on-site fuel conversion without counting its input fuel again.

• Selected flow: Diesel fuel 9d258d75-6792-4f1c-9856-81602ed8f816
• Flow property / unit: Mass / kg
• Amount rule: Collect raw quantities for this identity under cp_orchard_management_records and calculate the exchange per declared reference flow using the original attribution rules.
• Value mode: Foreground record (foreground_record)
• Specificity: Site-specific (site_specific)
• Normalization basis: per declared reference flow
• Basis kind: Reference flow (reference_flow)
• Evidence kind: Collected record (collected_record)
• Collection protocol: cp_orchard_management_records
• Sources: fao-agricultural-energy

Gasoline supplied to equipment (orchard_energy_input_gasoline)

Confirm identity, grade, state and unit from equipment, supplier and contemporaneous measurements; the UUID remains unverified. Retain the electricity supply point, fuel grade, density and heating-value basis. Distinguish purchased heat from on-site fuel conversion without counting its input fuel again.

• Selected flow: Gasoline supplied to equipment
• Flow property / unit: Mass / kg
• Amount rule: Collect raw quantities for this identity under cp_orchard_management_records and calculate the exchange per declared reference flow using the original attribution rules.
• Value mode: Foreground record (foreground_record)
• Specificity: Site-specific (site_specific)
• Normalization basis: per declared reference flow
• Basis kind: Reference flow (reference_flow)
• Evidence kind: Collected record (collected_record)
• Collection protocol: cp_orchard_management_records
• Sources: fao-forest-equipment

Waste flows

Elementary flows

Land occupation by avocado orchard (orchard_land_occupation)

Record orchard area and occupation duration, including non-bearing establishment years when they are part of the declared orchard life.

• Selected flow: Land occupation, orchard area

• Flow property / unit: Area-time / m2a or hayear

• Amount rule: orchard area multiplied by declared occupation time, allocated to accepted fruit output

• Value mode: Calculated value (calculated_value)

• Specificity: Site-specific (site_specific) Raw activity or stage basis: per orchard-year and converted to 1,000 kg accepted fruit.

• Normalization basis: per declared reference flow

• Basis kind: Crop cycle (crop_cycle)

• Evidence kind: Calculated from collection (calculated_from_collection)

• Collection protocol: cp_orchard_establishment_records

• Sources: fao-gap-framework-2003

Outputs

Product flows

Orchard management output to harvest (orchard_managed_production_output)

Pass the managed orchard-year production basis to the harvest process as an internal process link. It must not be counted as an additional marketable avocado flow.

• Selected flow: Managed avocado orchard production output

• Flow property / unit: Area or mass / ha or kg accepted fruit basis

• Amount rule: declared orchard-year area and associated accepted fruit output basis

• Value mode: Calculated value (calculated_value)

• Specificity: Site-specific (site_specific) Raw activity or stage basis: per 1,000 kg accepted fruit.

• Normalization basis: per declared reference flow

• Basis kind: Reference flow (reference_flow)

• Evidence kind: Calculated from collection (calculated_from_collection)

• Collection protocol: cp_orchard_management_records

• Sources:

Waste flows

Replaced or dead orchard trees sent to waste (orchard_tree_replacement_waste)

Record trees removed during establishment or productive replacement as waste when they do not become a declared co-product. Trees retained as mulch or biomass transfer require a destination and allocation treatment.

• Selected flow: Removed avocado orchard trees to waste treatment or unmanaged residue

• Flow property / unit: Mass / kg dry or as-received biomass

• Amount rule: measured or calculated removed-tree biomass by orchard block and year

• Value mode: Calculated value (calculated_value)

• Specificity: Site-specific (site_specific) Raw activity or stage basis: per orchard-year and converted to 1,000 kg accepted fruit.

• Normalization basis: per declared reference flow

• Basis kind: Crop cycle (crop_cycle)

• Evidence kind: Calculated from collection (calculated_from_collection)

• Collection protocol: cp_orchard_establishment_records

• Sources:

Elementary flows

Process: Avocado harvest and farm-gate handling (avocado_harvest_and_farm_gate_handling)

Inputs

Product flows

Managed orchard output entering harvest (managed_orchard_output_input)

Receive the managed orchard-year production context from orchard management. This row supports process linkage and must not duplicate the upstream orchard inventory.

• Selected flow: Managed avocado orchard production output

• Flow property / unit: Area or mass / ha or kg accepted fruit basis

• Amount rule: linked orchard-year harvested volume before grading or conditioning

• Value mode: Calculated value (calculated_value)

• Specificity: Site-specific (site_specific) Raw activity or stage basis: per 1,000 kg accepted fruit.

• Normalization basis: per declared reference flow

• Basis kind: Reference flow (reference_flow)

• Evidence kind: Calculated from collection (calculated_from_collection)

• Collection protocol: cp_harvest_output_records

• Sources:

Waste flows

Elementary flows

Outputs

Product flows

Harvested avocado fruit at farm gate (harvested_avocado_output)

Record fruit transferred at the declared farm-gate condition. This is the terminal reference output when conditioning is absent.

• Selected flow: Fresh avocado fruit, production mix, at farm gate, unprocessed

• Flow property / unit: Mass / kg Raw output measurement and reconciliation: measured accepted fruit mass at the declared hand-off condition

• Amount rule: measured net transfer mass, retaining lot, actual product state and moisture basis; reconcile to the final reference output at the declared handoff

• Value mode: Foreground record (foreground_record)

• Specificity: Site-specific (site_specific) Raw activity or stage basis: terminal output scaled to 1,000 kg reference fruit.

• Normalization basis: per declared reference flow

• Basis kind: Reference flow (reference_flow)

• Evidence kind: Collected record (collected_record)

• Collection protocol: cp_harvest_output_records

• Sources:

• Range: Provisional accepted avocado-yield screen

  • Range role: QA guardrail (qa_guardrail)
  • Lower: 2,000
  • Upper: 25,000
  • Unit: kg accepted fruit/ha/year
  • Basis: productive orchard-year; replace with orchard records and regional evidence
  • Basis kind: Crop cycle (crop_cycle)
  • Evidence kind: Reasoned estimate (reasoned_estimate)

Waste flows

Harvested fruit rejected or lost before hand-off (harvest_reject_and_loss_waste)

Record fruit left in the field, damaged during picking, downgraded without a declared co-product use, or otherwise rejected before hand-off. Fruit sent to a named destination is recorded separately as a co-product where justified.

• Selected flow: Avocado harvest reject or loss to waste

• Flow property / unit: Mass / kg

• Amount rule: measured or reconciled difference between harvested, accepted, and declared destination masses

• Value mode: Calculated value (calculated_value)

• Specificity: Site-specific (site_specific) Raw activity or stage basis: per 1,000 kg accepted fruit.

• Normalization basis: per declared reference flow

• Basis kind: Process output (process_output)

• Evidence kind: Calculated from collection (calculated_from_collection)

• Collection protocol: cp_harvest_output_records

• Sources:

Elementary flows

Process: Farm-gate avocado conditioning (farm_gate_avocado_conditioning)

Inputs

Product flows

Harvested fruit entering conditioning (conditioning_avocado_input)

Record harvested fruit entering a separate on-farm washing, sorting, grading, or handling step when that activity occurs before hand-off.

• Selected flow: Fresh avocado fruit entering farm-gate conditioning

• Flow property / unit: Mass / kg

• Amount rule: measured incoming fruit mass before conditioning

• Value mode: Foreground record (foreground_record)

• Specificity: Site-specific (site_specific) Raw activity or stage basis: per 1,000 kg accepted conditioned fruit.

• Normalization basis: per declared reference flow

• Basis kind: Process output (process_output)

• Evidence kind: Collected record (collected_record)

• Collection protocol: cp_conditioning_records

• Sources:

Waste flows

Elementary flows

Outputs

Product flows

Conditioned avocado fruit at farm gate (conditioned_avocado_output)

Record accepted conditioned fruit as the terminal reference output when conditioning is included in the declared boundary.

• Selected flow: Fresh avocado fruit, conditioned at farm gate, unprocessed

• Flow property / unit: Mass / kg Raw output measurement and reconciliation: measured accepted fruit mass after conditioning and before off-farm transport

• Amount rule: measured net transfer mass, retaining lot, actual product state and moisture basis; reconcile to the final reference output at the declared handoff

• Value mode: Foreground record (foreground_record)

• Specificity: Site-specific (site_specific) Raw activity or stage basis: terminal output scaled to 1,000 kg reference fruit.

• Normalization basis: per declared reference flow

• Basis kind: Reference flow (reference_flow)

• Evidence kind: Collected record (collected_record)

• Collection protocol: cp_conditioning_records

• Sources:

Waste flows

Conditioning rejects and removed material (conditioning_reject_waste)

Record fruit and material removed by washing, sorting, grading, or trimming when it is not transferred to a declared co-product destination.

• Selected flow: Conditioning rejects and removed material to waste

• Flow property / unit: Mass / kg

• Amount rule: measured or reconciled incoming mass minus accepted output and named destinations

• Value mode: Calculated value (calculated_value)

• Specificity: Site-specific (site_specific) Raw activity or stage basis: per 1,000 kg accepted conditioned fruit.

• Normalization basis: per declared reference flow

• Basis kind: Process output (process_output)

• Evidence kind: Calculated from collection (calculated_from_collection)

• Collection protocol: cp_conditioning_records

• Sources:

Elementary flows

Process: Product Measurement at the Declared Handoff (declared_reference_handoff)

This node records the actual product handoff at the existing system boundary for reconciliation and reference-quantity normalization. It adds no physical processing and does not presume drying, cooling, storage, packaging or transport. Each data package declares one actual route, one terminal product state, moisture or dry-matter basis, and gate. Feed only the accepted product delivered by that route at that gate into this node; do not add other routes as extra inputs. Record co-products separately and apply Section 7. Count preceding inputs, losses and emissions once. Normalize using the measured accepted net mass at the handoff; this measurement node changes neither mass, yield nor allocation.

Inputs

Product flows

Actual route product at handoff (actual_route_product_for_handoff)

Record the accepted product delivered by the actual terminal route and reconcile it with handoff weighing and lot records.

• Selected flow: Fresh avocado fruit, production mix, at farm gate, unprocessed
• Flow property / unit: Mass / kg
• Amount rule: measured accepted net product mass at the actual handoff, normalized to the reference quantity; do not sum preceding-stage quantities, other routes or co-products
• Value mode: Foreground record (foreground_record)
• Specificity: Site-specific (site_specific)
• Normalization basis: per declared reference flow
• Basis kind: Process output (process_output)
• Evidence kind: Collected record (collected_record)
• Collection protocol: cp_declared_reference_handoff
• Range: Handoff quantity normalization identity
  • Range role: QA guardrail (qa_guardrail)
  • Lower: 1
  • Upper: 1
  • Unit: kg/kg net handoff mass of the same state
  • Basis: normalization of the measured net mass of the same handoff state; not a physical-operation yield
  • Basis kind: Process output (process_output)
  • Evidence kind: Method formula (method_formula)
  • Sources: declared-handoff-measurement-definition

Waste flows

This measurement node adds no waste inputs.

Elementary flows

This measurement node adds no resource inputs.

Outputs

Product flows

Reference product at declared handoff (reference_product_at_declared_handoff)

• Selected flow: Fresh avocado fruit, production mix, at farm gate, unprocessed
• Flow property / unit: Mass / kg
• Amount rule: 1000 kg
• Value mode: Foreground record (foreground_record)
• Specificity: Site-specific (site_specific)
• Normalization basis: per declared reference flow
• Basis kind: Process output (process_output)
• Evidence kind: Collected record (collected_record)
• Collection protocol: cp_declared_reference_handoff Confirm the product UUID independently for the actual state. Until confirmed, retain unresolved identity instead of inheriting a UUID from a preceding stage or another route.
• Range: Handoff quantity normalization identity
  • Range role: QA guardrail (qa_guardrail)
  • Lower: 1
  • Upper: 1
  • Unit: kg/kg net handoff mass of the same state
  • Basis: normalization of the measured net mass of the same handoff state; not a physical-operation yield
  • Basis kind: Process output (process_output)
  • Evidence kind: Method formula (method_formula)
  • Sources: declared-handoff-measurement-definition

Waste flows

Record actual losses at the operation where they occur; do not duplicate them here.

Elementary flows

Record actual emissions at the operation where they occur; do not duplicate them here.

7. Allocation and Co-product Handling

rule_id	Applies to	Rule	source_ids
allocation_orchard_establishment_over_productive_life	orchard establishment, immature years, and replacement trees	Allocate establishment and non-bearing orchard inputs over the declared productive orchard life using orchard area and accepted fruit output. Report orchard life, establishment years, replacement events, and allocation basis.	fao-gap-framework-2003; iso-14067
allocation_accepted_and_named_destinations	accepted fruit, downgraded fruit, and residues	Assign mass to accepted avocado and a named co-product only when the destination is evidenced and physically or economically distinguishable. Do not treat unmarketable losses as a co-product without a declared use.	iso-14044
allocation_no_double_counting_internal_links	process links between orchard, harvest, and conditioning	Use internal process links for mass balance only; do not count the same orchard output or fruit mass as an additional market product.	iso-14044
allocation_mass_default_for_shared_fruit_output	multiple avocado grades or destinations	Use mass allocation for shared production when no stronger causal partition is documented, and disclose grade definitions, moisture or dry-matter basis, and rejected-fruit treatment.	iso-14044

If a study reports avocado fruit and a documented co-product from the same orchard or conditioning operation, the data package shall state the partitioning rule, common process inventory, and destination evidence. Economic allocation is not a default substitute for missing mass or causal data.

Concrete cards do not inherit numerical ranges from the former aggregate card. Determine quantities from original records, stock/meter reconciliation and the declared reference flow; no default quantity or numeric screen is supplied without evidence matching the identity, unit, period and boundary. Missing range evidence is a quality disclosure, not zero use or proof of completeness.

8. Foreground Data Collection, Calculation, and Quality Rules

Specific input identification before dataset completion

Identify the actual input for this operation from supplier specifications, equipment and primary records. This is a mandatory collection requirement, not an exchange. Before dataset completeness, represent each used material, formulated product, carrier or independently purchased service by one physically specific card with its native quantity/property; confirm a compatible UUID, or retain an explicit unresolved identity and do not claim a fully linked dataset. Do not substitute a conditional example for an unknown actual input, invent a recipe, omit required use or infer zero from missing records. Attribute shared use, reusable assets and inclusive services once; preserve the original stage/period and measured throughput link to final reference output. The former aggregate range is not a component limit or consumption default.

requirement_id	collection_protocol_id	Preserved collection scope
crop_protection_input_specific_input	cp_orchard_management_records	Operation avocado_orchard_establishment_and_management: Record each pesticide or other crop-protection formulation by product, active ingredient, application event, and treated area. Distinct formulations must remain identifiable. Original quantity method: sum measured formulation mass by product and application event
conditioning_inputs_specific_input	cp_conditioning_records	Operation farm_gate_avocado_conditioning: Record water, electricity, cleaning agents, and packaging aids used before hand-off. Packaging that remains with the product must disclose its material and mass; internal handling packaging is recorded when it crosses the boundary. Original quantity method: meter, invoice, batch log, or measured packaging mass assigned to accepted conditioned fruit

Route-specific energy identification requirements

Select energy exchanges from the actual product state, operation, equipment and supply records. The conditional cards below are not a mandatory or exhaustive fuel list. For each requirement, document applicability and the used carrier, supplier, service period, native quantity and allocation; add a separate physically specific card and verify its UUID for any actual input not yet represented. An unidentified input remains an explicit completeness gap, never a zero or a generic energy exchange. Evidence of manual work, ambient drying or a bypass can justify non-use only for the affected operation. Preserve every required operation even when no example card is supplied.

Separate purchased supply from on-site conversion. Link self-generated electricity internally to the foreground generator and count its actual fuel and emissions there once; do not also charge a purchased-electricity supply for the same internal transfer. Likewise do not count supplier-side fuel again with purchased heat. Reconcile shared meters and contractor-included energy against existing cards, with one physical quantity assigned once. Retain source quantities, output throughput, shared-service allocation and excluded post-gate activities. For each carrier, apply period/output attribution once and scale to the declared reference quantity using matched accepted final output in the same product unit; do not normalize an already normalized amount again. Process-native intensities require a measured throughput link to that final output. These requirements do not set a consumption default or certify dataset completeness.

requirement_id	collection_protocol_id	Required operation and evidence
harvest_energy_input_identification	cp_harvest_output_records	Picking, collection, field bins and pre-gate handling: determine manual work, powered equipment and contractor coverage first. Reuse existing carrier cards within their documented scope; additional harvest use must be separately attributed, not counted twice. Raw activity or stage basis: per harvest campaign and converted to 1,000 kg accepted fruit. (route-energy-fao)

Retain raw site, lot, cycle and stage quantities and denominators in each collection protocol. Reconcile stocks, losses, moisture and co-product attribution first, then normalize: normalized exchange = attributable raw exchange × declared reference quantity / accepted hand-off product quantity on the same boundary and measurement basis. Apply perennial-establishment and shared-operation attribution before this normalization. Never set an internal-transfer quantity equal to the final reference quantity. Per declared reference flow means the amount, unit and product state in section 3; the data package must declare its actual route and gate.

Data Collection Protocols

protocol_id	process_id	flow_role	record_type	raw_fields	collection_method	unit	frequency	temporal_coverage	site_scope	aggregation_rule	quality_evidence
cp_orchard_establishment_records	avocado_orchard_establishment_and_management	planting material; replacement trees; land occupation	orchard register, nursery invoice, planting map, removal log	block_id; cultivar; tree count; planting year; replacement count; area; previous land use; removed biomass; destination	reconcile orchard register, maps, invoices, and field records; Raw aggregation and attribution: aggregate by block, establishment year, and declared allocation horizon	trees, ha, kg, orchard-year	establishment and each replacement event; annual update	full establishment period and declared productive life	each orchard block	per declared reference flow	signed farm register, planting map, supplier record, or auditable field log
cp_orchard_management_records	avocado_orchard_establishment_and_management	nutrients; irrigation; energy; crop protection; emissions	input ledger, water meter, energy meter, spray record, contractor invoice	block_id; product; formulation; nutrient analysis; amount; date; area; water volume; energy carrier; fuel; treatment; soil or residue event	collect primary records and reconcile invoices, meters, and application logs; Raw aggregation and attribution: sum by block and year, then allocate shared inputs by documented area or activity crop_protection_input_specific_input: Operation avocado_orchard_establishment_and_management: Record each pesticide or other crop-protection formulation by product, active ingredient, application event, and treated area. Distinct formulations must remain identifiable. Original quantity method: sum measured formulation mass by product and application event Identify the actual input for this operation from supplier specifications, equipment and primary records. This is a mandatory collection requirement, not an exchange. Before dataset completeness, represent each used material, formulated product, carrier or independently purchased service by one physically specific card with its native quantity/property; confirm a compatible UUID, or retain an explicit unresolved identity and do not claim a fully linked dataset. Do not substitute a conditional example for an unknown actual input, invent a recipe, omit required use or infer zero from missing records. Attribute shared use, reusable assets and inclusive services once; preserve the original stage/period and measured throughput link to final reference output. The former aggregate range is not a component limit or consumption default. orchard_emissions_specific_emission: Calculate relevant emissions from collected nutrient, crop-protection, residue, and irrigation activity data using the selected geographically applicable method. Do not infer a specific elementary-flow identity until final flow binding is reviewed. calculate emissions using collected activity data and the declared method; keep each substance and receiving compartment distinct where supported This is a mandatory emission-identification requirement, not an aggregate elementary exchange. Identify every applicable substance and actual receiving compartment separately, with compatible units, measured activity or justified calculation method, parameter applicability and uncertainty. Preserve the original operation, period, allocation and final-reference normalization. Reconcile direct and indirect pathways and upstream coverage once; do not substitute total nitrogen, total combustion emissions or a generic pollutant for a named compound. Separately document actual environmental returns, with their material and destination, if relevant. Before dataset completeness create each required specific exchange, confirm a compatible UUID or explicitly retain its unresolved identity. Missing records do not establish zero or inapplicability. ipcc-2019-refinement; emep-eea-2023-guidebook	kg product, kg nutrient, m3, kWh, L, ha	each application or operation; annual aggregation	one production year plus establishment records where applicable	each orchard block and shared facility	per declared reference flow	invoices, meter readings, product labels, application logs, method calculation record
cp_harvest_output_records	avocado_harvest_and_farm_gate_handling	orchard output; harvest energy; accepted fruit; rejects and losses	harvest tickets, weighbridge record, bin log, contractor record, grading log	block_id; harvest date; cultivar; harvested mass; accepted mass; rejected mass; destination; carrier use; contractor activity; maturity or grade	reconcile field, bin, scale, grading, and destination records; Raw aggregation and attribution: aggregate by block, lot, and destination; retain mass balance Route-specific requirements: harvest_energy_input_identification: Picking, collection, field bins and pre-gate handling: determine manual work, powered equipment and contractor coverage first. Reuse existing carrier cards within their documented scope; additional harvest use must be separately attributed, not counted twice. Raw activity or stage basis: per harvest campaign and converted to 1,000 kg accepted fruit. (route-energy-fao) Verify actual use, equipment and supply for each applicable input; create one specific exchange per actual carrier before dataset completeness. Missing identity or quantity evidence remains unresolved, never zero. Distinguish purchased supply, internal generation and inclusive contractor services; count their energy once. Do not substitute the conditional examples for an unverified route.	kg, L, kWh, activity unit	each harvest lot; annual closure	one production year	each orchard block and harvest facility	per declared reference flow	weighbridge or scale record, lot traceability, grading report, contractor invoice
cp_conditioning_records	farm_gate_avocado_conditioning	incoming fruit; water; energy; packaging; accepted output; rejects	batch sheet, meter record, packaging ledger, waste log	batch_id; incoming mass; accepted mass; reject mass; water; electricity; cleaning agent; packaging material and mass; destination	batch reconciliation with meter and material records; Raw aggregation and attribution: reconcile inputs, accepted output, rejects, and named destinations by batch conditioning_inputs_specific_input: Operation farm_gate_avocado_conditioning: Record water, electricity, cleaning agents, and packaging aids used before hand-off. Packaging that remains with the product must disclose its material and mass; internal handling packaging is recorded when it crosses the boundary. Original quantity method: meter, invoice, batch log, or measured packaging mass assigned to accepted conditioned fruit Identify the actual input for this operation from supplier specifications, equipment and primary records. This is a mandatory collection requirement, not an exchange. Before dataset completeness, represent each used material, formulated product, carrier or independently purchased service by one physically specific card with its native quantity/property; confirm a compatible UUID, or retain an explicit unresolved identity and do not claim a fully linked dataset. Do not substitute a conditional example for an unknown actual input, invent a recipe, omit required use or infer zero from missing records. Attribute shared use, reusable assets and inclusive services once; preserve the original stage/period and measured throughput link to final reference output. The former aggregate range is not a component limit or consumption default.	kg, m3, kWh, kg packaging	each conditioning batch	declared production year	farm conditioning site	per declared reference flow	batch sheet, scale record, meter reading, packaging invoice, waste receipt
cp_declared_reference_handoff	declared_reference_handoff	reference_product_at_declared_handoff	handoff weighing and acceptance records	route, terminal_output_row_id, product_state, gate, lot, net_mass_kg, moisture_basis, acceptance, tare	Use calibrated scales or traceable weighing records; reconcile the actual terminal-operation handoff lot, accepted net mass, product state and moisture; exclude packaging tare and do not sum preceding-stage quantities.	kg	each handoff lot	declared reporting period	declared handoff gate	per declared reference flow	calibration or weighing tickets, acceptance and lot traceability

Calculation Rules

rule_id	Applies to	Formula or rule	Inputs	Output	source_ids
calc_area_to_reference_mass	all orchard-year flows	normalized amount = orchard-year activity total / accepted farm-gate fruit mass × 1,000 kg	activity total; accepted fruit mass; reference amount	amount per 1,000 kg accepted fruit
calc_orchard_life_allocation	establishment and replacement inputs	allocate establishment or replacement total to each declared production year using the documented productive-life horizon and accepted fruit output basis; retain non-bearing years in the denominator when specified	establishment total; replacement events; orchard life; annual accepted output	allocated orchard input per production year and reference flow	fao-gap-framework-2003; iso-14067
calc_nutrient_basis	nutrient and amendment input	nutrient mass = product mass × declared nutrient fraction; report product mass and nutrient mass separately	product quantity; label or supplier nutrient analysis	kg product and kg N, kg P2O5, or kg K2O	fao-gap-framework-2003
calc_mass_balance_harvest	harvest output and rejects	harvested mass = accepted fruit + named co-products + rejects/losses, with documented stock change and measurement basis	harvest tickets; accepted mass; co-product destinations; reject and loss mass; stock change	reconciled harvest balance
calc_conditioning_balance	conditioning output and waste	incoming fruit + conditioning inputs crossing as product or material = accepted conditioned fruit + named destinations + waste, after documenting moisture or handling adjustments	batch inputs; accepted output; destinations; waste; adjustment basis	reconciled batch balance
calc_direct_field_emissions	soil, residue, and crop-protection emissions	apply the selected geographically applicable method to collected nutrient, residue, and activity data; do not apply a generic factor without recording tier, geography, and activity basis	nutrient inputs; residue fate; soil or climate context; method parameters	substance-specific elementary flows by compartment	ipcc-2019-refinement; emep-eea-2023-guidebook

Data Quality Requirements

requirement_id	Applies to	Requirement	Evidence
dq_orchard_identity	all processes	Identify orchard block, cultivar or cultivar group, country and region, crop year, orchard age, productive status, and conditioning boundary.	orchard register; farm map; dataset metadata
dq_perennial_time_basis	establishment and management	State establishment year, non-bearing period, productive-life horizon, replacement events, and allocation basis used for orchard assets.	orchard history; allocation worksheet
dq_input_traceability	nutrients, irrigation, energy, crop protection, and planting material	Trace each material or energy input to an invoice, meter, product label, contractor record, or justified field record; retain product and nutrient identities separately.	primary farm records; supplier records
dq_mass_balance	harvest and conditioning	Reconcile harvested, accepted, rejected, co-product, stock-change, and waste masses within a documented tolerance and explain moisture or grading adjustments.	weighbridge, lot, grading, batch, and destination records
dq_temporal_coverage	all processes	Cover the full declared production year and include establishment or replacement records needed by orchard-life allocation.	annual production ledger; orchard history
dq_emission_method	elementary flows	Record method name, tier, geography, activity data, and assumptions for each calculated emission; keep evidence gap flow identity separate from amount evidence.	calculation worksheet; method reference

9. Validation Rules

rule_id	Applies to	Rule	source_ids
validation_reference_output	reference flow and terminal process	Exactly one terminal accepted avocado output shall be linked to the declared reference flow, with no fixed identity assumed until verified; the binding remains parameterized in this candidate.
validation_orchard_life_disclosure	orchard establishment and management	Reject or flag a dataset that includes perennial orchard production but omits orchard age, establishment period, productive-life horizon, replacement events, or allocation basis.	fao-gap-framework-2003; iso-14067
validation_irrigation_and_nutrients	irrigation and nutrient inputs	Check that zero irrigation or zero nutrient input is supported by farm records or documented production rationale, and that product mass is not confused with nutrient mass.	fao-gap-framework-2003
validation_mass_balance	harvest and conditioning	Check mass balance for each harvest or conditioning boundary and require explanation for evidence gap differences, reject destinations, stock changes, or moisture conversions.
validation_boundary_exclusions	downstream activities	Reject unreported inclusion of off-farm transport, storage, processing into oil or purée, retail, consumer use, or packaging end-of-life unless the study declares a boundary extension.
validation_bilingual_alignment	English and Chinese renderings	Require identical machine identifiers, controlled tokens, process ids, row ids, rule ids, protocol ids, requirement ids, and source ids in both language files.

10. Published Dataset Profile

Field	Value
dataset_role	secondary_dataset for a reviewed farm-gate avocado production dataset; background_dataset only when compatible upstream inputs and elementary flows are explicitly published
downstream_use	foreground data package construction, process projection, lifecycle model aggregation, and comparison of fresh avocado supply scenarios
allowed_use	fresh, unprocessed avocado fruit at a declared farm gate and conditioning state, with orchard-life allocation and quality metadata preserved
excluded_use	direct substitution for avocado oil, pulp, purée, frozen or dried products; direct use without regional, orchard-age, irrigation, cultivar, or market-state review; downstream logistics or consumer studies outside the declared boundary
required_metadata	canonical PCR id; CPC reference; orchard block or aggregation scope; cultivar; geography; crop year; orchard age; productive-life and allocation basis; irrigation; nutrient and crop-protection product basis; yield; accepted and rejected fruit; conditioning status; flow binding status
required_quality_disclosure	primary-record coverage, temporal coverage, mass-balance result, identity evidence gaps, concrete flow identity verification, emission method and tier, assumptions, and regional representativeness
update_trigger	change in orchard-life or allocation method, product identity taxonomy, concrete flow identity verification

Evidence applicability: cited general farm-record and postharvest frameworks do not supply crop-specific yields, lifetimes, gate cutoffs or LCA allocation defaults. Those are this PCR methodology decisions; qualify them by the actual species, route and period and obtain compatible agronomic evidence before asserting completeness. Provisional author ranges are screening aids, not empirical acceptance limits or substituted measurements.

11. Data Sources

Source id	Type	Reference	Used for
ipcc-2019-refinement	method_factor	2019 IPCC Refinement to the 2006 IPCC Guidelines for National Greenhouse Gas Inventories	managed-soil and residue emission calculation methods
emep-eea-2023-guidebook	method_factor	EMEP/EEA air pollutant emission inventory guidebook, current agricultural chapters	agricultural emission method selection and receiving-compartment treatment
iso-14044	standard	ISO 14044, Environmental management — Life cycle assessment — Requirements and guidelines	allocation hierarchy, co-product treatment, and validation expectations
iso-14067	standard	ISO 14067, Greenhouse gases — Carbon footprint of products	product-level boundary disclosure and perennial production allocation context

source_id	type	reference	used_for
declared-handoff-measurement-definition	method_factor	This PCR, Sections 3, 6 and 8: measured net mass at the same state and gate is its own normalization denominator, giving a mass ratio of 1; handoff measurement adds no physical processing.	Same-stage and handoff measurement identities; a definition, not an observed yield, empirical default or external publication.
fao-gap-framework-2003	official_guidance	FAO Committee on Agriculture, COAG/2003/6, Development of a Framework for Good Agricultural Practices, section IV paragraphs 24–26 and Annex, https://www.fao.org/4/y8704e/y8704e.htm	Generic monitoring and farm-record context only; crop-specific routes, lifetimes, quantitative ranges and LCA allocation are PCR choices requiring separate applicable evidence.
fao-fertilizer-identities	official_guidance	FAO Fertilizer Specifications, https://www.fao.org/agriculture/crops/thematic-sitemap/theme/spi/plantnutrition/fertspecs/en/	conditional concrete identities and method context; does not establish site use or quantities
fao-organic-nutrients	official_guidance	FAO How to Make and Use Compost, https://www.fao.org/4/i2230e/i2230e.pdf	conditional concrete identities and method context; does not establish site use or quantities
fao-agricultural-energy	official_guidance	FAO Energy demand and consumption in African agriculture, Annex C case-study results, https://www.fao.org/4/v9766e/v9766e08.htm	conditional concrete identities and method context; does not establish site use or quantities
fao-forest-equipment	official_guidance	FAO Appropriate technologies for forest harvesting, https://www.fao.org/4/x5596E/x5596e06.htm	conditional concrete identities and method context; does not establish site use or quantities
route-energy-fao	official_guidance	FAO, Energy-smart food for people and climate (2011), Annex 2; and Energy use in agriculture and industry, Annex IV. https://www.fao.org/4/i2454e/i2454e00.pdf ; https://www.fao.org/4/Q1085e/q1085e0d.htm	Equipment/carrier possibilities only; site records govern applicability. No intensity, fuel share or default recipe is adopted.