Figure 1. Project Info page overview, with the section progress shown in the left navigation and help icons beside individual prompts.

The Project Info page asks for the core facts and assumptions that explain why the project matters, how broad the change is, how ready the project is to support adoption, and how much of the value depends on people changing their ways of working.

· Project definition: the project name and a clear statement of objectives.

· Business alignment: how the project supports organizational values and strategy.

· Case for change: why the organization should change, why now, and what happens if it does not.

· Change profile: budget sufficiency, timing and flow, scope, impact, confidentiality, external stakeholder exposure, and perceived need for change.

· Readiness and governance: whether project management, work breakdown, resourcing, cadence, change management integration, and ownership are in place.

· Financial assumptions: overall project budget, change management budget, budget source, and the people-dependent ROI percentage.

Most prompts have a circular question-mark icon on the right side of the prompt line. Use this tooltip entry point when a question needs clarification before answering. The icon is visible next to text fields, scale questions, switches, readiness ratings, and budget inputs.

The narrative prompts capture the business rationale. Each open text box is followed by a completeness rating at the bottom of the field area. After writing the answer, select Incomplete, Acceptable, or Complete to indicate the quality of the response for model calibration.

· Use Incomplete when the answer is missing, too brief, speculative, or still needs stakeholder input.

· Use Acceptable when the answer is usable but may need sharper evidence, metrics, or executive wording.

· Use Complete when the answer is specific, decision-ready, and includes the business context needed for calibration.

Example: for Why change now?, a complete answer should explain the urgency, the readiness of the organization or technology foundation, the cost of delay, and the measurable value expected from acting now.

Figure 2. Open text prompts include a completeness rating directly beneath each response box.

The 1-5 scale questions describe the nature and degree of the change. The labels beneath the scale explain the meaning of the low, middle, and high anchors. Use the Clear button only when the current selection should be removed.

· For Scope of Change, select the point that reflects whether the change affects a team, a division or department, or the entire organization.

· For Impact of the Change, select the level that best reflects whether the change is incremental, significant, or transformational.

· For Perceived Need for Change, select a lower number where impacted people want the change, the middle where sentiment is neutral, and a higher number where people prefer the current state.

Figure 3. Five-point scales use numbered points with descriptive anchors beneath the scale.

Switch questions record whether a statement is currently true. In this section the switches ask whether the project is perceived as strategic and whether change competency has been developed for key roles.

Example: turn on This project is perceived as strategic when senior leaders, project sponsors, and impacted teams understand that the project supports an important business priority.

Figure 4. Binary switch questions are answered by toggling the control on or off.

The readiness questions use a 1-3 scale labeled Incomplete, Acceptable, and Complete. These questions check the project management and adoption foundations that need to be in place before change execution can be trusted.

· Select Incomplete when the item is not yet in place.

· Select Acceptable when the item exists but needs more definition, coverage, or confirmation.

· Select Complete when the item is in place, documented, and ready to support execution.

Example: for Has a project manager been assigned to oversee the entire project lifecycle?, select Complete only when a named project manager owns the lifecycle and has the authority to coordinate delivery.

Figure 5. Readiness questions use a compact three-point rating with the same Incomplete, Acceptable, and Complete language.

The final fields capture the financial assumptions used by the project model. Use whole numbers for budget fields unless your internal standard requires currency formatting, and use the percentage scale to estimate how much of the return depends on people adoption and sustained behavior change.

· Overall Project Budget: enter the total budget allocated to the project.

· Budget for Change Management: enter the budget available specifically for change management activities.

· Source of Budget: enter the owning function or funding source, such as Sales, IT, Operations, or a program budget.

· People Dependant ROI %: select the closest 10-point step that represents the share of value dependent on adoption, process compliance, and capability uplift.

Example: if most benefits rely on users adopting Copilot-assisted call preparation, follow-up, and coaching routines, a selection around 70% indicates that people adoption is a major value driver.

Figure 6. Budget fields use short text inputs, while People Dependant ROI % uses a 0-100 scale.

· Every narrative box has a response and a selected completeness rating.

· Scale questions reflect the labels shown beneath the control, not just a preferred numeric score.

· Switches are on only where the statement is currently true.

· Readiness ratings are evidence-based and not aspirational.

· Budget fields and ROI percentage are internally consistent with the project business case.

· Tooltip icons have been used where a question is ambiguous.

The next page contains the question-specific Help Center article map for this section.

​

Important: Each mapped Project Info question has a specific Adopt It help article to assist the respondent. Use the question-mark tooltip beside the front-end prompt, or open the relevant article below, before completing or rating a response. The article title is clickable, and the URL is also printed visibly so the reference is clear in Word preview and printed copies.

Full collection: Articulating the Project Information