--- title: "Raleigh development plans: requested and approved units" description: "Compare Raleigh development-plan units, lots, and requested square footage. Preserve blanks and zeros, then check project identity before adding totals." canonical: "https://scalewithsearch.com/articles/raleigh-development-plans-requested-approved-units" --- ## 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 development plans: keep requested and approved units in separate columns A studio comparing development plans needs a clear answer to “how large is the proposed program?” A single column called units makes that answer unreliable. It can mix requested quantities, reported approved quantities, and values whose meaning needs further investigation. Keep the original labels in the working table. Preserve missing values and zeros. Check whether two applications describe separate projects before adding their quantities. These reading choices give a principal a useful comparison without turning a public planning record into a claim about available design work. This guide uses Raleigh's Development Plans metadata. Every worked example is hypothetical. The method supports the broader [project research process for architects and designers](/intelligence/architects-and-interior-designers). It does not interpret zoning, establish architectural credit, or calculate a design fee. ## Read the published labels before comparing program size The [Raleigh Development Plans layer](https://services.arcgis.com/v400IkDOw1ad7Yad/ArcGIS/rest/services/Development_Plans/FeatureServer/0?f=pjson) exposes separate fields for requested and approved units. `units_req` is labeled Units Requested. `units_apprv` is labeled Units Approved. The same distinction appears in `lots_req` and `lots_apprv`, labeled Lots Requested and Lots Approved. The field `sq_ft_req` is labeled Square Footage Requested. The inspected layer has no corresponding approved-square-footage field. Keep that limitation visible when comparing floor-area figures. A requested square-footage value cannot fill an approved-square-footage column merely because another field reports an approval date. These are field labels, rather than a complete explanation of every record. The inspected schema does not establish how a particular plan's quantities relate to phases, revisions, or an ultimate buildout. That relationship needs the relevant official plan material or clarification from a responsible reviewer. The [dataset item description](https://www.arcgis.com/sharing/rest/content/items/0cded58c5048437d8da83608818650ba?f=pjson) says coverage includes submitted development plans approved or under review. It names Preliminary Subdivisions and Administrative Site Reviews. Therefore, treat the layer as a mixture of planning records requiring stage and type checks, rather than one list of approved construction projects. ## Keep dates and status alongside every quantity The schema labels `submitted` as Date Submitted and `approved` as Date Approved. It also contains a `status` field labeled Status. Keep those source values next to the quantities you review. A number separated from its record stage is difficult to assess responsibly. [Published Development Plans fields](https://services.arcgis.com/v400IkDOw1ad7Yad/ArcGIS/rest/services/Development_Plans/FeatureServer/0?f=pjson). Give your observation date another column. The date the studio checked a row should not replace either city date. If an approval date is absent, record it as unavailable. Do not calculate one from submission age, a meeting date, or a neighboring application. An approval date and a quantity can also create an unanswered question. Suppose a hypothetical record has a date approved but no approved-unit value. Preserve both observations. The date does not supply the missing quantity, and the blank quantity does not erase the date. For comparisons across a weekly research list, name the basis explicitly. You might compare requested units among records retained for further program review. Keep that title on the table. Avoid shortening it to “approved pipeline” when approval evidence was never the selection criterion. ## A hypothetical table that preserves awkward values The following values are invented for this guide. Blank means the example supplies no value. Each row is a review exercise, not an actual Raleigh application. | Example | Units requested | Units approved | Lots requested | Lots approved | Square footage requested | | --- | --- | --- | --- | --- | --- | | Cedar | 48 | Blank | 0 | Blank | 60,000 | | Birch | 32 | 24 | 8 | 6 | 40,000 | | Maple | 0 | 0 | 12 | 10 | Blank | | Oak | Blank | Blank | Blank | Blank | 18,000 | Cedar has a requested program figure and no supplied approved-unit quantity. Its requested-lot zero remains zero. Neither value explains whether a lot count is applicable or why approved values are absent. The next reviewer should see those questions, rather than a filled-in estimate. Birch supports a comparison between two reported quantities: 32 requested units and 24 approved units. The arithmetic difference is eight units. That subtraction does not establish a rejection, a redesign, or a reduction caused by the city. The record's supporting material must establish the relationship. Maple reports zero units in both columns and positive lot counts. Preserve the numbers under their original labels. Do not conclude that units and lots are interchangeable or that the zero proves no dwelling program exists. The inspected metadata supplies no universal explanation for such a combination. Oak supplies requested square footage while leaving other quantities blank. It can enter a table explicitly comparing requested floor area. It cannot enter a verified approved-floor-area total from this layer. The absent counterpart field makes that claim unsupported, even if Oak later receives a reported approval date. ## Treat zero, blank, and unavailable evidence differently Write zero as zero when the source reports it. Write blank or unavailable when the source provides no quantity. Avoid formatting both as a dash without a legend. That presentation conceals a distinction the reviewer needs to evaluate. The inspected quantity fields permit null values. Their metadata does not document a universal business meaning for every null or zero. A blank might require explanation, but the studio should not invent that explanation. Keep “reason not established” available as an honest review note. [Quantity field metadata](https://services.arcgis.com/v400IkDOw1ad7Yad/ArcGIS/rest/services/Development_Plans/FeatureServer/0?f=pjson). If you prepare a summary, distinguish supplied quantities from missing quantities in the narrative. For the hypothetical table, Cedar reports requested units while Oak does not. A subtotal across supplied values should identify that limited basis. Avoid presenting it as the entire program represented by all rows. Choose size bands only after choosing the quantity basis. A studio screening requested floor area should retain records with missing area in a separate review group. Dropping them from a size filter may be operationally convenient. It should not turn into a claim that they are smaller projects. ## Review project identity before adding quantities The schema includes Plan Number, Plan Name, Plan Type, and Acreage fields. These support record review, but the inspected metadata does not define a universal identifier for a whole commercial project. Preserve each application reference even when the studio suspects a shared project. [Plan identity fields](https://services.arcgis.com/v400IkDOw1ad7Yad/ArcGIS/rest/services/Development_Plans/FeatureServer/0?f=pjson). In a hypothetical example, one application describes a subdivision and another describes a site review within the same proposed development. Both might concern one broader project. Adding their unit figures without checking scope could count overlapping program evidence twice. Another hypothetical example has two nearby applications with similar names and different phases. Their quantities might be distinct, overlapping, or superseded. Similarity is a reason to investigate identity. It cannot decide which relationship applies. Use an internal grouping note with three possible outcomes: confirmed relationship, possible relationship, or separate records. Attach the evidence behind the decision. Keep possible matches out of combined project totals until a reviewer establishes the relationship and the quantity scope. Several parcels can also concern one project, while one project can carry several applications. Treat that as a possibility to examine in official project material. Do not assume each parcel means another complete program or that every application means another commission. A useful review question is precise: “Does this quantity describe the whole program or a distinct part?” The answer should identify the supporting material. If it remains unknown, keep the rows separate and say why the studio has withheld a combined total. ## Keep requested program size separate from service fit After checking quantity labels and identity, apply the studio's accepted sectors and size bands. This is a principal's screening judgment. It should appear in its own column, distinct from the public quantities and the city status. For example, Cedar's hypothetical requested floor area may fit the studio's initial screening band. That supports a decision to inspect program evidence. It does not support an estimate of design fees, a staffing commitment, or a claim that the studio can obtain the engagement. Keep a short explanation for rejected records as well. “Requested program outside our accepted size band” differs from “quantity basis unresolved.” The first may close the current review. The second names a question that could justify revisiting the record. If the studio's band changes, date the new rule. Earlier decisions should remain understandable under the criteria used at the time. This practice makes the research history useful when another principal takes over the review. ## Preserve the developer label without assigning design credit The layer contains a field labeled Developer. That label is not Architect of Record. The inspected metadata does not establish an architectural appointment from its value. Keep organization roles separate from the program quantities. [Developer field label](https://services.arcgis.com/v400IkDOw1ad7Yad/ArcGIS/rest/services/Development_Plans/FeatureServer/0?f=pjson). When a principal asks who is drawing the project, answer from suitable role evidence or write “design team unknown.” A company appearing in a developer field should not become a verified competitor, project architect, or available partner through inference. Likewise, an unresolved role is not an open role. Keep an appointment question distinct from a decision to approach anyone. The responsible human should evaluate relationships, appropriate procurement routes, and the basis for any later conversation. The [studio office-work overview](/for/architects-and-interior-designers) addresses inquiry summaries and accepted briefs. Public planning research precedes those private records. A promising program-size comparison should not enter an accepted-project list before the studio has the evidence and authority that list requires. ## Prepare a principal review that another person can repeat Give each reviewed record its source reference, quantity labels, date fields, and observation date. Add the identity decision, unresolved questions, and the principal's screening reason. Another reviewer should be able to reproduce the judgment from those materials. When a later observation changes a quantity, retain the earlier reading with its date. Describe the difference as a change between observed values. Do not assign a cause without supporting evidence. An approved-unit figure appearing later does not explain why an earlier figure was absent. The [business-memory guide](/articles/business-memory-for-ai-agents-guide) covers keeping decisions and corrections in owned records. Here, the valuable history includes rejected matches and unresolved totals. Those notes explain why the studio declined to publish a misleading aggregate. For a starting view, open [Plans in review](/tools/plans-in-review). Its published page distinguishes requested size and source-date meanings. It is a filtered demonstration, so inspect its stated coverage before comparing it with an unrestricted source review. This guide does not claim the demonstration displays approved-quantity columns. For the separate rezoning-stage question, read [Raleigh rezoning case status](/articles/raleigh-rezoning-case-status-design-research). Keep the sibling guides together when a candidate has both rezoning and development-plan evidence. Each record still needs its own stage, identifier, and quantity basis. A private studio process should name the source territory, quantity basis, identity reviewer, and decision owner in its [written scope](/work). The principal decides what fits. Qualified reviewers interpret technical material. A research table supplies evidence for those decisions without making them automatically. ## Source note Layer metadata and the Development Plans item description and terms were reopened October 28, 2026. The item describes daily updates, rather than guaranteeing every value is current. Its terms disclaim completeness, accuracy, and timeliness and reserve feed changes or discontinuation. The inspected schema provides field labels, nullable properties, and dates; it does not supply complete quantity or project-identity definitions. No live application quantities, addresses, personal contacts, or developer values were queried for this article. All table values and grouping examples are hypothetical. 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 rezoning records: read case status before calling a site a design opportunity](/articles/raleigh-rezoning-case-status-design-research). [architects and interior designers](/for/architects-and-interior-designers): website and search resources. ## Related: architects and interior designers - [Raleigh rezoning records: read case status before calling a site a design opportunity](/articles/raleigh-rezoning-case-status-design-research) - [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) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```