Project Initiation Request and Business Case in PM²: from request to investment decision
Twenty-fourth article in the “Learning PM² Through a Project” series
Not every idea deserves to become a project. Before planning activities, assigning people or choosing a solution, two things must be clear: what is being requested and why it is worth investing.
In PM², the Project Initiation Request (PIR) captures and structures the initial request. The Business Case assesses whether the project is justified by comparing expected value, options, costs, risks and impacts. They are connected, but they are not the same document.
Two artefacts, two questions
| Artefact | Central question | Result |
|---|---|---|
| Project Initiation Request (PIR) | Which problem, opportunity or need merits examination? | An initial request described clearly enough to start assessment. |
| Business Case | Is it worth investing in this initiative compared with alternatives? | A documented justification to decide whether to authorise the project and planning. |
A PIR may originate from a user, executive, audit, regulatory obligation, opportunity or operational problem. The Business Case turns that intuition into an informed decision.
The Project Initiation Request: clarify the starting point
The PIR is not a miniature project and should not contain a detailed plan. It prevents discussion from beginning with a preferred solution.
A useful PIR clarifies at least:
| Element | Example question |
|---|---|
| Need or opportunity | What problem exists today, and for whom? |
| Initial objectives | Which improvement is sought? |
| Expected benefits | Which value could it create? |
| Urgency and driver | Is there a regulatory deadline, cost, risk or opportunity? |
| Initial scope and boundaries | Which area is to be explored, without pretending it is already defined? |
| Stakeholders and sponsor | Who requests it, who is affected, who can authorise? |
| Assumptions and constraints | What data is missing, and which technology limits, indicative budget or dependencies exist? |
A good PIR does not say “develop a new app”. It might say: “late cancellations leave class places empty; we want to reduce no-shows and make availability visible.” The solution remains an open question until options and feasibility have been analysed.
The Business Case: justify the choice
The Business Case should enable governance to decide whether to proceed, change the idea, defer it or not invest. It is not a document that must prove the original idea right at all costs.
A practical structure includes:
| Section | What it clarifies |
|---|---|
| Context and problem | Current situation, causes and effects. |
| Objectives, outcomes and benefits | Which change is sought and how it will be measured. |
| Options | At least a “do nothing” or status-quo option, plus realistic alternatives. |
| Comparative assessment | Value, costs, effort, schedule, risks, impacts and feasibility of options. |
| Recommended option | Proposed approach and rationale. |
| Initial estimate | Order of magnitude for resources, costs, schedule and dependencies. |
| Risks and assumptions | What may invalidate or condition the choice. |
| Required governance | Decision, sponsor, owner and conditions for proceeding. |
Precision should be proportionate to the early stage. A preliminary estimate should not be presented as a final commitment; it helps decide whether to invest in planning that will provide more reliable data.
Options: a Business Case is not merely “do” versus “do not do”
The “do nothing” option does not necessarily mean irresponsible inaction. It makes the cost of the status quo visible: inefficiency, risk, missed opportunity, poor service or non-compliance.
| Option | When it can be useful to assess |
|---|---|
| Do nothing / maintain status quo | To understand the real cost of inaction. |
| Improve process without a new solution | When the problem is primarily organisational. |
| Buy or configure an existing solution | When speed, standardisation or total cost are advantageous. |
| Build or extend an existing solution | When integration or distinctive adaptation is needed. |
| Pilot project / proof of concept | When material uncertainties should be reduced before larger investment. |
A good recommendation also makes explicit what is being given up: no choice is without trade-offs.
The Annotatio case: Smart Bookings
PIR
The initial request could be expressed as:
In gyms using Annotatio, late cancellations and bookings managed by phone or WhatsApp create empty places, manual work and inconsistent data. We request an assessment of a way to make bookings and the waiting list more reliable.
The PIR indicates need, affected users, potential value and context. It does not yet decide whether a new app, a web module, a different process or an external integration is needed.
Business Case: simplified options
| Option | Value | Cost / risk | Assessment |
|---|---|---|---|
| Continue with WhatsApp and phone | No immediate cost. | No-shows and manual work remain; no reliable traceability. | Not recommended, but useful as baseline. |
| Operating rules without development | May reduce some disorder. | Fragile adoption; no automatic waiting list. | Possible temporary measure. |
| Extend Annotatio with booking and waiting list | Integrates existing data, roles and user experience. | Development, testing, support and adoption effort. | Recommended if benefits and capacity justify it. |
| Buy an external service | Potential initial speed. | Integration, data, recurring cost and supplier dependency. | Compare if time-to-market is priority. |
The decision is not “is the feature useful?”. It is “which option provides the best balance of benefits, costs, schedule, risks and sustainability?”
From Business Case to gate decision
The Business Case informs the RfP — Ready for Planning gate. Approval does not certify that every detail is defined: it authorises investment in Planning, with any conditions decided by governance.
| Possible outcome | Meaning |
|---|---|
| Approve | Move into planning. |
| Approve with conditions | Plan, but resolve specified uncertainties by defined dates and owners. |
| Defer | More data, analysis or clearer priorities are needed. |
| Reject / stop | Investment is not justified or is not a priority. |
A “no” or deferral can be an excellent governance outcome: it prevents resources being consumed by a project that is not sufficiently justified.
Do not confuse these
| Statement | Correction |
|---|---|
| “The PIR decides the solution.” | It describes the initial request and need; solutions must be assessed. |
| “The Business Case is to approve an idea already selected.” | It should enable an informed choice among alternatives and the status quo. |
| “If the benefit is high, the project should be done.” | Feasibility, cost, risk, priority and available capacity also matter. |
| “The initial estimate is the final budget.” | It is a preliminary reference to refine during Planning. |
Three questions to anchor it
- Which problem or opportunity does the PIR describe without presupposing a solution?
- Which real options does the Business Case compare, including the status quo?
- Which assumptions could change the recommendation?
Flashcards
Q: What is the Project Initiation Request for?
A: To capture and clarify an initial request, its need, context, stakeholders and potential benefits before detailed assessment.
Q: What is the Business Case for?
A: To justify — or not justify — investment by comparing options, benefits, costs, risks, schedule and feasibility.
Q: Why include the “do nothing” option?
A: To make the cost and risk of the status quo visible and compare it with alternatives.
Exam-style question
A sponsor requests a new portal and presents a Business Case that describes only the proposed solution and its advantages. It includes no alternatives, cost of the status quo or implementation risks.
What is the main gap?
Answer: the document does not enable an informed decision. A Business Case should compare realistic options — including doing nothing or maintaining the status quo — and assess benefits, cost, risk, feasibility and impact before making a recommendation.
Source
The Project Initiation Request, Business Case and RfP gate are described in the European Commission’s PM² Methodology Guide 3.1.
Next: Project Charter, the document that turns an approved idea into a clear project mandate.