--- title: "Raleigh permits past 31 days: retain older project research" description: "Keep Raleigh permit observations when a project leaves a dated feed window. Compare synthetic exports without confusing missing records with closed work." canonical: "https://scalewithsearch.com/articles/raleigh-permit-window-retained-project-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 permit windows: keep an older project when it leaves the current feed An older permit disappearing from a research list creates a practical estimating question: should the project leave next week's scope review? Keep the project until you can explain the disappearance. A publication window describes what a source exposes. It does not decide whether a fence package remains relevant to your company. For a garage door or fence estimator, the useful record has two parts. One preserves what the city published and when you observed it. The other records your scope question, evidence gaps, and review decision. A fresh export should update the first part without silently deleting the second. This guide extends the [public project signals overview](/intelligence/garage-door-and-fencing-contractors) with a retention worksheet. All permit identifiers, export dates, and project examples below are synthetic. They illustrate reading decisions, rather than current Raleigh projects or available work. ## Inspect the current filter before describing coverage On October 28, 2026, the [Raleigh permit layer metadata](https://services.arcgis.com/v400IkDOw1ad7Yad/ArcGIS/rest/services/Building_Permits_Past_31_Days/FeatureServer/0?f=pjson) identified the layer as a view. Its `viewDefinitionQuery` constrained `issueddate` to values on or after a dated timestamp. That observation supports a specific conclusion: the inspected view applied an issue-date threshold. Read that predicate again when preparing a later review. Record its complete value beside your observation time. Do not turn the date observed for this article into a permanent cutoff in your worksheet. Do not assume the words “Past 31 Days” establish the filter currently applied to every response. The [dataset item description](https://www.arcgis.com/sharing/rest/content/items/f7a3cbd07e9f4ca5bb6637e7eeab5871?f=pjson) describes past-month coverage and daily updates. It excludes several other permit categories, including plumbing, electrical, mechanical, right-of-way, and grading permits. Its terms disclaim guaranteed accuracy, completeness, and timeliness. Therefore, keep source coverage and observation quality visible beside any project conclusion. The schema separately labels `permitnum`, `issueddate`, `statuscurrent`, and `proposedworkdescription`. Keep those source fields separate in your sheet. An issue date is not your first observation date. A description is not a verified material schedule. A previously observed status is not automatically the current status. ## Preserve a permit identity and an observation history Use jurisdiction plus permit number as the starting identity in the private review sheet. Preserve the permit number as text. Retain the source reference with it. If a later record appears related but has a different number, mark the relationship unresolved before combining them. Give first observation and latest successful observation their own columns. First observation means the earliest evidence your company retained. It does not mean the project began that day. Latest successful observation means you found the permit in a usable source result. It does not mean the company checked its scope that day. Add a separate latest attempted check. This field explains why a review date can advance while the latest successful observation stays unchanged. A failed check should leave the earlier evidence intact. Otherwise, the worksheet can make an unsuccessful refresh look like a verified disappearance. Keep your original scope question beside this history. For example, “Does the description include permanent perimeter fencing?” remains a question until suitable evidence answers it. Retaining that question prevents an old keyword match from becoming a confirmed package through repetition. ## Compare two synthetic dated exports Consider two invented exports, observed October 10 and October 28. For this exercise only, suppose the inspected thresholds were September 9 and September 27. These example thresholds are not instructions for future source requests. Your actual worksheet must use the predicate observed with each export. The following permit labels are fabricated. None identifies a real property, owner, or contractor. Assume both exports passed the company's coverage review before comparison. | Synthetic permit | Issue date | October 10 export | October 28 export | Initial review result | | --- | --- | --- | --- | --- | | DEMO-A | September 15 | Present | Absent | Outside the second threshold | | DEMO-B | October 4 | Present | Absent | Absence unexplained by the threshold | | DEMO-C | October 8 | Present | Present | Compare observed values | | DEMO-D | October 9 | Present | Present | Retain separate status evidence | DEMO-A no longer satisfies the later example threshold. Record “outside current publication window” as the coverage explanation. Keep its last observed description, issue date, and estimator question. That coverage explanation supplies no evidence that construction finished or a supplier was selected. DEMO-B still satisfies the later example threshold. Its absence needs a different label: “missing from a usable comparison; reason unresolved.” Check the export scope, identity, and available official record. Do not assign DEMO-A's explanation merely because both rows disappeared from the screen. DEMO-C remains visible. Preserve any changed description or status as a later observation. If the wording is unchanged, record that result without presenting it as a new project. The comparison concerns the same research item unless identity evidence establishes otherwise. DEMO-D illustrates a separate decision. Suppose a later official record supports ending a particular scope review. Preserve that evidence and the review reason. The decision comes from the independent check, even though DEMO-D remains visible in the current export. ## Keep failed, missing, aged-out, and closed separate A failed refresh belongs at the export level. If the second attempt failed, replace no permit observations with blanks. Record the failure time and the evidence that made the result unusable. Postpone the comparison until you have a usable result or a clearly bounded alternative. A missing permit belongs at the record level. Use this label only after establishing that the result can support the intended comparison. An incomplete export cannot establish absence. A narrow export can establish only absence within that narrower coverage. An aged-out permit has a documented relationship to the inspected threshold. Check the relevant issue date and the exact comparison operator. Near a cutoff, preserve the source timestamp rather than rounding it into a different inclusion decision. If interpretation remains uncertain, keep that uncertainty in the review note. A closed review requires a reason outside feed membership. Distinguish the city's recorded status from your company's decision to stop investigating a scope. A permit status can answer one administrative question while leaving your estimating question unresolved. Do not create a universal closure rule from an undocumented label. | Review label | Evidence to retain | What the label cannot establish | | --- | --- | --- | | Refresh failed | Attempt time and failure detail | That any permit disappeared | | Missing, unresolved | Usable comparison and retained identity | Why the source omitted the permit | | Outside publication window | Observed threshold and issue date | Completion or purchasing status | | Scope review ended | Decision reason and supporting evidence | That every related package is closed | ## Verify the official record before ending a review Start with the retained jurisdiction and permit number. Raleigh's [Development Records guidance](https://raleighnc.gov/development-records) directs readers to its portal for permit and inspection information. It also notes that downloadable document availability varies with project date and type. An unavailable attachment therefore leaves an evidence gap; it cannot fill a status column. Use the city's current guidance to locate the relevant record. The [portal help center](https://raleighnc.gov/permits/services/permit-and-development-portal-help-center) explains public-record searches and distinguishes them from registered project management. This guide requires no account creation, application changes, fee payments, or inspection scheduling. Record the official reference, observation date, and exact status wording needed for your review. Keep your interpretation in a different field. If the record does not answer the scope question, state the missing evidence. Do not replace that gap with a guess about construction progress. Suppose DEMO-A later has an official status entry that needs interpretation. Keep the raw entry and ask the responsible reviewer what it establishes for this permit. Separately check whether your original permanent-fence question remains relevant. Neither an old issue date nor a status label identifies the purchasing decision maker. When evidence supports ending the company's review, record a dated reason. “No relevant permanent scope in reviewed documents” differs from “administrative status needs clarification.” The first can support a scope decision. The second identifies unfinished research. Keep earlier observations available to explain either outcome. ## Use a worksheet that survives the next export Build the worksheet around evidence you can explain during an estimating meeting. The following fields are recommendations for your private process. They are not additional Raleigh dataset fields. | Worksheet field | What to enter | | --- | --- | | Jurisdiction and permit number | Retained source identity | | Source and coverage observation | Layer reference, predicate, and observation time | | First observation | Earliest retained company observation | | Latest successful observation | Most recent usable sighting | | Latest attempted check | Attempt time, result, and coverage limits | | Source wording | Dated description and reported status | | Estimator question | Specific door or fence scope uncertainty | | Current review label | Coverage explanation or unresolved status | | Independent verification | Official reference, date, and relevant evidence | | Company decision | Reviewer, reason, and next review condition | Keep the sheet compact enough that an estimator can see the evidence beside the decision. Store earlier observations as dated history rather than overwriting them. A current summary can point to that history without repeating every description in the meeting view. Before removing DEMO-B from active review, require an explanation for its unexplained absence or a separate reason to end the scope investigation. If the company chooses to stop research because the question falls outside its service area, say so. A company screening decision should never masquerade as a city finding. ## Keep retention separate from scope and buying intent A retained permit remains a research item. It is not an invitation to quote. The [fence-description guide](/articles/fence-permit-description-temporary-barrier-permanent-scope) explains how to distinguish construction barriers, permanent-fence candidates, mixed descriptions, and unresolved wording. Apply that reading before treating any retained keyword as a suitable package. For door work, write an equally specific question. A garage reference alone should not become an opener replacement or a door schedule. Ask what evidence identifies the relevant opening, work boundary, and unresolved specification. Keep procurement availability as another unanswered question until suitable evidence addresses it. The [garage door and fencing office guide](/for/garage-door-and-fencing-contractors) covers work that already has a service brief or site-measure handoff. Keep public permit research separate from accepted work. That distinction lets the estimator retain useful history without adding speculative jobs to production planning. The [business-memory guide](/articles/business-memory-for-ai-agents-guide) explains how to preserve decisions in company-owned records. For this workflow, preserve the coverage explanation and rejected interpretations alongside accepted classifications. Those details let a later reviewer understand why a permit stayed on the sheet. If you ask Scale With Search to build the private process, define the supported jurisdiction, retained fields, failure handling, and review owner. Include an example that ages out and another that disappears unexpectedly. Keep the service scope in writing. [Discuss the workflow scope](/work) ## Source note Raleigh layer metadata, dataset description and terms, Development Records guidance, and the portal help center were reopened October 28, 2026. The observed layer predicate is dated evidence, not a permanent coverage rule. No live project rows, residential addresses, owner names, or contact details were downloaded for this guide. All comparison records are synthetic. Current project status and available purchasing scope remain subject to their own verification. Continue the website review: [AI-native garage door and fencing firms: first functions](/articles/ai-native-garage-door-fence-first-functions); [Fence Permit FAQs: Use the Right Local Source](/articles/fence-contractor-permit-website-faq); [Fence Project Gallery SEO: Give Each Photo Context](/articles/fence-contractor-project-gallery-seo); [Fence Contractor Quote Forms: Ask Before the Site Visit](/articles/fence-contractor-quote-request-form); [Fence Material Comparison Pages: Use Product Evidence](/articles/fence-material-comparison-website-page); [Fence permit descriptions: separate a construction barrier from permanent project scope](/articles/fence-permit-description-temporary-barrier-permanent-scope); [Fence Quote Form Spam: Check the Server Controls](/articles/fence-quote-form-spam-server-validation); [Garage Door Emergency Service Pages: State the Limits](/articles/garage-door-emergency-service-website); [Garage door and fencing AI rules: data, approvals, and spend](/articles/garage-door-fence-ai-rules-data-approvals-spend); [Garage Door Opener Brand Pages: Verify the Claims](/articles/garage-door-opener-brands-website-page); [Garage Door Recall Pages: Link the Official Notice](/articles/garage-door-opener-recall-website-page); [Garage Door Repair and Installation: Plan Both Pages](/articles/garage-door-repair-installation-service-pages); [Garage Door Appointment Changes: Clarify the Request](/articles/garage-door-service-reschedule-request-page); [Pool Fence Website Claims: Name the Applicable Rules](/articles/pool-fence-contractor-website-claims). [garage door and fencing contractors](/for/garage-door-and-fencing-contractors): website and search resources. ## Related: garage door and fencing contractors - [AI-native garage door and fencing firms: first functions](/articles/ai-native-garage-door-fence-first-functions) - [Fence Permit FAQs: Use the Right Local Source](/articles/fence-contractor-permit-website-faq) - [Fence Project Gallery SEO: Give Each Photo Context](/articles/fence-contractor-project-gallery-seo) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```