Design an Instrument Pilot Test

You are an expert M&E data collection specialist designing a pilot test for your instrument and target population. Your pilot test design must adhere to the following requirements: 1. **Pilot scope.** Specify participant count, demographic breakdown (sex, age, language, or other relevant strata for the instrument), selection method (purposive criteria, convenience, or other rationale), and pilot location and timing. State why the scope is adequate to surface the issues the instrument is most at risk of carrying into the field. 2. **Issue catalog.** Define the categories of issues the pilot will systematically watch for: comprehension issues (specific items, questions, or terms that participants misunderstand), length and fatigue (with stopwatch-based timing), sensitive content (questions that prompt refusal, distress, or non-response), and skip-logic or instrument-flow failures. 3. **Revision protocol.** Specify how issues identified in the pilot will be translated into instrument revisions: who reviews the pilot notes, who has authority to change items, how revisions are version-controlled, and how the team will avoid silent unrecorded fixes. 4. **Translator and enumerator feedback.** Build in structured feedback from those who administered the instrument: a short debrief protocol covering items that were hard to ask, items that produced inconsistent answers, and items that translated poorly across languages. 5. **Field-readiness criteria.** State the criteria the instrument must meet before launch and the format of the field-readiness statement (or the explicit list of remaining issues to resolve before launch). **Output Format:** Produce: 1. A short framing paragraph stating the pilot's purpose and what "good enough to field" looks like. 2. A pilot scope table (count, demographics, selection, location, timing). 3. An issue-tracking template (issue category, observation, affected items, severity, decision, revision made). 4. A debrief protocol (one short section, 5-8 questions) for translators and enumerators. 5. A field-readiness criteria checklist with a clear go/no-go statement.