PJM Manual 14H: Site Control Sections Decoded (Section 7 Coverage Math, 7.2 Parcel Modification Grammar, Officer Certification)

Why Manual 14H is the document that matters

PJM's Manual 14H — New Service Requests Cycle Process is the operational manual for the cycle-based interconnection regime adopted under FERC Order 2023. The Tariff supplies the legal authority. Manual 14H supplies the day-to-day procedure: what gets filed, when it gets reviewed, what triggers a deficiency, and what cures one. Inside Manual 14H, four sections carry almost all of the site control weight — Section 5 on Application Review Phase mechanics, Section 6 on deposits and withdrawal economics, Section 7 on the substantive site control bar, and the Officer Certification template attached as part of Section 7.3.

The structure matters because the legal stack has three layers, and each layer answers a different question. Tariff Part VII, Subpart A, Section 302 sets the substantive site control bar — what site control is. Tariff Part VII, Subpart C, Sections 305 and 306 set the procedural framework — what gets filed and how PJM reviews it. Manual 14H operationalizes both, with the math, the templates, the file formats, and the timing. A developer who knows only the Tariff and not the Manual will pass the legal test and fail the procedural one.

Section-by-section map of where site control lives in M-14H

Before diving in, here is the structural map. Every Manual 14H section that interacts with site control is listed below, alongside its Tariff cross-reference and the queue stage at which it bites. Use this as the index for the rest of this article.

Section 5 — Application Review Phase mechanics

Section 5 is the procedural clock. It defines the Application Review Phase as a sequence of three windows after the Application Deadline closes: (1) PJM's 15-Business-Day completeness review and deficiency-notice issuance; (2) the developer's 10-Business-Day cure window; and (3) PJM's 15-Business-Day validation window after receiving the cure response. Section 5 inherits its procedural authority from Tariff Part VII, Subpart C, Sections 305 and 306 and applies the same mechanics to RRI applicants and to standard cycle applicants.

