PJM Site Control Deficiency Response Guide

How to use this guide

This guide covers every site control deficiency type PJM can issue under the Cycle 1 Application Review Phase process established by OATT Part VII, Subpart A, Section 302 and PJM Manual 14H Section 7. For each type you will find: the trigger condition, whether the deficiency is fatal (cannot be cured after the application window closes) or curable (fixable within the 10-business-day response window), and the exact document or action needed to cure it.

One critical threshold to understand first: FERC Order 2023 requires 90% site control at application. PJM's Manual 14H requires 100%. A developer who reads the federal order and stops at 90% will receive a deficiency notice from PJM. This divergence accounts for a meaningful share of Cycle 1 deficiencies and is entirely avoidable.

The response window is 10 business days from receipt of the deficiency notice. The clock starts on receipt, not on acknowledgment. After the window closes, most site control deficiencies become fatal: the application is withdrawn and the project must reapply in the next cycle.

What HyperQ checks (and how it flags)

PJM's Application Review Phase for Cycle 1 uses HyperQ, an agentic AI system built by Tapestry (Alphabet X) on Google's Gemini models. For the first time in PJM's history, initial application review is completed in minutes rather than weeks. Understanding how HyperQ reads your package helps you anticipate what will be flagged.

HyperQ performs five specific checks on site control submissions:

1. Legal land rights verification. HyperQ reads the instrument language directly and validates that the developer holds a qualifying property right — deed, lease, option to lease or purchase, or other PJM-acceptable instrument — over an area large enough for the proposed project. It checks that the three-part test (conveyance, term, exclusivity) is satisfied simultaneously.
2. Acreage adequacy cross-reference. It compares the acreage covered by submitted instruments against the technology-specific density thresholds (5 acres/MW solar, 30 acres/MW wind, 1 acre/100 MWh storage, 10 acres/facility synchronous). A shortfall triggers a density deficiency flag.
3. Document clustering for multi-amendment packages. HyperQ groups related documents — original lease, first amendment, second amendment, memorandum, SNDA — into a single "agreement bundle" and reads them as a unified whole. This prevents the error where an amendment modifies the acreage or term, but a reviewer reading only the original instrument reaches the wrong conclusion. Missing amendments in a package are themselves a flag.
4. Signature verification (visual). HyperQ uses multimodal AI to identify signatures and their placement on documents. A missing wet signature on the Officer Certification or on a landowner attestation is flagged visually, not just via text extraction.
5. Citation anchoring. For every conclusion, HyperQ must cite a specific page and paragraph of the application as evidence. This means PJM's deficiency notice will reference the exact location in your submission where the issue was identified. Read that citation first when you receive the notice — it tells you precisely what HyperQ evaluated and where.

What HyperQ cannot do: it cannot determine whether a landowner has properly recorded an instrument with the county, cannot access lien databases in real time, and cannot evaluate the legal enforceability of complex contractual structures. These are areas where developer counsel remains essential.

Fatal vs. curable summary table

* Entity mismatch is curable if assignment documents exist and can be executed within 10 BD. If the instruments prohibit assignment without landowner consent that cannot be obtained quickly, it becomes practical-fatal.

1. Coverage Gap (Insufficient Acreage)

Trigger: The sum of acreage covered by executed, qualifying instruments is less than 100% of the project boundary submitted in the GIS file. PJM calculates coverage as: qualifying instrument acreage ÷ project boundary acreage = coverage ratio. Any ratio below 1.0 (100%) is deficient.

Why PJM is stricter than FERC: FERC Order 2023 set a minimum threshold of 90% site control at application. PJM's Manual 14H requires 100%. A developer who reads the federal order, assembles instruments covering 93% of the project boundary, and submits — confident they meet the FERC minimum — will receive a deficiency notice from PJM. This single divergence accounts for a disproportionate share of preventable deficiencies.

Common sub-patterns:

• Setback buffer not covered. State law requires setbacks of 50–300 feet from property lines (Virginia: 50–100 ft; Maryland: up to 300 ft; Pennsylvania: up to 300 ft depending on county; Ohio: 75 ft from property line or turbine height +10%). The project boundary in the GIS file must include these setback areas, and site control instruments must cover them — including areas where no equipment is placed.
• Parcel fringe gap. An instrument covers an entire parcel, but the GIS project boundary extends slightly into an adjacent parcel not under contract. A gap of even a few feet triggers this deficiency.
• Multi-project overlap. The same parcel acreage is submitted for two interconnection applications — whether both in PJM, or one in PJM and one in a neighboring RTO. PJM cross-references its own queue and, in some cases, adjacent RTO submissions. Duplicate acreage across applications triggers automatic termination of all affected requests under OATT §302.

Cure (pre-window close only): Execute new instruments covering the gap parcels before the application deadline. Post-window, no cure is available for a coverage gap. At Decision Points I or II, a developer may add adjacent parcels if site control for both the original and new area is demonstrated simultaneously; non-adjacent parcels require recorded easements between the two areas (Manual 14H §7.2.2).

OATT Part VII, Subpart A, §302(A)(3)   Manual 14H §7.1   Manual 14H §7.2.2

2. Disqualified Instrument Type (LOI / MOU)

Trigger: The developer submits a letter of intent, memorandum of understanding, term sheet, letter of authorization, or similar document as evidence of site control for a parcel. OATT §302 explicitly states that "memorandums and documentation solely evidencing an intent to purchase or control a Site" are not acceptable.

What qualifies: The only four instrument types accepted under OATT §302 are: (1) deed (fee simple ownership); (2) executed lease; (3) executed option to lease or purchase; (4) any other instrument that PJM determines grants a qualifying property right — in practice, recorded easements for generation facility footprints. A memorandum of lease does not satisfy this requirement; the full executed lease is required.

Common mistake — rights-of-way: ROW agreements are acceptable for interconnection facilities up to the Point of Interconnection, but do not satisfy the generation site control requirement for the generating facility footprint.

Cure (pre-window close only): Replace the disqualified instrument with a fully executed qualifying instrument before the application deadline. Because landlords sometimes resist executing a full lease or option without LOI stage negotiations, the practical fix is to negotiate and execute the binding instrument before the application window opens, not after it closes.

OATT Part VII, Subpart A, §302 (explicit prohibition on memorandums and intent-only documents)

3. Encumbrance / Missing SNDA

Trigger: A parcel covered by a submitted instrument has a recorded mortgage, deed of trust, agricultural easement, conservation easement, or other senior encumbrance that was not disclosed and not subordinated via an executed SNDA agreement. PJM cross-references title records when reviewing site control packages; undisclosed encumbrances are typically caught during the Application Review Phase.

Why it matters: An encumbered parcel creates a risk that the lender could foreclose and extinguish the developer's lease. Without an SNDA, the developer's rights are subordinate to the lender's — meaning foreclosure voids the lease. PJM requires that the developer's site control rights survive any such action.

What an SNDA requires: A Subordination, Non-Disturbance, and Attornment agreement executed by the landowner's lender must include three elements:

• Subordination: The lender acknowledges the developer's lease and agrees it is a recognized interest in the property.
• Non-Disturbance: The lender agrees that if it forecloses, it will not disturb the developer's possession rights under the lease.
• Attornment: The developer agrees that if the lender acquires the property through foreclosure, it will recognize the lender as the new landlord.

Lead time warning: Agricultural and rural lenders — which hold the mortgages on most parcels in PJM's service territory — typically require 60–90+ days to process an SNDA request. They route it through legal counsel, require board approval in some cases, and may negotiate terms. An SNDA request initiated after receiving a deficiency notice will not be processed in time to cure. The practical rule: identify all encumbered parcels during due diligence and initiate SNDA requests at least 90 days before the application window opens.

