---
artifact_id: A28
artifact_name: Communications and Reporting Record
artifact_type: template
version: "1.0.0"
status: Template · Active
parent_definition: artifacts/planning-and-baselines/A28-communications-reporting-record.md
authority: PMBOK8 Guide §2.5.2.3; §2.5.2.5; §2.5.2.7
---

# A28 — Communications and Reporting Record Template

> **Usage:** This is the single communications artifact — plan, delivery log, and monitoring in one record. Complete §1–§2 (Communications Management Plan) during Planning. Maintain §3 (Delivery Log) continuously throughout Executing. Update §4 (Monitoring) at each status cycle. Replace every `[FIELD: ...]` placeholder.

---

## Section 1 — Communications Management Plan

### 1.1 Record Header

| Field | Entry |
|---|---|
| Project or initiative name | [FIELD: Full project name] |
| Project ID | [FIELD: Project identifier] |
| Project manager / communications lead | [FIELD: Name(s) and role(s)] |
| Version | [FIELD: e.g., v1.0] |
| Status | [FIELD: Draft / Approved] |
| Approval date | [FIELD: YYYY-MM-DD] |
| Linked artifacts | A07 · A14 · A15 · A17 · A12 |

### 1.2 Communications Approach

| Field | Entry |
|---|---|
| Communications principles | [FIELD: e.g., single source of truth, no back-channel approvals, confirmed receipt for critical communications] |
| Feedback and escalation mechanism | [FIELD: How stakeholders raise concerns or questions — describe channel and SLA] |
| Communication tools and platforms | [FIELD: List approved tools — e.g., email, Teams, SharePoint, project portal] |
| Language and format standards | [FIELD: Language(s), report format, accessibility requirements] |
| Tailoring note | [FIELD: State if this plan is simplified or enhanced based on A06 governance tier] |

---

## Section 2 — Communication Matrix

> Every key stakeholder in A07 must have at least one communication entry. No stakeholder in A07 without a corresponding communication plan.

| Stakeholder / Group | A07 reference | Information need | Frequency | Format | Channel | Owner | Confirmation required? |
|---|---|---|---|---|---|---|---|
| [FIELD: Name or group] | [FIELD: A07 row ID] | [FIELD: What information does this stakeholder need and why] | [FIELD: Weekly / Bi-weekly / Monthly / Event-driven] | [FIELD: Status report / Dashboard / Email / Meeting / Presentation] | [FIELD: Email / Portal / Teams / In-person] | [FIELD: PM / Communications lead / Role] | [FIELD: Yes — describe confirmation method / No] |

---

## Section 3 — Delivery Log

> Record every communication sent. Maintain continuously throughout Executing and M&C.

| Log ID | Date | Communication type | Recipient / Audience | Channel used | Delivered by | Confirmation received? | Notes |
|---|---|---|---|---|---|---|---|
| COM-001 | [FIELD: YYYY-MM-DD] | [FIELD: Type — e.g., Weekly status report / Escalation notice / Phase gate presentation] | [FIELD: Individual or group name] | [FIELD: Channel used] | [FIELD: Name] | [FIELD: Yes / No / N/A] | [FIELD: Any relevant notes — follow-up needed, delayed, etc.] |

---

## Section 4 — Communications Monitoring

> Review at each status cycle. Update A17 with communications performance summary.

| Review date | Communications sent this period | Gaps identified | Feedback received | Effectiveness assessment | Re-plan decision | Owner |
|---|---|---|---|---|---|---|
| [FIELD: YYYY-MM-DD] | [FIELD: Count and types — reference COM IDs] | [FIELD: Describe any planned communications not delivered or stakeholders not reached] | [FIELD: Summary of stakeholder feedback on communications quality] | [FIELD: 🟢 Effective / 🟡 Partially effective — issues noted / 🔴 Ineffective — re-plan required] | [FIELD: No change / Minor adjustment / Re-plan required — describe action] | [FIELD: PM / Communications lead] |

---

## Section 5 — Plan Version History

| Version | Date | Status | Updated by | Change description |
|---|---|---|---|---|
| v1.0 | [FIELD: YYYY-MM-DD] | Approved | [FIELD: Name] | Initial communications plan approved |

---

*Authority: PMBOK8 Guide §2.5.2.3 Plan Communications; §2.5.2.5 Manage Communications; §2.5.2.7 Monitor Communications*
*Source type: PMI-derived · Version: 1.0.0 · Parent definition: A28-communications-reporting-record.md*
