According to the PMBOK® Guide, specifically the Develop Project Charter process, the Project Charter is the foundational document that bridges the gap between organizational strategy and project execution.

Formal Authorization: The Project Charter is the document that formally authorizes the existence of a project. Without a signed charter, a project does not officially exist in the eyes of the organization, and the project manager lacks the legal or administrative standing to proceed.

Empowerment of the PM: The most critical function of the charter in this specific scenario is that it provides the project manager with the authority to apply organizational resources to project activities. Until the charter is approved by the sponsor or the initiating entity, the project manager cannot officially assign staff, spend budget, or utilize company equipment.

High-Level Scope: It establishes the high-level objectives and boundaries of the project. This ensures that when the PM does start applying resources, they are doing so in alignment with the goals the sponsor has officially sanctioned.

Analysis of other options:

Option A: The Project Management Plan is a detailed document created after the charter has been signed. You cannot effectively build a project plan without the authority and high-level direction provided by the charter.

Option B: The Business Case provides the economic justification for the project. While it explains why the project should happen, it does not grant the project manager the authority to manage resources.

Option C: Budget requirements are specific financial needs identified during the planning phase. Like the project plan, a budget cannot be officially executed or managed until the PM is authorized via the charter.

Per PMI standards, the Project Charter is the only document that solves the project manager ' s dilemma by providing the formal authorization necessary to move from a conceptual idea to an active project with assigned organizational resources.