Lingfaro

A Title VI language-access checklist for healthcare teams

A written policy is only one part of language access. The people scheduling care need a usable request process; the care team needs to know what is confirmed; and the organization needs records that explain what happened. Use this checklist to organize that work with your compliance lead, not as a promise that a fixed set of documents will satisfy every review.

Start with the applicable program and guidance

Title VI prohibits discrimination based on race, color, or national origin in programs and activities receiving federal financial assistance. HHS’s language-access information describes duties for health and human-services programs under Title VI and Section 1557. Ask the person responsible for compliance to confirm the organization’s coverage, relevant funding conditions, and current requirements.

Federal guidance is changing. The Department of Justice says it is reviewing language-access guidance following the 2025 executive order and has suspended lep.gov operations pending that review. Avoid copying an old checklist into policy without checking the responsible agency’s current position. Legal duties, operational choices, and vendor promises should be recorded separately.

1. A plan staff can use

Name the person who owns language access and the contacts available to staff when an appointment changes. Describe how staff identify communication preferences, request an interpreter, confirm the assignment, and raise a problem. Include a route for urgent situations that does not rely on a patient arranging their own help.

Use local request information to understand the languages and settings the organization serves. Do not infer a person’s language from their name, appearance, or nationality. Consider written information, disability-related communication needs, and differences between locations as well as the spoken conversation.

  • Identify the plan owner, version, review date, and where staff find it.
  • Record the standard request process and who confirms that support is arranged.
  • Name the escalation contact and the process for a failed connection, absence, or unsuitable match.
  • Train staff on the process and revisit it when services, requirements, or recurring problems change.

2. Qualification and vendor records

Keep the evidence used to decide whether an interpreter is suitable for the assignment. Separate the language pair, interpreting training, assessment or credential, relevant experience, and any limitation that affects the work. A self-reported language skill or roster listing should not be relabeled as independently verified certification.

For contracted services, record who checks qualifications and how the client receives the information it needs. Keep agreed service terms, cancellation provisions, escalation contacts, and any applicable privacy agreement accessible to the staff who use them. A signed contract does not show whether an individual encounter worked; it belongs alongside operational records.

3. Notices and instructions people can understand

Map the places where people first encounter the service: phone, website, reception, intake documents, and appointment messages. Check that staff can explain how to request language assistance. Ask the compliance lead which notices, translations, languages, formats, and distribution requirements apply to this organization.

Keep an approved source version, a translation version, an owner, and the date of review for important materials. When a form changes, check its translated versions too. Do not assume an old list of languages or a notice copied from another provider is sufficient for every setting.

4. Encounter records and follow-up

Make it possible to connect a request to the service actually provided. Useful operational fields include date, language, format, assignment reference, session timing, and whether an issue was escalated. Distinguish requested, confirmed, cancelled, and completed work so a scheduled appointment is not mistaken for delivered interpretation.

Use the minimum information needed in operational reports. Restrict access and keep sensitive patient information in its appropriate system. Set retention and deletion rules with the organization’s records and privacy leads; neither indefinite retention nor a generic deletion period is a safe universal rule.

Try retrieving a small authorized sample across locations and formats. Check whether the records agree and identify gaps without altering the original facts. Assign each correction to an owner, give it a due date, and verify the result. A retrievable record helps the organization understand its work; it does not guarantee an audit outcome.

References

Let’s plan the conversation.

Share your setting, language needs, and timing with our team.

Talk with our team