Skip to main content

Title VI Language Access Plan Consulting for State and Local Agencies After Executive Order 14224

Executive Order 14224 revoked Executive Order 13166. It did not repeal Title VI, the program rules attached to your federal funds, or your state’s language access law. We rebuild language access plans for state agencies, counties and cities on the obligations in force today, and we find the Pashto- and Dari-speaking residents that standard Census tables hide.

See what is in force today

Start from your situation

Your language access plan, as the eight documents a reviewer is likely to ask for

Common gaps in plans written before 2025, and what the re-based plan holds instead.

  • Policy statement

    Common gapCites EO 13166
    Re-based planRe-based on the obligations in force, with dates.
  • Legal basis

    Common gapRests on rescinded guidance
    Re-based planAn obligations register, citation by citation.
  • Language data

    Common gapCensus summary tables only
    Re-based planACS microdata plus your records, with Pashto and Dari counted.
  • Contact points

    Common gapNot inventoried
    Re-based planEvery counter, line, field visit and transfer, with its language route.
  • Vital documents

    Common gapOut-of-date list
    Re-based planA register with languages, dates and owners.
  • Interpreting standards

    Common gapBilingual staff untested
    Re-based planA tested definition of “qualified,” including for Pashto and Dari.
  • Machine translation

    Common gapNo policy
    Re-based planA written line between machine and human.
  • Training and monitoring

    Common gapNo measures
    Re-based planModules, targets and an annual report.

What is Title VI language access plan consulting?

It is help for a state or local agency to decide what it still owes residents with limited English proficiency now that the Justice Department and several other agencies have withdrawn their LEP guidance, and to write that into a language access plan it can defend: the legal basis, the language data, vital documents, interpreter and translation standards, a machine translation policy, staff training and monitoring.

The order changed federal policy, not your obligations.

Executive Order 14224 governs federal agencies, and it says that “nothing in this order, however, requires or directs any change in the services provided by any agency.” Title VI still applies to every agency that takes federal money.

The legal basis moved.

Plans that cite EO 13166, the 2002 Justice Department guidance or its “safe harbor” now rest on documents that are no longer in force. Most of the obligations remain; the citations must change.

Your data probably hides Afghan residents.

Standard Census tables put Pashto in “Other Indo-European languages” and count Dari inside “Persian,” so a threshold test run on them misses the two main Afghan languages.

Check which rules bind your agency

Answer five questions. The list on the right is what your language access plan should cite.

Does your agency receive federal money, directly or passed through the state?

Which of these do you run or fund?

Where is your agency?

Does your city or county have a language access ordinance or policy?

Do you serve Afghan residents?

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Do you still need a language access plan?

Almost certainly, if you receive federal funds or work in a state or city with a language access law. For most agencies no federal rule requires the plan document itself, though FTA’s transit circular, the Section 1557 rule for health programs (45 CFR 92.8(d)) and several state laws do. The plan is how you show that you meet obligations that still exist: Title VI, the Justice Department’s coordination rule at 28 CFR 42.405(d)(1), the program rules for SNAP, WIOA, Medicaid, health programs, transit and disaster aid, and state and local law. Dropping the plan removes your evidence, not your obligations.

Our plan still cites EO 13166

Re-base it. Most obligations are unchanged; the citations are not. We map every citation to what is in force and redline the plan.

Our FTA Title VI Program is due

FTA still lists Circular 4702.1B. We write the Language Assistance Plan so it holds whether or not FTA revises the circular.

We run SNAP, WIOA or Medicaid

Those program rules are in force and unchanged. Your plan should cite them by section and meet their thresholds.

Our state has a language access law

State law is unaffected by EO 14224, and Maryland, Colorado and Washington have acted since the order. Your plan must meet the state test, not only the federal one.

We have no plan at all

Start with the obligations register and the language-need profile. The rest of the plan follows from those two documents.

We serve Afghan residents

Then the standard Census tables undercount them. We measure Pashto, Dari and the other Afghan languages directly.

What Executive Order 14224 changed, and what it did not

The status of each instrument a state or local language access plan is likely to cite, as of September 26, 2026. Each citation links to its primary source.

