Meeting Brief Prompt Library

Partners walk into client meetings with 15 minutes of prep time and expect you to have synthesized weeks of activity into a single page. This is your system for doing exactly that.

These prompts pull from CRM

data, email threads, and project management tools to generate partner-ready meeting briefs. Each prompt is designed to be pasted directly into Claude, ChatGPT, or your firm's AI assistant with minimal customization.

Copy this into your AI tool's system instructions before using any of the specific prompts below:

You are a senior project manager at a professional services firm preparing meeting briefs for partner-led client meetings. Your briefs are:

- One page maximum (600-800 words)
- Written for partners who have 5 minutes to read before the call
- Focused on decisions needed, not status updates
- Specific about numbers, dates, and dollar amounts
- Clear about who owns what action item

Format every brief with these sections:
1. Meeting Context (2 sentences: who, what, why now)
2. Key Numbers (revenue, hours, budget burn, timeline)
3. Decisions Needed (max 3, with your recommendation)
4. Risks to Surface (only if they require client action)
5. Action Items from Last Meeting (status only)

Never use: "as previously discussed", "per our conversation", "as you know", "moving forward", "going forward".

Use this when you need to generate a brief from scattered CRM

notes, emails, and activity logs.

Generate a meeting brief for [CLIENT_NAME] using the following data:

CLIENT CONTEXT:
- Engagement type: [litigation support / tax advisory / M&A due diligence]
- Current phase: [discovery / planning / execution / closeout]
- Total engagement value: $[AMOUNT]
- Burned to date: $[AMOUNT] ([X]% of budget)
- Original end date: [DATE]
- Current projected end date: [DATE]

RECENT ACTIVITY (paste from CRM):
[Paste last 10-15 activity log entries here, including emails, calls, meetings, deliverable submissions]

OPEN ACTION ITEMS (paste from project tracker):
[Paste current action item list with owners and due dates]

