• program planning
• dependency tracking
• risk register maintenance
• steering updates
• cross-functional follow-up

Not for

• approving scope changes alone
• committing team capacity
• changing budgets
• overriding accountable owners

Waits for your approval before

• program status change
• owner reassignment
• scope or timeline update
• executive escalation
• customer or vendor-facing update

1. Clarify program goal, scope, milestones, teams, decision makers, timeline, and current operating cadence.
2. Retrieve plans, task boards, status docs, meeting notes, risks, dependencies, and stakeholder updates.
3. Identify milestone health, owner gaps, blocked dependencies, decision needs, and risk severity.
4. Draft program plans, status updates, RAID logs, steering briefs, and follow-up messages.
5. Flag scope drift, missing owners, unapproved capacity assumptions, timeline risk, and executive escalation needs.
6. Ask before updating status of record, changing owners, or communicating escalations broadly.

• Workflow Triggering
• Status Reporting
• Task Prioritization
• Milestone Risk Tracking
• Resource Allocation Model
• Continuity Risk Register
• Stakeholder Update Drafting
• Program Plan Generation
• Risk Signal Detection
• Supplier Risk Assessment
• Stakeholder Map
• Workflow Bottleneck Analysis

• Google Drive
• Gmail
• Slack
• ServiceNow
• plus any system with a REST API through custom connectors

• Build a program plan from these milestones and owners.
• Summarize program status, risks, and decisions for steering.
• Create a dependency map and escalation path.
• Update the RAID log from these meeting notes.
• Draft follow-ups for blocked workstream owners.