Instrument
Status
What it means for your plan
InstrumentTitle VI of the Civil Rights Act of 196442 U.S.C. 2000d
StatusIn force
What it means for your planBars national-origin discrimination in any program that receives federal funds. Federal enforcement now targets intentional discrimination.
InstrumentJustice Department Title VI coordination rule28 CFR 42.405(d)(1)
StatusIn force
What it means for your planWhere a significant number or proportion of the people eligible to be served, or likely to be directly affected, need information in another language, you must take reasonable steps to provide it in appropriate languages.
InstrumentExecutive Order 14224, designating English as the official language90 FR 11363
StatusIn force for federal agencies
What it means for your planSigned March 1, 2025. Revokes EO 13166. Agency heads “are not required to amend, remove, or otherwise stop production of documents, products, or other services prepared or offered in languages other than English.”
InstrumentExecutive Order 13166, improving access for people with limited English proficiency65 FR 50121
StatusRevoked March 1, 2025
What it means for your planSigned August 11, 2000. A plan that cites it as its authority needs a new legal basis.
InstrumentJustice Department LEP guidance to funding recipients (2002)67 FR 41455
StatusRescinded March 21, 2025
What it means for your planThe source of the four-factor analysis and the “safe harbor.” The rescission notice (90 FR 15721) reminds recipients that denial of language assistance services “can be evidence of discrimination on the basis of national origin or disability under certain circumstances.”
InstrumentAttorney General memorandum implementing EO 14224July 14, 2025
StatusIn force for federal agencies
What it means for your planRescinded the Justice Department’s remaining language access guidance, told other agencies to review theirs, suspended LEP.gov pending review, and promised new guidance for public comment within 180 days. None had appeared in the Federal Register as of September 26, 2026.
InstrumentTitle VI disparate-impact provisions28 CFR 42.104(b)(2)
StatusRemoved December 10, 2025
What it means for your planThe Justice Department went first (90 FR 57141). By August 26, 2026 more than a dozen agencies had followed, among them Transportation, Agriculture, Labor, Homeland Security, Health and Human Services, Education, State, Defense and Treasury. HUD, Veterans Affairs and AmeriCorps have proposed the change.
InstrumentHUD, Treasury and DHS LEP guidance to recipientsFederal Register notices
StatusWithdrawn 2025–2026
What it means for your planHUD effective September 17, 2025; Treasury March 4, 2026; DHS July 14, 2026. The DHS notice still says language assistance “may be required under certain circumstances.”
InstrumentSNAP bilingual requirements7 CFR 272.4(b)
StatusIn force
What it means for your planTranslated materials where about 100 low-income households share one language, or about 5 percent in larger areas; bilingual staff or interpreters in those offices.
InstrumentWIOA Section 188 nondiscrimination rule29 CFR 38.9
StatusIn force
What it means for your planReasonable steps to give each person with limited English proficiency meaningful access; vital information translated for significant language groups.
InstrumentSection 1557 of the Affordable Care Act, for health programs45 CFR 92.201
StatusIn force
What it means for your planQualified interpreters and translators. Machine translation of critical content must be reviewed by a qualified human translator.
InstrumentMedicaid information and language services42 CFR 435.905(b)
StatusIn force
What it means for your planLanguage services at no cost to the individual, and taglines in other languages.
InstrumentFTA Circular 4702.1B, Title VI for transitFTA C 4702.1B
StatusListed; no change published
What it means for your planTransit Title VI Programs include a Language Assistance Plan built on the four-factor analysis. The Department of Transportation removed its disparate-impact provision on June 11, 2026.
InstrumentFHWA Title VI programs for state transportation departments23 CFR 200.9(b)(12)
StatusIn force
What it means for your planTitle VI information for the public, in languages other than English where appropriate.
InstrumentStafford Act Section 308, disaster assistance42 U.S.C. 5151
StatusIn force
What it means for your planDisaster relief without discrimination on grounds that include English proficiency.
InstrumentADA Title II web and mobile accessibility rule28 CFR 35.200
StatusIn force; dates moved April 20, 2026
What it means for your planWCAG 2.1 AA by April 26, 2027 for governments of 50,000 or more, and April 26, 2028 for smaller ones and special districts. It covers the translated documents you post online.
InstrumentState and local language access lawsSee the state table
StatusIn force
What it means for your planUnaffected by EO 14224. Maryland and Colorado added to theirs in 2025, and Washington passed a new law in 2026.

