--- title: "NYSERDA pipeline: application age and completion cohorts" description: "Read NYSERDA application ages, snapshot status, and program closeout dates. Compare equally aged cohorts and identify when private milestones are needed." canonical: "https://scalewithsearch.com/articles/nyserda-pipeline-age-completion-cohorts" --- ## 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) # NYSERDA pipeline projects: compare application age before reading completion rates An unfinished application has had some amount of time to progress. Without that age, a completion percentage can compare mature projects with applications submitted only recently. Start with the dates and observation cutoff before deciding what a pipeline count means. The [NYSERDA Solar Electric Programs dataset](https://data.ny.gov/Energy-Environment/Solar-Electric-Programs-Reported-by-NYSERDA-Beginn/3x8r-34rs) contains supported projects with reported completion or pipeline status. The [publisher overview](https://data.ny.gov/api/views/3x8r-34rs/files/0e05c65f-578f-4659-b6e9-7fca7b4f8e9f?download=true) describes pipeline work as still developing and subject to change or cancellation. An active application is not a promise of a future completed installation. The [solar installation page](/for/solar-installation) addresses work from approved office records. This guide helps an installer read public application history before using it in planning. It provides no installer ranking or forecast of available work. ## Keep four source fields separate The [official dictionary](https://data.ny.gov/api/views/3x8r-34rs/files/ef6547a8-b919-4e7d-81de-201d2db0183d?download=true) gives each date and status field a different job. Preserve those meanings in any report. | Source field | Meaning for this review | | --- | --- | | `reporting_period` | Period represented by the published data | | `date_application_received` | When the program received the application | | `date_install` | NYSERDA's recognition of operation and interconnection, with application closeout | | `project_status` | Reported Complete or active Pipeline classification | The API identifier `date_install` can invite an overly narrow reading. Its displayed label is Date Completed. The definition combines program recognition and closeout with interconnected, operational status. It does not isolate the day a crew finished physical installation. The [publisher metadata](https://data.ny.gov/api/views/3x8r-34rs.json) repeats these definitions. Use the definition when naming a chart or worksheet column. "Application received to program completion" is more defensible than "crew installation duration" for this pair of dates. Also record when you retrieved the source. Retrieval time tells the reader when your copy was obtained. It does not replace the reporting period or any project's milestone date. A later download can still describe an earlier reporting period. ## Start with the question a snapshot can answer For one saved reporting period, ask how many included supported records currently carry each status. That is a status composition question. It is different from asking how many new applications arrived or how many projects completed during a month. To describe new applications, define a receipt-date interval and count qualifying records within it. To describe program completions, define the completion-date interval. Keep both event intervals separate from the reporting-period filter. A snapshot containing years of projects cannot be labeled "this month's installations" because its reporting period is recent. The [solar intelligence overview](/intelligence/solar-installation) introduces this boundary for market planning. Apply it before comparing counties or considering crew capacity. For any completion share, write the numerator and denominator in words. One possible description is "records reported Complete among included applications in this receipt-date group at the observation cutoff." That wording preserves the population and the observation limit. Do not shorten it to "success rate" without deciding what success means and what happened to applications outside the observed population. Source status alone does not answer those questions. ## Measure age at the stated observation cutoff For this guide, application age means elapsed calendar days between program receipt and the chosen cutoff. Use the same date convention throughout the comparison. A cutoff is part of the analysis definition, not a new project milestone. Choose the reporting date represented by the saved source when that date supports your comparison. Do not measure old snapshots against today's date. Doing so gives projects extra apparent observation time without updating their recorded status. For a hypothetical example, choose 2026-09-30 as the observation cutoff. A fictional application received on 2026-09-01 has 29 elapsed days of observation. A fictional application received on 2026-01-01 has 272 elapsed days under that convention. Their unfinished statuses would carry very different observation histories. Neither status identifies the cause of the unfinished work. Put applications with missing or invalid receipt dates in an unknown-age category. A receipt date after the cutoff needs investigation rather than a negative-age group. Use the same capacity, sector, territory, and program criteria across the groups where those distinctions matter. Equal age fixes one comparison problem. It does not make different projects operationally identical. ## Compare hypothetical cohorts at equal ages The following exercise uses invented counts. It describes no actual county, installer, or NYSERDA performance result. Assume comparable saved observations support each stated checkpoint. | Hypothetical application group | Included applications | Age at observation | Reported Complete | Share at that age | | --- | --- | --- | --- | --- | | Group A | 100 | 180 days | 60 | 60% | | Group B | 100 | 180 days | 55 | 55% | | Recent group C | 100 | 30 days | 10 | 10% | Groups A and B have equal observation time in this exercise. Their five-percentage-point difference describes the selected groups at 180 days. It does not identify why they differ. The result needs its group definition, sample size, and source coverage alongside it. Group C has had only 30 days. Comparing its 10% directly with the 180-day shares confuses observation time with outcome. Keep it in a recent-application section until an equally aged comparison becomes available. Suppose an earlier saved observation showed Group A at 12% after 30 days. Comparing that checkpoint with Group C's 10% would align their ages. It would still leave calendar conditions, project mix, and coverage as possible differences to investigate. For simplicity, each fictional group here starts on one receipt date. Real monthly application cohorts contain a spread of ages. State whether your checkpoint applies to each application's elapsed days or to a receipt-date interval. Avoid treating a whole calendar month as a single exact age without explaining the approximation. ## Keep recent unfinished work in the denominator An unfinished project has not yet supplied an observed program-completion date. Its future is unknown at your cutoff. [NIST's explanation of right censoring](https://www.itl.nist.gov/div898/handbook/apr/section1/apr131.htm) describes an observation ending before an event is observed. Here, the event of interest is program completion. For a reader, the useful translation is: observation stopped before the outcome was known. Dropping unfinished applications and averaging only completed projects changes the question. The result describes completed records with usable dates. It does not describe the eventual duration of every application in the original group. For example, a synthetic group of 20 applications might contain five completed records after 90 days. A duration average based on those five cannot establish the typical eventual duration of all 20. The other 15 remain unresolved at that observation point. Keep an unfinished count and an age distribution beside any completed-only duration summary. Show how many applications lack usable dates. If the available evidence cannot support an eventual completion estimate, leave that estimate unstated. This guide proposes descriptive comparisons rather than a statistical forecasting model. A more advanced estimate would require a separately defined method and defensible treatment of disappearances, revisions, and incomplete histories. A percentage alone supplies none of those decisions. ## Do not turn closeout elapsed time into utility delay The interval from program receipt to `date_install` spans two source-defined endpoints. The dictionary does not supply a standalone utility-review clock through that pair. It also does not separate crew work from other project stages. To investigate an operational delay, use the installer's own milestone record. Relevant questions include when the design was approved, permits were received, equipment arrived, and physical work finished. Utility application completeness and permission milestones need their own confirmed dates. Consider two fictional projects with the same 200-day program interval. One could have waited earlier in its development; another could have waited later. The equal total cannot distinguish those paths. Do not assign responsibility from the total alone. Keep customer promises out of this calculation. A historical program interval cannot establish a promised date for a new job. The project owner needs current dependencies and confirmations before making that commitment. For cost questions, use the separate [reported dollars per DC watt guide](/articles/nyserda-project-cost-dollars-per-dc-watt). A completion-related date can help define the cost comparison's age. It cannot establish when every element of an expected cost was agreed. ## Understand what saved snapshots add A first observation establishes what the source showed at the time you inspected it. Without an earlier comparable observation, you cannot claim that a record just entered Pipeline or just changed status. Its first appearance in your files is an observation event. Two saved snapshots can show that a consistently identified record appeared in both and had different reported values. Describe the change between those snapshots. Do not infer an exact transition time unless a source-defined event date supports it. If a record disappears, mark it absent from the later observation. Absence alone does not establish cancellation, completion, or an error. A changed filter, source revision, or coverage difference may need investigation before interpretation. The [dictionary's project identifier description](https://data.ny.gov/api/views/3x8r-34rs/files/ef6547a8-b919-4e7d-81de-201d2db0183d?download=true) also notes historical identifier treatment involving an older system. Any historical comparison needs consistent identity handling. Keep project identifiers internal to an authorized analysis rather than publishing row-level histories. Compare the same population rules, field definitions, and date conventions across saved files. A monthly snapshot taken under a new filter can otherwise appear to create movement that reflects only your selection change. ## Write the exclusions before the interpretation Prepare a short cohort note before drawing a conclusion. Name the territory, sector, capacity range, receipt-date interval, observation cutoff, and source version. State which applications enter the denominator. List missing receipt dates, completion dates before receipt, receipt dates after the cutoff, and unresolved status conflicts. Keep those counts separate from recent unfinished applications. Recent work may be valid and fully observed for its current age. Decide how absent records affect each comparison before looking at its percentage. If you cannot explain that treatment, withhold an eventual-outcome claim. A fixed original denominator and a changing observed denominator answer different questions. The [publisher overview](https://data.ny.gov/api/views/3x8r-34rs/files/0e05c65f-578f-4659-b6e9-7fca7b4f8e9f?download=true) describes coverage exclusions and unavailable legacy information. Preserve program coverage in the cohort note. Your report should not expand a supported-project source into a count of every installation. Give the responsible operations reviewer the underlying group definition and unresolved questions. Useful decisions might include gathering private milestone evidence or postponing a territory comparison. The public count does not allocate crews or rank installer competence. ## Use the demo within its observation limits The [Solar activity comparison](/tools/solar-activity-comparison) shows aggregate application-age bands at its reporting date. Those bands cover both reported statuses. They are not a time series of observed completion transitions or an equal-age completion curve. Read its snapshot choice, missingness, and withheld values before discussing the result. A withheld cell does not mean zero. The current public controls offer county and sector comparisons, rather than private project-stage diagnosis. Keep a dated explanation with every accepted comparison. The [business memory guide](/articles/business-memory-for-ai-agents-guide) describes maintaining source records and decisions outside a temporary conversation. That record lets a later reviewer understand why a recent cohort remained unresolved. Scale With Search can scope source history and approved private inputs around a defined review question. Describe the intended comparison and its human decision owner through the [written scope process](/work). Keep operational commitments with that owner. ## Source note Sources reopened on 2026.10.28: dataset `3x8r-34rs`, publisher metadata, the attached data dictionary, the attached overview, and NIST handbook section 8.1.3.1 on censoring. Dictionary attachment: `ef6547a8-b919-4e7d-81de-201d2db0183d`. No printed dictionary revision date was identified. All sample groups, counts, percentages, and dates used for arithmetic are hypothetical. No current completion rate, utility-delay estimate, installer ranking, or private milestone history was measured. Continue the website review: [AI-native solar installation: the first functions to build](/articles/ai-native-solar-installation-first-functions); [NYSERDA project costs: compare reported dollars per DC watt with a solar quote](/articles/nyserda-project-cost-dollars-per-dc-watt); [Solar brochure PDFs: decide what search should find](/articles/solar-brochure-pdf-search-indexing); [Solar installation AI rules: data, approvals, and spend](/articles/solar-installation-ai-data-approval-spend-rules); [Solar project pages: separate installed work from estimates](/articles/solar-installation-project-case-study-page); [Solar installer review requests: keep the wording neutral](/articles/solar-installer-google-review-request-process); [Solar installer local SEO: connect coverage to real proof](/articles/solar-installer-local-seo); [Solar installer videos: give each useful clip a page](/articles/solar-installer-video-website-search); [Solar installer credentials: make website claims precise](/articles/solar-installer-website-certification-claims); [Solar website FAQs: publish answers you can maintain](/articles/solar-installer-website-faq-content); [Solar installer quote form: ask for the first useful facts](/articles/solar-installer-website-quote-form); [Solar website savings claims: show the assumptions](/articles/solar-installer-website-savings-claims); [Solar website warranty page: name the actual coverage](/articles/solar-installer-website-warranty-page); [Solar repair page: separate service from installation](/articles/solar-maintenance-repair-website-page). [solar installers](/for/solar-installation): website and search resources. ## Related: solar installers - [NYSERDA project costs: compare reported dollars per DC watt with a solar quote](/articles/nyserda-project-cost-dollars-per-dc-watt) - [Solar brochure PDFs: decide what search should find](/articles/solar-brochure-pdf-search-indexing) - [Solar installation AI rules: data, approvals, and spend](/articles/solar-installation-ai-data-approval-spend-rules) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```