City council authorizes converting a vacant lot into a neighborhood park. Detailed plant lists and irrigation drawings are not finished yet. What distinction does this illustrate?
Select an answer to reveal the explanation.
Short Explanation
Saying yes to the park is initiation; picking every shrub is planning. Authorization answers “should we?” while plant lists answer “how, exactly?” You do not need the full nursery order to decide the project is worth doing.
Full Explanation
City council authorization to convert a vacant lot into a neighborhood park before plant lists and irrigation drawings are finished illustrates a core distinction: initiation authorizes the undertaking, while planning elaborates how the work will be done. Civic sponsors often approve purpose and investment envelope first; horticultural and civil details are developed afterward under that mandate. Waiting for every drawing before any authorization would stall public projects unnecessarily.
Requiring detailed plant lists before any authorization collapses planning into initiation and misstates CAPM sequencing. Treating authorization and detailed design as identical documents confuses a decision to proceed with technical how-to artifacts. Placing irrigation drawings only in a benefits realization report misfiles design products into value-tracking documentation.
Exam caveat: Associates should be able to place charter/authorization upstream of detailed scope and design planning without claiming that initiation needs zero information—high-level purpose is required; construction-level detail is not.
Operational check: confirm council (or sponsor) authorization exists for the park concept and boundaries, then schedule planning workshops to produce plant lists, irrigation design, and related baselines under that approved undertaking.