DCFR Insight 41 / Development Agreements + Approval Conditions
Data Center Agreements, Approval Conditions, and Exactions
An approval can still destroy site value if its conditions, proffers, infrastructure obligations, fees, dedications, operating limits, or enforcement terms are legally uncertain, technically infeasible, or disconnected from the capacity plan.
Approval value is defined by its conditions
A rezoning, special-use approval, site plan, or development agreement may authorize the project while imposing obligations that reduce usable capacity, delay energization, increase capital cost, constrain operations, or create long-term compliance risk. Evaluate the decision as a complete package: approved plans, findings, conditions, proffers or undertakings, fees, dedications, infrastructure scope, performance security, reporting, expiration, enforcement, amendment, and appeal. The relevant question is not whether the vote was favorable; it is whether the resulting entitlement remains executable for the business need.
Separate requirements, negotiated terms, and public promises
Classify every obligation by source: generally applicable code or fee, project-specific condition, applicant-proffered commitment, development-agreement term, utility or service agreement, environmental permit, land instrument, economic-development agreement, or informal public statement. The legal standards, amendment path, remedies, successors, and decision authorities can differ. Counsel should determine legal character and enforceability; the delivery team should determine what the term requires physically, operationally, financially, and by date.
Confirm that a development agreement is authorized and useful
Development-agreement authority and effect come from the governing state and local law; it is not a universal contract form. Where authorized, an agreement may define development standards, phasing, infrastructure, mitigation, fees, review procedures, duration, amendment, recording, successor obligations, and certain protections against later regulatory change. It may also preserve public-health-and-safety authority or exclude powers not granted by statute. Define the exact value the agreement must create, the approvals it does not replace, and the conditions that remain outside the parties' control.
Test every condition against an acceptance standard
For each proposed condition, identify the issuing authority and legal basis with counsel, the impact or finding it addresses, required scope, location, capacity, design criteria, completion date, evidence of satisfaction, inspection and acceptance, funding, ownership, maintenance, reporting, duration, default, remedy, and amendment process. Then quantify the effect on IT capacity, phasing, reliability, site geometry, energy and water strategy, construction, operations, cost, and required-in-service date. Ambiguous conditions should not be carried as harmless text.
Treat exactions, fees, dedications, and mitigation as legal and commercial issues
Public improvements, land dedications, easements, fees, and mitigation may be governed by constitutional limits, enabling statutes, ordinances, adopted fee programs, and project-specific procedures. The United States Supreme Court's 2024 Sheetz decision confirms that permit conditions are not exempt from Takings Clause scrutiny merely because they were imposed legislatively, while leaving other questions to applicable law and further proceedings. Project teams should not make their own legal conclusions. They should give counsel the impact analysis, scope, cost, alternatives, and approval record needed to evaluate authority and negotiation posture.
Condition Acceptance Test
| Condition dimension | Question to resolve | Required evidence | Failure consequence |
|---|---|---|---|
| Authority and source | Who imposed or offered it, under what procedure and law? | Final instrument, code basis and counsel review | Uncertain enforceability, appeal or negotiation position |
| Technical scope | What exact asset, performance or restriction is required? | Accepted plan, criteria, quantities, location and phase | Capacity loss, redesign or unsatisfied condition |
| Cost and funding | Who pays, secures, receives credits, and carries escalation? | Estimate, allocation, security and reimbursement terms | Unbudgeted capital or stranded deposit |
| Schedule and dependency | What must occur, by whom, before which release? | Integrated path, third-party milestones and relief | Closing, permit, construction or energization delay |
| Acceptance and survival | How is completion proven and who owns the duty later? | Inspection, certificate, recordation, reporting and handoff | Default, enforcement, operational breach or lost rights |
Legal authority and available challenges are fact- and jurisdiction-specific. This operational test supports counsel and executive review; it does not determine legal validity.
Make infrastructure obligations fully executable
A commitment to improve a road, extend water, fund a substation interface, dedicate right-of-way, construct drainage, or provide emergency-response facilities needs more than a budget allowance. Define survey limits, technical criteria, capacity, agency and utility approvals, land rights, design and construction responsibility, estimate basis, escalation, security, schedule, change procedure, inspection, acceptance, reimbursement or credits, ownership, maintenance, and relief if a third party delays. Coordinate the obligation with the campus master plan and each capacity phase.
Control voluntary commitments before they become conditions
Applicant commitments may solve real impacts, but an offer made to secure support can outlive the assumptions behind it. Require cross-functional approval for material design, operational, infrastructure, environmental, workforce, fiscal, or community commitments. Test exact wording under base and downside scenarios, identify what the project controls, and avoid guaranteeing a utility, contractor, tenant, tax outcome, or future phase that another party decides. Maintain one negotiated-terms log so counsel, public policy, design, construction, finance, and operations work from the same position.
Preserve amendment and change-control paths
Data-center programs evolve: equipment yards shift, buildings grow, cooling changes, routes move, phasing accelerates, and utility facilities are redesigned. Define what constitutes substantial conformance, administrative modification, formal amendment, new hearing, or new agreement under the jurisdiction's rules. Build tolerance where lawfully available and technically acceptable, but do not use vague flexibility that undermines the approval record. Every proposed campus change should be screened against approved plans, conditions, findings, studies, commitments, easements, fees, and vesting assumptions before release.
Translate legal documents into a delivery register
Create a condition and obligation register that links each clause to the affected parcel, phase, drawing, specification, schedule activity, cost code, responsible organization, approval or inspection, evidence location, notice date, successor, and compliance status. Include recurring duties, operational limits, monitoring, reporting, maintenance, reimbursement, and expiration. The controlling language remains in the executed instrument; the register makes it possible for the project team to deliver and verify that language without relying on institutional memory.
Approval-Obligation Register
| Obligation type | Control record | Primary interfaces | Release gate |
|---|---|---|---|
| Land-use condition | Exact text, plan reference, finding, compliance evidence | Planning, legal, design and operations | Accepted capacity and compliance basis |
| Public infrastructure | Scope, right, estimate, schedule, security, inspection and ownership | Civil, utility, authority, finance and construction | Executable design and funded delivery path |
| Fee, dedication or mitigation | Calculation, trigger, credit, instrument, timing and legal review | Legal, finance, real estate and agency | Approved exposure and closing treatment |
| Operating commitment | Metric, location, scenario, monitoring, reporting and remedy | Operations, engineering, public policy and authority | Operational owner accepts the lifetime duty |
| Agreement milestone | Party, deliverable, notice, acceptance, cure, default and survival | Counterparty, legal, program and executive owner | Objective evidence satisfies the milestone |
Gate land and construction decisions on the net approval package
Before closing, major funding, or construction release, issue a cross-functional acceptance memo stating what was approved, what changed from the investment basis, which conditions remain unsatisfied, the total priced and unpriced exposure, the critical-path effect, retained legal and political risk, amendment constraints, and named owners. Possible outcomes include accept, accept with commercial protection, clarify, modify, reprice, phase, extend, challenge, or reject. Counsel advises on legal options; executives decide the risk the business will carry.
Early screening checklist
What to verify before advancing this site.
- The complete approval package is evaluated, including plans, conditions, fees, dedications, agreements, and operating limits
- Every obligation is classified by legal source and governing instrument with counsel
- Development-agreement authority, effect, recording, duration, and limitations are jurisdictionally confirmed
- Conditions have defined scope, criteria, cost, schedule, acceptance, owner, duration, and amendment path
- Exactions, fees, dedications, and mitigation receive project-specific constitutional, statutory, and ordinance review
- Infrastructure obligations include land rights, design, funding, security, construction, inspection, and ownership
- Voluntary commitments are authorized, technically deliverable, and limited to outcomes the project controls
- Campus changes are screened against approvals, findings, studies, obligations, rights, and vesting
- Executed terms are translated into a clause-linked delivery and compliance register
- Land closing and construction release use the net approval package, not the favorable vote alone
What DCFR would flag
Risks surfaced at the screening stage.
DCFR would flag any approval whose conditions, proffers, exactions, infrastructure duties, public commitments, amendment limits, or lifetime obligations have not been translated into capacity, cost, schedule, and accountable delivery controls.
Professional confirmation required
Items requiring licensed validation.
Qualified local land-use and transaction counsel should advise on authority, constitutional and statutory limits, drafting, procedure, enforceability, challenges, remedies, recording, successors, and amendment. Licensed consultants, utilities, authorities, finance, construction, and operations teams should confirm technical scope and execution.
Final takeaway
The real entitlement is the net package the project can lawfully build, fund, operate, change, and prove compliant—not the approval headline.
Screen up to 20 candidate sites before selecting one for the full DCFR report.
Each DCFR Report Package includes a preliminary 20-site comparison PDF / export package plus one selected planning-grade feasibility report.