Conservation and agricultural easements: Recorded conservation easements (held by land trusts) and USDA agricultural program easements (CRP, WRP, RCPP) create senior rights that may prohibit the uses required for a generation facility. Many rural landowners are unaware of these restrictions. A title search against every parcel before signing the lease is the only reliable way to identify them.

OATT Part VII, Subpart A, §302   Manual 14H §7.1.4

4. Wet Signature Missing or Deficient

Trigger: The Officer Certification or a required landowner attestation is signed via DocuSign, electronic signature platform, or other digital method, and PJM's review (or HyperQ's visual inspection) flags the absence of a physical wet signature. There is no explicit OATT provision requiring wet signatures for all instruments, but the Officer Certification has historically required a wet signature from an officer of the Project Developer entity, and HyperQ performs visual signature detection as a standard check.

HyperQ's specific check: HyperQ uses multimodal AI (it "sees" documents, not just extracts text) to identify signature blocks and confirm that signatures are present. It can distinguish a signed page from an unsigned page. A certification packet where the officer signature page is blank — even if the rest of the package is complete — will be flagged.

Sub-types:

• Officer Certification unsigned. The certification form was prepared but the signing officer has not yet executed it, or the signature page was omitted from the upload.
• Wrong signatory. The form was signed by an authorized representative rather than an officer of the Project Developer entity. PJM's Officer Certification template specifies that the signatory must be an officer (President, CEO, VP, or equivalent), not an agent, attorney, or project manager.
• Digital signature only. Instruments in some states are legally valid with electronic signatures, but PJM's review practice has historically preferred wet signatures for the Officer Certification specifically.

Cure: Re-execute the affected document with a wet signature from a qualifying officer of the correct entity, dated within the cure window, and resubmit through Queue Point. Update the Officer Certification date to reflect the cure-window re-execution — a certification dated before the cure window may itself be flagged as stale.

Manual 14H §7 — Officer Certification template

5. GIS / Parcel Boundary Mismatch or APN Error

Trigger (GIS mismatch): The boundaries in the submitted KML/KMZ or shapefile do not match the property boundaries described in the underlying site control instruments. Even a discrepancy of a few feet triggers a mismatch flag, because HyperQ cross-references the instrument's legal description against the GIS file boundaries. Common causes:

• KML drawn from satellite imagery rather than county parcel data — satellite-derived boundaries can deviate 5–30 feet from actual recorded parcel lines.
• GIS file includes adjacent parcels for visual context, which inadvertently expands the depicted project boundary beyond the area covered by instruments.
• Road rights-of-way, utility corridors, or drainage easements bisect the project boundary but are not separately addressed in the instrument package.
• Collector substation, gen-tie route, or POI switchyard footprint is not drawn as a distinct boundary layer when the instruments covering those areas differ from the main generation site instruments.

Trigger (APN error): The Assessor's Parcel Number listed in the parcel table (M-3.1S or its successor) does not match the county's format or refers to the wrong parcel. PJM requires APNs in the county's exact format. A parcel formatted as 123-456-789 in a county that uses 123.456.789 will produce a mismatch. The parcel table must also match the county and state to the APN precisely.

Trigger (acreage discrepancy): The acreage stated in the instrument says "approximately 50 acres" but the county assessor record shows 47.3 acres, creating a potential coverage shortfall. PJM will use the lower figure unless a PE-stamped survey resolves the discrepancy.

Cure:

1. Regenerate the GIS file from county parcel data (not satellite imagery), confirming that all boundaries match executed instrument descriptions.
2. Correct all APN entries in the parcel table to match the county's exact format, verified against the county assessor's database.
3. If acreage is disputed, submit a PE-stamped survey or a PE-stamped site plan certifying the correct acreage.
4. Resubmit the corrected GIS file (KML or KMZ preferred) and updated parcel table through Queue Point within the 10 BD window.

Manual 14H §7.1.5   OATT §302(A)(3) (adequacy verification requirement)

6. Exclusivity Failure (Including Tenancy-in-Common Gap)

