--- title: "Raleigh rezoning case status for design research" description: "Read Raleigh rezoning status, requested zoning, and source dates before a studio reviews project fit. Keep approval and design-team evidence separate." canonical: "https://scalewithsearch.com/articles/raleigh-rezoning-case-status-design-research" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Services - Services - [AI systems](https://scalewithsearch.com/ai-systems) - [Site build](https://scalewithsearch.com/work#site-build) - [Whole website fix](https://scalewithsearch.com/work#whole-website-fix) - [Content library with SEO](https://scalewithsearch.com/work#content-library) - [Working session](https://scalewithsearch.com/audit) - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Example scope](https://scalewithsearch.com/work#review-the-example-scope) - [Prices and terms](https://scalewithsearch.com/work#prices-and-terms) - Industries - Real estate - [Real estate agents and teams](https://scalewithsearch.com/for/real-estate) - [Platforms, ownership, and IDX](https://scalewithsearch.com/for/real-estate/real-estate-website-platforms-ownership-idx) - [Search, content, and AI](https://scalewithsearch.com/for/real-estate/real-estate-search-content-ai) - [Inquiries, campaigns, and handoffs](https://scalewithsearch.com/for/real-estate/real-estate-website-inquiries-campaigns-handoffs) - [Buyer, seller, and local pages](https://scalewithsearch.com/for/real-estate/real-estate-buyer-seller-local-resources) - [Rules, privacy, and trust](https://scalewithsearch.com/for/real-estate/real-estate-website-rules-privacy-trust) - Browse by business - [Trades and home services](https://scalewithsearch.com/for/#group-trades) - [Health, wellness, and animal care](https://scalewithsearch.com/for/#group-practices) - [Law, finance, and IT](https://scalewithsearch.com/for/#group-professional) - [Marketing and SEO agencies](https://scalewithsearch.com/for/#group-agencies) - [Shops and manufacturers](https://scalewithsearch.com/for/#group-manufacturing) - [Restaurants, shops, studios, and nonprofits](https://scalewithsearch.com/for/#group-local-services) - Chiropractic practices - [Chiropractic and wellness practices](https://scalewithsearch.com/for/chiropractic-and-wellness-practices) - [Chiropractic and physical therapy clinics](https://scalewithsearch.com/for/chiropractic-and-physical-therapy-clinics) - [All industries](https://scalewithsearch.com/for/) - Resources - Free tools - [AI readiness check](https://scalewithsearch.com/check) - [Free tools](https://scalewithsearch.com/tools/) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - Guides - [AI-native library](https://scalewithsearch.com/ai-native) - [Industry intelligence](https://scalewithsearch.com/intelligence) - [Office job guides](https://scalewithsearch.com/guides/) - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles - [All articles](https://scalewithsearch.com/articles/) - [What changed](https://scalewithsearch.com/changes/) - About - Evidence - [Proof](https://scalewithsearch.com/proof) - Scale With Search - [About](https://scalewithsearch.com/about) - [How it works](https://scalewithsearch.com/how-it-works) # Raleigh rezoning records: read case status before calling a site a design opportunity A rezoning record gives a design principal something to investigate. The first useful decision is whether the evidence supports another review. Before calling a site an opportunity, separate the requested zoning change, the reported case stage, and the studio's unanswered appointment questions. Keep those distinctions in the research card itself. A promising building type can survive the first filter while construction approval remains unverified. An attractive location can fit the studio while its design team remains unknown. Neither gap should disappear when someone shortens the card for a meeting. This guide uses Raleigh's published fields to prepare that review. The examples are synthetic. They describe a reading method, rather than current cases or available work. The broader [project-signal guide for architects and designers](/intelligence/architects-and-interior-designers) explains where this research fits within a studio's business development process. ## Start with the case identifier and the source date The [Raleigh rezoning layer schema](https://services.arcgis.com/v400IkDOw1ad7Yad/ArcGIS/rest/services/Rezoning_Case_Boundaries_View/FeatureServer/0?f=pjson) labels `ZONE_CASE` as Zoning Case. It also provides `PrevZoning`, `ZON_REQ`, `STATUS`, and `StatusDate`. Their published labels identify previous zoning, requested zoning, status, and status date. Write the case identifier exactly as supplied. Keep the jurisdiction next to it. Give the source link its own place on the card, so another reviewer can reopen the evidence. A neighborhood name or a memorable project description should supplement that identifier rather than replace it. Keep the status date separate from the day your studio read the record. One describes the source field. The other records your observation. If the date is absent, write “status date unavailable.” Do not substitute the retrieval date or a date guessed from the case number. A single observation does not establish when the studio first could have learned about the case. It also cannot establish every intervening stage. Start a dated observation history from what you have inspected. Describe older events only when a suitable source supports them. ## Preserve the requested change without interpreting the code Copy previous zoning and requested zoning into separate cells. Retain the published text, including conditions or suffixes in that text. If a value is incomplete or unclear, carry the uncertainty forward instead of simplifying it into a different zoning category. For example, a synthetic card might contain “previous zoning: R-1” and “requested zoning: R-6-CU.” Those strings illustrate two different fields. This guide does not interpret their permitted uses, conditions, density, or design implications. A qualified reviewer must consult the controlling zoning material for those questions. The useful principal question is narrower: does the request justify checking the possible building program? The answer can be yes while the program remains unresolved. Write “potential fit requires program evidence” rather than translating a zoning request into a confirmed commission type. Keep acreage in the same evidential category. It can support a studio's initial size filter, but it should not become an invented floor area. The [rezoning item notice](https://www.arcgis.com/sharing/rest/content/items/d1b51de659774914aff660e30d2d3d19?f=pjson) says its boundaries are informational and are not surveys. Boundary validation requires the official sources identified there. ## Read the status label, then follow current information The layer's `STATUS` domain lists four labels: In Process, Withdrawn, Approved, and Denied. The inspected schema supplies those values without a detailed narrative definition for every stage. Preserve the source label rather than expanding it into an undocumented operational meaning. [Raleigh rezoning status domain](https://services.arcgis.com/v400IkDOw1ad7Yad/ArcGIS/rest/services/Rezoning_Case_Boundaries_View/FeatureServer/0?f=pjson). The schema also contains `CurrentInfoLink`, labeled Link to Current Info. Follow that published link for the case under review. During this source check, an in-process result linked to Raleigh's [Rezoning Cases page](https://raleighnc.gov/planning/services/rezoning-process/rezoning-cases). The page was marked updated October 26, 2026. It presents case-specific application and status information, including review and meeting entries. That page does not supply a complete glossary mapping every layer status to a legal or commercial consequence. Keep any missing definition unresolved. A meeting entry can provide a question for the next review without proving an outcome or an appointment opening. An adopted-case link led to the city's [Finalized Rezoning Cases page](https://raleighnc.gov/planning/services/finalized-rezoning-cases). Its table separates the requested change, final action, and adopted ordinance. Use that separation when checking a finalized case. Do not transfer a final action from another row or a similarly named site. ## A synthetic case card with four distinct conclusions The following card is wholly hypothetical. Its labels illustrate a review structure, and its invented reference is not a Raleigh case number. | Card field | Synthetic entry | What the principal can conclude | | --- | --- | --- | | Studio reference | Example Cedar | Internal label only | | Requested zoning change | R-1 to R-6-CU | A request has been recorded in this example | | Reported case status | In Process | Preserve the label; review details remain to be checked | | Status date | Unavailable | No source date is supplied in this example | | Construction approval | Not verified | No supporting approval document has been reviewed | | Design-team evidence | Unknown | No appointment evidence has been reviewed | | Initial studio fit | Possible residential fit | An editorial screening decision, subject to program evidence | | Next question | What program and team does the application document? | A research task, rather than a contact instruction | Read the rows independently. “In Process” should not fill the construction-approval row. A requested zoning code should not fill the program row. Possible studio fit should not fill the design-team row. Suppose a later check changes the reported status to Approved. Update that cell and attach its evidence. Leave construction approval and design-team evidence unchanged until their own sources support a change. This approach prevents one encouraging update from rewriting the whole opportunity story. The principal can then choose to watch, investigate, or reject the candidate. Those are studio decisions. Store the decision separately from the city status so a colleague can distinguish public evidence from the firm's judgment. ## Ask appointment questions that the layer cannot answer Before assigning business development time, identify the role the studio hopes to perform. Architecture, interior design, and another advisory role need different appointment evidence. A general interest in a site is insufficient for deciding which service to discuss. Ask whether the reviewed material identifies a design team and the role of each named organization. A name alone should stay a name until the document establishes responsibility. Do not infer architect of record from a developer label, a filing relationship, or a familiar company name. Then ask whether any suitable role remains available. “Team unknown” describes an evidence gap. It does not describe a vacant appointment. Keep that wording visible when the card passes from a project architect to the principal. Finally, identify what would justify a conversation. An existing relationship, a documented request, or an appropriate procurement route may require different handling. The research card should record the basis for the proposed next step. A public filing by itself should not become an instruction to solicit. ## Run a weekly review around decisions Start the meeting with the studio's accepted territory, sectors, and service types. Use those written criteria to screen candidates consistently. If the criteria change, date the change so later reviewers can explain why similar cases received different decisions. For each retained case, have the researcher state the evidence before offering a recommendation. Read the case identifier, requested change, reported status, status date, and observation date. Then state the missing program or appointment facts. Keep the discussion tied to the linked documents. Give the principal a decision with a reason. “Watch until program evidence is available” is more useful than “interesting site.” “Reject because the documented program falls outside our accepted sector” is more useful than silently deleting the row. Assign an owner and a review trigger to each retained question. A trigger might be a published case update or a scheduled internal reconsideration. Record it as a research checkpoint. Avoid describing it as the date a project will become available. Close the review by checking unresolved conflicts. If the layer and linked page appear inconsistent, preserve both observations with their dates. Hold the interpretation for a responsible reviewer. Do not select whichever value makes the candidate appear more attractive. ## Record rejection reasons that support the next review Use reasons specific enough for another principal to understand. Territory mismatch, unsuitable building type, insufficient program evidence, and no identified service role are different conclusions. Combining them into “not a lead” loses information that could guide future research. Consider two hypothetical rejections. Example Cedar lacks program evidence, so the studio places it on watch. Example Birch documents a project type outside the studio's accepted work, so the principal rejects it. Both leave the active meeting list, but only one needs another source check. Retain the reason, decision date, reviewer, and evidence link. The [business-memory guide](/articles/business-memory-for-ai-agents-guide) explains why decisions and corrections belong in owned records. For planning research, those records should preserve what the studio knew when it made the decision. If new evidence arrives, add a dated reconsideration. Keep the earlier decision understandable. An honest change of view should show the new evidence that caused it, rather than making the previous research look more complete than it was. ## Use the public demonstration as an entry point [Plans in review](/tools/plans-in-review) provides a bounded Raleigh view with plan-type and acreage-band controls. Its published page describes selected review stages and distinguishes development-plan submission dates from rezoning status dates. It also states that developer and firm labels are omitted. Use the demonstration to reach source records and practice these distinctions. Consult its current limits before treating a missing result as meaningful. A filtered public view should not become the studio's complete case inventory or evidence that a design appointment exists. For the office process after an inquiry arrives, see the [architecture and interior design overview](/for/architects-and-interior-designers). For program quantities, use the sibling [requested and approved units guide](/articles/raleigh-development-plans-requested-approved-units). That guide addresses a separate question: what size is requested, and what quantities are reported approved? If your studio needs a private research process, describe the territory, review criteria, source evidence, and responsible reviewers in a [written project scope](/work). Keep technical interpretation, commercial decisions, and any later communication with the appropriate human. ## Source note Sources reopened October 28, 2026: the rezoning layer schema, its ArcGIS item notice, the published current-information links, and the linked city pages. The current-case page displayed an October 26 update. The finalized-case page displayed a September 29 update. Direct command-line requests to the city pages returned HTTP 403; the public web reader supplied readable page text. The schema supplies status labels, rather than a complete stage glossary. No personal contact fields were queried or reproduced. All case-card values and studio decisions above are synthetic recommendations. Continue the website review: [AI-native architects and interior designers: first functions to build](/articles/ai-native-design-studio-first-functions); [Local SEO for architects: publish the studio facts](/articles/architect-local-seo-studio-pages); [Architect website project credits: state your role](/articles/architect-project-credits-website); [Architect website credentials: link the right license](/articles/architect-website-license-verification); [Architecture portfolio SEO: give project images context](/articles/architecture-portfolio-image-seo); [Keep architecture project links working after a rebuild](/articles/architecture-portfolio-url-redirect-map); [Remove private project PDFs from a studio website](/articles/architecture-private-project-pdf-removal); [Design studio AI rules: data, approvals, and spend](/articles/design-studio-ai-data-approval-spend-rules); [Check an interior design before-and-after slider](/articles/interior-design-before-after-slider-accessibility); [Ask for interior design reviews without screening](/articles/interior-design-google-review-requests); [Add checked captions to interior design project videos](/articles/interior-design-project-video-captions); [Interior design service pages: define the scope](/articles/interior-design-service-page-scope); [Interior design inquiry forms: collect the project brief](/articles/interior-design-website-inquiry-form); [Raleigh development plans: keep requested and approved units in separate columns](/articles/raleigh-development-plans-requested-approved-units). [architects and interior designers](/for/architects-and-interior-designers): website and search resources. ## Related: architects and interior designers - [AI-native architects and interior designers: first functions to build](/articles/ai-native-design-studio-first-functions) - [Local SEO for architects: publish the studio facts](/articles/architect-local-seo-studio-pages) - [Architect website project credits: state your role](/articles/architect-project-credits-website) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```