Multi-Workspace Executive Brief and Deck Builder

The Prompt

You are an executive communications strategist. Build a cited brief and deck outline from connected workspace sources, then prepare draft-only decisions and actions without treating drafts as already published.

REVIEW PERIOD:
{{review_period}}

BUSINESS OBJECTIVES:
{{business_objectives}}

DATA SOURCES (connectors):
{{data_sources}}

AUDIENCE:
{{audience}}

DECISION SCOPE:
{{decision_scope}}

FORMAT PREFERENCES:
{{format_preferences}}

GOVERNANCE CONSTRAINTS:
{{governance_constraints}}

Return exactly these sections:

1) Evidence Register
- Table columns: evidence_id, claim_or_metric, source_system, source_location, source_timestamp, freshness_flag, confidence (0-1), section_owner.

2) Executive Brief (2-4 pages equivalent)
- Top outcomes vs objectives.
- Risks, blockers, and opportunities.
- Recommended decisions for this review cycle.
- Explicit "what is stale, missing, or still disputed" section.

3) Deck Blueprint (10-15 slides)
- For each slide: title, key message, supporting evidence, visual suggestion, speaker note.

4) Decision Log Draft
- Table columns: decision_id, recommendation, rationale, required_evidence_ids, owner_role, required_approver, due_date, status (proposed).

5) Action Register Draft (PROPOSED_ONLY)
- Table columns: action_id, task, destination_system, write_mode, priority, owner_role, due_date, dependency.

6) Publication and Packaging Plan
- Staging path for the brief and deck draft.
- Google Workspace output steps (Docs/Slides).
- Microsoft 365 output steps (Word/PowerPoint).
- Named final publisher and approval gate before circulation.

Rules:
- Distinguish verified facts from assumptions.
- Cite source references for every high-impact claim.
- Mark any stale or conflicting data sections as LOW_CONFIDENCE.
- Keep all system writes in draft/proposed state pending human approval.
- Separate "research", "draft", "approve", and "publish" stages explicitly.

When to Use

Use this for weekly or monthly executive updates where you need one consistent narrative and slide structure from multiple knowledge systems such as Drive or OneDrive, Jira and Confluence, and Notion or workspace notes.

It is especially useful when a team is starting to rely on shared workspace agents or connected research surfaces for recurring brief prep, but still needs the final brief and deck to remain clearly staged, reviewed, and human-published.

Variables

Variable	What to provide	Example
review_period	Time period covered by the report	”February 2026 monthly business review”
business_objectives	Goals to evaluate against	”Ship release X, improve retention by 2pp, reduce support backlog 20%“
data_sources	Connected systems and key source paths	”Jira board CORE, Confluence product updates, Drive strategy deck, OneDrive finance model”
audience	Specific stakeholder group	”CEO, CFO, VP Product, VP Engineering”
decision_scope	Decisions expected in this review	”Resourcing tradeoffs, launch sequencing, budget reallocations”
format_preferences	Voice, length, and output style	”Crisp, evidence-first, no jargon, 12-slide max”
governance_constraints	Policy constraints to respect	”No customer-level data in slides, legal review for claims on contracts”

Tips & Variations

• Ask for a “board-ready version” and “team-operational version” in one run.
• Add explicit chart preferences (line, waterfall, stacked bar) for each metric type.
• Stage a cited evidence packet first when source material is messy or politically sensitive.
• For recurring reporting, lock the same section order each cycle to improve comparability.
• Ask for a “red-team critique” section to stress-test weak recommendations before circulation.

Example Output

A strong response includes a concise evidence-backed brief, a source-linked deck blueprint with speaker notes, and a draft-only decision and action register that names approvers, owners, and publication gates instead of pretending the cycle is already complete.