Context Switch Briefing

How Coppermind automatically generates a transition brief when you have back-to-back meetings with different clients, so you never walk into a call wondering "wait, what were we doing with them?"

The Problem#

Fractional CMOs often have meetings stacked 30 minutes apart with completely different clients. Each client has its own brand voice, open action items, stakeholders, and recent history. Switching mental contexts between a casual startup and a formal enterprise client is one of the hardest parts of the job. Without a transition brief, the first few minutes of each meeting are spent mentally reconstructing where things stand.

How It Works#

When you run meeting prep and Coppermind detects that a different client's meeting occurred within the preceding 30 minutes, it automatically prepends a Context Switch section to the top of the meeting brief. No extra commands needed -- it appears whenever the conditions are met.

The detection logic:

1. Coppermind checks the meeting_log for a meeting with a different client mind that started within the 30 minutes before your upcoming meeting
2. If found, it generates a transition brief covering the gap between your last interaction with the upcoming client and now
3. The transition brief is prepended to the standard meeting brief

You get this automatically when meeting prep runs with a meeting_start_time parameter -- which calendar-driven auto-prep provides. You can also trigger it manually by mentioning the time:

"Prep my 2pm meeting with Bluebell"

What the Transition Brief Includes#

The Context Switch section covers four areas:

Last Interaction#

When you last met with or worked on this client. Gives you an immediate sense of how stale your context is.

**Last interaction:** 3 days ago (March 22)

Changes Since Then#

New memories that were created since your last meeting with this client -- decisions made, commitments added, facts captured. These are things that happened (possibly via email ingestion, transcript ingestion, or another session) that you might not have seen.

**Since then:**
- Sarah confirmed the Q2 budget at $50K (decision, March 23)
- Website redesign deliverable marked complete (March 24)
- New stakeholder identified: Marcus from procurement (fact, March 25)

Tone Shift#

When brand voice data exists for both clients, Coppermind surfaces the tone difference so you can mentally switch gears.

**Tone shift:** Switching from Acme's casual-startup to BigCorp's formal-enterprise style.

Open Items#

The top open commitments, issues, and agenda items for the upcoming client -- the things most likely to come up in the meeting.

**Top open items:**
1. Follow-up email RE: partnership proposal (commitment, 5 days old)
2. Q2 campaign brief review (agenda item, scheduled today)
3. Rebrand timeline discussion (issue, identified)

Full Example#

You: "Prep my 2pm meeting with Bluebell -- discussing content strategy"

Coppermind:

## Context Switch: Acme Corp -> Bluebell

**Last interaction:** 3 days ago (March 22)

**Since then:**
- Content calendar approved through May (decision, March 23)
- Lisa requested a case study draft by next week (commitment, March 24)

**Tone shift:** Switching from Acme's casual-direct to Bluebell's warm-professional style.

**Top open items:**
1. Case study draft for Lisa (commitment, 3 days old)
2. Social media audit results (agenda item, scheduled today)
3. Blog frequency discussion (issue, identified)

---

## Meeting Brief: Bluebell

(Standard meeting brief follows with stakeholders, action items,
recent decisions, campaigns, and key context...)

When It Appears#

Using It with Morning Briefing#

The morning briefing (/cmo-brief) shows all your meetings for the day. When it detects back-to-back client switches, it flags them:

"You have a context switch at 2pm: Acme (1:30pm) -> Bluebell (2:00pm).
Transition brief will be included in your Bluebell prep."

This lets you plan ahead for the mental shift rather than being surprised when you switch contexts.

Key Details#

• 30-minute window. The detection threshold is 30 minutes. Meetings further apart than that are not considered "back-to-back" and do not trigger a transition brief.
• Only confident matches. Both meetings must be confidently matched to client minds. Unmatched calendar events do not trigger transition briefs.
• No extra commands needed. If the conditions are met, the transition brief appears. If not, you get a standard brief.
• Works in raw mode too. Even when a client has fewer than 3 memories (raw mode), the transition brief still appears if a context switch was detected.
• Read-only. Like briefing, the context switch briefing does not modify any data.