For local governments

A county gets one chance to be ready.

Most of this firm's work is for developers. This page is about the other half of the table — the work you can hire us to do, and the rule that governs whether we are allowed to.

Readiness work

The work that decides whether a project becomes a fight — clear standards written in advance, a hearing procedure adopted before anyone is angry, honest public information, a benefits framework the county wrote instead of received — almost always has to happen before the first application lands. After that, everyone is reacting.

We do that work for counties, development authorities, chambers, and regional organizations. It is the same knowledge, pointed the other direction.

What we do

  • Readiness assessment. What your ordinance actually says about this use, how your hearing procedure works under pressure, what the last three contested land-use fights in your county tell you about the next one, and who in your community will be at the front of it. Written, specific, and yours.
  • Hearing and meeting procedure. Residency and time-ceding rules adopted as standing procedure while nothing is controversial, rather than imposed once something is. Room capacity planned for the turnout you will actually get. The open-house format that lets people ask a real question instead of the town-hall format that hands one person a microphone.
  • Public information that holds up. A published set of answers with real numbers in them — gallons per day, decibels at the property line, megawatts, acres, dollars to the tax digest. Residents will get numbers from somewhere. The only question is whose.
  • Model benefits standards. What your county requires of any project of this size, written before a specific project asks: water reporting, noise and buffer standards, decommissioning, local hiring, road commitments, and how compliance gets reported in public. Drafted by an attorney, because these are contracts.
  • Regional coordination. For multi-county and multi-state organizations, one standard across the region so a developer cannot shop the weakest jurisdiction and neighboring counties are not bidding against each other with their own residents' patience.

Scoped per engagement. Most of this work is grant-fundable, and we will say so when it is.

The conflict rule

One side per county, stated plainly

We work one side per county — a developer or a community in a given county, never both.

If we are engaged by a county or a regional organization, we will not represent a developer siting in that county, in that engagement or afterward, for as long as the relationship stands. It runs the other way too: where we represent a developer in a county, we decline community-side work there. Before we accept any engagement we check it against a log of our active matters — client, county, and dates — so the rule is enforced by process rather than memory. That is a real cost to us and it is the point. A firm that would take either side in the same county is useful to neither.

We will tell you, before you hire us, whether we have any relationship in your county. If we do, we will decline.

Limits

What we don't do for a community

We don't recruit projects for you, and we don't oppose them. We are not an economic development contractor and we are not an advocacy group.

We prepare a community to make a decision on its own terms and to be able to defend it afterward either way. If you want a firm that will deliver a particular answer, that is a different engagement and we are not it.

If we work for the developer

Who pays us, and what you can hold us to

Everything below applies when our client in your county is the applicant rather than you. If our name is attached to a project in your county, this is the answer to the questions you would otherwise have to ask us in a meeting.

The developer is our client. The developer retains us, pays us, and directs the scope of our work. We are an agent of the applicant.

In that county we are not an adviser to your government, not a neutral party, and not a representative of your residents. If someone has described us to you in any of those terms, that description is wrong, and we would like to know who gave it.

When we introduce ourselves in a public meeting, the first sentence names the client. We hold to that whether or not anyone asks.

Role and boundaries

Working for the applicant: what we do and what we don't

  • What we do

    • Brief officials and staff early, before an application is public where the client permits it
    • Organize and facilitate public information sessions
    • Maintain a written question-and-answer register, including unanswered questions
    • Help draft community benefits commitments in specific, enforceable language
    • Document what the community raised, what changed, and what did not
    • Publish reporting against commitments after a decision
    • Route complaints and track them to resolution
  • What we don't

    • Draft or advise on your ordinances, conditions, or staff recommendations
    • Speak for your government, your staff, or your residents
    • Generate correspondence or testimony under other people's names
    • Form or fund community groups
    • Verify our own client's technical claims
    • Contact you in ways that would compromise a quasi-judicial record
    • Promise you that a project will be approved, or suggest that it should be

Public record and process

Open meetings and open records. We operate on the assumption that our correspondence with your staff and elected officials is a public record subject to the Georgia Open Records Act, and we write it accordingly. We do not ask officials to route communication around records obligations, use private channels to avoid disclosure, or treat a briefing as off the record.

Quasi-judicial proceedings. Rezonings and special use permits carry ex parte constraints, and the constraint belongs to your officials, not to us. Where a matter is quasi-judicial, we take direction from your county attorney on what contact is permissible, and we would rather forgo a conversation than create an appellate issue in your record. If you tell us contact is closed, it is closed.

Lobbying. Any activity that constitutes lobbying under Georgia law is registered and disclosed as required. If you want to know whether a particular contact was registered, ask and we will tell you.

Conflicts and political activity. Conflicts are screened in writing before an engagement begins. If a conflict emerges during one, we disclose it to both parties.

The open-records, ex parte, and lobbying-disclosure descriptions on this page state our practice. They are not legal advice and not a representation that any particular engagement complies with any particular statute. Your county attorney governs what is permissible in your jurisdiction, and we take direction from them.

Technical claims

We are not qualified to verify what a data center will draw, emit, or generate, and we will not act as though we are.

Every technical claim about a project — water demand and source, electrical load and interconnection, backup generator emissions and runtime, noise at the property line, lighting, traffic during construction, stormwater, tax revenue projections — originates with a qualified expert who is accountable for it. Our role is to make sure the community can see who that is.

What that means in practice. Public materials we produce attribute technical figures to their source and to the study or model they came from. When a question requires analysis that has not been performed, the register says so rather than offering an estimate. When a figure changes, the change is documented alongside the reason.

Your independent review. Nothing we produce is a substitute for your own staff, consultants, or peer review. If your county wants an independent technical review of an applicant's claims, we will not oppose it, and we will tell our client that resisting it is the wrong instinct.

Documentation

How commitments get reported

If a benefits agreement is part of an approval in your county, the reporting against it should be something a commissioner can read in five minutes and a resident can check without filing a request. This is the format we use.

Illustrative format — not a real project
CommitmentSourceDueStatusEvidence
Annual potable water use capped at the stated figure, reported quarterlyBenefits agreement §3.1QuarterlyReported — under capUtility billing summary, filed with county
Noise not to exceed the stated limit at the nearest residential property lineZoning condition 7ContinuousTwo complaints — one openThird-party monitoring report; complaint log
Named road improvement completed before certificate of occupancyBenefits agreement §5.2Pre-occupancyIn progress — behind scheduleCounty public works acceptance letter pending
Local hiring target for construction workforceBenefits agreement §6.1AnnualReported — below targetContractor payroll summary; variance explanation

Two rules make this worth reading. Status is reported the same way when it is bad — below target and behind schedule appear in the example above because they appear in real reports. And every row points to evidence somebody other than us produced.

See the full set of example records

Official inquiries

Ask us directly, or hire us

If you want readiness work, tell us the county and what is in front of you. We will tell you whether we are free to take it before we talk about anything else.

If you are an elected official, staff member, or county attorney with a question about our role in someone else's project, contact us and we will answer in writing. We will tell you who we work for. If we are engaged in your county, we will say so.