The clock asymmetry is load-bearing. PJM's two 15-day windows are Reasonable Efforts targets — soft caps that PJM aims for but is not bound to. The developer's 10-day window is a hard cap. Missing it terminates the application. There is no extension, no good-faith carveout, and no provisional acknowledgment. The clock starts on receipt of the deficiency notice (PJM's outbound email timestamp), runs business days only, and excludes federal holidays. Day 1 is conservatively the receipt day itself.

Section 5 also defines what counts as a "complete" application, which is the trigger for whether a deficiency notice issues at all. Completeness requires, at a minimum, the Application and Studies Agreement (ASA), the M-14H Section 7 site control package (including the Officer Certification under 7.3), the Site Plan, the GIS file (KML or KMZ preferred), the Critical Path Construction Schedule, the Study Deposit, and the Readiness Deposit. Any missing item triggers a deficiency notice; the cure window is the same 10 Business Days regardless of whether the missing item is a single signature or the entire site control package. For more on the cure-period playbook, see PJM Cycle 1 Deficiency Notice: How to Respond.

Section 6 — Withdrawal economics and the deposit ladder

Section 6 governs the financial commitment structure. It defines the Study Deposit (tiered by project size, $75K to $400K+), the Readiness Deposit ($4,000/MW capped at $2M), and the refund schedule across the three Decision Points. From a site control perspective, Section 6 matters because it sets the cost of failure: a project withdrawn for site control reasons before validation recovers most of its deposits, while a project terminated after validation pays a meaningful share of the cluster's actual study costs.

The mechanics tie back to Section 7 in two ways. First, a project that fails the Section 7 site control bar at Application receives a deficiency notice under Section 5 and, if the cure fails, is rejected with a partial deposit refund. Voluntary pre-validation withdrawal is almost always strictly better than letting PJM reject the application after the cure window expires — the Readiness Deposit is refunded in full and the Study Deposit is refunded less PJM's actual incurred cost. Second, a project that passes Section 7 at Application but fails the higher Section 7 bar at Decision Point I forfeits the entire Study Deposit and is allocated a proportional share of the cluster's network upgrade costs.

The link between site control failure and cycle exit is mechanical. There is no "site control deficiency" classification with softer financial treatment. A failure at any milestone triggers the same deposit treatment as any other failure at that milestone. The financial differentiation is by timing, not by reason. This is why Section 7's parcel modification grammar (Section 7.2) is operationally so consequential: a site control gap that surfaces after DP1 and cannot be cured within the DP1 cure window forces a withdrawal at the worst-possible point on the deposit ladder.

Section 7 — The substantive site control bar

Section 7 is the heart of Manual 14H for site control. It is divided into 7.1 (the substantive bar at Application), 7.2 (parcel modifications between Application and DP1), and 7.3 (the Officer Certification). Each subsection of 7.1 carries a specific operational rule.

Section 7.1.1–7.1.3 — Definitions

Section 7.1.1 defines the Project Developer — the legal entity making the New Service Request, which must match the entity named on the ASA, the Officer Certification, and (subject to assignment documentation) the site control instruments. Section 7.1.2 defines the Site as the aggregate of parcels submitted at Application, which becomes the comparison baseline for all future submissions under Section 7.2. Section 7.1.3 distinguishes the Generating Facility footprint (the area within which generation equipment will be installed, including setbacks, access roads, and collector lines) from the Interconnection Facilities footprint (the area for the gen-tie, switchyard, and POI infrastructure). Both footprints must be under site control. The two are often submitted as a single Site, but if Interconnection Facilities cross parcels not under control, the application is deficient even if the Generating Facility footprint is fully covered.

Section 7.1.4 — Eligible instruments (and what doesn't qualify)

Section 7.1.4 enumerates the instrument types that can carry site control:

• Deed (fee simple ownership). The strongest form. No expiration, no counterparty risk, no conversion required.
• Executed lease. A fully executed lease covering the project footprint, signed by all required owners, not expired.
• Option-to-lease or option-to-purchase. A contractual right to execute a lease or purchase the property. Accepted at full weight through the Facilities Study; excluded at IA execution. The option must be active and signed by all required owners.
• Recorded easement. A recorded easement granting the developer rights to use the property for the Generating Facility or Interconnection Facilities. Accepted at all stages, including IA execution.

Equally important is what Section 7.1.4 explicitly disqualifies:

• Letters of intent (LOIs). Intent is not exclusivity. An LOI does not satisfy the Section 302 standard.
• Memoranda of understanding (MOUs). Same reasoning. MOUs do not by themselves convey a property interest.
• Memoranda of lease (in isolation). A short recorded memorandum referencing an unrecorded full lease can establish public notice but does not by itself satisfy Section 7.1.4 unless the full executed lease is also produced.
• Internal corporate acknowledgments. A statement by a parent company that an affiliate has site control is not site control.
• Site control already attributed to a parallel queue request in another RTO. PJM cross-references against neighboring RTO queues during review.

Section 7.1.5 — The exclusivity / conveyance / minimum-term test

Section 7.1.5 articulates the substantive test inherited from Tariff Section 302. Three things must be true simultaneously:

1. Exclusivity. The Project Developer holds an exclusive right to the use of the parcel for the proposed generating facility. A non-exclusive license, a lease that reserves grazing rights to the landowner across the entire footprint, or a parallel grant to a competing developer are all disqualifying.
2. Conveyance. The right is conveyed by an instrument that creates an interest in real property — deed, lease, option-to-lease, recorded easement. Promises of future conveyance do not count.
3. Minimum term. The instrument must run for at least one year from the Application Deadline. This is a hard floor with no rounding. A 364-day option dated the day before the Application Deadline does not satisfy the test.

Section 7.1.6 — Density rules and the coverage math

Section 7.1.6 sets the density rules and the coverage arithmetic. Density rules establish a per-technology minimum acreage for the project's MFO; if the project's modeled acreage is below the density floor, the layout is presumed infeasible and must be re-justified with a PE-stamped Site Plan showing the higher-density configuration is achievable.

Coverage math is simpler than it looks but unforgiving in execution. The coverage ratio is:

Coverage % = (sum of acreage in qualifying instruments) ÷ (acreage in project boundary)

For PJM, the threshold is 100% at Application and at every subsequent stage. There is no ramp. Three rules govern the numerator: (1) only acreage from qualifying instruments per Section 7.1.4 counts; (2) at IA execution, options are excluded entirely (option weight 0.0), so acreage covered only by an unconverted option drops out of the numerator; (3) acreage covered by two qualifying instruments (e.g., a primary lease and an overlapping easement) counts once, not twice.

The denominator is the modeled project boundary in the Site Plan and GIS file. The boundary must include the Generating Facility footprint, the Interconnection Facilities footprint, and any setback buffer required by state or local law. For a deeper dive on PJM coverage thresholds at every stage, see PJM Site Control Requirements in 2026: The Complete Developer Guide.

Section 7.1.7 — Encumbrances

Section 7.1.7 governs encumbrances — mortgages, liens, conservation easements, agricultural preservation easements, and any other third-party interest that may restrict the developer's ability to use the parcel. The current rule is to flag at Application and disqualify at later stages. A flagged-but-not-disqualifying encumbrance at Application typically requires a Subordination, Non-Disturbance, and Attornment (SNDA) agreement before DP1 to remain valid.

The most common encumbrance pattern in PJM's mid-Atlantic footprint is a mortgage on the leased parcel. The cure is an SNDA among developer, landowner, and lender, in which the lender subordinates its lien to the lease. Conservation easements are more difficult: if the easement prohibits commercial energy development, the parcel is permanently disqualified. Agricultural preservation easements vary by jurisdiction; some permit solar with conditions, others prohibit it outright.

Section 7.2 — The parcel modification grammar

Section 7.2 is the most-cited subsection of Manual 14H in deficiency notices, and it is the section most often misunderstood. The grammar is: supplement always, substitute often, expand rarely. The Site you submit at Application is the comparison baseline, and what you can do to that baseline between Application and DP1 is tightly constrained.

The operational implication of Section 7.2 is that the Application submission is a strategic choice, not just a snapshot. Under-submitting (filing only the parcels you are sure about) limits your ability to expand at DP1. Over-submitting (filing parcels you may not actually have control over) risks deficiency notices for the parcels themselves. The right approach is to file the largest defensible Site at Application, then use 7.2.3 substitution to upgrade evidence quality between Application and DP1, and reserve 7.2.2 additions only for parcels that are clearly adjacent or easement-connected.

Section 7.3 — The Officer Certification

Section 7.3 prescribes the Officer Certification — a sworn attestation, executed by an officer of the Project Developer entity, certifying the accuracy of the site control evidence and committing the developer to the Critical Path Construction Schedule. Without it, the application is incomplete on its face. Section 7.3 establishes three rules: (1) the certification must use the current PJM template, (2) it must be signed by an officer of the Project Developer entity itself (not the parent), and (3) it must reference the as-filed evidence by filename and date.

The "officer" requirement means a person with corporate signing authority — President, Vice President, CEO, CFO, Treasurer, Secretary, or Manager (in an LLC). Title alone is necessary but not sufficient: the entity's operating agreement or bylaws must authorize the signatory to bind the entity. For LLCs without designated officers, the manager listed on the certificate of formation is typically the appropriate signatory; if a different person signs, an authorizing resolution should accompany the certification.

The "as-filed evidence" requirement means the certification must list the specific site control documents being relied upon. A certification that says "the Project Developer has site control" without enumerating the instruments is incomplete. The current template includes a schedule of evidence with filename, date of execution, parcel APN, and instrument type for each document. The certification's date must be at or after the date of every listed document; a certification dated before the most-recent lease amendment is treated as evidence the officer did not certify the as-filed materials.

Section 8 — Decision Points I, II, and III

Section 8 governs the three Decision Points that punctuate the cycle process. Each Decision Point is a formal go/no-go gate at which the developer must elect to proceed or withdraw, and at each gate the site control bar tightens. The Section 8 site control rules layer on top of Section 7's substantive bar, not replace it.

The DP1 bar is the most consequential because it locks in the Site for the rest of the cycle. After DP1, the parcel modification grammar of Section 7.2 no longer applies in full — substitution remains permitted, but new parcel additions are barred. This is why the Application-to-DP1 window is the most strategically important period of a cycle from a land team perspective: every modification you might want to make must happen during this window.

Attachment Q — Officer Certification template and evidence schedule

The Officer Certification template lives as an attachment to Manual 14H (currently styled as Attachment Q in the version of M-14H accepted by FERC in Docket ER25-1544-000; the attachment number can change between revisions, so always verify against the current Manual). The template has three sections: (1) the attestation language, (2) the evidence schedule, and (3) the signatory block.

The attestation language is fixed. Developers do not modify it. Material modifications to the attestation language (adding qualifications, removing certifications, or substituting "best knowledge" for "exercises commercially reasonable best efforts") render the certification non-conforming.

The evidence schedule is a structured table with one row per instrument. Required fields include: instrument type (deed, lease, option, easement, ROW agreement); execution date; expiration date (where applicable); parcel APN(s) covered; county and state; landowner of record; signatory(ies) on the instrument; acreage covered; and encumbrance status. The schedule must be internally consistent with the GIS file and the Site Plan, and the parcel APNs must match the county assessor's format exactly (a leading zero or punctuation difference will not match, and PJM's automated cross-reference will flag it).

The signatory block names the officer, recites the title, and includes the signature and date. PJM does not currently require notarization for the Officer Certification, but some developers notarize as a practice for evidentiary strength. Notarization does not substitute for using the correct template — a notarized certification on the wrong template is still non-conforming.

How Manual 14H interacts with the Tariff and FERC orders

Manual 14H is not a standalone document. It operates within a stack of authority that includes the Tariff, FERC orders accepting Tariff revisions, and the underlying FERC Order 2023 framework. A developer who reads only the Manual will miss the legal context; a developer who reads only the Tariff will miss the operational mechanics. Three relationships matter most:

1. Tariff Subpart A, Section 302 supplies the substantive bar. Section 302 is the legal source of "exclusivity, conveyance, and minimum term." Manual 14H Section 7.1.5 operationalizes it. If Section 302 changes, Manual 14H must change to track it.
2. Tariff Subpart C, Sections 305 and 306 supply the procedural framework. Section 305 governs eligibility (including for the RRI cohort — see PJM RRI Site Control: What the 51 Selected Projects Need to Know Before TC2). Section 306 governs the Application Review Phase. Manual 14H Section 5 operationalizes both.
3. FERC orders accepting Tariff revisions are the binding instrument. The July 2025 Manual 14H site control update was filed in Docket ER25-1544-000 and accepted by FERC June 10, 2025. The complaint that prompted it — Docket EL25-22-000 — is the public record of why specific tightening rules were added. When in doubt about the intent of a Section 7 rule, the eLibrary record of EL25-22-000 is the source of truth.

A working checklist for using M-14H as a reference

For developers preparing or auditing a Cycle 1 package, the practical workflow against Manual 14H looks like this:

1. Verify the as-filed Manual version. Always work against the version on PJM's site, not a downloaded copy.
2. Run every parcel through Section 7.1.4. Flag any parcel relying on an LOI, MOU, or unrecorded memorandum.
3. Test every instrument against Section 7.1.5. Exclusivity, conveyance, one-year minimum term — all three simultaneously.
4. Run the Section 7.1.6 coverage math. Qualifying acreage over project boundary, threshold 100%.
5. Inventory encumbrances under Section 7.1.7. Start SNDA negotiation early.
6. Plan Section 7.2 modifications now. Confirm adjacency or easement-connection for likely DP1 expansion parcels.
7. Build the Section 7.3 Officer Certification on the current template. Verify signatory authority and evidence-schedule completeness.
8. Cross-walk to Section 8. For every option, plan the conversion timeline against DP3 / IA execution.

The free PJM Cycle 1 Submission Toolkit operationalizes this workflow.

Glossary

• Manual 14H — PJM's New Service Requests Cycle Process manual, the operational rulebook for cycle-based interconnection.
• Section 302 — PJM Tariff Part VII, Subpart A, Section 302. The substantive site control standard.
• Subpart C — PJM Tariff Part VII, Subpart C. Sections 301–306 contain the procedural framework for cycle-based interconnection requests.
• Application Review Phase — The procedural window after Application Deadline during which PJM reviews completeness, issues deficiency notices, and validates or rejects applications. Defined in Manual 14H Section 5 and Tariff Section 306(B).
• Officer Certification — The sworn attestation under Manual 14H Section 7.3 by an officer of the Project Developer entity, certifying site control accuracy and committing to the Critical Path Construction Schedule.
• Site — The aggregate of parcels submitted at Application, defined in Section 7.1.2. Becomes the comparison baseline for all future submissions under Section 7.2.
• Generating Facility footprint — The area within which generation equipment will be installed, including setbacks, access roads, and collector lines (Section 7.1.3).
• Interconnection Facilities footprint — The area for the gen-tie, switchyard, and POI infrastructure (Section 7.1.3).
• Decision Point I (DP1) — The first formal go/no-go milestone after Phase I results. Site finalized; Section 7.2 modifications close.
• MFO — Maximum Facility Output. Peak generation capacity, used to compute density requirements under Section 7.1.6.
• SNDA — Subordination, Non-Disturbance, and Attornment agreement. The standard cure for a mortgage encumbrance under Section 7.1.7.
• Reasonable Efforts — Tariff term meaning PJM will attempt to meet the timing target but is not bound to it. Applied to PJM's 15 Business Day windows, not to the developer's 10 Business Day cure window.

Frequently asked questions

Does Section 7 apply to RRI applicants the same way it applies to Cycle 1 applicants?

Yes. The substantive site control bar in Section 7 is identical for RRI and Cycle 1 applicants. The procedural framework differs — RRI is governed by Tariff Subpart C, Sections 305 and 306, with RRI-specific milestone names — but the Section 7.1 evidence rules, the Section 7.2 modification grammar, and the Section 7.3 Officer Certification apply equally. See PJM RRI Site Control for the procedural overlay.

Can I use Manual 14H Section 7.2.4 to "redraw" a parcel boundary that I drew incorrectly at Application?

Yes, within limits. Section 7.2.4 allows GIS-based boundary corrections that do not enlarge the parcel beyond its parcel-of-record acreage. If the original GIS file underdrew the boundary by a few feet relative to the surveyed line, re-snapping is permitted. If the correction would absorb acreage from an adjacent parcel that was not in the original Site, that absorption is treated as adding a new parcel under Section 7.2.2 and must satisfy the adjacency or recorded-easement test.

What is the relationship between Manual 14H Section 5 and Tariff Section 306(B)?

Section 5 of Manual 14H operationalizes the procedural framework set out in Tariff Section 306(B). The Tariff section supplies the legal authority for the 15 / 10 / 15 Business Day windows; Manual 14H Section 5 supplies the implementation details (what counts as "receipt," what counts as "complete," and how the deficiency notice is delivered). When the Tariff and the Manual conflict, the Tariff governs.

Does Manual 14H ever require notarization of the Officer Certification?

Section 7.3 does not currently require notarization. Some developers notarize as a practice for evidentiary strength. Notarization does not cure the use of an outdated template or a signatory without corporate authority. The current template, the right entity, and the right signatory are the three substantive requirements; notarization is optional polish.

How often does Manual 14H change?

PJM revises Manual 14H regularly — typically once or twice a year. Major revisions go through a stakeholder process and are filed at FERC for acceptance (e.g., the July 2025 update in Docket ER25-1544-000). Minor revisions and clarifications can be issued more frequently. Always work against the version posted on PJM's website at the time you are preparing your submission.

Sources

• PJM Manual 14H: New Service Requests Cycle Process — Sections 5 (Application Review Phase), 6 (Deposits), 7 (Site Control), 8 (Decision Points), and Attachment Q (Officer Certification template)
• PJM Tariff Part VII, Subpart A, Section 302 — Site Control standard
• PJM OATT Part VII, Subpart C, Sections 305 & 306 — Application eligibility and Application Review Phase
• FERC Docket ER25-1544-000 — Manual 14H site control update FERC filing (accepted June 10, 2025)
• FERC Docket EL25-22-000 — Manual 14H site control update enforcement complaint
• FERC Docket ER25-712-000 — RRI Tariff filing
• FERC Order 2023 Interconnection Final Rule explainer
• PJM MRC Site Control Modification Presentation, July 23, 2025
• PJM Interconnection Process Subcommittee (IPS) — education materials
• PJM Public Knowledge: New Generator Interconnection Site Control

Related articles

• PJM Reliability Resource Initiative (RRI) Site Control: What the 51 Selected Projects Need to Know Before TC2
• PJM Site Control Requirements in 2026: The Complete Developer Guide
• PJM Cycle 1 Deficiency Notice: How to Respond and the 5 Most Common Site Control Reasons Projects Get Flagged
• PJM Cycle 1 Phase 1 Study Results: A Developer's Guide
• Option-to-Lease Expiration and Interconnection Milestones
• FERC Order 2023 Site Control Compliance Guide
• PJM Cycle 1 Submission Toolkit