A consultant must follow a structured project management methodology to ensure a Nonprofit Cloud implementation is delivered on time and within budget. The standard lifecycle, aligned with the Project Management Institute (PMI) and Salesforce best practices, consists of five distinct phases.

Initiate: This is the "Discovery" and "Alignment" phase. The consultant identifies the key stakeholders, defines the high-level project goals (the "Why"), and secures the project charter. For a nonprofit, this often involves the "Power of Us" application and licensing verification.

Plan: In this phase, the consultant defines the "How." This includes gathering detailed requirements, creating the Solution Design Document (SDD), mapping the data migration strategy, and finalizing the project schedule.

Execute: This is the "Build" phase. The consultant and developers configure the Nonprofit Cloud (Objects, Flows, DPE, etc.), perform data migrations, and build any necessary integrations.

Monitor and Control: This phase runs concurrently with Execute. The consultant tracks progress against the plan, manages "Scope Creep," performs User Acceptance Testing (UAT), and handles quality assurance. It ensures that the project doesn't deviate from the organization's mission-critical needs.

Close: The final phase involves the formal "Go-Live," end-user training, handing over documentation to the nonprofit's admin, and conducting a "Lessons Learned" session.

Why Option B and C are incorrect: You cannot "Plan" (Phase 2) effectively until you have "Initiated" (Phase 1) the project and identified who the stakeholders are and what the project charter entails. Furthermore, "Monitor and Control" must happen before you can officially "Close" the project.