---

Tasleemat Forms Guide

Project Artifact: Stakeholder Register

Document Reference: PMO-03.04

This document provides a comprehensive, professional reference to understand the purpose and effective usage of the Stakeholder Register in alignment with the Tasleemat framework.

---

1. What?

A centralized register listing all stakeholders with their contact information, expectations, requirements, and classification.

---

2. Why?

Effective stakeholder engagement is critical to managing expectations, securing alignment, and project success.

---

3. When?

Created during project initiation and maintained continuously throughout the project lifecycle.

---

4. Who?

Created and managed by the Project Manager with input from project sponsors and team members.

---

Tailoring Tips

• Categorize stakeholders by influence and interest to tailor communication strategies.
• Regularly review contact details and role changes during phase transitions.

---

Alignment & Dependencies

1. Pre-requisites & Inputs (Upstream Dependencies)

• Mandatory:
  • Project Charter (PMO-03.01)
  • Procurement Agreements (External)
• Optional / Contextual:
  • Program Charter (PMO-00.02)
  • Organizational Charts (External)

2. Downstream Dependents

• Mandatory:
  • Stakeholder Analysis (PMO-03.05)
  • Stakeholder Engagement Plan (PMO-04.10.01)
  • Communications Management Plan (PMO-04.07.01)
• Optional / Contextual:
  • OCM Strategy and Plan (PMO-04.11.01)
  • Team Charter (PMO-04.06.05)

---

5. How?

To accurately and professionally complete the Stakeholder Register, the responsible party must populate the following critical sections based on the project context (ensure parameters.md is referenced for global project variables):

• ID: Unique identifier for the stakeholder (e.g., SH-01).
• Name: Stakeholder’s name. If unknown, specify the position or organization.
• Position/Role: The position or functional role the stakeholder holds in the organization or project.
• Contact information: Communication channels for the stakeholder such as email address or phone number.
• Requirements: High-level needs and critical requirements for the project and deliverables.
• Expectations: Main expectations regarding project execution, outcomes, and governance.
• Classification: Stakeholder categorization (e.g., internal/external, high/medium/low impact).

---

6. Reference Example

A fully completed, gold-standard reference example illustrating this artifact in practice is available:

📖 Completed Example: 03_04_Stakeholder_Register_Example.md