PJM Cycle 1 Deficiency Notice: How to Respond and the 5 Most Common Site Control Reasons Projects Get Flagged

The deficiency notice nobody plans for

Every developer filing a Cycle 1 application by the Sunday, April 27, 2026 deadline will land inside a 15-business-day window during which PJM may issue a Notice of Deficiency. The notice is not a rejection. It is a procedural starting gun for a 10-business-day clock that determines whether your application is validated, rejected, or terminated outright.

Because the cycle-based process is new under FERC Order 2023, very few teams have run the cure-period playbook in production. The procedure is set forth in PJM Manual 14H Section 7 and Tariff Part VII, Subpart C, Section 306(B). Both make a single point clear: missing the 10-business-day window is a project-killing event. There is no extension, no good-faith carveout, no sympathetic reading of the Tariff. The clock either runs out or it does not.

This article is the operational guide we wished existed for our customers in March. It covers what a PJM deficiency notice looks like, how the cure-period clock works under Tariff Part VII, Subpart C, what to put in the response packet, the five site control deficiency patterns we expect to dominate Cycle 1 notices, and the decision framework for cure vs withdraw vs reapply in Cycle 2.

What a PJM deficiency notice actually is

A Notice of Deficiency is PJM's formal determination that one or more elements of an application are missing, incomplete, or non-compliant with the Tariff. It arrives by email from your assigned PJM Project Manager. It identifies each deficient element and references the underlying Tariff or Manual section.

The notice does not reject the application on issuance. It opens the Application Review Phase — the procedural window during which you can cure the deficiency and earn validation. The Application Review Phase is the same procedure used for Reliability Resource Initiative (RRI) applicants and for any New Service Request that enters the cycle process.

Three timing facts govern the entire window:

• 15 Business Days — PJM's window to issue any deficiency notice after the close of the Application Deadline. PJM exercises "Reasonable Efforts" to meet this window but the deadline is a soft target, not a hard cap.
• 10 Business Days — the developer's window to respond. This is a hard cap. Failure to respond results in termination.
• 15 Business Days — PJM's window to validate or reject the application after receiving the response. Validation moves the project into Phase I. Rejection ends Cycle 1 participation.

The cure-period clock, day by day

The clock starts on the day the deficiency notice is received — not the day it is acknowledged, opened, or escalated to counsel. Receipt is documented by PJM's outbound email timestamp. The 10-business-day window excludes federal holidays and weekends but includes every other day, including the day of receipt itself in some readings of the Tariff. The conservative practice is to treat receipt day as Day 1.

This means a notice issued on Tuesday, May 5, 2026 would have a response deadline of Tuesday, May 19, 2026 (10 business days later, assuming no intervening federal holiday). A notice issued on Friday, May 8 would have a deadline of Friday, May 22.

Day	Action	Owner
Day 0	Application Deadline closes (Sunday, April 27, 2026)	Developer
Day 1–15 (BD)	PJM completeness review; deficiency notice issued if applicable	PJM
Day 1 of cure	Notice received; cure clock starts	Developer
Day 1–10 (BD)	Developer cures deficiency and submits response packet via Queue Point + IPSecureShare	Developer
Day 11+ (BD)	PJM reviews response (up to 15 BD); validates or rejects	PJM

The window does not pause for negotiation. It does not pause if PJM responds late to a clarifying question. It does not pause if the deficiency notice itself contains an error. If the cure clock is running and you believe the notice is wrong, you must still respond on schedule with the best evidence you have, then escalate the dispute through PJM's Interconnection Process Subcommittee after the fact.

The 5 site control deficiency patterns most likely to flag your project

Site control is historically the leading source of deficiency findings under the cycle process. PJM's July 2025 Manual 14H site control update (FERC Docket EL25-22-000 and ER25-1544-000, accepted June 10, 2025) added new requirements specifically because the prior cycles surfaced repeating failure modes. The five patterns below account for the majority of site control deficiency notices we expect Cycle 1 applicants to receive.

1. Acreage that does not satisfy the Manual 14H density rules

Manual 14H now specifies minimum acreage per technology type. If your site plan does not satisfy these densities or you have not provided a PE-stamped layout drawing showing how a denser configuration is feasible, the application is deficient.

Technology	Required Acreage	Source
Solar	5 acres/MW	Manual 14H Section 7.1.6
Wind	30 acres/MW	Manual 14H Section 7.1.6
Battery Storage	1 acre per 100 MWh	Manual 14H Section 7.1.6
Synchronous Generator	10 acres per facility	Manual 14H Section 7.1.6

If your project density exceeds these allowances, the deficiency cure requires a PE-stamped Site Plan, signed by a Professional Engineer licensed in the state of the facility, showing the proposed generation arrangement and specifying the Maximum Facility Output (MFO). A drawing stamped by a PE in a neighboring state is not curative. The seal must match jurisdiction.

2. Officer Certification missing, expired, or signed by the wrong entity

The Site Control Officer Certification is a sworn attestation, executed by an officer of the Project Developer entity, verifying the accuracy of the site control evidence and certifying that the developer will exercise commercially reasonable best efforts to achieve the milestones in the Critical Path Construction Schedule. PJM's slide deck is explicit: applications without the attestation are considered incomplete.

