Navigation Section
Communications Management
β Document Index
Why This Folder Exists
This folder governs how communication happens across the project β not just tools, but purpose, timing, ownership, and backup plans. If youβre looking for answers like:
- What should I send, and to whom?
- What platform do we use for X?
- Who owns communication with the sponsor?
- How do we handle breakdowns or blackouts?
Youβll find them all here.
This is the operational and strategic communications system for Project PASS PMP.
What Youβll Find Here
π Communications Management Plan
Defines what gets communicated, when, by whom, and how often. Covers stakeholder needs, frequency, delivery channels, and responsibilities. This is the central plan that ties everything else together.
π PACE Communications Policy
Outlines our PACE structure β Primary, Alternate, Contingency, and Emergency communication channels. Establishes tool hierarchy, escalation protocols, and what happens when normal channels fail.
π Collaboration Platform Procedure
A practical walkthrough of which tools we use and how they work together. Covers GitHub, Pumble, Jitsi, Trello, and fallback workflows. If youβre looking for βwhat to clickβ and βwhen to reply,β start here.
π Communications Log
A chronological record of significant communication events, decisions, requests, blockers, and escalations. Supports transparency, traceability, and stakeholder reporting.
Suggested Reading Order
Start with the Communications Plan
β Read the PACE Policy to understand escalation
β Use the Platform Procedure to see what tools to use
β Review the Log to see whatβs already been communicated