Trigger: The submitted instrument does not demonstrate exclusive right of the Project Developer to occupy and use the site. OATT §302(A)(8)(b) requires "written acknowledgment from the landowner" confirming the developer has "exclusive use of the Site for the Term" and the landowner "cannot make the Site Control available to any other entity for any purpose that will interfere with the rights granted to Project Developer."

The tenancy-in-common (TIC) problem — the most dangerous exclusivity trap in PJM territory: A tenancy-in-common is a form of co-ownership where multiple parties each hold an undivided interest in the property. In rural mid-Atlantic states, TIC ownership is endemic in multi-generational inherited farmland. A parcel in Pennsylvania, Virginia, or Maryland may have 5–15 co-owners, some of whom may not know they own it, may live in other states, or may be deceased with unsettled estates.

OATT §302 requires "written acknowledgment from the landowner" — legally interpreted to mean all owners. A lease signed by 2 of 3 co-owners provides zero site control coverage for that parcel. The co-owner who did not sign retains an undivided interest that gives them the right to use, occupy, and potentially grant competing rights to the same parcel.

Why this is fatal in practice: Identifying and locating all TIC co-owners requires a full title search plus skip-tracing. Negotiating with multiple co-owners — some of whom may be contentious or unreachable — takes months. Probate proceedings to clear an estate interest can take 6–18 months. A developer who discovers a TIC issue after submitting an application has no path to cure within 10 business days.

Other exclusivity failures:

• Non-exclusive easement: an easement that expressly states it is non-exclusive, or that grants competing rights to third parties over the same footprint.
• Shared-use lease: a lease that permits the landowner to continue farming or granting hunting/grazing rights that could interfere with construction or operations.
• Prior option or right of first refusal: a previously executed option agreement or ROFR in favor of a third party that could supersede the developer's instrument.

Cure (pre-filing only):

• For TIC co-ownership: execute instruments with all co-owners. If a co-owner is deceased, initiate probate proceedings. If co-owners are contentious, consider a partition action (long-lead, litigation risk).
• For non-exclusive easements: negotiate and execute a replacement exclusive easement, or execute a supplemental agreement with the landowner expressly prohibiting competing grants.
• For prior options/ROFRs: confirm they have lapsed, obtain written release from the option holder, or confirm they apply to fee sale only (not to a leasehold).

OATT §302(A)(8)(b) (exclusivity requirement)

7. Officer Certification Error

Trigger: The Officer Certification has one of three sub-errors that PJM's review (and HyperQ's document analysis) flags as a deficiency:

• Wrong entity. The certification is signed by an officer of the parent company, holding company, or development entity, rather than an officer of the Project Developer entity named in the Application and Studies Agreement. Even if the parent is the ultimate guarantor, the certification must be in the exact name of the Project Developer SPV or entity on the ASA.
• Stale or inconsistent dates. The certification date predates the most recently executed amendment to any of the submitted instruments. PJM treats a pre-amendment certification as evidence that the certifying officer did not review the as-filed materials. HyperQ cross-references the Officer Certification date against the execution dates on all instruments in the package and flags cases where the certification is earlier than the most recent instrument.
• Wrong template. An older Officer Certification template from a Transition Cycle application, or a custom attestation drafted by counsel, was used instead of PJM's current published template. The template changes with Manual revisions; the July 2025 update included structural changes to the certification language.

Cure: Obtain PJM's current Officer Certification template from its website. Execute a new certification: (a) in the name of the Project Developer entity on the ASA; (b) signed by a qualifying officer (President, CEO, VP, General Counsel, or equivalent); (c) dated on or after the execution date of the most recently executed instrument in the package; and (d) explicitly referencing the documents being certified by filename and execution date. Resubmit through Queue Point with a cover letter identifying the specific deficiency item being cured.

Manual 14H §7 — Officer Certification template   Manual 14H Rev. per July 23, 2025 MRC update

