# Stakeholder Communications Guide

**Purpose**: Templates and procedures for keeping stakeholders informed
**Audience**: Project managers, communications leads, team leads
**Status**: Ready-to-use communication templates

---

## Communication Strategy

### Audience Levels

**Level 1: Executive Stakeholders** (CEO, CFO, sponsors)
- Frequency: Daily or milestone-based
- Detail level: High-level only
- Focus: Schedule, cost, risks

**Level 2: Department Heads** (Manager, team lead)
- Frequency: Every 2-4 hours during execution
- Detail level: Moderate
- Focus: Progress, blockers, resource needs

**Level 3: Technical Team** (Developers, QA)
- Frequency: Every 30 minutes
- Detail level: Technical details
- Focus: Status, next steps, issues

---

## Daily Status Report Template

**Subject**: WDMaker Project Status - [Date]

**Body**:
```
PROJECT STATUS: [ON TRACK / AT RISK / DELAYED]

Current Phase: [Design / Implementation / Finalization / Batch 010]
Progress: [X / 517] sites at required status (XX%)
Time Elapsed: [X hours]
Time Remaining: [Estimated X hours]

Key Metrics:
- Throughput: [X sites/minute]
- System Health: [Healthy / Degraded / Critical]
- No blockers: [Yes / No]

Highlights:
- [Achievement 1]
- [Achievement 2]
- [Achievement 3]

Issues (if any):
- [Issue]: [Status] [Resolution]
- [Issue]: [Status] [Resolution]

Next 24 Hours:
- [Action 1]
- [Action 2]
- [Action 3]

Contact: [Your name] for questions
```

**Example**:
```
PROJECT STATUS: ON TRACK

Current Phase: Implementation (Waves 4-9)
Progress: 350 / 517 sites at I status (67.7%)
Time Elapsed: 4 hours
Time Remaining: Estimated 3-4 hours

Key Metrics:
- Throughput: 1.5 sites/minute
- System Health: Healthy
- No blockers: Yes

Highlights:
- Wave 6 completed successfully (25 sites)
- System running stably
- Excellent team coordination

Issues: None

Next 24 Hours:
- Complete implementation (target: 22:00 UTC)
- Execute finalization (< 1 minute)
- Process batch 010 (30-60 min)
- Project completion (estimated 23:30 UTC)

Contact: John Doe for questions
```

---

## Milestone Announcement Template

**Subject**: WDMaker - MILESTONE: [Milestone Name] Completed

**Body**:
```
🎉 MAJOR MILESTONE COMPLETED 🎉

Milestone: [Name]
Completed: [Date/Time]
Impact: [What this enables]

Stats:
- Sites affected: [Number]
- Quality: [Percentage or assessment]
- Time to milestone: [Duration]

What's Next:
[Next phase description]

Questions? Contact [name]
```

**Example**:
```
🎉 MAJOR MILESTONE COMPLETED 🎉

Milestone: Batch 001 Implementation Complete
Completed: 2026-03-24 22:00 UTC
Impact: Ready for finalization - official project completion within reach

Stats:
- Sites implemented: 517
- Quality: 100% design compliance verified
- Time to milestone: 8 hours

What's Next:
- Finalization execution (< 1 min to transition I → Q)
- Batch 010 processing (30-60 min)
- Project verification (10 min)
- Official completion (estimated 23:30 UTC)

Questions? Contact John Doe
```

---

## Risk Alert Template

**Subject**: ⚠️ WDMaker - Risk Alert: [Risk Name]

**Body**:
```
RISK ALERT: [Risk Name]
Severity: [Low / Medium / High / Critical]
Status: [Identified / Mitigating / Resolved]

What Happened:
[Description of issue]

Impact:
[What could happen if not addressed]

Action Being Taken:
[Resolution steps]

Timeline:
[When resolution complete]

Escalation:
[Who to contact if needed]
```

**Example**:
```
RISK ALERT: Progress Slower Than Expected
Severity: Low
Status: Identified and Monitoring

What Happened:
Throughput dropped from 2 sites/min to 1 site/min in last 2 hours

Impact:
May delay project completion by 1-2 hours

Action Being Taken:
1. Monitoring system resources
2. Investigating agent performance
3. Ready to redeploy additional wave if needed

Timeline:
Next assessment in 30 minutes

Escalation:
Contact John Doe if continues 45+ minutes
```