Three sub-patterns produce deficiency notices:

• Wrong entity. The Officer Certification must be in the name of the Project Developer entity, not the parent company. A certification signed by a parent or holding company will be flagged even if the parent is the ultimate guarantor.
• Stale dates. The certification must reflect the same site control documents being submitted in the application. A certification dated before the most recent lease amendment is treated as evidence that the executive did not certify the as-filed materials.
• Wrong template. PJM publishes the current Officer Certification template on its website. Earlier versions, including any used during Transition Cycle 1 or RRI, are not interchangeable.

3. Company-name mismatch between Project Developer and Site Control instruments

The Project Developer entity named in the Application and Studies Agreement (ASA) must match the entity named on the deed, lease, option, or easement. When they do not, PJM requires evidence of the relationship between the entity controlling the Site and the Project Developer — typically a written assignment, joinder, or an internal corporate resolution.

This pattern is common when site control was assembled through a development LLC, then assigned to a project-specific SPV after financing. If the assignment was executed but never recorded against the lease or option, PJM has no document trail to verify the relationship and will flag it.

4. Site Control evidence types that do not qualify under Tariff Part VII Subpart A Section 302

Several document types are explicitly disqualified at the Application Phase even though they look like site control to a developer's land team:

• Memoranda — a memorandum of lease or memorandum of understanding does not by itself satisfy Section 302. The full executed instrument is required.
• Letters of intent or evidence of intent to purchase — intent is not exclusivity, and exclusivity is the foundation of the Section 302 standard.
• Site control for a property already used for an interconnection request in an adjacent RTO — the same parcel cannot underwrite two interconnection applications across markets. PJM cross-references against neighboring RTO queues during review.
• Evidence with a term of less than one year from the Application Deadline — the minimum term is one year. A 364-day option dated April 28, 2026 is deficient.

These rules are the operational application of the exclusivity, term, and conveyance triad that defines Section 302 site control.

5. GIS files that do not match the lease boundaries

Every Application requires both a PE-stamped Site Plan and a GIS data file (Google Earth KML or KMZ preferred, ESRI shapefile accepted). The boundaries in the GIS file must match the property boundaries described in the underlying site control instruments. When they do not — even by a few feet — PJM treats the discrepancy as evidence that the site control is not consistent with the modeled project footprint.

The most common failure modes are: KMLs drawn from satellite imagery rather than parcel data, KMLs that exclude road right-of-ways used for interconnection facilities, and KMLs that include neighboring parcels for visual context but accidentally inflate the site footprint.

What goes in the response packet

A deficiency response packet is not a letter. It is a re-submission to Queue Point with cured documents, accompanied by an updated Site Control Review Spreadsheet and a cover letter that maps each cure to the specific deficiency item. Use the same Existing Requests > Supporting Documents tabs in Queue Point that were used for the original application. Large files go to IPSecureShare@pjm.com with the project reference number conspicuously marked.

A complete response packet contains, at minimum:

1. Cover letter. One PDF, addressed to the assigned PJM Project Manager, with a numbered list mapping each deficiency item from the notice to the cured document filename and Queue Point upload location.
2. Cured site control documents. The corrected lease amendment, joinder, recorded assignment, or replacement instrument. If a memorandum was originally filed, the full executed instrument now replaces it.
3. Refreshed Officer Certification. A new attestation, dated within the cure window, signed by an officer of the Project Developer entity, referencing the cured documents by filename and date.
4. PE-stamped Site Plan if the deficiency relates to acreage density or layout. The seal must be from a PE licensed in the facility state.
5. Corrected GIS files. KML or KMZ with boundaries that exactly match the cured site control. Site boundaries, collector substation, interconnection switchyard, and POI must all be present.
6. Updated Site Control Review Spreadsheet — both the Document Details tab and the Application Review Phase tab.

