Eliciting requirements sounds simple, until you realise that everyone has a different view of what’s “needed.” Many new business analysts find themselves in meetings full of opinions, conflicting priorities, and vague statements like “We just need it to be faster.”

Yet one of the most overlooked steps in business analysis is planning how you’ll elicit those requirements in the first place.

That’s where a requirements elicitation plan comes in. It turns chaos into structure and helps you ask the right questions, involve the right people, and collect information that leads to clear, validated requirements.

In this article, we’ll explore what an elicitation plan is, why it matters, and how to create one, step by step, using best practices from the IIBA BABOK® Guide and BCS Requirements Engineering framework.

What Is a Requirements Elicitation Plan?

According to the BABOK® Guide, elicitation refers to the tasks used to “draw out, discover, and understand stakeholder needs.” The plan ensures that this process is not left to chance. A requirements elicitation plan is a document or outline that defines how a business analyst will gather information about stakeholder needs, goals, and constraints.  

It typically answers:
– Who needs to be consulted (stakeholders)
– What techniques will be used (interviews, workshops, etc.)
– When and how the sessions will take place
– How information will be documented, verified, and approved
In other words, the elicitation plan acts as your map through the discovery phase of business analysis.

Why an Elicitation Plan Matters

Without a plan, elicitation becomes reactive—you chase stakeholders, miss critical perspectives, and risk incomplete or conflicting requirements.

A well-prepared plan brings several benefits:
– Clarity: Everyone understands the purpose, scope, and expected outcomes of elicitation activities.
– Stakeholder alignment: The plan helps build trust and engagement by showing transparency in how information will be gathered.
– Efficiency: Resources, sessions, and documentation are well-organized, saving time and rework later.
– Risk reduction: Anticipating constraints and dependencies prevents missed requirements or surprises during solution delivery.
Think of it as preventive medicine for project misunderstandings.

Core Elements of an Elicitation Plan

Every effective elicitation plan contains a few essential elements. Whether you use a spreadsheet, Word document, or online collaboration tool, include the following sections:

1. Stakeholder Identification

List everyone who has a stake in the outcome of the project: users, customers, managers, sponsors, IT staff, regulators, etc.
Use techniques like the Stakeholder Checklist or Onion Model to ensure coverage. Don’t forget indirect or supporting roles.

2. Elicitation Techniques

Specify which techniques you’ll use for each stakeholder group. Choose based on a.o. the stakeholders’ availability, knowledge, and the type of information needed.

3. Logistics and Scheduling

Define how and when activities will take place:
– Date, time, and duration of each session
– Location (physical or virtual)
– Tools used (e.g., Miro, Zoom, or MS Teams)
– Required materials (e.g., templates, process maps)

4. Documentation and Validation

Explain how findings will be recorded (e.g., meeting notes, requirements log, stakeholder register) and how you’ll confirm accuracy with participants.

How to Create Your Own Elicitation Plan (Step-by-Step)

Let’s bring it all together. Follow these five steps to develop your own elicitation plan.

Step 1: Define the purpose and scope

Start by clarifying why you are performing elicitation.

– What is the business problem or opportunity?

– Which part of the project or product are you focusing on?

– What outcomes do you expect from elicitation?

Documenting scope prevents overreach and keeps sessions result-oriented.

Step 2: Identify and document stakeholders

List all relevant individuals, groups or organizations that contribute to the requirements elicitation. Previously mentioned techniques like stakeholder  nomination, stakeholder checklist, or onion model can help you here. It is recommended to document the stakeholder together with some additional information, e.g. what is role and stake of the stakeholder in the project.

Step 3: Match elicitation techniques to stakeholders or stakeholder groups

Choose the right combination of techniques.  When preparing the requirements elicitation, we need to consider the nature of our project, the characteristics of the business situation, stakeholders’ availability and, based on advantages and disadvantages of elicitation techniques, then select the most appropriate techniques.

The research shows that business analysts do not select elicitation techniques based on their suitability to the business situation; instead it is based on how proficient a Business Analyst is in a particular technique. Doing so is like trying to use a screw and a hammer. Consequently the result of elicitation may not be satisfactory. Use the right tool for the job, always!

Step 4: Plan Logistics

Schedule sessions, book rooms, or set up online tools. Define responsibilities—who will facilitate, take notes, or manage recordings.
Don’t forget to consider time zones and accessibility if you have remote participants.

Step 5: Define Outputs and Validation

Decide how findings will be captured: templates, mind maps, or requirement logs—and how you will confirm their correctness.
A simple review meeting or email confirmation can prevent misunderstandings later.

Expert advice for using the Elicitation Plan

1. It is a living document, it is not set in stone. As you learn mode about the project and stakeholders, you may revisit and update the plan.

2. Communicate the plan and share it with your project team and key stakeholders. It helps managing the expectations.

3. Include justification of your choices. If you want to conduct a survey among users, explain why you think it is the best technique to apply.

4. Keep it proportional, a small project needs perhaps less formal approach to documenting that a big one.

5. Always confirm the elicitation results with stakeholders. It helps keeping them engaged, too!

Bringing It All Together

A strong requirements elicitation plan sets the tone for a successful project. It helps you approach discovery with structure, confidence, and professionalism—key traits every business analyst should master.

If you’re just starting your BA journey, use the BABOK® and BCS materials as your compass. Over time, you’ll learn to adapt and refine your elicitation approach based on project type, culture, and stakeholder dynamics.

Final words

Ready to take your business analysis skills further?  Explore more practical resources on techniques on BA Coach or visit IIBA.org to deepen your professional journey. Our course BCS Requirements Engineering guides you through all the activities needed to develop and manage requirements successfully.