<- [[:charlottesville|Charlottesville Regulatory Process Guide]] | Shared Sub-Process -> ====== Common Review Procedures (Spine, Dev Code 5.2.1) ====== Governed by **Chapter 34, Article 5, Div. 5.2.1 (Common Review Procedures)**. This is the reusable application-intake **spine** shared by every approval process in Article 5 Div. 5.2 and Article 6 (Subdivision), per 5.2.1.A. Other process diagrams invoke it through a BPMN **Call Activity** (calledElement Process_CommonReviewProcedures). Statutory anchors: Code of Virginia 15.2-2280 et seq.; intake/notice per 15.2-2204. It covers application preparation and submittal (5.2.1.C.1-C.3), routing by the Administrator (5.2.1.C.6), the 5-day completeness determination (5.2.1.C.4), the revision loop with a 3-revision fee cap (5.2.1.C.6.c), and withdrawal at any time (5.2.1.C.7). **Process ID:** Process_CommonReviewProcedures - reference this from a Call Activity in any calling process. **Called by:** * [[:charlottesville:zoning_map_amendment|Zoning Map Amendment / Rezoning (5.2.5)]] **Key links:** * [[https://library.municode.com/va/charlottesville|Chapter 34 - Zoning (Municode)]] Reusable application-intake spine common to all approval processes in Article 5 Div. 5.2 and Article 6 Subdivision (per 5.2.1.A). Intended to be invoked by a Call Activity from each specific process. Statutory anchor: Code of Virginia 15.2-2280 et seq.; intake/notice per 15.2-2204. Initiation per the calling process (e.g., owner/agent for rezoning 5.2.5.B.1, or City for public facilities). Pre-application conference, where required, is modeled in the calling process, not here. Flow_Start_Prepare 5.2.1.C.1 file with Neighborhood Development Services on required forms; 5.2.1.C.2 disclose real parties in interest (required for special use permit, Code amendment, special exception, variance); 5.2.1.C.3 pay fees in full (delinquent-tax evidence may be required). Submit per published schedule (5.2.1.C.5). Flow_Start_Prepare Flow_Prepare_Route 5.2.1.C.1.a and 5.2.1.C.6 the Administrator (NDS) routes materials to the appropriate review bodies. No materials go directly to PC, BZA, BAR, Mayor, or Council. Flow_Prepare_Route Flow_Route_Complete 5.2.1.C.4 the Administrator has 5 days to review and determine completeness. Fees must be paid in full for an application to be considered complete (5.2.1.C.3.c). Flow_Route_Complete Flow_Revise_Recheck Flow_NewFee_Recheck Flow_Complete_Gateway Non-interrupting monitor of the 5.2.1.C.4 statutory 5-day completeness clock. Used for conformance checking against NDS case logs. Flow_Deadline_End "P5D" Flow_Complete_Gateway Flow_Yes_Complete Flow_No_Notify 5.2.1.C.4.a applicant is notified of an incomplete application; the application does not proceed for review or decision until complete. Flow_No_Notify Flow_Notify_Revise 5.2.1.C.6 revised materials routed through NDS; must be submitted at least 30 days before a scheduled meeting/hearing (later accepted at Administrator discretion). Flow_Notify_Revise Flow_Revise_Count 5.2.1.C.6.c up to 3 revisions before a new application fee is required for further review (Administrator may waive for circumstances beyond the applicant's control). Flow_Revise_Count Flow_WithinLimit_Recheck Flow_OverLimit_NewFee 5.2.1.C.6.c new application fee required for further review after 3 revisions, unless waived. Flow_OverLimit_NewFee Flow_NewFee_Recheck Hand-off point. The calling process resumes with its specific review and decision steps (e.g., PC public hearing, Council decision). Flow_Yes_Complete Flow_Deadline_End 5.2.1.C.7.a written notice to the Administrator at the applicant's discretion. 5.2.1.C.7.b no fee refunded. Flow_Wd_Announce 5.2.1.C.7.c if a meeting/hearing was advertised, the withdrawal is announced at it. Flow_Wd_Announce Flow_Wd_End Flow_Wd_End complete == True revisionCount <= 3