8. Entity Mismatch (Applicant ≠ Instrument Grantee)

Trigger: The Project Developer entity named in the interconnection application and ASA differs from the entity named as grantee on the site control instruments. PJM's tariff is explicit: evidence of site control "must be from the same company name that is providing the New Service Request."

Common scenarios:

• Site control was assembled in the name of the development company, then an SPV was formed to hold the project and file the application. The instruments remain in the parent's name.
• The developer restructured, changed its legal name, or merged after executing the instruments. The instruments reflect the old entity name.
• A project was transferred between development companies; instruments are in the prior developer's name with no recorded assignment.

Cure:

1. Execute an assignment of site control instruments from the current grantee entity to the Project Developer entity. Most leases and options require written notice to (and sometimes written consent from) the landowner for a valid assignment.
2. If the instruments prohibit assignment, execute new instruments in the correct entity's name.
3. Prepare an organizational chart or corporate resolution demonstrating the legal relationship between the entity on the instruments and the Project Developer entity.
4. Submit the executed assignment and organizational documentation with the Officer Certification to Queue Point within 10 BD.

Watch for consent requirements: Many agricultural leases include anti-assignment clauses requiring the landowner's written consent. If the landowner is unresponsive or contentious, the assignment may not be executable within 10 business days, converting this deficiency from curable to practical-fatal.

OATT §302   Manual 14H §7.1.2

9. Term Deficiency (Option Expiration Before Decision Point III)

Trigger: An option to lease or purchase has an initial term that expires before the developer would reach Decision Point III (Grid Interconnection Agreement execution, projected 2028–2029 for Cycle 1 projects). OATT §302 requires that the instrument run for the term necessary at each milestone. At DP III / IA execution, instruments must have a minimum 3-year remaining term.

The extension trap: OATT §302(A)(8)(a) states that extensions satisfy term requirements only if those extensions have been "exercised and any requisite conditions fulfilled, including any payment obligations, by the Project Developer at the time evidence of Site Control is provided." An unexercised option extension — even if available — does not satisfy term requirements. The developer must actually exercise the extension (and pay any associated option payment) before submitting as evidence.

Cycle 1 timeline math: PJM projects IA execution for Cycle 1 in 2028–2029. An option submitted at application (April 2026) with an initial 2-year term and no extensions expires April 2028 — before projected IA execution. Even if the option has a developer-exercisable 3-year extension, that extension must be exercised to count.

At application vs. at Decision Points: A term deficiency at application that does not affect the 1-year minimum required at submission may not generate an immediate deficiency notice, but will produce a fatal deficiency at DP III if not resolved. PJM tracks instrument terms through the cycle and will flag expirations at each milestone.

Cure:

• For options with available extensions: exercise the extension and provide PJM with evidence of exercise (executed extension agreement + payment confirmation) before the relevant Decision Point.
• For options with insufficient total term: renegotiate for a longer term or convert to an executed lease before DP III.
• Planning rule: begin option conversion planning at least 12 months before projected IA execution. For Cycle 1 projects, this means initiating conversion discussions no later than Q1 2027.

OATT §302(A)(8)(a) (term and extension exercise requirements)

10. Technology Density Failure

Trigger: The total acreage covered by qualifying instruments, as measured against the Manual 14H technology-specific density requirements, is insufficient for the stated nameplate capacity. OATT §302(A)(3) states that failure to verify adequate acreage "shall result in the New Service Request being deemed terminated and withdrawn." This is one of the few explicitly terminal deficiency categories in the tariff text.

The PE-stamp cure: If a developer believes their project can achieve a higher panel density or smaller footprint than the standard density table implies — for example, using a bifacial single-axis tracking layout at a higher MW/acre density — they may submit a PE-stamped site plan drawing, signed by a Professional Engineer licensed in the state of the facility, showing the proposed generation arrangement and specifying the Maximum Facility Output (MFO) for that configuration. The PE seal must be from a PE licensed in the facility state; a neighboring-state PE seal is not curative.

