OpenAI published a National Community Compact on November 5, 2026, setting out promises for US communities near future data centres the company owns and operates. It says each campus will have a locally tailored compact, early resident input, a local contact and annual public progress reports.
For nearby residents, the immediate value is a clearer basis for asking about construction, water, noise and hiring—not evidence that promised benefits have arrived.
The accompanying Compute Campus Policy Blueprint asks policymakers to introduce wider rules for the industry. Publishing those proposals does not put them into law.
Start with who owns and runs the site
A campus supplying computing capacity to OpenAI is not necessarily an OpenAI-owned facility. The company’s PORTS-Pike announcement says SB Energy will build, own and operate that Ohio data centre under a 20-year lease to OpenAI. It also sets out separate local commitments, including annual reporting.
The practical implication is to ask who is responsible for the proposed site and which commitments apply there. OpenAI’s name alone does not establish coverage under the new national compact. The company describes the November package as an extension of its earlier Stargate community commitments, not its first local pledge.
Ask for plans before the campus opens
The national compact promises several disclosures that neighbours can use to frame specific questions:
Construction. Plans describing temporary traffic, noise and lighting effects. Ask which roads and working hours the latest plan covers.
Noise. Independent studies before operations begin and annually afterward, covering site boundaries and immediately neighbouring areas. Ask where sound will be measured and when findings will be released.
Water and electricity. Location-specific water reporting, cooling descriptions and electricity-use disclosure, including on-site generation and consumption. Ask when estimates will be replaced by measurements.
For noise, the policy blueprint recommends checks covering night-time conditions, backup generators and cooling equipment as well as normal operations. Residents can use that proposed standard to ask what a local study includes, without assuming it is already a nationwide requirement.
These documents could make consultation useful before a campus opens: a proposed traffic route or measurement location is something concrete to discuss. That is a practical opportunity, not a guarantee that every requested change will be accepted.
Read the water figure’s small print
The blueprint’s water recommendations separate the initial cooling-system fill from ongoing demand, water withdrawn from water consumed, and forecasts from measured data. Those distinctions matter when comparing a proposal with local supply.
For example, the Project Camellia FAQ says its 30,000-gallon daily planning estimate for Effingham County, Georgia, excludes the cooling system’s initial fill. The developer says the fill volume and final ongoing annual demand are still being determined through design and water-service planning.
That makes the daily estimate an incomplete answer to how much water the project will need overall. Ask for the initial fill volume, its source and timing separately from recurring demand. Recirculating water does not mean the first fill—or subsequent maintenance needs—disappears.
Separate future jobs from opportunities available now
The compact’s workforce commitments include annual hiring and training reports covering worker counts, hours, job types and apprenticeships. Local-hiring targets depend on local labour conditions; the document does not set a universal hiring percentage.
Effingham illustrates why timing matters. Its FAQ describes a commitment to at least 400 permanent on-site jobs initially and expects more than 1,000 roles at full buildout. These refer to different phases of a planned project, not current vacancies.
Residents can register interest through Project Camellia’s Future Talent Network, which says hiring will happen over time as development advances. Joining is an expression of interest, not a job offer.
For businesses, the local suppliers page invites interest in potential work and says the team will follow up when appropriate. Registration is not an awarded contract. Ask about purchasing schedules and qualification requirements before treating a forecast as a business opportunity.
Find out who checks progress
Public reporting and independent auditing are different. The national compact explicitly promises independent noise studies, but does not specify an independent audit of every commitment.
The Effingham project announcement goes further, promising an annual audit by an independent firm with results made public. That is a project-specific promise of future scrutiny, not evidence that an audit has already been completed. Residents should ask what the audit will cover and when the first report is due.
The blueprint also proposes public terms for government incentives, measurable commitments and provisions to recover benefits if material commitments are missed. That proposal does not itself create a remedy for a particular campus. Local agreements and existing rules may contain additional obligations.
Power costs are a related but separate question. OpenAI says it will cover its electricity and required infrastructure costs. RohitAI’s electricity-bills explainer examines the local agreements and assumptions behind grid-cost and household-savings claims.
A useful next step is to request the latest local compact, the party responsible for each commitment, expected reporting dates and the process for raising an unresolved concern. In Effingham, the Project Camellia contact page provides a public route for those questions. A national promise becomes easier to follow when residents know which local document, person and deadline to return to.