# Rare-pair sourcing checklist

Use this when a standard roster cannot confirm the pair fast enough.

## Checklist

- Pair status is named: active bench, vetted network, or on-request sourcing.
- Dialect, region, and script are separated before assignment.
- Reviewer profile is named for the domain and deliverable.
- Lead-time risk is written down before scope lock.
- Pilot batch trigger is clear: new pair, new domain, or high compliance risk.
- QA log expectation is named before the first batch starts.

## Questions to ask

- How many qualified linguists are confirmed for this timeline?
- Which credentials or work samples are on file?
- What happens if one linguist becomes unavailable?
- Does the pair need a pilot before the full batch?
- What will the QA log show after delivery?

If the response is silent on any item, the work has been priced but not scoped.