The MW reduction option: A developer can reduce the stated nameplate capacity in the application to match the available acreage. A 100 MW solar project with 420 acres of qualifying instruments — which covers only 84 MW at 5 acres/MW — can be resubmitted as an 84 MW project. This reduces study deposits and changes the network upgrade cost profile but preserves the application position.

Cure:

1. Add adjacent qualifying parcels to bring total acreage to the required density (must be done pre-window close at application; at DP I with adjacency documentation).
2. Submit a PE-stamped site plan demonstrating higher-density feasibility for the stated MW.
3. Reduce the stated MW to match the qualifying acreage and resubmit the application within the cure window.

OATT §302(A)(3) (termination consequence for density failure)   Manual 14H §7.1.6

Assembling the Response Packet

A deficiency response is not a letter. It is a structured re-submission to Queue Point that includes cured documents, an updated parcel attestation, and a cover letter that maps each cure to the specific deficiency item in the notice. Follow this structure:

1. Cover letter. One PDF addressed to the assigned PJM Project Manager. Number each deficiency item from the notice. For each item, identify: (a) the nature of the deficiency as you understand it; (b) the cure document by filename; (c) the Queue Point upload location. This is the roadmap PJM's reviewer uses. A cover letter that requires the reviewer to hunt through documents to confirm a cure is being addressed will slow validation.
2. Cured site control instruments. The replacement lease, option, amendment, recorded assignment, or executed SNDA — as applicable to each deficiency type. Instruments that are in good order do not need to be resubmitted.
3. Refreshed Officer Certification. A new certification dated within the cure window, in the Project Developer entity's name, referencing the cured documents by filename and execution date. Even if the original certification was not itself deficient, redate it to certify the cured package.
4. PE-stamped site plan (if density or acreage deficiency applies). The PE seal must be from a PE licensed in the facility state.
5. Corrected GIS file. KML or KMZ with boundaries reflecting the cured instrument package. Site boundary, collector substation, interconnection switchyard, and POI must all be present and accurately drawn from parcel data.
6. Updated parcel table. Correct all APN format errors, acreage discrepancies, and entity name fields.

Large files go to IPSecureShare@pjm.com with the project queue number in the subject line and body. Standard documents upload through Queue Point under Existing Requests > Supporting Documents. File naming convention: [QueueNumber]_Deficiency_Cure_[YYYYMMDD]_[DocType].pdf.

The 10 business day window does not stop for PJM responses to clarifying questions. If you ask PJM a question about the deficiency notice on Day 3, you still have only until Day 10 to submit the response packet — not Day 10 from when PJM responds. Submit the best available response within the window, then escalate any disputes after the fact.

Sources

• PJM OATT Part VII, Subpart A, Section 302 — Site Control (current version, Docket ER24-2398-000, effective Aug 28, 2024)
• PJM Manual 14H: New Service Requests Cycle Process, Revision 03 — Sections 6, 7, 7.1–7.3, 8, Attachment Q
• Manual 14H Site Control Changes — July 23, 2025 MRC Presentation
• Manual 14H Revisions — March 19, 2025 MRC Presentation
• FERC Order 2023 — Interconnection Final Rule explainer
• FERC Order No. 2023 (July 28, 2023)
• PJM Inside Lines: 811 Projects, 220 GW in Cycle 1 (April 29, 2026)
• Tapestry: How Agentic AI Can Help Grid Operators Speed Up Interconnection (HyperQ white paper)
• Latitude Media: Tapestry is using AI to help PJM clear its interconnection backlog
• PJM Public Knowledge: New Generator Interconnection Site Control

Related resources

• All Free Developer Resources
• PJM Cycle 1 Deficiency Notice: How to Respond (procedural playbook)
• PJM Manual 14H Site Control: Section-by-Section Analysis
• PJM Cycle 1 Submission Toolkit (free download)
• FERC Order 2023 Site Control Thresholds by RTO