---

## Success Announcement Template

**Subject**: 🎊 WDMaker Project SUCCESS! 🎊

**Body**:
```
PROJECT COMPLETE

Completion Date: [Date/Time]
Final Status: SUCCESS
Sites Finalized: [Number] / 568 (XX%)

Project Metrics:
- Design phase: [X hours]
- Implementation phase: [X hours]
- Total execution: [X hours]
- Quality: [X% compliance]

Team Achievement:
[Highlight team performance]

What Was Generated:
- [X] HTML5 websites
- [X] CSS stylesheets
- [X] JavaScript files
- Design compliance: 100%

Key Statistics:
- Throughput: [X sites/minute average]
- Completion rate: [X%]
- Zero critical issues

What Happens Next:
1. Documentation archival
2. Lessons learned session
3. Team celebration and recognition
4. Planning for similar projects

Thank you to the team for excellent execution!

[Signed]
[Your name]
```

---

## Escalation Alert Template

**Subject**: 🚨 WDMaker - ESCALATION REQUIRED: [Issue Name]

**Body**:
```
ESCALATION ALERT - ACTION REQUIRED

Issue: [Name]
Severity: CRITICAL / HIGH
Status: [Status]
Time Since Start: [Duration]

What Happened:
[Clear description]

Why It's Critical:
[Impact on project]

Recommendation:
[What should be done]

Your Approval Needed For:
[Specific decision or action]

Context:
- [Key fact 1]
- [Key fact 2]
- [Key fact 3]

Contact: [Name] immediately for decision

```

**Example**:
```
ESCALATION ALERT - ACTION REQUIRED

Issue: Progress Completely Stalled - No Movement 1 Hour
Severity: CRITICAL
Status: Ongoing

What Happened:
I-status count stopped increasing at 450/517 for over 1 hour. All agents appear inactive.

Why It's Critical:
- Unable to progress toward finalization
- May miss project deadline (22:00 UTC target)
- System appears to have crashed or hit major issue

Recommendation:
Either: A) Redeploy remaining agents for final 67 sites
Or: B) Accept current progress (88% completion) and finalize early

Your Approval Needed For:
Which option: Full completion attempt (A) or early completion (B)?

Context:
- System resources appear adequate
- No obvious errors in logs
- Last progress was 1 hour ago

Contact: John Doe immediately for decision
```

---

## Weekly Report Template

**Subject**: WDMaker Project Weekly Report - Week of [Date]

**Body**:
```
WEEKLY PROJECT REPORT
Week of [Date]

EXECUTIVE SUMMARY
Status: [Green / Yellow / Red]
Progress: [X% complete]
Schedule: [On Track / At Risk / Behind]

Key Achievements This Week:
- [Achievement 1]
- [Achievement 2]
- [Achievement 3]

Metrics:
- Sites processed: [X]
- Average throughput: [X sites/min]
- Success rate: [X%]
- System uptime: [X%]

Risks & Issues:
- [Issue 1]: [Status] [Action]
- [Issue 2]: [Status] [Action]
- [Issue 3]: [Status] [Action]

Next Week Priorities:
1. [Priority 1]
2. [Priority 2]
3. [Priority 3]

Budget Status: [On budget / Over budget / Savings]

Questions? Contact [name]
```

---

## Shift Handoff Template

**Subject**: WDMaker Shift Handoff - [Time] to [Time]

**Body**:
```
SHIFT HANDOFF REPORT

Previous Shift:
- Start: [Time] - End: [Time]
- Operator: [Name]

Status When Handoff:
- I-status count: [X] / 517
- System health: [Healthy / Degraded]
- Current phase: [Design / Implementation / Finalization]

What Happened:
- [Summary of progress]
- [Issues encountered and resolved]
- [Any pending issues]

Current State:
- System running normally / has issue
- No blockers / has blocker [describe]
- Monitoring: active / needs attention

Handoff To:
- Operator: [Next person]
- Monitoring every 30 minutes
- Escalation contact: [Name] if needed

Special Notes:
- [Anything important to know]
- [Things to watch for]
- [Commands to run if issue]

Previous shift operator available for questions until [time]
```