Pending and dated

  • Justice Department guidance promised in the July 14, 2025 memorandum: not issued as of September 26, 2026.
  • HUD’s proposed change to its Title VI rule: comments close October 9, 2026.
  • State deadlines: Illinois compliance reports and Colorado’s assessment, December 31, 2026; Maryland enforcement, July 1, 2027, and full compliance, July 1, 2028; Washington guidelines, December 1, 2027, and agency plans, June 30, 2028.

We re-check this register every month and date each change. It is a reference, not legal advice; your counsel’s reading governs.

State and local language access laws still apply

Executive Order 14224 does not reach state or local law. Since the order, Maryland and Colorado have added to theirs, Washington has passed a new law, and New York’s Office of Language Access has said the order and the federal guidance “neither affect nor revoke” New York’s Language Access Law.

Jurisdiction
Law
Since
Test for translation
JurisdictionCalifornia
LawDymally-Alatorre Bilingual Services Act, Gov. Code §§ 7290–7299.8
Since1973
Test for translationState offices: 5% of an office’s clients. Local agencies decide what a “substantial number” is.
JurisdictionColorado
LawHouse Bill 25-1153
Since2025
Test for translationA statewide assessment of agencies’ language access, due December 31, 2026; not yet a mandate.
JurisdictionDistrict of Columbia
LawLanguage Access Act of 2004
Since2004
Test for translation3% or 500 people, whichever is fewer, of those served or likely to be served; a plan every two years.
JurisdictionHawaii
LawHawaii Revised Statutes chapter 321C
Since2006
Test for translationWritten translation for 5% or 1,000 people, whichever is less; interpretation for everyone.
JurisdictionIllinois
LawLanguage Equity and Access Act, Public Act 103-0723
Since2024
Test for translationMore than 1,000 people or 5% of those served; compliance reports due December 31, 2026.
JurisdictionMaryland
LawState Government §§ 10-1101 et seq., amended by Chapter 434 of 2025
Since2002 and 2025
Test for translation0.5% of the state’s population since the 2025 amendments (previously 3% of a local office’s area); enforcement from July 1, 2027, full implementation by July 1, 2028.
JurisdictionMichigan
Law2023 Public Act 241
Since2023
Test for translation3% of an area, or 3% or 500 of an office’s clients; interpreting by a relative, friend or bystander does not meet its requirements.
JurisdictionNew Jersey
LawP.L. 2023, chapter 263
Since2024
Test for translationThe seven most common languages; interpretation in any language.
JurisdictionNew York
LawExecutive Law § 202-a
Since2022
Test for translationThe twelve most common languages, plus up to four more per agency; interpretation in any language.
JurisdictionWashington
LawSubstitute House Bill 2475
Since2026
Test for translationStatewide guidelines by December 1, 2027; agency plans by June 30, 2028.

City ordinances

  • New York CityLocal Law 30 · Ten designated languages
  • San FranciscoLanguage Access Ordinance · 6,000 residents citywide, from January 1, 2026
  • OaklandEqual Access to Services Ordinance · 10,000 residents
  • BostonCity Code § 6-10.1 · 5% or 1,000

Fixed language lists that leave out Pashto and Dari

  • New York State12 languages, no Pashto or Dari
  • New Jersey7 languages, no Pashto or Dari
  • New York City10 languages, no Pashto or Dari
  • District of Columbia6 languages, no Pashto or Dari
  • San Francisco4 languages, no Pashto or Dari
  • Seattle15 languages, no Pashto or Dari
Pashto and Dari are on none of these fixed lists. Afghan residents reach your obligations through tests based on an office’s own caseload, which is why your own records matter more than a statewide list.
Virginia, home to one of the three largest Afghan-born populations, has no statewide language access law; its official-English statute neither requires nor bars other languages “except as provided by law.” Prince William County’s 2024 review lists Pashto and Dari/Farsi among its six largest limited-English groups.

Why standard Census tables hide Pashto and Dari speakers

