A. Applicability. The common procedures of this section
21.03.020 shall apply to all applications for development activity under this title unless otherwise stated.
B. Pre-application conferences.
1. Purpose. The pre-application conference is an informal discussion to familiarize the applicant and the municipal staff with the applicable provisions of this title that are required to permit the proposed development.
2. Applicability.
a. Required for new applications. A pre-application conference is required prior to submittal of the following types of applications:
i. Rezonings (Map Amendments) except those initiated under AMC Section
21.03.160L;
ii. Subdivisions, except for most Abbreviated Plats (section
21.03.200);
vii. Girdwood Area Master Plans and Development Master Plans (section
21.09.030E and
F);
viii. Abbreviated plats (section
21.03.200) or administrative site plan reviews (section
21.03.180C) which include Class A or B wetlands within or adjacent to the application area;
ix. Abbreviated plats for unit lot subdivisions (section
21.08.070E); and
x. Small Area Implementation Plan (section
21.03.115).
No application for these types of approvals shall be accepted until after the pre-application conference is completed and the applicant receives written notification of the conclusions. |
b. Exception for some changes to already-approved applications. Pre-application conferences are not required for minor amendments to already-approved conditional uses or site plans. All other changes to already-approved applications require a pre-application conference.
c. Optional for all other applications. A pre-application conference is optional prior to submittal of any other application under this title not listed in subsection
B.2.a above.
d. Waiver. The director may waive the pre-application requirement if the director finds that the projected size, complexity, anticipated impacts, or other factors associated with the proposed development clearly, in his or her judgment, make a pre-application conference unnecessary. The waiver shall be made in writing and shall become a part of the case record for the application.
3. Initiation of pre-application conference.
a. The potential applicant shall request a pre-application conference with the director by email, phone, or in writing. The director shall schedule a pre-application conference after receipt of a proper request.
b. At least one week prior to the pre-application conference, the applicant shall provide to the director a description of the character, location, and magnitude of the proposed development and any other supporting documents such as maps, drawings, models, and the type of entitlement sought. It is the applicant's responsibility to provide sufficiently detailed plans and descriptions of the proposal to enable staff to make the informal recommendations discussed below.
4. Pre-application conference content.
a. At the conference, the applicant, the director, and any other persons the director deems appropriate and available to attend shall discuss the proposed development. Based upon the information provided by the applicant and the provisions of this title, the parties should discuss in general the proposed development and the applicable requirements and standards of this title.
b. The conference attendees shall discuss the desired development activities with respect to the following items:
i. Applicability of municipality policies, plans, and requirements as they apply to the proposed development.
ii. Appropriateness of the development with respect to the policies set forth in the comprehensive plan and the regulations in this title.
iii. Need, if any, to prepare a subdivision plat.
iv. Any site plan considerations or requirements.
v. Any concerns or requirements related to the anticipated impact upon public rights-of-way and public improvements, and appropriate requirements to mitigate those impacts, including but not limited to traffic impact analyses.
vi. Any concerns related to neighborhood impacts, land use, landscaping concepts, and overall project design.
vii. Possible alternatives or modifications related to the proposed application.
viii. Procedures that will need to be completed to review and act on the proposed application.
c. A checklist of discussion items indicating topics discussed at the pre-application conference shall be provided to the applicant within ten days of the conference. The checklist shall be considered proprietary information until an application has been submitted.
5. Informal review comments not binding. The review comments of the director are not binding upon the applicant or the municipality, but are intended to serve as a guide to the applicant in making the application and to advise the applicant in advance of the formal application of any issues which will or may subsequently be presented to the appropriate decision-making body. Because a pre-application conference precedes the actual application, some key issues relating to a specific proposal may not be apparent at the pre-application conference.
6. Application required within six months. After a pre-application conference has been completed, an application must be submitted within six months, unless one extension is granted by the director not to exceed an additional six months. If a complete application is not submitted within six months or an extension has not been granted, a new pre-application conference shall be required prior to submitting an application.
C. Community meetings.
1. Purpose. The community meeting is an informal opportunity for the developer to inform the surrounding area residents and property owners of the details of a proposed development and application, how the developer intends to meet the standards contained in this title, and to receive public comment and encourage dialogue at an early time in the review process.
2. Applicability.
a. Types of applications. The applicant shall hold a community meeting for any of the following types of applications.
i. Rezonings (zoning map amendments) except section
21.03.160I rezonings that implement the comprehensive plan (or eliminate a special limitation), and section
21.03.160L rezonings initiated by the assembly, the administration, or the planning and zoning commission, such as area wide rezonings, targeted area rezonings, and overlays;
ii. Subdivisions, except for abbreviated plats;
iv. Marijuana—Special land use permit, associated endorsements, and modifications requiring a public hearing;
v. Institutional master plans;
vii. Public facility site selection;
viii. Small area implementation plan; and
ix. Reinvestment focus areas.
b. Community councils. The applicant shall use as its first choice the community council(s) meeting of the project area as the community meeting when the community council(s) meeting is available. If an applicant chooses not to use the community council for the community meeting, the applicant shall provide a written explanation to the director outlining the reasons for this decision. The explanation shall be available to the appropriate board or commission at the time of authorization review. If the community council(s) meeting for the project area is not scheduled in a timely manner, the applicant shall organize a community meeting. If the project area spans more than one community council and the applicant chooses to attend community council meetings, the applicant shall attend the community council meetings of all applicable community councils.
3. Timing and number of community meetings. When required, there shall be at least one community meeting held within six months prior to the submittal of an application, unless one extension is granted by the director not to exceed an additional six months. If a complete application is not submitted within six months or an extension has not been granted, a new community meeting shall be required prior to submitting an application.
4. Notice of community meeting. The applicant shall provide written (mailed) notice of the community meeting in accordance with subsection
H.3 below, at least 21 days prior to the community meeting. If the applicant does not use the community council meeting as the community meeting, the applicant shall provide community council notice in accordance with subsection
H.6 below.
5. Attendance at community meeting.
a. If a community meeting is required, the applicant or applicant's representative shall attend the community meeting. The applicant shall be responsible for scheduling the community meeting, coordinating the community meeting, and for retaining an independent facilitator if the applicant determines one is needed.
b. All community meetings shall be convened at a place in the vicinity of the proposed development.
6. Summary of community meeting. The applicant shall prepare a written summary of the community meeting(s), which shall be submitted to the director and the affected community council(s) no later than seven days after the date of the meeting. The written summary shall be included in the departmental report. At a minimum, the written summary shall include the following information:
a. Dates and locations of all meetings where citizens were invited to discuss the applicant's proposals;
b. Content and dates of mailing, and number of mailings, including letters, meeting notices, and any other written material;
c. The number of people that participated in the meeting(s);
d. A summary of concerns, issues, and problems expressed during the meeting(s), including:
i. The substance of the concerns, issues, and problems;
ii. How the applicant has addressed or intends to address concerns, issues, and problems expressed at the meeting(s); and
iii. Concerns, issues, and problems the applicant is unwilling or unable to address and why.
D. Authority to file applications.
1. When an authorized agent files an application under this title on behalf of a property owner, the agent shall provide the municipality with written documentation that the owner of the property has authorized the filing of the application.
2. When a review or decision-making body initiates action under this title, it does so without prejudice toward the outcome.
E. Application contents, submittal schedule, and fees.
1. Form of application. Applications required under this chapter shall be submitted on the appropriate form provided by the department and in such number as required for the individual application type.
2. Processing fees. Applications shall be accompanied by the fee amount established by the assembly and listed in AMCR Chapter
R21.20. Fees are not subject to waivers except as specifically allowed by this title.
3. Waivers. The director may waive certain submittal requirements in order to reduce the burden on the applicant and to tailor the requirements to the information necessary to review a particular application. The director may waive such requirements where he or she finds that the projected size, complexity, anticipated impacts, or other factors associated with the proposed development clearly, in his or her opinion, support such waiver. The waiver shall be made in writing and shall become a part of the case record for the application.
F. Verification of application completeness.
1. The director shall only initiate the review and processing of an application if such application is complete. The director shall make a determination of application completeness and notify the applicant in writing within 15 days of application filing. If the application is determined to be complete, the application shall then be processed according to this title. If an application is determined to be incomplete, the director shall provide an explanation of the application's deficiencies. No further processing of an incomplete application shall occur until the deficiencies are corrected.
2. An application shall be considered complete if it is submitted in the required form, includes all mandatory information, and is accompanied by the applicable fee. A pre-application conference shall have been held, if required, pursuant to section
21.03.020B, pre-application conferences.
3. As a consequence for any false or misleading information submitted or supplied by an applicant on an application, that application shall be deemed incomplete.
G. Additional information.
1. Requested information. Nothing in this section prohibits the department or the decision-making body on the application from requesting additional information deemed necessary for review, after the application is complete. Any supplemental technical reports, special studies, and/or revised application materials that are requested following the original application must be received at least 30 days prior to a public hearing. The municipality may postpone and reschedule a public hearing or approval deadline if such reports and studies are submitted less than thirty days prior to a public hearing, unless the applicable board or commission waives this time limit in a specific case for cause. Copies of such additional materials shall be delivered to all reviewers who received the original application packet.
2. Voluntary information. Any supplemental information, such as revised application materials, that is voluntarily submitted by the applicant, should be submitted before the departmental report is finalized. Any such information submitted after the departmental report is finalized shall cause the application to be automatically postponed to the next regular meeting in order for the department to have time to review the new information, unless the board or commission determines that the new information does not significantly alter the application.
H. Notice.
1. Content of notices. Public notice required under this chapter shall, unless otherwise specified in this title:
a. Identify the date, time, and place of the public hearing or community meeting, if applicable;
b. If applicable, describe the property involved in the application by street address or by legal description and nearest cross street;
c. Describe the nature, scope, and purpose of the proposed action;
d. If applicable, indicate that interested parties may appear at the hearing or community meeting and speak on the matter; and
e. Indicate where additional information on the matter may be obtained.
2. Summary of notice requirements. The following Table 21.03-1 summarizes the notice requirements of the procedures set forth in this chapter. Unless otherwise specified in this title, procedures not listed in this table have no public notice requirements.
TABLE 21.03-1: SUMMARY OF NOTICE REQUIREMENTS |
|---|
Type of Application or Procedure | Section | Notice Required |
|---|
Written (Mailed) | Published | Posted | Community Council |
|---|
Alcohol—Special Land Use Permit | | ✓ | ✓ | ✓ | ✓ |
Alcohol—Modification of a Special Land Use Permit Requiring Public Hearing | | ✓ | ✓ | ✓ | ✓ |
Appeals to Board of Adjustment | | ✓ | ✓ | - | - |
Appeals to ZBEA | | ✓ | ✓ | - | ✓ |
Comprehensive Plan Amendments, Substantive | | - | ✓ | - | ✓ |
Conditional Uses | | ✓ | ✓ | ✓ | ✓ |
Marijuana—Special Land Use Permit and associated endorsements | | ✓ | ✓ | ✓ | ✓ |
Marijuana—Modification of a special land use permit requiring public hearing | | ✓ | ✓ | ✓ | ✓ |
Marijuana—Variances | | ✓ | ✓ | ✓ | ✓ |
Master Plan, Area | | ✓ | ✓ | ✓ | ✓ |
Master Plan, Development | | ✓ | ✓ | ✓ | ✓ |
Master Plan, Institutional | | ✓ | ✓ | ✓ | ✓ |
Neighborhood or District Plans | | - | ✓ | - | ✓ |
Nonconforming Uses of Land or Structures, Replication of | | ✓ | ✓ | ✓ | ✓ |
Nonconforming Structures, Replication of | | ✓ | ✓ | ✓ | ✓ |
Public Facility Site Selection | | ✓ | ✓ | ✓ | ✓ |
Reinvestment Focus Area | | ✓ | ✓ | ✓ | ✓ |
Rezonings when a comprehensive plan map amendment is required | | ✓ | ✓ | ✓ | ✓ |
Rezones that implement the comprehensive plan (or eliminate a special limitation) | | ✓2 | ✓ | ✓ | ✓ |
Rezonings to create, alter, or eliminate overlay districts | | ✓ | ✓ | ✓ | ✓ |
Rezonings to planned community development district (PCD) | | ✓ | ✓ | ✓ | ✓ |
Rezonings initiated by the assembly, the administration, or the planning and zoning commission, such as area wide rezonings, targeted area rezonings, and overlays | | - | ✓ | - | ✓ |
Site Plan Review, Administrative | | ✓1 | ✓ | - | ✓ |
Site Plan Review, Major | | ✓ | ✓ | ✓ | ✓ |
Small Area Implementation Plan | | ✓ | ✓ | ✓ | ✓ |
Street Name Alterations | | ✓ | ✓ | - | ✓ |
Street and Trail Review | | - | ✓ | - | ✓ |
Subdivisions (with existing physical access) | | ✓ | ✓ | ✓ | ✓ |
Subdivisions (without existing physical access) | | ✓ | ✓ | - | ✓ |
Abbreviated Plats | | - | ✓ | - | ✓ |
Modification or Removal of Plat Notes | | ✓ | ✓ | ✓ | ✓ |
Title 21, Text Amendments | | - | ✓ | - | ✓ |
Vacation of Public and Private Interest in Land | | ✓ | ✓ | ✓ | ✓ |
Variances | | ✓ | ✓ | ✓ | ✓ |
Administrative Variances | | ✓ | ✓ | ✓ | ✓ |
Notes: |
|---|
1 | Written (mailed) notice shall be provided only when the "administrative site plan review with notice" process is specifically required by this title. |
2 | Written (mailed) notice for rezones that implement the comprehensive plan (or eliminate a special limitation) in § 21.03.160I will only be to property owners within the affected area and those property owners immediately adjacent to the affected area. |
3. Written (mailed) notice. When Table 21.03-1 requires that written notice be provided, the director (or developer when noticing a community meeting) shall deposit such notice into first class mail at least 21 days prior to the scheduled date of the hearing or community meeting. In computing such period, the day of mailing shall not be counted, but the day of the hearing or community meeting shall be counted. Written notice shall be provided to the following persons or groups:
a. Owners of subject property. All persons listed on the records of the municipal assessor as owners of land subject to the application, at the mailing addresses of such persons in the records of the municipal assessor.
b. Adjacent property owners and residents/occupants. All persons listed on the records of the municipal assessor as owners of any land within 500 feet of the outer boundary of the land subject to the application, or owners of the 50 parcels nearest to the outer boundary of the land subject to the application, whichever is the greater number of parcels, at the mailing addresses of such persons in the records of the municipal assessor; and all residents/occupants of land in the same area as required above, at the property addresses. Any mailing to the 50 nearest parcels shall not include parcels that are entirely located more than a mile from the land subject to the application, which may reduce the number of mailings.
c. Joint Base Elmendorf-Richardson. The commander of Joint Base Elmendorf-Richardson (JBER) when the subject parcel is within 500 feet of JBER or within 500 feet of the boundary of a safety zone or noise contour that emanates from JBER and has been shared with and accepted by the department.
d. Additional persons. Such additional persons or geographic areas as the director may designate.
e. Street name alterations. Notwithstanding the remainder of this subsection
H.3, written notice for street name alterations shall be limited to all owners of property fronting on a subject street. Such notice shall be mailed at least 21 days before the street name alteration is submitted to the mayor in accordance with section
21.03.185. The notice shall state the present and proposed street names and shall direct that any comments on the alteration be submitted in writing to the director.
4. Published notice. When Table 21.03-1 requires that notice be published, the director shall cause a notice to be published on the municipal public notice web page of the municipal website. The notice shall be published at least 21 days before the scheduled hearing date. In computing such period, the day of publication shall not be counted, but the day of the hearing shall be counted.
5. Posted notice. When Table 21.03-1 requires that notice be posted, the applicant shall cause a notice(s), on a form(s) provided by the department, to be posted on the property, visible from each developed right-of-way adjacent to the property, for at least 21 days before the scheduled public hearing date. In computing such period, the day of posting shall not be counted, but the day of the public hearing shall be counted. If no part of the subject property is visible from the public right-of-way, the notice shall be posted along the nearest street in the public right-of-way. Posted notices shall include the case number or case type, a contact phone number, and the municipal website address. Before the public hearing, the applicant shall submit to the department an affidavit, signed by the person who did the posting or the person who caused the posting to be done, that notice was posted as required by this subsection. Posted notices shall be removed by the applicant within 30 days after the close of the public hearing on the application.
6. Community councils. When Table 21.03-1 requires that notice be given to community councils, any officially recognized community council whose boundary includes any part of the subject property, and any additional such council whose boundary lies within 1,000 feet of any part of the subject property shall receive written (mailed) notice in accordance with H.3. above. Furthermore, the department shall provide notice to additional community councils in the following instances:
a. Each recognized community council within the municipality shall receive written notice where the subject parcel is one of the following regional public lands or facilities: Ted Stevens Anchorage International Airport; Merrill Field Airport; Birchwood Airport; Far North/Bicentennial Park; Kincaid Park; Russian Jack Springs Park; Beach Lake Park; Edmonds Lake Park; Bird Creek Regional Park; Chugach State Park; Anchorage Coastal Wildlife Refuge; BLM tract(s) near Far North/Bicentennial Park.
b. If the subject parcel is a branch public facility that serves a specific delineated area, such as a public school or fire station, then any community council whose boundaries lie within the delineated district of service of a branch public facility shall receive written notice. This requirement shall only take effect after the municipality has established maps delineating areas of service for the type of branch facility, and has adopted procedures and responsibilities for updating service area boundaries.
c. Any community council whose boundaries lie beyond the minimum notification distance shall receive notice regarding proposals of potentially major scope or controversy that, in the opinion of the director, are likely to have a significant impact on the residents of the community council beyond the minimum notification distance.
d. Any community council within the impact area of a street or trail project, a neighborhood or district plan, or other area-specific element of the comprehensive plan, shall receive written notice. The impact area shall, at a minimum, include all community councils within 1,000 feet of the project/plan boundaries. The impact area shall include additional community councils if the recommendations in the project/plan affect specific public lands or facilities as provided in subsection
H.6.a or
H.6.b above, or are likely to impact residents beyond the minimum impact area, as provided in subsection
6.c above.
e. All community councils shall receive notice of substantive amendments to the comprehensive plan (except as provided in subsection
6.d above), and amendments to the text of Title
21.
7. Constructive notice. Minor defects in any notice shall not impair the notice or invalidate proceedings pursuant to the notice if a bona fide attempt has been made to comply with applicable notice requirements. Minor defects in notice may include, but are not limited to, errors in a legal description or typographical or grammatical errors that do not impede communication of the notice to affected parties. Failure of a party to receive written notice shall not invalidate subsequent action. In all cases, however, the requirements for the timing of the notice and for specifying the time, date, and place of a hearing shall be strictly construed. If questions arise at the hearing regarding the adequacy of notice, the decision-making body shall make a formal finding as to whether there was substantial compliance with the notice requirements of this title.
8. Presumption of notice. When the records of the municipality document the publication, mailing, and posting of notices as required by this subsection, it shall be presumed that notice of a public hearing was given as required by this subsection.
I. Departmental report. For every decision that requires a public hearing or where otherwise required by this title, the department shall prepare a report to be given to the decision-making body approximately one week before the initial public hearing on the application. The report shall include project background, public comments received, the summary of community meeting (if applicable), and the department's recommendation for action. The report shall be posted on the municipal website.
J. Referrals. The applicant, boards, commissions, or the municipal administration may request that government agencies, non-governmental agencies, and other boards and commissions besides the decision-making body review an application, but the final decision-making authority shall remain with the body identified in this chapter.
K. Concurrent processing.
1. Where possible without creating an undue administrative burden on the municipality's decision-making bodies and staff, this title intends to accommodate the simultaneous processing of applications for different permits and approvals that may be required for the same development project in order to expedite the overall review process. Review and decision-making bodies considering applications submitted simultaneously shall render separate reports, recommendations, and decisions on each application based on the specific standards applicable to each approval.
2. Some forms of approval depend on the applicant having previously received another form of approval, or require the applicant to take particular action within some time period following the approval in order to avoid having the approval lapse. Therefore, even though this title intends to accommodate simultaneous processing, applicants should note that each of the permits and approvals set forth in this title has its own timing and review sequence.
3. The expected time frame and approval process for a consolidated application shall follow the longest time frame and approval process required from among the joined application types.
L. Postponements.
1. If only five or fewer board or commission members are in attendance at the hearing, the applicant may request a postponement of his or her case, and the fee for the first postponement request shall be waived.
2. The applicant may request a postponement of his or her case for any other reason, which he or she shall state to the decision-making body. If the decision-making body grants the postponement request, the applicant shall pay the postponement fee as required by AMCR Chapter
R21.20, and a new hearing date shall be determined by the department.
a. If public notice pursuant to subsection
H above has not been given, the director is the decision-making body for the purpose of granting a postponement.
b. If public notice pursuant to subsection
H above has been given, the decision-making body is the board or commission identified in this chapter for the entitlement requested.
3. Re-notice of the new time for hearing is only required if the postponement is for more than 30 days, or if no date certain is set for the hearing at the time of postponement.
M. Conditions of approval.
1. The decision-making body is authorized to impose such conditions upon the entitlement as may be necessary to conform to the standards of this title, reduce or minimize any potential adverse impact upon other property in the area, or to carry out the general purpose and intent of the comprehensive plan and this title. In such cases, any conditions attached to approvals shall be directly related to the impacts of the proposed use or development and shall be roughly proportional in both extent and amount to the anticipated impacts of the proposed use or development.
2. No conditions of approval, except for those attached to variance approvals, shall be less restrictive than the requirements of this title or applicable special limitations.
3. Unless there is a time schedule stated as part of the approval or conditions of approval, all conditions of approval shall be met within one year of the date of approval (unless the condition is ongoing, such as a specification of hours of operation).
N. Decision. Recommendations and decisions shall be made in accordance with Title
4.
O. Lapse of approval.
1. The lapse of approval time frames established by the procedures of this title may be extended only when all of the following conditions exist:
a. The provisions of this title must expressly allow the extension;
b. An extension request must be filed prior to the applicable lapse-of-approval deadline; and
c. The extension request must be in writing and include justification.
2. Unless otherwise noted, authority to grant extensions of time shall rest with the decision-making body that granted the original approval (the one being extended).
P. New application required. If an application is inactive for one year awaiting action by the petitioner, the application shall be discarded and a new application shall be required.
(AO 2012-124(S), 2-26-2013; AO 2013-117, 12-3-2013; AO No. 2015-131, § 1, 1-12-2015; AO No. 2015-142(S-1), § 1(Exh. A), 6-21-2016; AO No. 2016-3(S), § 3, 2-23-2016; AO No. 2017-75, § 1, 5-9-2017; AO No. 2017-175(S), § 1, 2-13-2018; AO No. 2019-67, § 1, 6-18-2019; AO No. 2021-46(S), § 5, 6-8-2021; AO No. 2021-69, § 1, 8-10-2021; AO No. 2021-89(S), § 21, 2-15-2022; AO No. 2022-62(S), § 4, 10-11-2022; AO No. 2023-25(S), § 2, 3-7-2023; AO No. 2023-77, § 1, 7-25-2023; AO No. 2025-40(S), § 1, 4-22-2025)