While the inclusion of contextual inquiry can be anticipated during the creation of the project plan, only basic assumptions, such as the number of interviews that will be conducted, can be made for the purposes of scheduling and budgeting. High-level scheduling should account for time needed to prepare for the sessions, for conducting the session, and for analyzing the data.

Typical planning steps for contextual inquiries include:

1. Formulating research goals:
   • The sequencing of processes and actions that define the user's motivation when using the product.
   • Detailed understanding of the processes that drive the user's interactions with the product, including inputs and outputs, dependency on other products, or sources of information.
   • How well is the product suiting the user's need?
   • Are there opportunities to improve processes by simplification or elimination?
   • Are there barriers for introducing change?
2. Determining which segments of the target audience are most capable of providing the relevant answers to the research, and should be tapped to participate. Also, determine the proportion of user types. This determination is often influenced by practical considerations--stakeholders typically have a good idea of who can be reached.
3. Determining the logistical challenges and a closer estimate of time and budget needs, based on the geographical location.
4. Determining who will do the recruiting--internal resources, or a third-party company who is specialized in recruiting.

5. Developing a screener based on the profile of segments of the target audience; a screener is a short questioner that helps recruiters find participants who match the required research needs.
6. Developing the CI facilitator guide. Contextual inquiry begins with a tight script that is intended to ensure: 
   • Consistency across all interviews, regardless of the interviewee
   • That all topics that make up the research are covered
7. Preparing for the sessions:
   • Dry runs help iron out the flow of the session and the sequencing of questions.
   • Test recording equipment--in addition to taking notes, the sessions are typically recorded using an audio recorder, and sometimes, if possible and relevant, a video recorder. When the topic is software, screen-sharing and recording applications are used as well.
8. Conducting the activity:
   • It is essential to make the participant feel at ease, and express appreciation for the time they spend on this activity.
   • It is important to stress to the user when the CI is scheduled, and at the beginning of the session, that this is not a test of the user, but rather--a test of sorts for the product. This is very important because many participants may feel a need that their job or privacy are threatened.
   • It is also vital to ask the users to verbalize their thoughts as much as possible, and share with the researcher their motivation and thinking before, during, and after performing a task.
   • It is crucial to ask participants to be as honest as possible--for various reasons, participants may feel that it is rude or inappropriate, or risky to share their true feelings, and try to please the designer by glossing over the negative feedback.
   • A contextual inquiry, while structured, provides the designer with many opportunities to switch from asking pre-defined to asking context-specific questions that emerge during the conversation. These often lead to uncovering unexpected information which can be a turning point in thinking about the design.
9. Analyzing and presenting results, and coming to an agreement on the approach.