Stakeholder Register

سجل المعنيين

tasleemat asset PMO-03.04 template --lang en

Deliverable Summary & Governance Boundaries

Lifecycle Phase Alignment

Phase 03: Initiating

Sizing Tier Requirements

Tier 1 Tier 2

Validation Contract

This deliverable conforms to a strict companion Draft 2020-12 JSON Schema for automated structural and semantic validation.

tasleemat validate PMO-03.04 ./completed_data.json

Template Markdown (Bilingual)

<!--  LLM INSTRUCTIONS: Fill in the [ Add details... ] placeholders based on project context.

Section Instructions:
*   **ID:** Unique identifier for the stakeholder (e.g., SH-01).
*   **Name:** Stakeholder’s name. If you don’t have a name you can substitute a position or organization until you have more information.
*   **Position/Role:** The position and/or role the stakeholder holds in the organization. Examples of positions include programmer, human resources analyst, or quality assurance specialist. Roles indicate the function the stakeholder performs on the project team.
*   **Contact information:** How to communicate with the stakeholder, such as their phone number, email address, or physical address.
*   **Requirements:** High-level needs for the project and/or product.
*   **Expectations:** Main expectations of the project and/or product.
*   **Classification:** Some projects may categorize stakeholders as friend, foe, or neutral; others may classify them as high, medium, or low impact.
-->

<h3 align="right">{{Company_Name}}</h3>
<h2 align="right">{{Project_Name}} - {{Project_ID}}</h2>
<h1 align="center">STAKEHOLDER REGISTER</h1>

| **Date Prepared:** {{Current_Date}} | **Project Manager:** {{Project_Manager_Name}} | **Prepared By:** {{Prepared_By}} |
| :--- | :--- | :--- |  

---

## Stakeholder Register Entries
<!-- 
Please populate the table below with the following details:
- **ID:** Unique identifier for the stakeholder (e.g., SH-01).
- **Name:** Stakeholder’s name. If you don’t have a name you can substitute a position or organization until you have more information.
- **Position/Role:** The position and/or role the stakeholder holds in the organization. Examples of positions include programmer, human resources analyst, or quality assurance specialist. Roles indicate the function the stakeholder performs on the project team.
- **Contact information:** How to communicate with the stakeholder, such as their phone number, email address, or physical address.
- **Requirements:** High-level needs for the project and/or product.
- **Expectations:** Main expectations of the project and/or product.
- **Classification:** Some projects may categorize stakeholders as friend, foe, or neutral; others may classify them as high, medium, or low impact.
-->
| ID | Name | Position/Role | Contact information | Requirements | Expectations | Classification |
| :---: | :--- | :--- | :--- | :--- | :--- | :--- |
| [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] |
| [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] |
| [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] |


---

### Sign-off and Approvals

| Role | Name | Signature | Date |
| :--- | :--- | :---: | :---: |
| **Project Manager** | {{Project_Manager_Name}} | _______________________ | [ .... - .... - .... ] |
| **Stakeholder Relations Lead** | {{Stakeholder_Lead_Name}} | _______________________ | [ .... - .... - .... ] |
| **Project Sponsor** | {{Project_Sponsor_Name}} | _______________________ | [ .... - .... - .... ] |
---

<div align="right" style="margin-top: 20px; font-size: 12px; color: #7f8c8d;">
  <span>Electronic Audit Trail: Hash SHA256: {{Audit_Trail_SHA256_Hash}}</span> <br>
  <strong>Template:</strong> Stakeholder Register | <strong>Ref:</strong> PMO-03.04 <br>
  <i>Generated on: {{Current_Timestamp}}, by <a href="https://github.com/fakhruldeen/Tasleemat/" style="color: #7f8c8d;">Tasleemat</a></i>
</div>

User Guide & Practitioner Instructions

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
Optional / Contextual:
- Program Charter (PMO-00.02)
- Organizational Charts

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:
- Change Management Strategy (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

LLM Generation Prompt & Agent Instructions

Stakeholder Register - Generation Prompt

System Instructions: This document contains instructions for generating the «Stakeholder Register». When asked to fill this template, follow the section-by-section instructions below. Refer to parameters.md for project variables.

Context and Definition: A project document including the identification, assessment, and classification of project stakeholders.

Alignment & Dependencies: * Pre-requisites (Inputs): * Mandatory: Project Charter (PMO-03.01), Procurement Agreements * Optional: Program Charter (PMO-00.02), Organizational Charts * Downstream Dependents: * Mandatory: Stakeholder Analysis (PMO-03.05), Stakeholder Engagement Plan (PMO-04.10.01), Communications Management Plan (PMO-04.07.01) * Optional: Change Management Strategy (PMO-04.11.01), Team Charter (PMO-04.06.05)