12.1 Gathering Assignment Information: Logistics, Scope & Intended Outcomes

The CASLI Fundamentals of Interpreting blueprint opens with a domain most study guides skip entirely: pre-commitment activities — "those activities that occur before the interpreter accepts or declines an engagement." The first enumerated task is to gather information about the encounter, "including logistics, scope of work and intent of the assignment," and to determine "the purpose and intended outcomes of the encounter."

This is not administrative trivia. Everything downstream — whether you are qualified, whether a team is needed, whether a Certified Deaf Interpreter belongs in the room, what you prepare, where you stand — depends on information you either extract at the request stage or never get at all. On the exam, a great many items and case-study steps hinge on whether the candidate asked the right question before saying yes.

1. Why the information gap exists

Most requests reach interpreters through a referral agency or a scheduler who is not present at the encounter and often does not know what it is really about. A request that says "1 hour, medical, 2pm, Riverside Clinic" is compatible with a routine blood draw and with an oncology consultation delivering a terminal diagnosis. Those two assignments have different demand profiles, different team requirements, and different consequences for error.

RID's CPC makes gathering this information a professional obligation rather than a courtesy. Illustrative Behavior 2.2 requires interpreters to "assess consumer needs and the interpreting situation before and during the assignment and make adjustments as needed," and 3.1 requires consulting "with appropriate persons regarding the interpreting situation to determine issues such as placement and adaptations necessary to interpret effectively."

2. The four information categories

Intent and intended outcome are different things and the blueprint lists them separately. A performance-improvement meeting has the intent of documenting a problem; the employer's intended outcome may be a signed acknowledgement, while the Deaf employee's intended outcome may be to contest the write-up. Interpreting that meeting well requires knowing both, because register, pacing, and the handling of ambiguity all change.

3. What you can ask, and what you cannot be told

Interpreters routinely hesitate to ask questions, worried that requesting information is intrusive or will cost them the job. Two correctives:

1. Asking is the professional standard, not an imposition. A qualified practitioner cannot assess fit without information. Agencies that treat questions as difficulty are describing their own workflow problem, not an ethical boundary.
2. Sometimes the information genuinely cannot be released. A hospital may not disclose a diagnosis before you arrive; a law firm may not reveal the subject of a deposition. When specifics are unavailable, shift to category-level questions that do not breach anyone's confidentiality: Is this a routine follow-up or a consultation where significant news may be delivered? Should I plan for one hour or three? Will there be more than two participants? Is a Deaf interpreter already scheduled? These answers let you assess demand without exposing private facts.

4. Turning information into a go/no-go decision

Information gathering exists to support a decision. Work it through in this order:

REQUEST ARRIVES
   |
   v
[1] LOGISTICS complete?  -- no --> Ask. Unresolved logistics = do not accept.
   | yes
   v
[2] SCOPE clear?         -- no --> Clarify product, duration, materials.
   | yes
   v
[3] INTENT understood?   -- no --> Ask category-level questions.
   | yes
   v
[4] OUTCOMES identified for BOTH/ALL parties?
   | yes
   v
[5] Feed into: qualification check (12.2), language-needs check (12.3),
    environmental/intrapersonal check (12.4), team/CDI decision
   |
   v
ACCEPT  /  ACCEPT WITH CONDITIONS  /  DECLINE AND REFER

"Accept with conditions" is a real and often-correct answer on case studies: I can take this if a team interpreter is added, or if the pre-conference happens, or if the materials are sent 48 hours in advance. Stating a condition in writing at the request stage is a pre-assignment control in Demand-Control Schema terms, and it is almost always cheaper than managing the same demand live.

5. Documenting the agreement

Confirm the agreed scope in writing — email or the agency platform — before the day. A confirmation that records start and end time, location, the identified contact, the agreed number of interpreters, and any conditions serves three purposes: it prevents scope creep ("while you're here, can you also…"), it supports accurate invoicing under CPC Tenet 6, and it creates the record you need if the assignment later goes wrong. Keep the written record consistent with Illustrative Behavior 1.2, which requires managing "data, invoices, records, or other situational or consumer-specific information in a manner consistent with maintaining consumer confidentiality."

6. Common pre-commitment failures the exam tests

• Accepting on duration alone. "It's only 30 minutes" is not an assessment; a 30-minute psychiatric intake can be the hardest half hour of your month.
• Assuming the setting label tells you the demand. "Educational" covers a kindergarten circle time and a doctoral defence.
• Treating the scheduler's summary as verified. Schedulers relay what the requester told them, which is frequently wrong about modality, language preference, and participant count.
• Discovering scope at the door. Arriving to find a second Deaf participant, a video that needs sight translation, or a four-hour agenda means the decision to accept was made on false information — and you now have to manage it in front of consumers.
• Never asking about recording. Whether the encounter is recorded, streamed, or transcribed changes your confidentiality analysis and may require consumer notice.