NYC Nonprofit Lobbying: Compliance Traps to Avoid
Forty-three organizations appeared in 2025 state lobbying records but not in the corresponding New York City registration records.
The number was down from 107 the year before, but the underlying problem remains familiar to anyone who has tried to manage nonprofit advocacy across overlapping rules: a filing that is complete in Albany may still leave a gap in New York City.
The data shows a registration mismatch. It does not, by itself, show why each organization was missing from the city rolls. Some may have misunderstood the rules; others may have misclassified an activity, missed a deadline, or simply failed to complete a required filing. The practical lesson is narrower and more useful: state and city compliance systems must be reviewed separately, activity by activity.
The NYC Lobbying Bureau identified 399 late filings of registrations and reports in 2025, resulting in more than $95,000 in aggregate civil penalties. Late filings for the end of 2024 and annual client reports generated another $175,000 in penalties. These are not abstract risk indicators. They are line items on balance sheets that nonprofit organizations can ill afford.
For NYC nonprofits engaged in advocacy—whether seeking discretionary funding, testifying on local legislation, influencing city policy, or navigating land use approvals—the compliance landscape is a minefield of overlapping thresholds, jurisdictional mismatches, and recently updated regulatory standards. The difficult part is not finding one magic number. It is identifying which law applies to which activity, where the contact occurred, who made it, and what the organization spent to support it.
The Dual-Jurisdiction Trap: Why State Registration Is Not Enough
The most persistent compliance failure in NYC nonprofit lobbying is the assumption that New York State and New York City are operating one shared registration system. They are not. The systems are maintained by different bodies, use different forms and reporting processes, and carry separate enforcement consequences.
New York State lobbying registration falls under the Commission on Ethics and Lobbying in Government, or COELIG. New York City lobbying registration falls under the NYC Lobbying Bureau and the city’s own lobbying law. A nonprofit may therefore have obligations in one jurisdiction, both jurisdictions, or neither, depending on the activity, the public official or body contacted, the subject of the communication, and the applicable compensation-and-expense threshold.
That qualification matters. The $5,000 figure is not a universal switch that automatically creates two filings for every form of advocacy. The relevant question is whether the organization has reached the applicable threshold for lobbying activity covered by the particular jurisdiction. An activity that is reportable under city law may not be reportable under state law. Land use and ULURP advocacy are the clearest example: they generally fall within the city regime but outside the scope of New York State lobbying law.
The 2025 cross-referencing data still deserves attention. COELIG and the NYC Lobbying Bureau found 43 entities registered at the state level but absent from the city rolls. In 2024, the figure was 107. The reduction may indicate better coordination or greater awareness, but the records themselves establish only the mismatch—not the individual organizations’ reasons for it.
For a nonprofit, the first operational step is to separate its advocacy into jurisdictional buckets:
1. State-covered lobbying. Review contacts and expenditures involving New York State legislative or executive officials under the state lobbying definition.
2. City-covered lobbying. Review contacts involving New York City officials and city policy, budget, procurement, or land use matters under the city definition.
3. Overlapping activity. Identify communications that may touch both systems, such as a statewide funding campaign that also involves City Council members or city agencies.
4. Excluded or differently treated activity. Document activities that are not lobbying under one framework even if they resemble lobbying under another.
Only after that classification should the organization determine whether a registration threshold has been met. If the relevant NYC activity crosses the city threshold, a city filing may be required. If the relevant NYS activity crosses the state threshold, a COELIG filing may be required. If both sets of activity qualify, both registrations may be necessary. Filing with one body does not satisfy the other.
The registration question is not “Did we file somewhere?” It is “Which jurisdiction covers this activity, and did we file there?”
The calendar creates a second layer of risk. A nonprofit that registers once and then stops monitoring its activity can miss the point at which an additional filing, amendment, or periodic report becomes necessary. The city’s annual registration deadline and its rule requiring action within a specified period after crossing the applicable threshold should be treated as separate calendar events, not as a substitute for ongoing analysis. State filing cycles must be tracked independently.
A defensible internal record should show:
- who was contacted;
- which government body or official was involved;
- what issue was discussed;
- whether the communication was initiated by the nonprofit or made in response to an official request;
- the staff time, consultant compensation, and expenses attributed to the activity; and
- why the organization concluded that city, state, or both jurisdictions applied.
That last item is often missing. The problem is not always an absent form. It is an absent explanation for why no form was filed.
Defining Reportable Advocacy: Discretionary Funding and Land Use
The second major compliance trap is the classification of advocacy itself. Nonprofit leaders often describe their work in mission language: community engagement, public education, coalition building, budget testimony, or relationship management. Those descriptions may be accurate, but they do not answer the legal question. A communication can be central to the mission and still be lobbying.
Under NYC law, contacting City Council members or other city officials to request discretionary funding can constitute lobbying when the applicable conditions and threshold are met. The distinction between initiating a request and responding to an official’s request for information is important. A nonprofit that sends a Council office a request for an allocation is in a different position from one that answers factual questions after the office reaches out.
The direction of the communication is not the only factor, but it is a useful starting point. So are the purpose of the contact, the identity of the decision-maker, and whether the request concerns a specific budget allocation or other governmental action.
This is particularly important for organizations that participate in city budget advocacy. In 2025, 31% of reported NYC lobbying activity related to the city budget. The figure does not mean that every budget-related conversation by every nonprofit was reportable lobbying. It does show how much of the city’s disclosed lobbying activity is concentrated in an area where nonprofit organizations are deeply involved.
A development director may view a meeting with a Council member as fundraising. A policy director may view the same meeting as advocacy. For compliance purposes, the organization needs to examine what was actually requested. A general presentation about a program is not automatically the same as a request for discretionary funding. A direct request that a specific official include a specific allocation in the city budget presents a much clearer lobbying question.
Land use is a separate analytical problem
Land use adds another layer because city and state definitions do not line up neatly. NYC’s lobbying law covers lobbying concerning many phases of the city’s land use and zoning procedures, including the Uniform Land Use Review Procedure, or ULURP. Those activities generally fall outside New York State lobbying law and are also treated differently under federal tax rules governing 501(c)(3) organizations.
That creates a familiar compliance paradox: an organization may be comfortable that an activity is permissible under its federal tax status and still need to analyze whether the activity must be disclosed under NYC lobbying law. Federal permissibility is not a city registration exemption.
The reverse can also happen. A communication may be reportable under one jurisdiction but not another. The matrix below is a starting point, not a replacement for reviewing the facts of a particular contact.
| Activity | NYC Lobbying Law | NYS Lobbying Law | IRS 501(c)(3) Limits |
|---|---|---|---|
| Requesting discretionary funding from a City Council member | May be reportable when the city definition and threshold apply | May be reportable when the state definition, jurisdiction, and threshold apply | Generally permitted, subject to federal limits |
| Testifying at a City Council hearing | Treatment depends on the circumstances, including whether the testimony is given in response to an invitation or request | Treatment depends on the applicable state definition | Generally permitted, subject to federal limits |
| Lobbying on ULURP or other city land use matters | Generally within the city lobbying framework when the applicable conditions and threshold are met | Generally outside the state lobbying framework | Generally treated differently from direct legislative lobbying |
| Contacting city officials to influence a specific city policy | May be reportable when the city definition and threshold apply | Not necessarily covered unless the state jurisdiction and definition also apply | Generally permitted, subject to federal limits |
A nonprofit should not use the phrase “we testified” as the end of the analysis. It should record whether the testimony was invited, whether staff separately contacted officials before or after the hearing, whether the organization paid outside advocates, and whether the testimony concerned a matter covered by city law.
The same discipline applies to coalitions. If a nonprofit joins a campaign, pays for shared research, supplies staff to coordinate meetings, or asks another organization to make contacts on its behalf, those contributions may matter when calculating lobbying compensation and expenses. The fact that the nonprofit did not personally attend every meeting does not necessarily remove the activity from its compliance review.
A useful activity log
A practical log does not need to turn every policy conversation into a legal memo. It should, however, capture enough information to support the organization’s classification:
- Date and participants: including government officials and nonprofit staff.
- Governmental target: City Council, city agency, mayoral office, state legislature, state agency, or another body.
- Subject: budget allocation, legislation, rulemaking, procurement, land use, zoning, or general education.
- Purpose: information sharing, response to an inquiry, public testimony, or a request for governmental action.
- Costs: staff time, consultant fees, travel, event costs, and campaign expenses.
- Classification: NYC lobbying, NYS lobbying, both, or outside the relevant definitions—with a brief reason.
The point is not bureaucratic perfection. It is to prevent a year-end scramble in which no one can reconstruct what the organization actually did.
New COELIG Standards for Responsible Parties and Ethics Training
Effective February 19, 2025, COELIG clarified the definition and requirements for an organization’s designated Responsible Party. The change is easy to misread as a form update. It is more significant than that because it focuses attention on the individual who has authority to stand behind the organization’s state lobbying filings.
Under the updated requirements, the Responsible Party must generally be:
- an employee, partner, owner, or officer employed by the organization;
- an individual with legal authority to bind the organization; and
- someone whose sole duty is not lobbying compliance.
The last requirement has practical consequences for nonprofits that rely heavily on outside counsel, consultants, or a narrowly defined compliance position. A consultant may prepare filings, maintain the calendar, and advise staff. That does not necessarily make the consultant an eligible Responsible Party. The designation is intended for someone inside the organization with broader authority and an actual ability to direct or bind the entity.
This does not mean compliance work should be pushed onto an already overextended executive. It means the organization needs to distinguish between administrative support and legal responsibility. A finance or operations leader may be able to serve in the role if the person is employed by the organization and has the required authority. An external provider can remain part of the compliance system without being presented as the person who carries the organization’s formal designation.
COELIG also implemented updated mandatory ethics training requirements beginning January 1, 2025. The Responsible Party and individual lobbyists must complete the online ethics training on the applicable three-year cycle. The Responsible Party is responsible for submitting completion information, while individual lobbyists must retain their executed completion forms for three years.
For a nonprofit with five staff members who qualify as individual lobbyists, the obligation is not satisfied by having one senior employee complete training. Each covered individual needs to be tracked. The organization should maintain a record of completion dates, forms, renewal dates, and any changes in staff status that affect who is treated as an individual lobbyist.
A simple internal training record can include:
| Record | Why it matters |
|---|---|
| Name and role | Establishes who was treated as a Responsible Party or individual lobbyist |
| Completion date | Supports the three-year training cycle |
| Executed completion form | Preserves the documentation required for the individual |
| Responsible Party submission record | Shows that organizational reporting was completed |
| Staff-status changes | Prevents departing or newly covered employees from disappearing from the process |
The Responsible Party should also have a route to escalate uncertainty. If the organization’s policy staff are planning a new campaign, the person responsible for the filing should know before the first series of government contacts, not after the reporting deadline. That requires a standing relationship among executive leadership, finance, development, government affairs, and outside advisers.
The Responsible Party cannot be treated as a name attached to a form. The role requires organizational authority, a working knowledge of the activity, and enough visibility to identify a problem before it becomes a late filing.
COELIG’s broader regulatory direction also points toward closer scrutiny of individual responsibility. Proposed legislative agenda amendments for 2026 were aimed at clarifying individual liability for Responsible Parties. Whether any proposal has become enforceable law is a separate question and should not be presented as settled. The prudent response is still clear: organizations should keep the designation current, document who has authority, and avoid treating the role as ceremonial.
The High Cost of Administrative Oversight: Analyzing 2025 Penalties
The financial penalties for noncompliance are neither theoretical nor symbolic. They are documented, aggregated, and published.
In 2025, the NYC Lobbying Bureau conducted 45 random audits. Available reporting does not break out how many audited entities were nonprofits, so the audit number should not be converted into a nonprofit-specific enforcement rate. It does, however, show that the city’s oversight is active. The penalty data provides a clearer picture of the cost of administrative failure:
| Violation category | 2025 data |
|---|---|
| Late filings of registrations and reports | 399 instances |
| Civil penalties from those late filings | More than $95,000 |
| Late reports for the end of 2024 and annual client reports | More than $175,000 in penalties |
For a small or mid-size nonprofit, a penalty of several thousand dollars can displace a meaningful amount of program spending. The irony is sharp: organizations may engage in advocacy to secure public funding for their missions, then lose scarce resources because the administrative system supporting that advocacy was not maintained.
The common causes are usually operational rather than dramatic:
1. Missed reporting cycles. Staff who are accustomed to annual grant reports or quarterly financial close processes may not have a system for city reporting deadlines that occur more frequently.
2. No threshold monitoring during the year. An organization may begin with occasional contacts and cross the applicable threshold after hiring a consultant, expanding a campaign, or adding staff time. If no one is reviewing cumulative costs, the trigger arrives unnoticed.
3. Failure to amend a registration. Changes in lobbyists, clients, subjects, or other registration information may require an amendment. Treating registration as a once-a-year filing leaves no mechanism for updating the record.
4. Incomplete disclosure. Reports may require information about clients, subjects, contacts, and expenditures. A vague description that made sense internally may not be sufficient for a filing.
5. Calendar misalignment. State and city deadlines are independent. A shared spreadsheet with one column labeled “lobbying filing” is an invitation to confusion.
6. Staff turnover. When the employee who knows the system leaves, the organization may lose the institutional memory behind its calculations and filings.
7. Unclear treatment of coalition expenses. Shared consultants, joint events, paid travel, and campaign materials can be omitted when no one has been assigned responsibility for allocating them.
The infrastructure needed to reduce these risks is not exotic. It includes a designated internal point person, a calendar that identifies the responsible jurisdiction for each deadline, a method for tracking staff and consultant time, a record of government contacts, and a document-retention system for ethics training.
The strongest programs also build in a review before a major advocacy push. Before launching a budget campaign or entering a land use process, the nonprofit should ask:
- Which government officials are likely to be contacted?
- Is the campaign directed at city, state, or both levels?
- Are the contacts requests for governmental action, responses to inquiries, public education, or some combination?
- Who will perform the work, and how will compensation and expenses be counted?
- Does the campaign involve a consultant or coalition whose work needs to be included in the organization’s records?
- Are events with public servants creating a separate gift or ethics question?
That review is much cheaper than reconstructing the campaign after a notice of deficiency.
Gift Bans and Fundraising: Navigating Interactions with Public Servants
Fundraising creates a different kind of exposure. Nonprofits regularly invite elected officials and government staff to galas, site visits, award ceremonies, policy briefings, and community events. Those invitations can involve food, admission, travel, honoraria, or other things of value. When the organization or an employee is engaged in lobbying, the interaction deserves a careful gift-law analysis.
The risky assumption is that a nonprofit event is automatically exempt because it serves a charitable or public purpose. It is not safe to assume that a complimentary ticket, meal, or invitation is merely a courtesy. The value, the recipient’s status, the giver’s relationship to the recipient, the purpose of the event, and any applicable exception all matter.
The rules also differ between New York City and New York State. A city official and a state official may be subject to different restrictions. An invitation that appears permissible under one set of rules may require a different analysis under the other. The label “nominal” should not be used casually, and the fact that the event is open to many attendees does not eliminate the need to examine the benefit provided to the public servant.
Before extending an invitation, the nonprofit should consider:
1. Who is the recipient? Confirm whether the person is a city public servant, state public servant, elected official, government employee, or someone outside the relevant rules.
2. What is being provided? Identify the value of admission, food, drinks, travel, lodging, entertainment, materials, or an honorarium.
3. Who is providing it? Determine whether the invitation comes from the organization, a registered lobbyist, an employee, a donor, a vendor, or a coalition.
4. What is the context? A fundraising dinner occurring while the organization is seeking a discretionary allocation deserves heightened review.
5. Does an exception apply? Do not rely on a general understanding of the rules. Confirm the specific exception and preserve the basis for using it.
6. What documentation exists? Keep the invitation, valuation, approval, and any ethics advice with the event records.
The interaction between fundraising and lobbying is especially sensitive when the same Council members or agency officials are being asked to support the nonprofit’s budget request. That does not mean officials can never attend nonprofit events. It means the organization should not treat the event as a routine development activity simply because the invitation is part of a standard fundraising calendar.
The safest protocol is not an automatic ban on contact with public servants. It is a pre-clearance process that identifies the recipient, calculates the value, checks the applicable city or state rule, and documents the decision. If the organization cannot explain why an invitation is permissible, it should pause before sending it.
Building a Compliance System That Matches the Work
The regulatory architecture for NYC nonprofit lobbying is dense, but it becomes more manageable when the organization builds its system around actual work rather than around filing forms.
Start with the activity, not the registration
At the beginning of each advocacy project, identify the contacts and the governmental decisions the organization is trying to influence. A campaign may include public education, press work, coalition meetings, testimony, direct requests, and responses to officials. Those components should not be collapsed into one label.
A short project memo can record:
- the policy or funding objective;
- the city and state officials likely to be contacted;
- the expected duration;
- internal staff and outside consultants involved;
- the anticipated expenses; and
- the person responsible for reviewing lobbying status.
The memo does not need to predict every conversation. It creates a baseline against which the organization can compare what actually happened.
Keep separate city and state files
A combined advocacy folder can still be useful, but the organization should maintain clearly separated city and state filing records. Each file should contain the relevant registration, amendments, reports, supporting calculations, correspondence, and deadline history.
The separation is not cosmetic. It forces the team to ask whether a particular activity belongs in the city system, the state system, or both. It also makes it easier to respond if one regulator asks about an activity that the other does not cover.
Give finance a seat at the table
Lobbying compliance is not only a government affairs function. The threshold calculation may depend on compensation and expenses, which means finance needs to understand how staff time, consultant invoices, travel, event costs, and shared campaign expenses are classified.
Finance does not need to make every legal judgment. It does need a process for flagging:
- invoices from government-relations consultants;
- staff time charged to advocacy campaigns;
- payments for coalition work;
- travel and event expenses involving public officials; and
- changes that may push covered activity toward the applicable threshold.
A monthly review is often more useful than a year-end exercise. By the time annual totals are available, the organization may already have missed a registration or reporting window.
Treat exclusions as conclusions that need support
If the organization decides that an activity is not lobbying, the conclusion should be recorded briefly. For example, the file might state that the communication was a response to an official’s request for information, concerned a matter outside the applicable jurisdiction, or involved land use activity that was reviewed under city law but not state law.
This is not an invitation to create legal paperwork for every email. It is a way to preserve the reasoning behind decisions that may otherwise look arbitrary months later.
What Leadership Should Review Now
A nonprofit leadership team does not need to wait for an audit or a deficiency notice to test its system. The review can be focused and practical:
1. Reconstruct the current year’s advocacy. List direct contacts, testimony, budget requests, land use work, coalition activity, and consultant engagements.
2. Separate the jurisdictions. For each activity, ask whether NYC law, NYS law, both, or neither applies. Do not treat a state registration as evidence that the city question has been resolved.
3. Recalculate compensation and expenses. Use actual staff and consultant activity rather than relying on the project’s original budget.
4. Confirm registration and amendment status. Check that the filing reflects current lobbyists, subjects, clients, and responsible personnel.
5. Review the Responsible Party designation. Confirm that the person is employed by the organization, has authority to bind it, and has duties beyond compliance administration.
6. Check ethics training records. Confirm completion for the Responsible Party and each individual lobbyist, then verify the three-year retention system.
7. Review public-servant interactions. Examine invitations, meals, travel, honoraria, and event access provided in connection with fundraising or advocacy.
8. Assign every deadline to a person. A calendar is useful only when a named employee owns each filing and a second person can cover during leave or turnover.
9. Preserve the analysis. Keep the facts and reasoning supporting the organization’s classification decisions, especially where city and state treatment diverge.
The point of this review is not to turn nonprofit advocacy into a compliance exercise detached from the mission. It is to make sure that the organization’s policy work is not undermined by an avoidable administrative gap.
The 2025 data makes two things clear. Enforcement is active, and cross-jurisdictional comparisons are not theoretical. But the data does not support a story about 43 organizations sharing one identical motive. It supports a more precise warning: a state filing is not proof of city compliance, and a city-facing activity cannot be classified correctly by looking only at federal tax rules or state lobbying law.
For NYC nonprofits, the durable solution is a working map of the activity—who was contacted, about what, where, at what cost, and under which legal framework. Once that map exists, registration and reporting become manageable. Without it, even a well-intentioned organization can discover that the missing filing was not the only problem.