BASIC DOCUMENTATION

I02-1 Agriculture Narrative

READY AUDIT
A one-to-three-page narrative written by the landscape architect or other appropriate project team member describing the methods of agriculture used to meet the Imperative (crops planted, livestock raised, etc.), their intended use, and a long-term support and harvest plan. The narrative should address:

  • Why the selected strategies were chosen and how non-edible plants, if any, meet related requirements.
  • How the surrounding climate is supportive of the proposed species as a harvestable resource.
  • Occupants’ access to the infrastructure necessary for harvest and use of agriculture.
  • A clear plan of use for the harvest and how the urban agriculture will be maintained over time.

Where production is being carried out on the project site by outside parties, also include a copy of the agreement demonstrating a minimum 15-year commitment.

I02-2 Weekly Food Access Narrative (if relevant)

READY AUDIT
Project teams choosing the weekly food access pathway must provide a narrative that describes the strategies used to provide community access to healthy local food. This narrative should identify specifically how access is meeting a community need, including:

  • The community need being addressed and how it was identified.
  • The food or activity being provided, and how it meets the need.
  • Where/how the access is being provided, how frequently, and how much of the year.
  • Who is benefitting.
  • What external partners are involved, if any.
  • The arrangements put in place to support the activity long-term.

I02-3 Resilience Narrative & Calculations

READY AUDIT
Non-residential projects must provide a narrative describing:

  • Provisions made to ensure access to the required quantity of emergency food.
  • Maintenance plans addressing how food quality will be maintained and how periodic resupplying will be managed without waste.
  • Calculations showing compliance with Imperative requirements.

Residential projects must provide a narrative describing:

  • The project’s food-storage capacity.
  • Rationale and calculations used to determine the number of occupants.
  • Other calculations showing compliance with Imperative requirements.

I02-4 Photographs or Graphic Depictions

FINAL AUDIT

  • Representative photographs and/or diagrams showing the agriculture area and use patterns throughout the year. If the agriculture area has not yet been used across all seasons, provide diagrams or drawings of predicted use patterns.
  • When the weekly food access pathway is pursued, also include photographs and/or diagrams of sites or activities developed to provide community access to local food, and a link to the program’s website or other evidence of availability.

I02-5 Annotated Site Plan and Agriculture Area Calculation

READY AUDIT

  • Annotated and dimensioned site plan, keyed to I02-1 Narrative, showing agricultural locations.
  • Calculations demonstrating that the and a link to the program’s website or other evidence of availability has been provided.

I02 Case Study

FINAL AUDIT
A summary narrative describing the project team’s approach to the imperative, highlighting any lessons learned or particularly rewarding outcomes

EXCEPTION DOCUMENTATION

Projects that use Exceptions or compliance paths that are not standard for all projects must submit additional documentation per the below. Unless the exception is tied to the 12-month performance period, all exception documentation must be submitted at the Ready Audit.

I02-a Exception Narrative

A brief narrative explaining the project’s eligibility for, and compliance with, Exception requirements.

I02-b Non-Edible Plant List

An annotated list of plants describing how selected plants and allotted areas comply with Exception requirements.

I02-c Technical Documents

Documentation such as bylaws or IRS status, official contracts, signed letters or other official records demonstrating compliance with Exception requirements.

I02-d Calculations and Data

Calculations and/or data demonstrating compliance with Exception requirements.