Census table B16001 places Pashto in “Other Indo-European languages” and counts Dari inside “Persian (incl. Farsi, Dari).” The shorter table C16001 hides both. The American Community Survey microdata codes them separately, Pashto 1327, Dari 1292 and Farsi 1290, and that is where we start, before adding your own intake fields, interpreter logs, school home-language surveys and resettlement data.

Language
Table B16001 (42 groups)
Table C16001 (12 groups)
Microdata code (LANP)
LanguagePashto
Table B16001 (42 groups)Other Indo-European languages
Table C16001 (12 groups)Other Indo-European languages
Microdata code (LANP)1327
LanguageDari
Table B16001 (42 groups)Persian (incl. Farsi, Dari)
Table C16001 (12 groups)Other Indo-European languages
Microdata code (LANP)1292
LanguageFarsi (Iranian Persian)
Table B16001 (42 groups)Persian (incl. Farsi, Dari)
Table C16001 (12 groups)Other Indo-European languages
Microdata code (LANP)1290
LanguageUzbeki
Table B16001 (42 groups)Other languages of Asia
Table C16001 (12 groups)Other Asian and Pacific Island languages
Microdata code (LANP)1652

Sources: Census Bureau language-use documentation and ACS variable lists, 2022 and 2024.

Where Afghan-born residents live

  • California76,546 ±9,670
  • Texas27,014 ±6,850
  • Virginia26,559 ±4,361
  • Washington17,694 ±6,052
  • New York12,485 ±3,805
  • Maryland9,973 ±4,098

Afghan-born residents, American Community Survey 2024 1-year estimates, table B05006, with 90% margins of error. These six states hold 72.8% of the national total.

The largest metro populations are the Washington, D.C. area and Sacramento, about 19,000 each, and the San Francisco–Oakland area, about 13,000 (Migration Policy Institute, 2018–22 ACS).

Home languages of Afghan immigrants

32%Pashto
27%Persian (Farsi)
26%Dari
15%Other

Languages spoken at home by Afghan immigrants (Migration Policy Institute, 2022 ACS). Many Afghans call Dari “Farsi,” so part of the Farsi share is Afghan Dari.

Pashto is not a dialect of Dari or Farsi, and Dari is not Farsi

Pashto is a separate language. Dari, the Persian of Afghanistan, and Farsi, the Persian of Iran, differ in everyday words, official terms and pronunciation. A notice written in Iranian Persian reads as foreign to many Afghan residents, and many Pashto speakers cannot use it at all. Your plan should list Pashto, Dari and Farsi separately, and let residents ask for their own variety of Pashto or dialect of Dari, and for a same-gender interpreter.

Pashto
ژباړونکي ته اړتیا لرم.
Dari (Afghanistan)
به ترجمان ضرورت دارم.
Farsi (Iran)
به مترجم نیاز دارم.
“I need an interpreter,” in Pashto, Afghan Dari and Iranian Persian. The Dari and Farsi lines share a grammar and differ in both key words.

Most Afghan residents arrived after 2010, during and after the Afghan war, as Special Immigrant Visa holders, refugees or 2021 evacuees, many of them families of people who worked alongside U.S. forces. The Afghan-born population grew 89% between 2021 and 2024, so the need is ongoing, not a surge. Your plan should serve the Afghan diaspora in your jurisdiction the way it serves every other language community.

Many Afghan people in your jurisdiction lived through the war and the 2021 evacuation, and some carry moral injury, sometimes called moral trauma. A plan that serves them names trauma-informed interpreting for public safety, social services and immigration-related interviews, offers a same-gender interpreter on request, and never uses children as interpreters. Diana Ayubi, Psy.D., reviews our protocol for these interviews.

How we build your language access plan

Review, rebuild, run. Three steps, with the detail below.

  1. 1Weeks 1–4

    Review

    Obligations register, citation redline, language-need profile.
  2. 2Weeks 5–12

    Rebuild

    The plan, its standards and policies, community review and adoption.
  3. 3Quarterly

    Run

    Measures, test contacts and a register kept current.
  1. Weeks 1–3

    Obligations

    We read your current plan, grants, program rules, state law and local ordinances, and build the obligations register.

    You receive: Obligations register and a redline of your current plan

  2. Weeks 2–6

    Evidence

    We build the language-need profile from ACS microdata and your records, inventory every contact point, and run test calls and visits in Pashto, Dari and your top languages.

    You receive: Language-need profile, contact-point inventory and test findings

  3. Weeks 5–10

    Design

    We draft the plan: vital documents, interpreter and translation standards, the machine translation policy, notices and training.

    You receive: Draft plan for staff and counsel review

  4. Weeks 9–12

    Review and adoption

    Community reviewers and our Cultural Compliance Bureau read every line residents will see. We brief leadership and prepare the adoption materials.

    You receive: Final plan and adoption brief

  5. Quarterly, then yearly

    Monitoring

    We report against the plan’s measures and update the register when the law moves.

    You receive: Quarterly note and annual report

