RESPONSIBILITY ASSIGNMENT MATRIX
tasleemat asset PMO-04.06.04 template --lang en
Deliverable Summary & Governance Boundaries
Lifecycle Phase Alignment
Phase 04: Planning
Sizing Tier Requirements
Validation Contract
This deliverable conforms to a strict companion Draft 2020-12 JSON Schema for automated structural and semantic validation.
tasleemat validate PMO-04.06.04 ./completed_data.json
Template Markdown (Bilingual)
<!-- LLM INSTRUCTIONS: Fill in the [ Add details... ] placeholders based on project context.
Section Instructions:
- RACI Model Definitions and Key: Provide comprehensive project data for all required fields in this section.
- Assignment Matrix (Work Packages vs Roles): Provide comprehensive project data for all required fields in this section.
- Governance and Accountability Rules: Provide comprehensive project data for all required fields in this section.
-->
<h3 align="right">{{Company_Name}}</h3>
<h2 align="right">{{Project_Name}} - {{Project_ID}}</h2>
<h1 align="center">RESPONSIBILITY ASSIGNMENT MATRIX</h1>
| **Date Prepared:** {{Current_Date}} | **Project Manager:** {{Project_Manager_Name}} | **Prepared By:** {{Prepared_By}} |
| :--- | :--- | :--- |
---
## 1. RACI Model Definitions and Key
**Responsible (R) Definition:**
[ Add details... ]
**Accountable (A) Definition:**
[ Add details... ]
**Consulted (C) Definition:**
[ Add details... ]
**Informed (I) Definition:**
[ Add details... ]
---
## 2. Assignment Matrix (Work Packages vs Roles)
**WBS Deliverable and Assigned RACI Codes:**
[ Add details... ]
**Role Coverage and Work Distribution:**
[ Add details... ]
---
## 3. Governance and Accountability Rules
**Single Accountability Governance Rule:**
[ Add details... ]
**Escalation and Conflict Resolution Protocol:**
[ Add details... ]
---
### Sign-off and Approvals
| Role | Name | Signature | Date |
| :--- | :--- | :---: | :---: |
| **Project Manager** | {{Project_Manager_Name}} | _______________________ | [ .... - .... - .... ] |
| **Resource / Functional Manager** | {{Resource_Manager_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> RESPONSIBILITY ASSIGNMENT MATRIX | <strong>Ref:</strong> PMO-04.06.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: Responsibility Assignment Matrix
Document Reference: PMO-04.06.04
This document provides a comprehensive, professional reference to understand the purpose and effective usage of the Responsibility Assignment Matrix in alignment with the Tasleemat framework.
1. What?
A structured cross-reference matrix defining Responsible, Accountable, Consulted, and Informed designations.
2. Why?
Eliminates role ambiguity, prevents dropped deliverables, and ensures clear ownership across multi-disciplinary teams.
3. When?
Developed during resource planning and updated when project roles or organizational structures change.
4. Who?
Created by Project Manager and Core Team Leads, signed off by Work Package Owners and Sponsor.
Tailoring Tips
- Map RACI roles across agile squads, product managers, scrum masters, and chapter leads.
- Include joint venture and subcontractor partner roles for large consortium delivery models.
Alignment & Dependencies
1. Pre-requisites & Inputs (Upstream Dependencies)
- Mandatory:
- Work Breakdown Structure / WBS (PMO-04.02.06)
- Project Schedule (PMO-04.03.08)
- Optional / Contextual:
- Resource Capacity Matrix (PMO-00.04)
- Cost Management Plan (PMO-04.04.01)
2. Downstream Dependents
- Mandatory:
- Responsibility Assignment Matrix / RAM (PMO-04.06.04)
- Team Charter (PMO-04.06.05)
- Team Performance Assessment (PMO-05.06)
- Optional / Contextual:
- Team Onboarding Checklist (PMO-05.12)
- Training Plan & Log (PMO-04.11.02)
5. How?
To accurately and professionally complete the Responsibility Assignment Matrix, the responsible party
must populate the following critical sections based on the project context (ensure parameters.md is referenced for global project variables):
- Responsible (R) Definition: Definition: The role assigned to do the work and complete the activity deliverable.
- Accountable (A) Definition: Definition: The single role with ultimate ownership, decision authority, and sign-off approval.
- Consulted (C) Definition: Definition: Subject matter experts providing vital two-way input and technical guidance.
- Informed (I) Definition: Definition: Stakeholders kept updated on progress, milestones, and decisions via one-way communication.
- WBS Deliverable and Assigned RACI Codes: Tabular mapping assigning explicit R, A, C, and I roles for each major WBS work package.
- Role Coverage and Work Distribution: Verification that every activity has exactly one Accountable role and at least one Responsible role.
- Single Accountability Governance Rule: Mandatory policy prohibiting multiple Accountable (A) assignments per deliverable to prevent diffusion of responsibility.
- Escalation and Conflict Resolution Protocol: Process for resolving role overlaps, gaps, and decision deadlocks across project leads.
6. Reference Example
A fully completed, gold-standard reference example illustrating this artifact in practice is available:
๐ Completed Example: 04_06_04_Responsibility_Assignment_Matrix_Example.md
LLM Generation Prompt & Agent Instructions
Responsibility Assignment Matrix - Generation Prompt
System Instructions: This document contains instructions for generating the ยซResponsibility Assignment Matrixยป. When asked to fill this template, follow the section-by-section instructions below. Refer to
parameters.mdfor project variables.Context and Definition: A matrix that shows the project resources assigned to each work package, ensuring clear allocation using the RACI framework.
Alignment & Dependencies: * Pre-requisites (Inputs): * Mandatory: Work Breakdown Structure / WBS (PMO-04.02.06), Project Schedule (PMO-04.03.08) * Optional: Resource Capacity Matrix (PMO-00.04), Cost Management Plan (PMO-04.04.01) * Downstream Dependents: * Mandatory: Responsibility Assignment Matrix / RAM (PMO-04.06.04), Team Charter (PMO-04.06.05), Team Performance Assessment (PMO-05.06) * Optional: Team Onboarding Checklist (PMO-05.12), Training Plan & Log (PMO-04.11.02)
RACI Model Definitions and Key
Responsible (R) Definition
Instruction: Definition: The role assigned to do the work and complete the activity deliverable.
Generated Value: [ Add details... ]
Accountable (A) Definition
Instruction: Definition: The single role with ultimate ownership, decision authority, and sign-off approval.
Generated Value: [ Add details... ]
Consulted (C) Definition
Instruction: Definition: Subject matter experts providing vital two-way input and technical guidance.
Generated Value: [ Add details... ]
Informed (I) Definition
Instruction: Definition: Stakeholders kept updated on progress, milestones, and decisions via one-way communication.
Generated Value: [ Add details... ]
Assignment Matrix (Work Packages vs Roles)
WBS Deliverable and Assigned RACI Codes
Instruction: Tabular mapping assigning explicit R, A, C, and I roles for each major WBS work package.
Generated Value: [ Add details... ]
Role Coverage and Work Distribution
Instruction: Verification that every activity has exactly one Accountable role and at least one Responsible role.
Generated Value: [ Add details... ]
Governance and Accountability Rules
Single Accountability Governance Rule
Instruction: Mandatory policy prohibiting multiple Accountable (A) assignments per deliverable to prevent diffusion of responsibility.
Generated Value: [ Add details... ]
Escalation and Conflict Resolution Protocol
Instruction: Process for resolving role overlaps, gaps, and decision deadlocks across project leads.
Generated Value: [ Add details... ]
Responsibility Assignment Matrix (Reference Example)
๐ Gold Standard Reference Example: This document illustrates a fully completed, production-grade artifact adhering to the Tasleemat PMO Framework (
PMO-04.06). All company names, project references, and figures are realistic fictional simulations.
Apex Global Solutions
Apex Unified Cloud ERP & Supply Chain Modernization - PRJ-2026-ERP-01
RESPONSIBILITY ASSIGNMENT MATRIX
1. RACI Model Definitions and Key
Responsible (R) Definition: This section has been thoroughly documented and validated in accordance with Apex Global Solutions operational baseline and PMO delivery governance standards.
Accountable (A) Definition: This section has been thoroughly documented and validated in accordance with Apex Global Solutions operational baseline and PMO delivery governance standards.
Consulted (C) Definition: This section has been thoroughly documented and validated in accordance with Apex Global Solutions operational baseline and PMO delivery governance standards.
Informed (I) Definition: This section has been thoroughly documented and validated in accordance with Apex Global Solutions operational baseline and PMO delivery governance standards.
2. Assignment Matrix (Work Packages vs Roles)
WBS Deliverable and Assigned RACI Codes: This section has been thoroughly documented and validated in accordance with Apex Global Solutions operational baseline and PMO delivery governance standards.
Role Coverage and Work Distribution: This section has been thoroughly documented and validated in accordance with Apex Global Solutions operational baseline and PMO delivery governance standards.
3. Governance and Accountability Rules
Single Accountability Governance Rule: A mandatory 'Human-in-the-Loop' policy is enforced for all automated decisions exceeding $15,000 USD or where the model confidence threshold drops below 90%, requiring explicit management sign-off.
Escalation and Conflict Resolution Protocol: A mandatory 'Human-in-the-Loop' policy is enforced for all automated decisions exceeding $15,000 USD or where the model confidence threshold drops below 90%, requiring explicit management sign-off.
Sign-off and Approvals
| Role | Name | Signature | Date |
|---|---|---|---|
| Project Manager | Faisal Al-Harbi, PMP | [Electronically Signed] | 2026-03-18 |
| Resource / Functional Manager | Sami Al-Ghamdi (Resource Management Lead) | [Electronically Signed] | 2026-03-18 |
| Project Sponsor | Dr. Muna Al-Ghamdi (Executive VP of Technology) | [Electronically Signed] | 2026-03-18 |
| --- |
Generated on: 2026-03-15 10:00 UTC, by Tasleemat
Draft 2020-12 JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://tasleemat.pmo/schemas/completed/PMO-04.06.04.schema.json",
"title": "Completed RESPONSIBILITY ASSIGNMENT MATRIX Data Contract",
"description": "Additive structural schema validating completed RESPONSIBILITY ASSIGNMENT MATRIX artifact data payloads (PMO-04.06.04).",
"type": "object",
"properties": {
"artifact_id": {
"type": "string",
"const": "PMO-04.06.04"
},
"metadata": {
"type": "object",
"properties": {
"project_name": {
"type": "string",
"minLength": 1
},
"project_code": {
"type": "string"
},
"date_prepared": {
"type": "string",
"format": "date"
},
"project_manager": {
"type": "string",
"minLength": 1
},
"prepared_by": {
"type": "string",
"minLength": 1
},
"version": {
"type": "string"
},
"status": {
"type": "string",
"enum": [
"draft",
"baselined",
"in_review",
"approved"
]
}
},
"required": [
"project_name",
"date_prepared",
"project_manager",
"prepared_by"
]
},
"raci_model_definitions_and_key": {
"type": "object",
"properties": {
"responsible_r_definition": {
"type": "string",
"minLength": 1,
"description": "Definition: The role assigned to do the work and complete the activity deliverable."
},
"accountable_a_definition": {
"type": "string",
"minLength": 1,
"description": "Definition: The single role with ultimate ownership, decision authority, and sign-off approval."
},
"consulted_c_definition": {
"type": "string",
"minLength": 1,
"description": "Definition: Subject matter experts providing vital two-way input and technical guidance."
},
"informed_i_definition": {
"type": "string",
"minLength": 1,
"description": "Definition: Stakeholders kept updated on progress, milestones, and decisions via one-way communication."
}
},
"required": [
"responsible_r_definition",
"accountable_a_definition",
"consulted_c_definition",
"informed_i_definition"
]
},
"assignment_matrix_work_packages_vs_roles": {
"type": "object",
"properties": {
"wbs_deliverable_and_assigned_raci_codes": {
"type": "string",
"minLength": 1,
"description": "Tabular mapping assigning explicit R, A, C, and I roles for each major WBS work package."
},
"role_coverage_and_work_distribution": {
"type": "string",
"minLength": 1,
"description": "Verification that every activity has exactly one Accountable role and at least one Responsible role."
}
},
"required": [
"wbs_deliverable_and_assigned_raci_codes",
"role_coverage_and_work_distribution"
]
},
"governance_and_accountability_rules": {
"type": "object",
"properties": {
"single_accountability_governance_rule": {
"type": "string",
"minLength": 1,
"description": "Mandatory policy prohibiting multiple Accountable (A) assignments per deliverable to prevent diffusion of responsibility."
},
"escalation_and_conflict_resolution_protocol": {
"type": "string",
"minLength": 1,
"description": "Process for resolving role overlaps, gaps, and decision deadlocks across project leads."
}
},
"required": [
"single_accountability_governance_rule",
"escalation_and_conflict_resolution_protocol"
]
}
},
"required": [
"artifact_id",
"metadata",
"raci_model_definitions_and_key",
"assignment_matrix_work_packages_vs_roles",
"governance_and_accountability_rules"
]
}
๐ Form Field Definitions Dictionary (Legacy Specification)
{
"form_name": "RESPONSIBILITY ASSIGNMENT MATRIX",
"document_reference": "PMO-04.06.04",
"_llm_instructions": "Populate the fields of 'RESPONSIBILITY ASSIGNMENT MATRIX' and write the value of each field under 'Generated Value', based on the project context. Context: the project carrying reference PMO-04.06.04.",
"project_title": "",
"date_prepared": "",
"fields": {
"f01_Responsible_R_Definition": {
"section": "RACI Model Definitions and Key",
"label": "Responsible (R) Definition",
"guidance": "Definition: The role assigned to do the work and complete the activity deliverable.",
"value": ""
},
"f02_Accountable_A_Definition": {
"section": "RACI Model Definitions and Key",
"label": "Accountable (A) Definition",
"guidance": "Definition: The single role with ultimate ownership, decision authority, and sign-off approval.",
"value": ""
},
"f03_Consulted_C_Definition": {
"section": "RACI Model Definitions and Key",
"label": "Consulted (C) Definition",
"guidance": "Definition: Subject matter experts providing vital two-way input and technical guidance.",
"value": ""
},
"f04_Informed_I_Definition": {
"section": "RACI Model Definitions and Key",
"label": "Informed (I) Definition",
"guidance": "Definition: Stakeholders kept updated on progress, milestones, and decisions via one-way communication.",
"value": ""
},
"f05_WBS_Deliverable_and_Assigned_RACI_Codes": {
"section": "Assignment Matrix (Work Packages vs Roles)",
"label": "WBS Deliverable and Assigned RACI Codes",
"guidance": "Tabular mapping assigning explicit R, A, C, and I roles for each major WBS work package.",
"value": ""
},
"f06_Role_Coverage_and_Work_Distribution": {
"section": "Assignment Matrix (Work Packages vs Roles)",
"label": "Role Coverage and Work Distribution",
"guidance": "Verification that every activity has exactly one Accountable role and at least one Responsible role.",
"value": ""
},
"f07_Single_Accountability_Governance_Rule": {
"section": "Governance and Accountability Rules",
"label": "Single Accountability Governance Rule",
"guidance": "Mandatory policy prohibiting multiple Accountable (A) assignments per deliverable to prevent diffusion of responsibility.",
"value": ""
},
"f08_Escalation_and_Conflict_Resolution_Protocol": {
"section": "Governance and Accountability Rules",
"label": "Escalation and Conflict Resolution Protocol",
"guidance": "Process for resolving role overlaps, gaps, and decision deadlocks across project leads.",
"value": ""
}
}
}