UPCOMING MEETING DETAILS:
- Date/Time: [DATE/TIME]
- Attendees: [LIST]
- Stated purpose: [CLIENT'S REASON FOR MEETING]

Focus the brief on what decisions the partner needs to drive in this meeting. If the client requested the meeting, identify what they're likely concerned about based on recent activity patterns.

Example output structure:

Meeting Context: Quarterly business review with Acme Corp's CFO and Controller. They requested this meeting after receiving our Phase 2 budget revision. We're 67% through budget with 45% of scope complete.

Key Numbers:

• Original budget: $340K | Spent: $228K | Remaining: $112K
• Hours: 1,520 of 2,100 (72% burned)
• Timeline: 8 weeks behind original schedule
• Scope completion: 45% (data migration complete, analytics build in progress)

Decisions Needed:

1. Approve $85K budget increase for expanded analytics scope (recommend: yes, client requested these features in writing on 3/15)
2. Accept 6-week timeline extension to 8/30 (recommend: yes, driven by client's delayed credential access)
3. Prioritize Phase 3 features now or defer to separate engagement (recommend: defer, keeps current project focused)

Use this when a project has problems that require partner intervention.

Generate an escalation brief for [CLIENT_NAME] covering the following issue:

ISSUE SUMMARY:
[Describe the problem in 2-3 sentences]

BUSINESS IMPACT:
- Financial: [dollar amount at risk, budget overrun, revenue impact]
- Timeline: [delay in days/weeks, missed milestones]
- Relationship: [client satisfaction score, escalation level, at-risk renewal]

TIMELINE OF EVENTS:
[List 5-8 key events that led to this issue, with dates]

WHAT WE'VE TRIED:
[List 3-5 actions already taken to resolve]

WHAT WE NEED FROM THE CLIENT:
[Specific asks with deadlines]

RECOMMENDED RESOLUTION:
[Your proposed path forward, including any fee adjustments, timeline changes, or scope modifications]

Format this for a partner who needs to call the client today. Lead with the business impact, not the technical details.

Example output:

Issue: Client's IT team has blocked API access to their financial systems for 3 weeks, preventing our data extraction work.

Business Impact:

• $45K in team costs with no billable progress
• 3-week timeline delay, pushing go-live from 7/15 to 8/5
• Risk of missing client's fiscal year-end reporting deadline (8/31)

We've escalated through: project sponsor (3x), IT director (2x), written memo to CFO (4/22). No response to any channel.

What We Need: Partner-to-C-suite call to unblock API

access by 5/10. If access isn't granted by 5/10, we need to discuss pausing the engagement to avoid further non-billable costs.

Use this for recurring check-ins with long-term clients.

Generate a QBR brief for [CLIENT_NAME] covering [QUARTER/YEAR]:

ENGAGEMENT PORTFOLIO:
[List all active matters/projects with current status]

FINANCIAL SUMMARY:
- Total fees this quarter: $[AMOUNT]
- YTD fees: $[AMOUNT]
- Projected annual fees: $[AMOUNT]
- Comparison to last year: [up/down X%]

VALUE DELIVERED:
[List 3-5 specific outcomes, with quantified results where possible]

UPCOMING OPPORTUNITIES:
[List 2-4 potential new engagements or expansions, with estimated value]

RELATIONSHIP HEALTH:
- Primary contacts: [names and titles]
- Last executive touchpoint: [date]
- NPS or satisfaction score: [number]
- Concerns or risks: [list any]

DISCUSSION TOPICS FOR THIS QBR:
[3-4 strategic topics beyond project status]

Frame this brief to position our firm as a strategic partner, not just a vendor. Focus on business outcomes, not hours delivered.

Use this for first meetings with new clients.

Generate a kickoff meeting brief for new client [CLIENT_NAME]:

CLIENT BACKGROUND:
- Industry: [industry]
- Size: [revenue, employees, locations]
- Key decision makers: [names, titles, backgrounds]
- How they found us: [referral source, RFP, existing relationship]

ENGAGEMENT SCOPE:
- Services: [list]
- Duration: [timeline]
- Budget: $[AMOUNT]
- Success criteria: [how client will measure success]

WHAT WE KNOW ABOUT THEIR SITUATION:
[Paste notes from sales process, RFP response, discovery calls]

WHAT WE DON'T KNOW YET:
[List 5-7 questions we need answered in kickoff]

POTENTIAL RISKS:
[List any red flags from sales process]

KICKOFF MEETING OBJECTIVES:
1. [Objective with specific outcome]
2. [Objective with specific outcome]
3. [Objective with specific outcome]

Include a "first 30 days" plan that shows the client we've done this before.

Use this when a client requests work outside the original agreement.

Generate a scope change brief for [CLIENT_NAME]:

ORIGINAL SCOPE:
[Paste original SOW deliverables section]

REQUESTED CHANGE:
[Describe what client is asking for]

EFFORT ANALYSIS:
- Additional hours: [number]
- Additional cost: $[AMOUNT]
- Timeline impact: [days/weeks]
- Resource requirements: [roles needed]

STRATEGIC CONSIDERATIONS:
- Is this a natural expansion or scope creep? [your assessment]
- Will saying no damage the relationship? [your assessment]
- Is this a door to a larger engagement? [your assessment]

RECOMMENDATION:
[Approve with fee adjustment / Approve as goodwill / Decline and explain why / Defer to Phase 2]

TALKING POINTS FOR PARTNER:
[3-4 specific points to make in the conversation]

Frame this to help the partner make a business decision, not just a project management decision.

Before you paste any prompt:

1. Pull the actual data from your systems. Don't make the AI guess at numbers.
2. Replace all [PLACEHOLDERS] with real information.
3. Include dates in MM/DD format, not relative terms like "last week".
4. Paste actual text from emails or notes rather than summarizing them yourself.

After the AI generates the brief:

1. Verify every number against your source data.
2. Remove any hedging language ("may", "could", "potentially").
3. Add your own judgment to the recommendations section.
4. Cut anything that doesn't help the partner make a decision or run the meeting.

What makes a brief partner-ready:

• Partner can read it in under 5 minutes
• Every decision has a clear recommendation
• Every number is accurate and sourced
• Every risk has a proposed mitigation
• No surprises that should have been escalated earlier

The goal is not to impress the partner with how much work you did. The goal is to make them look smart and prepared in front of the client.