How to choose an interpreter vendor in Minnesota: a client evaluation guide

1. Define your language and format mix

Before speaking with providers, list the languages your organization requests and the types of appointments behind them. Include typical locations, expected duration, in-person versus external video needs, and any specialized subject matter. Use your own request history where available. This turns a general discussion into concrete scenarios that a provider can answer.

Include both frequent appointments and less common ones. If a language or format appears only occasionally, note that fact without assuming it is easy or difficult to fill. Ask what information the provider needs to assess an individual request, and how it will tell you if the request is still pending.

• Languages and any dialect preferences reported by the people you serve.
• Settings such as clinic visits, school meetings, court-related matters, or community services.
• Appointment formats and locations your organization may request.
• Typical duration, schedule patterns, and any recurring terminology or materials.
• The staff who place requests, review proposals, and respond to access issues.

2. Verify qualifications and how they are reviewed

Ask which qualifications, training, or roster status the provider can document for each type of work you may request. Ask how it verifies that information, how it handles changes, and what your organization can review before accepting an assignment. Requirements can vary by setting and institution, so have your own compliance lead identify the relevant standard rather than treating one credential list as universal.

A provider should be able to explain what it means when it describes an interpreter as qualified for a particular setting. Ask for the written process, a sample credential record with personal details removed, and a clear way to raise a concern about language fit.

3. Test request status and change handling

Ask to walk through a request from submission to confirmation. Find out what “received,” “offered,” “accepted,” and “confirmed” mean in that provider’s process. A request sent to a pool does not necessarily mean an interpreter has accepted it. Ask who contacts your team if a request remains unfilled, the interpreter cancels, or the appointment changes.

Use a realistic scenario in the conversation: change the room, adjust the start time, or specify a language variety. Observe whether the provider identifies what must be updated and who owns the next step. Do not assume that a provider offers automatic backup or an escalation process unless it explains that process and its terms.

4. Inspect sample records and exports

Ask for a sample completed-session record and a sample export for a date range, with identifying details removed. Check whether the fields match your organization’s needs. Depending on your workflow, useful fields may include appointment date, requested language, format, interpreter name or identifier, documented qualifications, confirmation status, duration, outcome, and any agreed follow-up.

Try to retrieve the sample information using the process your staff would actually use. Ask who owns the record, how corrections are handled, what privacy protections apply, and how long the provider makes records available. Your organization remains responsible for deciding what to retain and how to meet its recordkeeping rules. A sample record can show process capability; it does not guarantee the result of a future review.

5. Compare the full proposed price and terms

Ask the provider to explain the proposed amount and the conditions that could change it. Depending on the provider, relevant terms may include interpreter time, preparation, travel, minimum duration, additional time, after-hours scheduling, taxes, rescheduling, cancellation, and payment timing. Some of these may not apply to a particular request. Compare the total proposal for the same scenario instead of relying only on an advertised hourly figure.

Lingfaro displays operator-approved proposed terms before financial commitment. The client confirms the proposed terms, and payment follows session review through Stripe-hosted processing. Keep the proposal and confirmation with the appointment record.

6. Run a small pilot against your real requests

Before making a long-term choice, choose a time-limited pilot that is large enough to include the appointment types and formats you actually need. Include at least one less frequent language or a more involved scenario when it is part of your real work; do not fabricate test demand or treat one request as proof of broad coverage. Agree on what information will be reviewed and who will assess it.

Track results from completed and unfilled requests alike. A provider’s clear explanation of an unfilled request is useful evidence about its process, even when it cannot meet the request. Do not infer that a provider supports a language or guarantees a fill from a language list alone.

• Request status and confirmation time for each scenario.
• Whether the proposed interpreter and format matched the request.
• How schedule changes or technical issues were handled.
• Whether the final record contained the fields your team needs.
• The proposed price and any condition that changed the total.
• Feedback from the people who scheduled and received the service.

Make the decision with a shared scorecard

For each provider, record the evidence and any unresolved question. Have the program owner, the people who place requests, and the staff responsible for compliance and finance review the same findings. A provider with good documentation may not meet every format need; a provider with a broad service area may not fit every local appointment. The choice should follow your organization’s priorities and the provider’s written terms.

If you use more than one provider, write down which team handles each request type, how staff avoid duplicate bookings, and where the completed-session record belongs. Review the arrangement when service needs or provider terms change.