A review of an existing plan takes three to four weeks. A full plan for a county, city or state agency typically takes ten to fourteen weeks.

What you get: a language access plan you can defend

  • Obligations register

    Every law, rule, grant condition and ordinance that binds you, with its status, citation and date, re-checked when the law moves.
  • Language-need profile

    Who you serve and in which languages, from ACS microdata and your own records: Pashto, Dari and every language over your threshold, not only the top ten.
  • Contact-point inventory

    Every place the public meets you, from the front counter and phone lines to field visits, hearings and 911 transfers, and the language route at each.
  • Vital-document register

    Which documents are vital, from benefit notices to public safety orders, in which languages, by what date, with a named owner for each.
  • Interpreter and translation standards

    What “qualified” means in your agency, including for Pashto and Dari, where no U.S. interpreter certification exam tests either language; dialect and gender matching; no children or relatives as interpreters.
  • Machine translation and AI policy

    What may be machine-translated with a notice, what needs review by a qualified human translator, and what must be human from the start.
  • Notices, taglines and “I speak” cards

    A notice of free language help, taglines for vital documents, and language identification cards that include Pashto and Dari.
  • Staff training

    Front-line, supervisor and leadership modules: identifying a language, booking an interpreter, working with one, and what never to do.
  • Complaint procedure

    How a resident complains in their own language, who answers, and the record it leaves.
  • Monitoring framework

    Measures, targets and an annual report template, so your next review starts from evidence.
  • Adoption brief

    A staff report, resolution language and a one-page summary for your council or board and the public.
  • Implementation roadmap

    First-year steps in order, with owners and the drivers of cost.

Delivered as editable Word and Excel files and as accessible PDFs that meet WCAG 2.1 AA, ready to enter your public records.

A small Afghanistan flag among rows of small United States flags on a lawn in front of a stone campus building

Why Ariana Nexus for language access planning

No U.S. interpreter certification exam tests Pashto or Dari, so your plan has to define “qualified” itself. We assess and train Pashto and Dari interpreters, our own and others across the Afghan diaspora, so we know what that definition must test, and we write it as requirements any provider can meet.

  • Plans built on law in force

    Every citation is dated and linked to its primary source. Nothing in your plan rests on a revoked order or rescinded guidance.
  • The residents your data misses

    We measure Pashto, Dari and the other Afghan languages with microdata and your own records, and use the same method for every small language group you serve.
  • A definition where no exam exists

    Your plan gets a definition of a qualified Pashto or Dari interpreter that it can defend in a review or a complaint, written as testable requirements, not as a brand.
  • Standards, never vendors

    We also provide interpreting and translation, so we say so on every deliverable. Your plan names requirements, not suppliers, and where your procurement rules require it, we step aside from the work the plan describes.
  • Scholars, not bilinguals

    Your plan is written by people educated at Cornell, the University of Chicago, the University of British Columbia and Otto von Guericke University Magdeburg, who come from the Afghan communities your plan must reach.
  • One firm, one point of accountability

    Every part of the plan, from the legal register to the Pashto “I speak” card, is produced by our own people.

Security, privacy and compliance

Registered for public work

SAM.gov active, UEI M2UDMUDFXGL9, CAGE 1Z3A3.

Resident data by agreement only

We work from aggregate data by default. Resident-level records move only under a signed data agreement, to named people, and are returned or destroyed at close with a written record.

Confidential before transfer

A nondisclosure agreement is signed before any internal document leaves your agency.

Accessible by default

Every deliverable meets WCAG 2.1 AA, the standard the ADA Title II web rule applies to what you post.

Ready for public records