Save the cover letter as [Queue#]_Deficiency_Response_[YYYYMMDD].pdf. PJM staff handle hundreds of submissions during the review phase. Filename hygiene is not pedantry — it is the difference between getting reviewed inside the 15-business-day window and being deprioritized.

Cure vs withdraw vs reapply: a decision framework

Not every deficiency is curable inside 10 business days. Some require a recorded amendment that will not be on file in time. Some require a replacement lease that the landowner refuses to execute under pressure. The decision is not binary; it is a comparison of three forward paths with materially different financial and timing consequences.

Cure (the default)

Cure when (a) the deficiency is documentary or formatting (wrong template, mismatched names, missing seal), and (b) the underlying site control is real and curable inside 10 business days. The Study Deposit and Readiness Deposit you posted at application remain at risk through Phase I, which is the lowest-friction path to validation.

Withdraw before validation

Withdraw before validation when the deficiency is structural — the project does not actually have 100% site control coverage, the layout cannot fit the MFO under Manual 14H density rules, or a critical landowner has revoked exclusivity since application. Voluntary pre-validation withdrawal returns the Readiness Deposit in full and the Study Deposit less actual cost, per OATT Part VII, Subpart A, Section 302 and Manual 14H Section 6. The financial recovery is materially better than letting PJM reject the application after the cure window expires.

Reapply in Cycle 2

Reapply when the project is real but the site control work cannot be completed inside the cure window. The cost is a 12 to 18 month delay before re-entering the queue, plus a fresh Study Deposit and Readiness Deposit at Cycle 2 application. The benefit is a full year to assemble a clean package and to address the failure mode that caused the original deficiency. Many of the strongest projects we see now would have benefited from this discipline in TC1.

Path	Time Cost	Financial Outcome	When to Choose
Cure inside 10 BD	None	Deposits remain at risk through Phase I	Documentary or formatting deficiency
Withdraw pre-validation	One cycle (12–18 mo)	Readiness refunded in full; Study refunded less actual cost	Structural deficiency; cannot cure in time
Let PJM reject	One cycle (12–18 mo)	10% of Study Deposit non-refundable; Readiness refunded	Almost never — voluntary withdrawal is strictly better
Reapply in Cycle 2	One cycle (12–18 mo)	New Study + Readiness deposits required	Project is real but needs more time

What changes between Application and Decision Point I

The Site Control package submitted at application establishes the initial Site. PJM's Manual 14H Section 7.2.1 makes the comparison rule explicit: future submissions at Decision Point I will be measured against the parcels submitted at application. This has two practical implications for any developer responding to a deficiency notice.

First, your response cannot expand the Site beyond the parcels in the original application. You can supplement evidence on existing parcels, you can substitute one form of instrument for another (a recorded lease replacing a memorandum), and you can correct boundaries that were misdrawn in GIS. You cannot add parcels that were not in the original submission.

Second, the parcels you submit during cure become the comparison baseline at DP1. Any DP1 additions must be either adjacent to the cured Site or covered by a recorded easement to the cured Site. Section 7.2.2 of Manual 14H sets this rule and the July 2025 update reinforced it. A developer who rushes a deficiency response with a smaller Site footprint, intending to expand at DP1, may discover at DP1 that the desired expansion parcels are non-adjacent and ineligible.

Glossary

• Application Review Phase — The procedural window after the Application Deadline during which PJM reviews completeness, issues deficiency notices, and validates or rejects applications. Defined in Tariff Part VII, Subpart C, Section 306(B).
• ASA — Application and Studies Agreement. The executed agreement between Project Developer and PJM that governs participation in a New Service Request cycle.
• Cure period — The 10 Business Day window during which the Project Developer may respond to a Notice of Deficiency.
• Decision Point I (DP1) — The first formal go/no-go milestone after Phase I results, at which the Project Developer commits to continuing in Phase II or withdraws.
• IPSecureShare — PJM's secure file-transfer endpoint (IPSecureShare@pjm.com) used for large attachments outside Queue Point.
• M-3.1S — The site control attestation language formerly required under PJM's pre-cycle process. Now folded into the Officer Certification template.
• MFO — Maximum Facility Output. The peak generation capacity of the facility, used to compute density requirements and study deposit tiers.
• Notice of Deficiency — PJM's formal written determination that an application is incomplete or non-compliant. Issued during the Application Review Phase.
• Officer Certification — The sworn attestation by an officer of the Project Developer entity, verifying site control accuracy and committing to the Critical Path Construction Schedule.
• Queue Point — PJM's online application submission system. Located inside the Planning Center.
• Reasonable Efforts — Tariff term meaning PJM will attempt to meet the stated timing target but is not bound to it. Applied to PJM's 15 Business Day review windows, not to the developer's 10 Business Day cure window.

What to do this week

Whether or not your deficiency notice has arrived, the next 30 business days are the most consequential of Cycle 1 for your land team. Three things to do this week:

1. Pre-stage your cure documents. Identify the three or four most likely deficiency patterns for your project. Have replacement evidence ready: corrected Officer Certification, recorded lease amendments, refreshed GIS files. Most deficiency notices are not surprises — they target known weaknesses.
2. Audit your acreage against the density rules. Run your project MW against the Manual 14H density table. If your acreage is tight, commission a PE-stamped layout drawing now. PE turnaround can be 5–10 business days — longer than your cure window.
3. Decide your withdrawal threshold. Define the conditions under which you would voluntarily withdraw pre-validation rather than try to cure. This decision is much easier to make on a clean afternoon than on Day 9 of a cure window.

Sources

• PJM Manual 14H: New Service Requests Cycle Process, Revision 03 — Sections 6 (Study and Readiness Deposits) and 7 (Site Control)
• PJM Tariff, Part VII, Subpart A, Section 302 — Site Control standard
• PJM OATT, Part VII.A 302 Site Control
• Site Control Modification Manual 14H Update, July 23, 2025 MRC presentation
• FERC Order 2023, Interconnection Final Rule explainer
• PJM Inside Lines: Cycle 1 Application Deadline announcement
• PJM Public Knowledge: New Generator Interconnection Site Control

Related articles

• PJM Site Control Requirements in 2026: The Complete Developer Guide
• Interconnection Queue Withdrawal Penalties by RTO
• FERC Order 2023 Site Control Coverage Thresholds by RTO and Stage