AI-Powered Status Reporting and Communication

Generate a weekly project status report from these inputs:

PROJECT: AP Automation — Week 4 of 24

THIS WEEK'S UPDATES (raw notes):
- Requirements workshops complete, 31 user stories accepted by product owner
- 3 open questions on approval thresholds still pending CFO answer
  (sent email Monday, no response yet)
- Dev team setup complete, started sprint 1 Monday
- SAP integration scoping call Thursday — IT confirmed 6-week integration
  window needed (we had budgeted 4 weeks — 2-week gap)
- AP team lead raised concern about training timeline — want 3 weeks
  not 2 as planned
- QA team joining next week

AUDIENCE: Executive sponsor (CFO), steering committee

FORMAT:
- Overall status: GREEN/YELLOW/RED with 1-sentence rationale
- Accomplishments this week (bullet points)
- Planned for next week
- Issues and risks (with owner and due date for each)
- Decisions needed (with deadline)
- Budget and schedule summary (I'll fill in actuals)

Tone: concise, factual, no jargon. Flag the SAP timeline issue
prominently — it is a real risk to the delivery date.

I need to escalate a project issue to the CFO (project sponsor).

Issue: The SAP integration scope has expanded beyond original estimate.
IT assessment says 6 weeks of integration work is needed;
we budgeted 4 weeks. This threatens the go-live date by 2 weeks
unless we either compress elsewhere or adjust the timeline.

Options I've analyzed:
A. Extend the go-live date by 2 weeks (from June 30 to July 14)
B. Reduce scope — defer the vendor self-service portal to Phase 2,
   which frees 2 weeks of developer time
C. Add a temporary contractor to support the integration work
   (estimated cost: $18,000)

Draft an escalation email to the CFO that:
1. States the issue clearly without alarming language
2. Quantifies the impact
3. Presents the three options with honest pros/cons
4. Makes a clear recommendation (I'll decide which after reviewing)
5. States what decision is needed and by when
6. Does not make the IT team look bad — this was a discovery, not a failure

Tone: professional, direct, solution-oriented. 300 words maximum.

Draft a weekly team update based on these notes: [paste notes]

Audience: Project team (developers, QA, BA, technical architect)
Format:
- What happened this week
- What everyone is focused on next week
- Where help or coordination is needed
- Any process changes or important reminders
- Wins to celebrate

Tone: direct and operational. Collegial, not formal.
Use team members' first names where relevant.

Convert these meeting notes to structured meeting minutes:
[paste raw notes]

Format:
- Meeting: [name], [date], [attendees]
- Purpose
- Decisions made (numbered, each with decision owner)
- Action items (each with: action, owner, due date)
- Open items / parking lot (topics raised but not resolved)
- Next meeting: [date, agenda items]

Do not editorialize — only include what is in the notes.
Flag any items where the notes are ambiguous about what was decided.

I need to communicate to the steering committee that the
project will miss its deadline by 3 weeks.

Context:
- Original commitment: June 30 go-live
- New realistic date: July 21
- Root cause: SAP integration complexity discovered in testing
  was not visible during planning — this is a genuine discovery,
  not a planning failure
- Team has already found the most efficient path forward

Draft a steering committee presentation (5 slides or equivalent
structured content) that:
1. Opens with a direct statement of the situation
2. Explains the root cause without excuses
3. Shows what the team has already done to minimize the impact
4. Presents the revised plan with the July 21 date
5. Explains what the business impact of the 3-week delay is
   (and isn't — minimize unnecessary alarm)
6. States what the steering committee needs to do or decide

Tone: professional, accountable, solution-focused.
Do not minimize the issue but do not catastrophize it.