1. What is the Initiating Process Group?

According to the PMBOK® Guide by the Project Management Institute (PMI), the Initiating Process Group includes the processes performed to:

• Define a new project or a new phase of an existing project;
• Obtain formal authorization to start the project or the phase;
• Lay the foundation for initial objectives, high-level scope, stakeholders and accountability.

Put simply, Initiating answers the question: “Do we really need this project? What problem should it solve, and who will be accountable?”

2. Why is the Initiating stage so important?

Many projects fail not because of technical complexity, but because they start in a fuzzy way: unclear objectives, conflicting expectations and no real owner.

Here are some reasons why the Initiating stage is crucial:

• Clarifies the “Why & What” from day one: Initiating helps sponsors, clients and internal leaders understand why the project is needed and what the initial outcomes should be.
• Reduces conflicts & uncontrolled changes: When goals, high-level scope, constraints and priorities are documented in the Project Charter, later changes can be assessed and controlled professionally.
• Builds a solid foundation for Planning, Executing and Controlling: If the Initiating step is weak, the project plan will be vague, control will be messy and reports will be much less convincing.
• Gives “legitimate power” to the Project Manager: With clear authority stated in the Charter, the Project Manager has a real mandate to work with internal teams, contractors, clients and regulators.

For construction, infrastructure, plant projects, logistics or export – the type of projects that INDUSVINA often gets involved in – strong Initiating helps prevent costly conflicts and saves a lot of “fire-fighting” later on.

3. Two core processes in the Initiating group

In earlier editions of PMBOK®, the Initiating Process Group is mainly built around two core processes:

3.1. Develop Project Charter

The Project Charter is the official “birth certificate” of the project. It typically includes:

• Project objectives (business need, problems to solve, benefits to deliver);
• High-level scope (not detailed yet, but clear enough to guide planning);
• Key constraints: time, budget, legal and technical requirements;
• Major assumptions;
• Sponsor and major stakeholders at a high level;
• Appointment of the Project Manager with initial roles and authority.

Once the Charter is approved and signed, the project has an official management and legal footing inside the organisation.

3.2. Identify Stakeholders

Every project affects different groups of people: investors, clients, contractors, suppliers, local authorities, communities, future operations teams and more.

The Identify Stakeholders process helps you:

• Build a stakeholder register with relevant contact and role information;
• Analyse influence and interest (e.g. high / medium / low power & interest);
• Spot potential “time bombs” – people who could block the project if ignored;
• Prepare for communication and stakeholder management planning later on.

For projects with significant regulatory or community impact (industrial parks, plants, infrastructure), doing Stakeholder Identification properly from the beginning helps you avoid being “stuck” at later gates.

4. Key outputs from the Initiating stage

The Initiating group produces several key outputs that become direct inputs to Planning:

• Project Charter – approved and signed by the sponsor or authorised decision-maker.
• Stakeholder Register – a list of key stakeholders with roles, influence, expectations and preferred communication channels.
• Go / No-Go decision – a formal decision by the organisation to proceed with detailed planning or not.

These documents form a reference frame. When disputes arise about scope, responsibilities or priorities, the team can come back to the original Initiating documents instead of arguing based on personal opinions.

5. Practical tips for INDUSVINA and other businesses

Here are some practical recommendations if you are working in construction, industrial projects, supply chain, export or similar fields:

• Always have at least a Project Brief and a Project Charter: Even for small projects, use a short (1–3 page) initiating document before “jumping into execution”.
• Include legal and standards information early: List relevant laws, regulations and standards (TCVN, QCVN, ISO, ASTM, etc.) right from the Charter.
• Appoint the Project Manager clearly: Avoid situations where “everyone is responsible, so no one is accountable”.
• Create the Stakeholder Register as early as possible: This is especially important when dealing with local communities, authorities and strategic suppliers.
• Define SMART objectives from the start: Make sure goals are measurable, time-bound and aligned with the company strategy.

Once these practices are turned into internal templates at INDUSVINA, new project managers and site engineers will find it much easier to start projects the right way.