Drafts are marked as drafts, finals are written to be published, and nothing depends on a proprietary tool.

Interests declared

Our interest in interpreting and translation work is stated on every deliverable.

No channels into Afghanistan

We never route documents, data or inquiries through channels controlled by the de facto authorities in Afghanistan.

Counsel stays in charge

The register is a reference, not legal advice. We work alongside your counsel, who signs the legal reading.

The team behind your language access plan

Your plan is written by a consulting team, not a vendor’s bilingual staff: alumni and scholars of leading universities who have studied the law, the data and the languages, and who know the communities the plan must reach.

Hassan Ukasha, Managing Partner, Ariana Nexus
Program oversight

Hassan Ukasha

Managing Partner
Oversees the firm’s operations and its language access planning program for state and local agencies, and is accountable for every plan we deliver.
  • B.S., Global and Public Health Sciences, Cornell University
  • M.P.H., Infectious Diseases, Cornell University

Grew up in Herat. Languages: Pashto, Dari, English, Urdu and Hindi; working Arabic.

LinkedIn · ORCID · Google Scholar

  • Zeba Haqbani

    Zeba Haqbani

    Senior Partner
    • B.Sc., University of British Columbia
    Builds the plan’s systems: the contact-point inventory, language records, monitoring measures and annual reporting.

    Lived in Kabul.

  • Hussain Ahmad

    Hussain Ahmad

    Analyst
    • M.Eng., Cornell University
    • Ph.D., University of Chicago
    Leads the language-need profile and the machine translation policy: ACS microdata, agency records and the line between machine and human.
  • Wasil Peroz

    Wasil Peroz

    Principal
    • B.A., Milli University
    • M.Sc., Otto-von-Guericke University Magdeburg
    Leads the obligations register: federal, state and local law, grant conditions, and European public-law parallels for clients abroad.
  • Maryam Safi

    Maryam Safi

    Principal
    • B.A., Cornell University
    Leads language quality: interpreter and translation standards, vital-document review and the Pashto and Dari materials.

Cultural Compliance Bureau

Our internal review practice. It reads every Pashto, Dari and other Afghan-language line your plan puts in front of residents, and tests notices and “I speak” cards with community reviewers before adoption.

Language specialists

Native-speaker specialists across the 24 Afghan languages review materials in the smaller languages your data shows, from Uzbeki and Turkmeni to Pashayi and the Nuristani languages.

Languages we plan for and work in

A language access plan must cover every language your residents speak, and we write plans for all of them. We work directly in Pashto, Dari and 22 more Afghan languages, in English, and in twelve more languages.

Iranian 12
  • Pashto
  • Dari
  • Aimaq
  • Balochi
  • Ormuri
  • Parachi
  • Wakhi
  • Shughni
  • Sanglechi
  • Ishkashimi
  • Munji
  • Yidgha
Turkic 3
  • Uzbeki
  • Turkmeni
  • Kyrgyz
Indo-Aryan 3
  • Pashayi
  • Gawarbati
  • Tirahi
Nuristani 5
  • Nuristani (Ashkun group)
  • Kati
  • Prasun
  • Waigali
  • Tregami
Dravidian 1
  • Brahui

We match Pashto’s regional varieties, such as Kandahari and Nangarhari, and Dari’s dialects, such as Kabuli, Herati, Badakhshi and Hazaragi.

English and twelve more languages

  • English
  • French
  • German
  • Spanish
  • Italian
  • Hebrew
  • Urdu
  • Arabic
  • Hindi
  • Portuguese
  • Chinese
  • Russian
  • Turkish

Language access planning for public bodies outside the United States

Public bodies in Germany, the United Kingdom, Canada, Australia and the Netherlands serve large Afghan populations and face the same questions: which languages, which documents, which standard. We work with them in English, German or French, and in Pashto, Dari and the other Afghan languages.

  • 449,780GermanyAfghan nationals, December 31, 2025. Destatis.
  • 59,797Australiaborn in Afghanistan, 2021 Census. Australian Bureau of Statistics.
  • 55,195CanadaAfghans arrived from August 2021 to November 1, 2024. IRCC.
  • 43,402Netherlandsborn in Afghanistan, January 1, 2025. Eurostat.
  • 39,058United Kingdomresettled under Afghan schemes, to June 30, 2026. Home Office.

