Resources · Language Access Law
NYC Local Law 30: The Complete Guide to New York City’s Language Access Law
What the law actually requires, who it covers, which languages are designated, what changed in 2023, and what compliance looks like in practice.
Quick Answer
New York City Local Law 30 of 2017 is the city’s language access law. It requires every city agency providing direct public services or emergency services to translate its most commonly distributed documents into ten designated citywide languages — Spanish, Chinese, Russian, Bengali, Haitian Creole, Korean, Arabic, Urdu, French, and Polish — provide telephonic interpretation in at least 100 languages, post multilingual signage about free interpretation, appoint a language access coordinator, and publish a language access implementation plan updated at least every three years. It is codified at NYC Administrative Code §§ 23-1101 to 23-1102 and took effect July 1, 2017. 45 agencies reported as covered in fiscal year 2025.
What Local Law 30 is
Local Law 30 of 2017 amended the New York City Charter and Administrative Code “in relation to improving access to city services for limited English proficiency individuals.” It was introduced as Council Int. No. 1181-A of 2016, passed by the Council on February 15, 2017, and returned unsigned by the Mayor on March 20, 2017 — which under the City Charter allowed it to become law without signature. It took effect July 1, 2017.
A drafting detail worth knowing if you ever cite this law: because the Mayor neither signed nor vetoed it within thirty days, Local Law 30 became law by operation of the City Charter rather than by mayoral approval. This has no effect on its force.
The law does four structural things:
- Adds a new Chapter 11 (Language Access) to Title 23 of the Administrative Code, at §§ 23-1101 and 23-1102
- Rewrites City Charter § 15(c), expanding the duties of the Office of the Language Services Coordinator, which sits within the Mayor’s Office of Operations
- Amends City Charter § 18(b), updating the mandate of the Mayor’s Office of Immigrant Affairs (MOIA)
- Amends Administrative Code § 23-301 so that any 311 complaint about language accessibility is forwarded both to the agency involved and to the Language Services Coordinator
The Council’s stated rationale is in the law itself: the city recognizes that “the well-being and safety of the city as a whole is put in jeopardy if the people of the city are unable to access city services or effectively communicate with city agencies.”
Local Law 30 replaced a narrower regime. Its predecessor, Executive Order 120 of 2008, applied to a smaller set of agencies and fewer languages, and being an executive order rather than legislation, could be rescinded by a future mayor. Putting the obligations in the Administrative Code made them durable.
Who is covered — and who isn’t
§ 23-1101 defines covered agencies as “every city agency that provides direct public services or emergency services,” and defines direct public services as “services administered by an agency directly to program beneficiaries, participants, or applicants.”
Note what this does not do: it does not list agencies by name. Coverage is functional. If an agency delivers services directly to the public, it is covered. In fiscal year 2025, 45 agencies reported as covered agencies in MOIA’s annual report.
The ten designated citywide languages
The statute does not name the ten languages. It specifies a method for deriving them, in § 23-1101:
- The top six limited English proficiency languages spoken in New York City, determined by the Department of City Planning and the Office of the Language Services Coordinator using U.S. Census data
- The next four LEP languages spoken by the population served or likely to be served by city agencies, determined by the Language Services Coordinator using Department of Education data, excluding any language already designated from Census data
Applying that method in 2017 produced this list, which has not changed since:
| # | Language | Source of designation |
|---|---|---|
| 1 | Spanish | U.S. Census data (top six) |
| 2 | Chinese | |
| 3 | Russian | |
| 4 | Bengali | |
| 5 | Haitian Creole | |
| 6 | Korean | |
| 7 | Arabic | NYC Department of Education data (next four) |
| 8 | Urdu | |
| 9 | French | |
| 10 | Polish |
MOIA reports that these ten languages collectively serve approximately 1.5 million New Yorkers with limited English proficiency — about 85% of the city’s total LEP population.
Two practical notes. First, “Chinese” is designated as a single language, but in delivery it splits: written translation is typically produced in Simplified or Traditional characters, while interpreting requires a specific spoken variety, most often Mandarin or Cantonese. Agencies that procure “Chinese” without specifying which get the wrong interpreter. Second, MOIA is explicit that ranking is not priority: “population size and ranking do not determine the importance or priority of any language community.”
The six core requirements
Distilled from § 23-1102, every covered agency must:
- Translate its most commonly distributed public documents into all ten designated citywide languages — specifically those documents that “contain or elicit important and necessary information regarding the provision of basic city services.”
- Provide interpretation services, including telephonic interpretation.
- Provide telephonic interpretation in at least 100 languages, covering “both common and esoteric languages” as identified by the Language Services Coordinator. This is a separate and much broader obligation than the ten-language translation duty, and it is the one agencies most often underestimate.
- Post multilingual signage in conspicuous locations advertising the availability of free interpretation.
- Designate a language access coordinator and publish that person’s name and title conspicuously on the agency website.
- Develop, publish and maintain a language access implementation plan, updated at least every three years.
The compliance deadlines have long passed. For any designated language an agency was not already serving when the law was enacted, services were required by July 1, 2018 generally, and by July 1, 2020 for issuing a licence, permit or registration.
Inside the language access implementation plan
The implementation plan (LAIP) is where most of the real obligation sits, and it is more demanding than most summaries suggest. § 23-1102(b) requires twelve distinct elements. A plan must:
- Designate a language access coordinator, named and titled on the agency website
- Describe how the agency will deliver the required services
- Weigh four factors: the proportion of LEP people in the eligible service population; how often LEP individuals contact the agency; the importance of the service and the consequences of inadequate interpretation; and the resources and costs involved
- Evaluate the language needs of the service population, and consider whether some services should be offered in languages beyond the ten designated ones
- Address language access in emergency preparedness and response
- Cover agency communications — emergency notifications, public hearings, press releases
- Apply plain language principles, replacing technical and legal jargon where possible and using layout and design to make documents easier to act on
- Train frontline workers and managers on language access policy
- Include public awareness strategies
- Include a process to monitor and respond to complaints in a timely way
- Determine the agency’s capacity, “both through agency staffing and contracts with third parties”
- Describe the steps by which the policy will be effectuated
Element 7 is quietly significant and widely ignored: plain language is a statutory requirement, not a style preference. A document that is accurately translated but incomprehensible does not satisfy the intent of the law. In practice, the English source document usually needs simplifying before translation, not after.
Element 11 is the one that matters commercially: the statute explicitly contemplates that agencies will meet capacity through contracts with third parties, not staffing alone.
Temporary languages
This is the part most summaries of Local Law 30 miss, because it is not in Local Law 30. Local Law 13 of 2023 (Council Int. 0697-2022) added a separate mechanism: the Office of the Language Services Coordinator designates temporary languages spoken by groups who have arrived in the city seeking services because of “a global event, occurrence, trend, or pattern.”
Once designated, agencies must translate relevant materials and provide interpretation in that language in addition to the ten citywide languages.
Throughout fiscal year 2025, New York City’s designated temporary languages were Wolof and Fulani/Pulaar, reflecting arrivals from West Africa. MOIA selects them from Office of Asylum Seeker Operations data on preferred languages in non-DHS emergency shelters, using a 1% population threshold.
Both are predominantly oral languages with limited standardized written form, which changes what compliance looks like: the workable route is usually recorded audio, interpreter-led sessions and community intermediaries rather than translated documents. MOIA has issued guidance to agencies on precisely this point.
What changed in 2023
The City Council passed four laws in 2023 that extend the Local Law 30 framework. Anyone working from the 2017 text alone is working from an incomplete picture.
| Law | What it added |
|---|---|
| Local Law 6 of 2023 | Reporting requirements on language services contracts, and moved reporting to a fiscal-year basis. Agencies now report contracts whose principal purpose is language services, including whether a community-based organization was involved. |
| Local Law 13 of 2023 | Created the temporary language designation. |
| Local Law 14 of 2023 | Enhanced language access for small business owners. |
| Local Law 15 of 2023 | Translation of compliance materials. |
The Local Law 6 contract-reporting change has an underappreciated side effect: because agencies must now report language services contracts and payments annually, MOIA’s report has become a public record of who the city buys language services from. For anyone assessing this market, it is the best open data source available.
How it’s enforced
Local Law 30 has no civil penalty scheme and no private right of action. Enforcement runs on transparency:
- 311 routing. Under the amended § 23-301, every 311 call, email or message reporting a language access complaint is forwarded to both the agency named and the Language Services Coordinator.
- Annual public reporting. The Language Services Coordinator reports each year to the City Council and posts publicly — naming each agency’s language access coordinator, publishing its implementation plan, and reporting complaint data and how complaints were resolved.
- Monitoring. The Coordinator monitors agency performance including signage compliance, availability of interpretation, frontline staff familiarity with policy, and reviews of translated documents for accuracy.
The fiscal year 2025 citywide figures give a sense of scale:
| Telephonic interpretation services provided | more than 1,544,100 |
|---|---|
| In-person and remote interpretation services | more than 76,500 |
| Translation services provided | more than 5,523 |
| Language access complaints received via 311 | 406 |
| Language access requests or questions via 311 | 367 |
| Covered agencies reporting | 45 |
MOIA describes these as minimum counts — tracking methods vary between agencies and not every language access interaction is systematically captured.
How Local Law 30 fits with federal law
Local Law 30 sits on top of a federal framework that has recently moved in the opposite direction, which has made the city law more consequential rather than less.
The federal baseline is Title VI of the Civil Rights Act of 1964, which prohibits national origin discrimination by recipients of federal financial assistance and has long been read to require meaningful access for LEP individuals. That reading was operationalized by Executive Order 13166 (2000), “Improving Access to Services for Persons with Limited English Proficiency.”
In March 2025, a federal executive order designated English as the official language of the United States and rescinded the EO 13166 framework, with subsequent Department of Justice guidance on implementation. MOIA’s FY25 report describes the resulting position directly: federal policy has shifted toward minimizing multilingual services, and residents are “increasingly turning to their local governments as their primary source of language-accessible information.”
What is likely to change
MOIA has publicly identified a structural weakness in the law — a notable thing for an implementing agency to say about its own statute.
Local Law 30 specifies no review cycle for the language designations. The ten languages set in 2017 remain the ten languages today. MOIA’s FY25 report states that this “creates operational challenges”: agencies lack predictable timelines for resource planning, emerging language communities may not be captured in time, and there is no systematic process for testing whether the methodology still identifies the right languages.
Neighbouring frameworks have moved further:
- New York State designates 12 languages based on Census data, under Executive Law § 202-a
- NYC Public Schools has increased to the 12 most common parent-preferred languages
MOIA’s report concludes that the core elements of Local Law 30 — including the designation methodology and update frequency — “merit periodic consideration and refinement.” Read plainly, that is the implementing agency inviting the Council to amend the law. Organizations planning multi-year language access budgets should assume the designated list is more likely to expand than contract.
Meeting the requirement in practice
§ 23-1102(b)(11) requires agencies to assess capacity “both through agency staffing and contracts with third parties.” In practice most agencies use a mix, and the distribution follows the shape of the obligation:
- The 100-language telephonic requirement is almost always contracted. No agency staffs a hundred languages internally. This is an on-demand over-the-phone interpreting contract by nature.
- Document translation into the ten citywide languages tends to be project work, spiking when forms, notices or benefit materials are revised.
- Scheduled in-person interpreting — hearings, IEP meetings, benefits appointments, community sessions — is typically booked per assignment.
- Temporary languages are the hardest to source, because designation is reactive and the languages involved are often ones with thin professional interpreter supply in the United States.
A few things reliably cause problems for agencies, in our experience working with New York City public-sector and public-facing clients:
- Procuring “Chinese” without specifying Mandarin or Cantonese for spoken assignments, or Simplified versus Traditional for written ones
- Translating a document that was never plain-language edited, satisfying the letter of element 1 while failing element 7
- Treating the 100-language telephonic duty as satisfied by the ten-language translation vendor — they are separate obligations with separate capacity requirements
- Using bilingual staff as ad hoc interpreters, which MOIA specifically identifies as an ad hoc practice and area for growth
- Overlooking ASL. Local Law 30 is about spoken and written languages; access for deaf New Yorkers runs through the ADA and needs separate qualified ASL interpreting provision
Frequently asked questions
What is NYC Local Law 30?
Local Law 30 of 2017 is New York City’s language access law. It requires every city agency that provides direct public services or emergency services to translate its most commonly distributed documents into ten designated citywide languages, provide interpretation including telephonic interpretation in at least 100 languages, post multilingual signage about free interpretation, appoint a language access coordinator, and publish a language access implementation plan. It is codified at New York City Administrative Code Title 23, Chapter 11, sections 23-1101 and 23-1102, and took effect July 1, 2017.
What are the ten designated citywide languages under Local Law 30?
Spanish, Chinese, Russian, Bengali, Haitian Creole, Korean, Arabic, Urdu, French, and Polish. These ten languages have been unchanged since they were designated in 2017. According to the Mayor’s Office of Immigrant Affairs, they collectively serve approximately 1.5 million New Yorkers with limited English proficiency, or about 85 percent of the city’s total LEP population.
Does Local Law 30 apply to private businesses or private hospitals?
No. Local Law 30 applies only to covered city agencies, defined as every city agency providing direct public services or emergency services. It does not impose obligations on private employers, private hospitals, private landlords, or private schools. Private organizations that receive federal financial assistance have separate language access obligations under Title VI of the Civil Rights Act of 1964, and healthcare providers have obligations under Section 1557 of the Affordable Care Act, but those are different laws with different requirements.
How many agencies are covered by Local Law 30?
45 agencies reported as covered agencies in fiscal year 2025, according to the Mayor’s Office of Immigrant Affairs annual Local Law 30 report. The statute does not name agencies individually; coverage is functional, applying to any city agency that provides direct public services or emergency services.
What are temporary languages under NYC law?
Temporary languages are an additional designation created by Local Law 13 of 2023, not by Local Law 30 itself. The Office of the Language Services Coordinator designates a temporary language when a global event, occurrence, trend or pattern brings a group of speakers of that language to New York City seeking city services. Once designated, agencies must translate relevant materials and provide interpretation in that language in addition to the ten citywide languages. Throughout fiscal year 2025, Wolof and Fulani/Pulaar were New York City’s designated temporary languages.
How often must agencies update their language access implementation plan?
At least every three years, based on changes in the agency’s service population or services. The updated plan must be published on the agency’s website. Separately, the Office of the Language Services Coordinator reports annually to the City Council on every covered agency’s compliance.
What are the penalties for violating Local Law 30?
Local Law 30 does not create a private right of action or a civil penalty scheme. Enforcement operates through transparency and oversight rather than fines: complaints are routed through 311 to both the agency involved and the Office of the Language Services Coordinator, and the Language Services Coordinator reports publicly to the City Council each year on each agency’s performance. In fiscal year 2025, 406 language access complaints were received through 311.
Can city agencies use machine translation to comply with Local Law 30?
The statute does not address machine translation directly. It requires that documents be translated and that the Language Services Coordinator monitor agency performance including reviews of translated documents for accuracy. In practice, agencies are expected to ensure translations are accurate and usable, which is a quality standard rather than a technology mandate. Agencies remain responsible for the accuracy of what they publish regardless of the tools used to produce it.
Sources
This guide is based on the text of the law and on the City’s own reporting. Primary sources are linked so you can verify any statement here directly.
- Local Law 30 of 2017, full text (Council Int. No. 1181-A of 2016) — City of New York
- NYC Administrative Code § 23-1101, Definitions — American Legal Publishing
- Local Law 30 Report for Fiscal Year 2025 — NYC Mayor’s Office of Immigrant Affairs
- Local Laws Reports — NYC Mayor’s Office of Immigrant Affairs
- New York State Executive Law § 202-a — New York State Senate
- Language Access Policy — NYC Public Schools
- Limited English Proficiency — U.S. Department of Justice, Civil Rights Division