The EDGE App relies on location-specific climate data to calculate resource savings, but not all cities are listed. The EDGE User Guide provides guidance for such cases: "If the project city is not listed in the EDGE App, the user should choose the closest city to the project location that is available in the database. If necessary, the user can edit the climate data (e.g., temperature, humidity) to better reflect the project’s actual conditions, ensuring accurate calculations" (EDGE User Guide, Section 2.2: Project Setup). Option B, choose the closest city and edit the climate data if necessary, directly matches this protocol. Option A (write to EDGE Certifier and wait) is incorrect, as this is not a required step: "Users are not required to request new cities; they can proceed by selecting the closest city" (EDGE User Guide, Section 2.2: Project Setup). Option C(select any city in the same climate zone globally) is too broad and inaccurate: "Choosing a city from a different region, even in the same climate zone, may lead to incorrect assumptions about local practices and climate" (EDGE Methodology Report Version 2.0, Section 3.2: Climate Data Inputs). Option D (choose the capital city) is also incorrect unless it is the closest: "The capital city should only be selected if it is the nearest available option in the database" (EDGE User Guide, Section 2.2: Project Setup). Thus, the correct protocol is to choose the closest city and edit climate data (Option B).