How public bodies ask for this work in their language

  • FrenchPlans d’accès linguistique pour les services publics, en pachto et en dari
  • GermanSprachmittlung und Sprachzugangskonzepte für Behörden – Paschtu und Dari
  • SpanishPlanes de acceso lingüístico para organismos públicos, en pastún y darí
  • ItalianPiani di accesso linguistico per enti pubblici, in pashto e dari
  • Hebrewתוכניות נגישות לשונית לרשויות ציבוריות בפשטו ובדרי
  • Urduسرکاری اداروں کے لیے پشتو اور دری میں لسانی رسائی کے منصوبے
  • Arabicخطط الوصول اللغوي للجهات الحكومية باللغتين البشتوية والدرية
  • Hindiसरकारी विभागों के लिए पश्तो और दारी में भाषाई पहुँच योजनाएँ
  • PortuguesePlanos de acesso linguístico para órgãos públicos, em pastó e dari
  • Chinese为政府机构制定普什图语和达利语语言服务计划
  • RussianПланы языкового доступа для государственных учреждений: пушту и дари
  • TurkishKamu kurumları için Peştuca ve Darice dil erişimi planları

How agencies engage us

Engagement
Typical length
What it covers
EngagementPlan review against current law
Typical length3–4 weeks
What it coversA citation-by-citation review of your current plan, an obligations register and a redline.
EngagementFull language access plan
Typical length10–14 weeks
What it coversThe complete plan, from the obligations register to the adoption brief.
EngagementProgram plans
Typical lengthScoped per program
What it coversFTA Title VI Language Assistance Plans, SNAP and WIOA language plans, Section 1557 plans for health departments, and disaster and election language plans.
EngagementStatewide and multi-agency programs
Typical lengthScoped per program
What it coversGuidance, templates and plan reviews for state language access offices and multi-department rollouts.
EngagementMonitoring and annual review
Typical lengthQuarterly and yearly
What it coversMeasures, test calls in Pashto and Dari, and a register kept current.

What changes the scope

  • The number of departments and programs
  • The languages over your threshold
  • The volume of vital documents
  • The community engagement you want
  • The number of staff to train
  • Access to your records and data
  • Your state’s reporting deadlines

How agencies buy

Agencies engage us through a small-purchase or informal quote under their threshold, an RFP or RFQ, a subcontract under their transit or planning consultant, or a sole-source justification where Afghan-language expertise is the need.

SAM.gov active · UEI M2UDMUDFXGL9 · CAGE 1Z3A3 · Capability Statement

Questions agencies ask about language access plans after Executive Order 14224

Does Title VI still require language access after Executive Order 14224?

Yes, in a narrower form. Title VI still bars national-origin discrimination by any agency that receives federal funds, and the Justice Department’s April 2025 rescission notice says denial of language assistance services “can be evidence of discrimination on the basis of national origin or disability under certain circumstances.” What changed is enforcement: federal agencies now pursue intentional discrimination, not disparate impact. Program rules and state and local law still apply in full.

Do we still need a language access plan?

Almost certainly, if you receive federal funds or work in a state or city with a language access law. For most agencies no federal rule requires the plan document itself, though FTA’s transit circular, the Section 1557 rule for health programs (45 CFR 92.8(d)) and several state laws do. The plan is how you show you meet obligations that still exist. Dropping it removes your evidence, not your obligations.

Does the English official language executive order apply to state and local governments?

Not directly. Executive Order 14224 directs federal agencies. It revoked EO 13166 and told the Attorney General to replace federal language access guidance, and it states that “nothing in this order, however, requires or directs any change in the services provided by any agency.” State and local agencies feel it through federal funding, reviews and enforcement, not as a rule of their own.

Is Executive Order 13166 still in effect?

No. Executive Order 13166 of August 11, 2000 was revoked by Executive Order 14224 on March 1, 2025. A plan that cites EO 13166 as its authority should be re-based on the obligations in force today.

Was the DOJ LEP guidance rescinded, and what replaces it?