---

## Issue Resolution Report Template

**Subject**: WDMaker - Issue Resolved: [Issue Name]

**Body**:
```
ISSUE RESOLVED

Issue: [Name]
Severity: [Was High / Medium / Low]
Reported: [When]
Resolved: [When]
Duration: [How long]

Root Cause:
[What caused it]

Resolution:
[How it was fixed]

Impact:
[Whether it affected progress]

Prevention:
[What we'll do to prevent recurrence]

Lessons Learned:
[What we learned]

Time Cost:
[How much time it took to resolve]
```

**Example**:
```
ISSUE RESOLVED

Issue: Registry Corruption (Duplicate Entries)
Severity: Was High
Reported: 2026-03-24 15:30 UTC
Resolved: 2026-03-24 15:50 UTC
Duration: 20 minutes

Root Cause:
Concurrent write conflict when two agents updated registry simultaneously

Resolution:
- Restored clean registry from git
- Identified 3 duplicate entries
- Cleaned up duplicates
- Verified integrity
- Restarted affected agents

Impact:
Minor - affected only 2 sites, quick recovery

Prevention:
- Increased atomic write robustness
- Added duplicate detection to validation script
- Will monitor more carefully next project

Lessons Learned:
- Atomic operations are critical at scale
- Need pre-project validation
- Git history useful for recovery

Time Cost:
20 minutes to identify and fix (negligible impact on schedule)
```

---

## Communication Frequency Guide

| Event | Frequency | Audience | Template |
|-------|-----------|----------|----------|
| Normal execution | Every 2 hours | Level 2 | Daily Status |
| Milestone reached | Immediately | All levels | Milestone Announcement |
| Issue detected | Immediately | Level 2-3 | Risk Alert |
| Critical issue | Within 5 min | All levels | Escalation Alert |
| Issue resolved | Within 30 min | All levels | Issue Resolution |
| Shift change | Every 8 hours | Level 2-3 | Shift Handoff |
| Weekly recap | Once weekly | All levels | Weekly Report |
| Project complete | Immediately | All levels | Success Announcement |

---

## Key Messages for Each Audience

### For Executives
- ✅ Focus: Schedule, cost, risk
- ✅ Tone: Professional, concise
- ✅ Detail: High-level only
- ✅ Frequency: Daily
- ❌ Don't: Technical jargon, excessive detail

### For Managers
- ✅ Focus: Progress, blockers, team needs
- ✅ Tone: Collaborative, direct
- ✅ Detail: Moderate technical detail
- ✅ Frequency: Every 2-4 hours
- ❌ Don't: Over-promise, minimize risks

### For Technical Team
- ✅ Focus: Status, next steps, technical details
- ✅ Tone: Collaborative, action-oriented
- ✅ Detail: Full technical depth
- ✅ Frequency: Every 30 minutes
- ❌ Don't: Assume high-level understanding

---

## Crisis Communication

If serious issue or failure occurs:

1. **Immediate** (within 5 min): Alert all stakeholders
   - Use: Escalation Alert template
   - Include: What happened, current impact

2. **Status updates** (every 15 min): Brief on recovery efforts
   - Use: Status template modified for crisis
   - Focus: What we're doing, timeline for resolution

3. **Resolution** (when fixed): Full incident report
   - Use: Issue Resolution template
   - Include: Root cause, prevention measures

---

## Tone & Language Guide

**✅ Use**:
- Clear, simple language
- Active voice
- Specific numbers
- Action-oriented

**❌ Avoid**:
- Jargon
- Vague promises
- Passive voice
- Technical minutiae

**Example good**:
"We completed 350 of 517 sites (67.7%). Current pace: 1.5 sites/minute. On track for 22:00 UTC finalization."

**Example bad**:
"We've made significant progress. The system is running well. We should finish soon, probably around 10 PM or so."

---

## Conclusion

**Effective communication**:
- ✅ Keeps stakeholders informed
- ✅ Enables confident decisions
- ✅ Manages expectations
- ✅ Builds trust
- ✅ Prevents surprises

**Use these templates consistently** throughout project execution.

---

*Stakeholder Communications Guide: 2026-03-24*
*Purpose: Professional communication with all audiences*
*Status: Ready for immediate use*