Checklists are used for quality control when verifying requirements and designs. Checklists may include a standard set of quality elements that business analysts use to verify the requirements, or they may be specifically developed to capture issues of concern. The purpose of a checklist is to ensure that items determined to be important are included in the final requirements deliverables, or that steps required for the verification process are followed.

Reference:
BABOK v.3.0 - IIBA - A Guide to the Business Analysis Body of Knowledge - International Institute of Business Analysis (2015) (Page 47)

Explanation
The two key objectives when organizing requirements are to understand which models are appropriate for the business domain and solution scope and to identify model interrelationships and dependencies.
Answer B is incorrect. This is not a valid statement about the task of organizing requirements.
Answer D is incorrect. Each requirement will have a key performance indicator, but it's not an element for
organizing requirements.
Answer A is incorrect. There is not a structural or organizational reason to sort requirements by functional or
non-functional decomposition.

Explanation
Requirement's verification allows the business analyst and key stakeholders to define any additional information that will allow any additional work to be performed. In other words, once the current requirements are approved, the tasks may continue forward based on what's been analyzed so far.
Answer D is incorrect. Gaining approval of the cost and schedule is not an accurate answer.
Answer B is incorrect. Chartering a project isn't the best answer for this question.
Answer A is incorrect. The requirements comprise the solution scope for the business need, so this isn't the
best answer for the question.