Project initiation checklist: what to confirm before planning and mobilisation

In brief

Use this checklist to test whether a project has enough authority, definition, ownership and early control for its next approved stage. Review the initiation checklist, see how to handle gaps or explore the Project Starter Bundle.

1. What a project initiation checklist is

A project initiation checklist reviews the decisions, evidence, roles and early controls needed before a proposed project moves into its next approved stage. It supports a readiness conversation and decision record. Completing it does not authorise work by itself.

Project lifecycles and document names vary. An organisation may use a business case, project mandate, charter, Project Initiation Document (PID), combined approval pack or another model. The sequence may also differ according to delivery method, scale, risk and governance requirements.

It helps to distinguish the common functions:

• A business case supports an investment or option decision by bringing together the problem, options, costs, benefits and risks. The Australian Government's business-case guidance describes this function in a Commonwealth investment context. Use the guide to writing a business case if this evidence needs work.
• Under PMI terminology, a project charter records formal project authority. A project management plan explains how the project will be managed through delivery and closure.
• Some organisations use a broader PID that overlaps with a project management plan.
• Detailed delivery plans and registers develop or mature as the project receives authority to proceed.

These distinctions can help a review, but they do not prescribe a universal document set or sequence. Follow your organisation's delegations, assurance, procurement, privacy, security, finance and records requirements. Obtain specialist advice where relevant.

As a practical model, the project manager may coordinate the review. The sponsor, business owner and authorised decision-maker can confirm the mandate and decisions. PMO, finance, commercial, risk, technology, change or assurance roles can contribute where the context requires them. Scale the participants and evidence to the project.

2. When to use the checklist

Use a project initiation checklist when a team needs to establish whether it has enough decision evidence for the next step. Typical moments include:

• before requesting approval to begin detailed planning or mobilisation
• when a portfolio or PMO accepts a project into its governance process
• when a project manager takes over work with incomplete initiation evidence
• before a kick-off meeting, so participants start from a clear mandate
• after a material change challenges the basis on which the project was initiated

The output should reflect the decision needed now. A project may be ready to develop a detailed plan without being approved for full delivery. A kick-off meeting can coordinate an authorised start, but the meeting itself does not create authority to mobilise.

PMOEasy uses three possible overall review outcomes:

• Ready: The evidence and decisions needed for the requested next stage are sufficiently clear. This does not mean every later activity is approved.
• Ready with conditions: The current decision remains supportable despite a visible gap. The authorised decision-maker accepts the condition within their authority and records an owner, closure action, due point and limit on what may proceed before closure.
• Not ready: A material gap prevents a valid decision about the mandate, authority, funding for the requested step or authorised decision-maker.

These are overall outcomes, not scores for individual rows. The authorised reviewer should decide the result from the materiality and decision impact of the evidence and gaps.

Your organisation may use different gate language. Only an appropriately authorised decision-maker can accept conditions or waive a requirement within their authority. The checklist owner cannot do so simply to obtain a pass. Applicable safety, legal and policy questions require the organisation's specialist and governance processes.

3. Common initiation mistakes

Treating document presence as evidence

An uploaded file may be out of date, contradictory or never approved. Check whether its content is current, useful for the decision and connected to an accepted decision or named action.

Applying identical depth to every project

A lightweight internal change and a complex, high-risk investment do not need the same evidence depth or review group. Scale the checklist while retaining the decision evidence required by your organisation.

Starting mobilisation without clear authority

Record what has been approved, by whom, for which stage and within what limits. Do not let activity begin merely because a team is available or a meeting is scheduled.

Leaving ownership ambiguous

Name the sponsor, business owner, project manager and decision pathway where those roles apply. Make responsibilities, authority limits and escalation routes understandable.

Demanding false precision too early

Initiation should establish enough definition for the next decision without pretending that every cost, date, requirement or solution is final. Separate confirmed information from assumptions and items to resolve during planning.

Overlooking affected people

Identify relevant stakeholder groups, likely impacts, engagement ownership and immediate communication needs. More detailed analysis can continue in a Stakeholder Register.

Hiding gaps to produce a pass

Visible uncertainty gives the decision-maker a basis for setting conditions, limiting authority or requesting revision. Record the gap, owner, action and decision date.

Holding a ceremonial kick-off too early

Confirm the mandate, participants, key decisions and immediate actions before presenting the project as mobilised. An editable kick-off meeting agenda and minutes template can help structure the meeting and preserve its action record.

Failing to revisit the initiation basis