Yes. The Justice Department rescinded its 2002 guidance to funding recipients on March 21, 2025, and the Attorney General’s July 14, 2025 memorandum rescinded its remaining language access guidance, told other agencies to review theirs and suspended LEP.gov. The memorandum promised new guidance for public comment; none had appeared as of September 26, 2026. HUD, Treasury and DHS have also withdrawn their guidance to recipients.

Do transit agencies still need a Language Assistance Plan for FTA Title VI?

As of September 26, 2026, FTA still lists Circular 4702.1B, which asks recipients for a Title VI Program that includes a Language Assistance Plan based on a four-factor analysis, and it has published no change. The Department of Transportation removed its disparate-impact provision on June 11, 2026, so we write your plan to hold whether or not FTA revises the circular.

What is a four-factor analysis, and should we still use it?

It weighs four things: the number or proportion of people with limited English proficiency you serve or are likely to meet, how often they contact you, how important the program is to their lives, and your resources and costs. It came from the rescinded federal guidance, but it remains the clearest way to show your choices were reasonable, and FTA’s circular still uses it.

What is the safe harbor provision, and does it still apply?

The former Justice Department guidance treated translating vital documents for each language group of 5 percent or 1,000 people, whichever is less, as strong evidence of compliance. That federal guidance was rescinded in 2025. The same test survives in state and local law: Hawaii uses 5 percent or 1,000, Illinois more than 5 percent or 1,000, and Boston 5 percent or 1,000.

What counts as a vital document?

Any document critical to getting or keeping a service or benefit, or required by law: applications, consent and complaint forms, notices of rights, eligibility and denial letters, notices of hearings and deadlines, and emergency and public-safety information. Your plan should list them by name and program, with the languages each must be in.

Can we use Google Translate or AI to translate government documents?

For low-risk, informal content with a notice, sometimes. For vital documents, not without review by a qualified human translator. Health programs are already bound by that rule under 45 CFR 92.201(c)(3). Machine output in Pashto and Dari is less reliable than in major languages, so your plan should say which content may be machine-translated and who checks it.

Can bilingual staff or family members interpret for the public?

Bilingual staff can, if your plan requires them to pass a language and interpreting assessment first; speaking a language is not the same as interpreting. Family members and friends should interpret only in an emergency, and children never. Michigan’s 2023 law says interpreting by a relative, friend or bystander does not meet its requirements for state agencies.

Is Dari the same as Farsi when we book an interpreter?

No. Pashto is a separate language, not a dialect of either. Dari is the Persian of Afghanistan and Farsi the Persian of Iran; they differ in everyday words, official terms and pronunciation, and a Farsi interpreter can miss meaning with an Afghan resident. List Pashto, Dari and Farsi separately. Pashto is the single most reported home language among Afghan immigrants, at 32%.

How do we find how many Pashto and Dari speakers live in our county?

Not from the standard Census tables. Table B16001 puts Pashto in “Other Indo-European languages” and counts Dari inside “Persian (incl. Farsi, Dari).” Use the ACS microdata, where Pashto (1327), Dari (1292) and Farsi (1290) have their own codes. Its smallest areas hold about 100,000 people, so combine it with your intake language fields, interpreter logs, school home-language surveys and resettlement data.

Which states have language access laws?

State laws cover state agencies in California, Hawaii, Illinois, Maryland, Michigan, New Jersey, New York, Delaware, Minnesota and Nevada, and in the District of Columbia; Massachusetts acts by executive order, and Washington’s 2026 law phases in through 2028. Cities including New York, San Francisco, Oakland and Boston have ordinances. Their tests differ, so your plan must meet the one that applies to you.

How long does a language access plan take, and what does it cost?

A review of an existing plan against current law takes three to four weeks. A full plan for a county, city or state agency typically takes ten to fourteen weeks. Cost depends on the departments and programs covered, the languages over your threshold, the volume of vital documents, community engagement and training, and we scope it after one call with your coordinator.

Will you recommend your own interpreting services in our plan?

No. Our plans set standards, not vendors: they say what a qualified interpreter or translation must meet, never who supplies it. We declare our interest in interpreting and translation work on every deliverable, and where your procurement rules bar the author of a specification from bidding on the work it describes, we step aside from that work.

Start with the plan you have

Send us your current language access plan, or tell us you do not have one. A partner in our Washington, D.C. office replies within one business day with the questions that decide scope.