Prepare materials for a weekly team meeting
Gather context from connected work apps and prepare a presentation for a team meeting.
How this works
Gather context from connected work apps and prepare a presentation for a team meeting. Use this for a recurring team meeting that needs consistent, current material from several work systems. The deck should focus on decisions and exceptions rather than reproduce every activity update.
Define a stable meeting outline and gather a dated snapshot of relevant projects, metrics and commitments. AI drafts the narrative; source records establish status. Keep missing updates visible and distinguish a completed task from an unverified claim of completion.
Before you start
Meeting outline
Agree recurring sections, audience and decisions the meeting should support.
Source scope
Select permitted trackers, reports and documents for this team.
Metric definitions
Obtain formulas, owners and reporting cutoffs for recurring charts.
Prepare the inputs
- meeting_date
- Required
date, timezone and reporting window
Use consistent cutoffs for all sections.
- work_snapshots
- Required
project IDs, status, owner, milestones and evidence
Record retrieval time and identify missing updates.
- metric_series
- Required
values, periods, units and definitions
Keep absent values distinct from zero.
- prior_actions
- Required
previous meeting commitments and decisions
Retain agreed owners and due dates.
Implementation, step by step
Collect the snapshot
- Retrieve the selected work records for the reporting window.
- Use file exports when connectors are unavailable and record their age.
Checkpoint: A source manifest defines coverage.
Reconcile status
- Compare current updates with prior actions and milestone evidence.
- Flag conflicting status reports rather than silently selecting the newest sentence.
Checkpoint: A status table separates verified changes and questions.
Draft the meeting story
- Organize progress, exceptions, decisions needed and next actions.
- Keep routine detail in notes and reserve slides for discussion-worthy items.
Checkpoint: The outline matches the meeting's purpose.
Build the deck
- Create charts from verified data and concise project summaries.
- Add source references and cutoffs in notes; tailor detail to the audience's access.
Checkpoint: A rendered draft is ready to inspect.
Review and refresh
- Verify numbers, owners and dates and inspect the rendered slides.
- Refresh material changes before the meeting and record which version was used.
Checkpoint: The team receives a coherent, current review packet.
Decisions along the way
Project owner has not updated status
Show update missing and retain the prior status with its date.
Metric definition changed
Separate the series or explain the break instead of drawing a misleading trend.
A slide contains restricted details
Create an audience-appropriate summary without leaking the underlying content.
What you will produce
weekly-team-deck.pptx
PresentationA meeting-ready draft with evidence in notes.
Include: progress · metrics · decisions · risks · actions
meeting-source-manifest.csv
CSVA compact audit trail and refresh list.
Include: section · source_id · cutoff · owner · gap
Check the result
- Reconcile chart values with source records.
- Confirm action owners and deadlines were agreed rather than generated.
- Inspect all slides for truncation, illegible charts and missing labels.
- Verify each status claim has current evidence or an explicit caveat.
When something goes wrong
A source export fails
Mark the affected section unavailable rather than reuse stale values silently.
Deck renderer drops content
Inspect the affected slide and simplify the layout.
Late update changes a decision
Revise the relevant slide and retain the previous version.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Synthetic: prepare a weekly operations deck.
Inputs
Project P2 is marked complete in a chat, but its tracker shows testing open. Metric M1 is 42 this week; last week is missing. Prior action A3 remains overdue.
Expected result
Synthetic result: show P2 completion unverified, M1=42 without invented growth, and A3 as an overdue agreed action. Put the P2 test decision on the agenda.
Run a small pilot
Start small
Prepare two consecutive meetings using the same outline.
Record the baseline
Record manual preparation time and corrections raised in the meeting.
Agree success criteria
Agree freshness, factual accuracy and decision usefulness before scheduling recurring preparation.
Stop or revise
Stop automatic sharing when source coverage or audience restrictions cannot be verified.
Keep the scope clear
- Preparing a deck does not update project statuses or create new commitments.
- Share only through the channels and audience authorized for the meeting.
Check before using
Check statuses, dates, and the intended audience; remove sensitive details.
Business activities
- Review business performance
- Coordinate meetings and follow-ups
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Calendar · Work discussions · Project documents
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow