According to the BABOK^® v3 guide, the purpose of Confirm Elicitation Results is as follows:

The primary reason the business analyst should always check the information that was obtained during an elicitation session is to uncover any errors, conflicting information, any missing information, and potential ambiguities that might need to be clarified with stakeholders.

The business analyst should compare the elicitation results against any existing information and/or the results of similar sessions to ensure the information is consistent. It might be required for the business analyst to engage stakeholders to clarify or confirm that their information was correctly captured during the elicitation session. Depending on how accurate the information is, it might be required to plan additional elicitation sessions to elaborate or clarify any misinformation or discrepancies with stakeholders. It is however recommended to try to avoid unnecessary repeats of similar conversations or elicitation sessions to prevent stakeholders from losing confidence in the business analysis team's capabilities during elicitation itself. 

It is worth noting that this task of confirming the elicitation results is much less rigorous and more of an informal review than what occurs during the analysis stages of business analysis work.

Example of confirming elicitation results

In a practical example, you might simply compile all the elicitation results into a formatted document, which is then circulated back to the stakeholder group who participated during the elicitation workshop you facilitated. You then invite everyone to review the provided information with a view to ensure it is accurate and captures the scope of what was agreed during the elicitation activity itself. As a business analyst, you should make sure to follow up with any stakeholder who requires changes or corrections to ensure you maintain a strong and trusted relationship for future elicitation activities.