Reassess the evidence when a material change affects the mandate, sponsorship, outcomes, scope, funding, governance or risk context. Whether formal re-authorisation is needed depends on the organisation's tolerances and decision pathway.

4. Project initiation checklist

Treat each item as an evidence question. A useful response identifies the evidence or decision, a status and, where needed, an owner and due date. These groups are practical PMOEasy guidance informed by public initiation and assurance guidance. They are not a universal stage-gate standard.

Decision and mandate

• What is the next decision being requested: discovery, planning, mobilisation, delivery or another defined stage?
• Is there current evidence of the business need and recommendation being considered?
• Is the mandate or equivalent authority record clear about boundaries and limits?
• Can the team identify the authorised decision-maker and accepted decision-record mechanism?

If the mandate needs work, use the guide to writing a project charter and Project Charter Checklist.

Outcomes and boundaries

• Are the intended outcomes understandable and connected to the business need?
• Are success measures proportionate to the maturity of the evidence?
• Are the high-level scope and material exclusions visible?
• Are the principal deliverables clear enough for the next stage without demanding a complete delivery plan?

Ownership and governance

• Are sponsorship, business ownership and project management responsibilities identifiable where they apply?
• Are decision rights, authority limits, governance forums and escalation routes clear enough for the project's scale?
• Are relevant finance, commercial, risk, technology, privacy, security, change or assurance contributors identified?
• Does each material approval condition have an owner and closure path?

Funding, timing and resources

• Can the reviewer distinguish the current funding or resource envelope from an estimate or future request?
• Are the immediate planning horizon and key decision milestones visible?
• Are important resource assumptions and constraints stated?
• Is the proposed next step within the authority and funding requested or approved?

Stakeholders and mobilisation

• Have affected and influential stakeholder groups been identified at a useful early level?
• Is there an owner for immediate engagement and communication?
• Are kick-off participants, objectives, decisions and first actions clear?
• Is the team avoiding commitments or communications that exceed the current approval?

Uncertainty and connected evidence

• Are material assumptions, dependencies, initial risks and known issues visible?
• Is each significant gap linked to an action, decision or accepted condition?
• Are the business case, mandate, stakeholder information and kick-off inputs consistent?
• Can a reviewer identify the current versions and decision record?

Illustrative readiness review

This fictional example shows how to record representative findings. It is not customer evidence, a benchmark or a complete checklist for every project.

Scenario: An internal project is seeking authority to plan an improved expenditure-approval process before purchase commitments are made.

Row statuses are inputs to the overall decision. They are not counted or averaged. The authorised reviewer determines the overall result from each gap's materiality and decision impact.

This example does not add the ready items to produce a score. A missing operational owner might be accepted as a time-bound condition in one context, while the same gap may prevent approval in another.

How to handle initiation gaps

1. Test materiality. Give immediate attention to gaps affecting authority, safety, legality, funding, ownership or the ability to make the next decision. Seek specialist advice rather than using this checklist to interpret an obligation.
2. Name the owner and decision. Record who must provide evidence, decide or act, with an appropriate due date. Naming an owner does not make a decision-blocking gap suitable for conditional acceptance.
3. Record conditions and limits. If the authorised decision-maker accepts conditional readiness, state what is authorised, what remains prohibited and how the condition will close.
4. Escalate through the correct route. A project manager or checklist facilitator should not waive a requirement outside their authority.
5. Carry valid open work forward. Link unresolved items to the relevant plan, register or action log. Retain their connection to the initiation review.

5. How PMOEasy helps

You can run this review using your organisation's existing evidence. If you need editable starting points, the PMOEasy Project Starter Bundle combines four initiation artefacts. They can help teams prepare and organise evidence for the investment decision, project mandate, stakeholder setup and kick-off.

The included artefacts have distinct roles:

• the Business Case template supports the investment or option recommendation
• the Project Charter template supports the high-level mandate, boundaries and authority
• the Stakeholder Register supports structured stakeholder analysis and engagement inputs
• the Kick-off Meeting Agenda and Minutes supports a controlled meeting and record of early actions

These editable documents do not form a complete initiation system. Adapt them to your project's context and use them within your organisation's governance and specialist requirements.

6. Explore the Project Starter Bundle

Prepare the connected initiation evidence using a coordinated set of editable starting points.

Explore the Project Starter Bundle.

Is the main gap a clear mandate, scope boundary or authority record? Explore the Project Charter template.

The templates do not guarantee approval, compliance, completeness or project outcomes.