Prepare Client Meeting Agendas and Decision Briefs with AI

A client meeting can spend its first twenty minutes discovering what the team already knew. Someone rereads the last update, finds the unresolved questions, and tries to remember which deadline was a suggestion. Preparation is the opportunity: get the facts and decisions together before the call.

In Clanker Cloud Workspace, the client Project can hold the last approved update, current notes, and open decisions. Ask an Agent to prepare an agenda around what the meeting needs to resolve, with a separate brief the account owner can inspect.

Name the meeting's purpose

“Prepare our client meeting” leaves too much open. Specify the audience, available time, and desired decision. A routine progress check and a scope discussion need different agendas.

Use this fictional preparation note:

Meeting: Cedar Studio launch review.
Duration: 30 minutes.
Purpose: agree the next review steps and identify blockers.
Page copy is approved; designs await client feedback.
Product photos are missing.
Launch timing depends on photos and design approval.
Translation was requested but is not approved scope.
Client participants and final decision-maker are unconfirmed.

Add the current brief and previous meeting notes as separate Project files. Identify their dates. Ask the Agent to treat earlier actions as open until a current source confirms completion.

Prepare an agenda and an owner's brief

Start a Session in the client Project with this prompt:

Prepare a 30-minute agenda for the launch review.
Use the current brief, latest update, and meeting notes.
For each agenda item, state the purpose and time allowance.
Keep the allowances within 30 minutes.

Save meeting-agenda.md for client review.
Save owner-decision-brief.md with source filenames,
open decisions, missing participants, and questions to confirm.
Separate confirmed facts from proposals and assumptions.
Do not schedule a meeting, invite anyone, or promise dates.

A reasonable illustrative agenda might use five minutes to confirm progress, ten for design feedback, ten for blockers and next steps, and five to recap decisions. That structure is a suggestion to review, not evidence that those participants or decisions are already confirmed.

Open both saved files. The owner's brief should make the missing decision-maker obvious. The client agenda should contain the questions people can actually answer, without including internal commentary about the account.

Make decisions easier to reach

For each unresolved item, ask what information is needed and who has authority to decide. If the packet does not identify an owner, keep that unknown. A contact who supplies photos is not automatically the person who approves a scope increase.

In the fictional example, translation belongs in a scope discussion. Missing photos belong in the blocker discussion. Neither should appear as completed work. A proposed launch date should be presented as a question with dependencies, not a calendar commitment.

Check the time budget too. A beautifully organized list of eight ten-minute topics does not fit a half-hour meeting. Ask for a shorter agenda when the decision load is too large, and keep supporting detail in the owner's brief.

Keep the post-meeting record useful

After the call, add notes identifying decisions, owners, and dates actually agreed. Ask for a decision log and a revised action list. Do not let a draft agenda become proof that a discussion happened or that its proposed actions were accepted.

Use the meeting action tracker when the next job is organizing the call's outcomes. For a client-facing summary, use the agency weekly reporting workflow.

Keep each meeting's agenda, source packet, and decision note dated in the Project. Reuse the preparation method through an Agent or Skill, while obtaining current evidence for every new meeting. You can add a Schedule after testing the task, provided someone supplies the latest inputs and the worker's timing is explicit.

Start through the client-report flow, then copy the meeting prompt into your Session. The first measure of success is whether the account owner arrives knowing which questions need an answer and which facts support the discussion.

Sources

• Client notes starting flow
• Meeting action tracker
• Project files and instructions
• Reusable Skills
• Loops and Schedules