Meeting management language at C1 — opening, parking lots, decisions, and action items

A well-run meeting is a small piece of high-stakes choreography: someone opens it, someone keeps it on track, someone surfaces decisions, someone captures action items, someone closes it. At B2, you could participate in meetings competently — agree, disagree, ask questions, summarize. At C1, you can run them, including meetings with senior people in the room, ambiguous agendas, hostile dynamics, and tight time constraints. The vocabulary of meeting management is one of the cleanest signals of executive maturity in American business contexts.

US meeting culture has converged on a set of conventions: tight openings, explicit agendas, time-boxed discussions, named decisions, captured action items with owners and dates, and crisp closes. The vocabulary includes a layer of facilitation idioms (let me table that, parking lot, let’s circle back, take it offline), decision-making frameworks (RACI, DACI, DRI), and the rhythm phrases that signal you know how meetings are supposed to flow (we’re at time on this agenda item, let’s land this and move on, can we get a decision in the next 90 seconds). Russian-speaker traps at C1 include treating meetings as open-ended discussions rather than time-boxed decision forums, missing the action-item capture, and not using the standard facilitation vocabulary — all of which make even a substantively good contribution feel un-American to the room.

This lesson covers opening and closing meetings, parking lot moves, decision-making frameworks, summarizing for clarity, action-item capture, and the rhythm phrases that mark a meeting as well-run.

Opening a meeting

The first three minutes of a meeting set the tone for the next 60. C1 openings are tight and explicit.

Standard professional opening

• Let’s get started. Thanks for being here.
• I’d like to kick us off.
• We’ve got a tight 30 minutes; let me walk through the agenda quickly.

Stating the purpose

• The goal of this meeting is to land a decision on X by 3:30.
• We’re here to align on Y and walk out with three action items.
• Purpose for today: get to a shared view on X. Not in scope: Y, Z.

Stating the agenda

• Three agenda items: A, B, C. I’d like to spend 10 minutes on A, 15 on B, 5 on C.
• I want to spend the first 20 minutes on diagnosis and the last 10 on next steps.
• Quick agenda check — does anything need to be added or reprioritized?

Setting the meeting rules

• Let’s keep this conversational — interrupt me if you have a question.
• I’ll hold questions until the end of each section.
• We’ll use the parking lot for anything off-topic.
• I’d like to keep this to phones-down — let’s give it 30 minutes of full attention.

Doing the round-robin

• Quick round the room — what’s most on your mind coming into this?
• I’d love a one-sentence intro from everyone before we start.
• Let’s do a 60-second check-in each.

Parking lot moves

The parking lot is the standard American meeting tool for handling off-topic-but-important items. Naming something for the parking lot keeps the meeting on track without dismissing the contribution.

Standard parking lot phrases

• Let me put a pin in that and come back to it.
• I want to park that for now — it’s important, and it’s not the topic for today.
• Adding that to the parking lot.
• Let me table that. (Note: this means “set aside” in AmE, opposite of BrE!)
• That’s a great question and a different meeting.
• I’m going to defer that to the right forum — let’s set it up separately.

Returning to the parking lot

• Coming back to the parking lot items: …
• We had three things on the parking lot — let’s see if any need to be addressed before we close.
• Worth picking up the X item in a follow-up.

Soft redirect

• Let me keep us on track — I want to make sure we get to a decision on X before time runs out.
• Worth flagging that we’re 12 minutes in on the first agenda item.
• Let me put us back on the rails.

Decision-making frameworks

US business culture has a standard vocabulary for clarifying decision rights. Knowing the frameworks and using them fluently is a strong C1 signal.

RACI — Responsible, Accountable, Consulted, Informed

• Responsible — does the work
• Accountable — owns the outcome (only one A)
• Consulted — input is sought
• Informed — kept in the loop

Usage:

• Who’s the A on this decision?
• I want to clarify RACI on the launch — who’s responsible, who’s accountable, who’s consulted, who’s informed?
• I’m consulted, not accountable, on the pricing decision.
• Let’s RACI this so we don’t end up confused next week.

DACI — Driver, Approver, Contributors, Informed

A variant used heavily in product and program management.

• Driver — drives the decision-making process
• Approver — has final approval authority
• Contributors — provide input
• Informed — kept in the loop

DRI — Directly Responsible Individual

Apple-originated; widely used in US tech. The single person who owns an outcome.

• Who’s the DRI on this?
• I’ll be the DRI on the migration.
• Every initiative needs a named DRI.

Type 1 vs Type 2 decisions (Bezos framework)

A common heuristic in US tech and consulting.

• Type 1 — irreversible decisions; deserve careful, slow process.

• Type 2 — reversible decisions; should be made quickly and adjusted.

• Is this a Type 1 or Type 2 decision?

• This is a Type 2 — let’s just decide and adjust.

• Be careful — this is a Type 1, we don’t get to walk it back.

Decision-call language

• Let me make the call.
• I’m going to make the call on this one.
• Who’s making the final call here?
• I’d like to formally make the decision: we’re going with Option B.
• On the record: decision is X.

Summarizing for clarity

A C1 facilitator summarizes constantly — at the end of each agenda item, before each transition, and at the end of the meeting.

Section summaries

• Let me summarize where we landed on this one.
• Quick recap before we move on: …
• Let me play back what I heard…
• Where we are: …

Confirming alignment

• Are we aligned on that?
• Anyone want to push back before we move on?
• Last call on this — anyone disagree?
• Hearing no objections, we’re going with X.

End-of-meeting summary

• Let me close us out with a quick recap.
• Three takeaways from today: …
• Action items: A (by Friday, owner Sarah), B (by next Tuesday, owner Marcus), C (by EOQ, owner Priya).
• Decisions made: X. Items deferred: Y. Parking lot: Z.

Action items — the captured commitment

Every well-run US meeting ends with action items. The structure: what + who + when.

Capturing action items

• Action item: Sarah will draft the customer email by Friday.
• Marcus is going to own the data validation, due Tuesday.
• Priya, you’re on for the legal review — what’s a reasonable date?
• Let me capture that as an action item: …

Confirming action items

• Reading back the action items I have: …
• Let me play back the actions: …
• Three actions out of this meeting: …

Action items in writing

• I’ll send a recap with the action items by end of day.
• I’ll drop the action items in Slack right after this.
• Notes and actions will be in the shared doc — please review by tomorrow.

When someone is hesitant on a date

• Can you commit to a date, even a soft one?
• I’d rather have a soft date we adjust than no date at all.
• What would be a reasonable target you’d feel good about?

Time-keeping phrases

A C1 facilitator manages time visibly.

Time checks

• Time check: we’re at 15 minutes, halfway through.
• We have 10 minutes left — three items remaining.
• Reminder: we’re at time on this agenda item; let’s land it and move on.

Running short

• We’re not going to get to everything; let me triage.
• Given the time, let me prioritize: we need to land X today; Y and Z can move.
• I want to get us out on time — let’s skip ahead to the decision needed.

Running over

• We’re 5 minutes over — let me wrap us up.
• I want to honor people’s calendars; let’s close.
• Going to be brutal about time now: action items only, no new discussion.

”Let’s circle back” and the bridging phrases

These are the rhythm phrases that mark fluency.

Circle back / loop back

• Let’s circle back on that.
• I want to circle back to what Sarah raised earlier.
• Coming back to the question Marcus asked at the top of the meeting…

Take it offline

• Let’s take this offline. (Discuss outside the meeting.)
• That’s an offline conversation.
• I’ll grab time with you offline.

Sync up

• Let’s sync up on this after.
• Quick sync tomorrow?
• We should sync before the board meeting.

Loop in

• I want to loop in Sarah on this.
• Make sure to loop in legal before we send.
• We should loop in the security team.

Touch base

• Let’s touch base on this Thursday.
• I want to touch base before the all-hands.

Closing a meeting

The close is a 60-90 second moment, but it shapes how the meeting is remembered.

Standard close

• Let me close us out. Three decisions: X, Y, Z. Three action items: A (Sarah, Friday), B (Marcus, Tuesday), C (Priya, EOQ). Parking lot: D. I’ll send the recap by EOD. Thanks, everyone.
• That’s a wrap. I’ll send the notes shortly.
• Going to give you four minutes back. Thanks for the energy in the room.

Warm close

• I appreciate the engagement on this — it was a hard conversation and we got somewhere.
• Good meeting. Thanks for bringing it.

When the meeting hasn’t fully resolved

• We didn’t get to a decision today, and I want to name that. Here’s how we close the loop: …
• Open question we need to resolve before next time: …
• Carrying X forward as unresolved.

Mini-dialogue — a full short meeting

Facilitator (you): Let’s get started. Thanks for jumping on. We’ve got 30 minutes. Goal for today: land a decision on the Q3 marketing budget allocation. Three agenda items — review the current spend, look at the two proposed reallocations, make the call. Going to keep us tight on time. (opening: purpose + agenda + time)

Maria: Quick question before we start — should we include the partnership-marketing line in scope?

You: Good question. For today, let’s keep it out of scope; we’ll address it in next week’s meeting with the partnership team. (parking lot soft) Adding it to the parking lot for then.

[Discussion ensues.]

You: Time check — we’re at 18 minutes, two-thirds in. Let me summarize what I’m hearing. (time check + summary) The room is split between Option A (reallocate 20% from paid to content) and Option B (reallocate 30% but stage it over two quarters). Marcus, you’re closer to the data — what’s your strong recommendation?

Marcus: B. I think 20% is too small to move the needle and 30% in one quarter is too risky.

You: OK. I’m going to make the call: we go with Option B, 30% reallocation staged over two quarters. (decision call) Are we aligned? (confirm) Last objection?

Sarah: I want to flag that we should set a clear off-ramp if the content investment isn’t tracking.

You: Good flag. That becomes an action item. (capture) Let me read back what we have. Decision: Option B, 30% reallocation staged over two quarters. Action items: Marcus to draft the off-ramp criteria by Thursday; Sarah to align with finance on the budget transfer by next Wednesday; I’ll draft the announcement to the broader team by Friday. (action items: what + who + when) I’ll send the recap by EOD. Thanks, everyone. (close)

Phrase bank — meeting management at C1

AmE-specific functional language

• Table that — AmE: defer, BrE: discuss now — high-stakes false friend.
• Parking lot — AmE meeting standard for deferred items.
• Take it offline — discuss outside the meeting; AmE business.
• Loop in — include someone in a conversation; AmE.
• Touch base — brief check-in; AmE business.
• Circle back / loop back — return to a topic later; AmE.
• Sync up — brief alignment meeting; AmE tech / business.
• DRI — Directly Responsible Individual; AmE tech (Apple-origin).
• EOD / EOW / EOQ / EOY — End of Day / Week / Quarter / Year; AmE business shorthand.
• Out of scope / in scope — AmE project management.
• Off-ramp / on-ramp — exit / entry plan for a decision; AmE business.
• Move the needle — produce measurable change; AmE.

BrE meeting culture leans on raise / shelve / agenda items / take it forward / minutes where AmE uses flag / table / parking lot / take it offline / recap notes.

Cultural notes

US meeting culture rewards:

• Brevity and time-discipline — meetings that run over are read as poorly facilitated.
• Explicit decision-making — let me make the call is professional, not arrogant.
• Named accountability — every decision and action item has a named owner. Someone should look into that is not an action item.
• Visible structure — purpose, agenda, time, decisions, action items. The structure is named.
• Phones-down norms — many high-performing US teams enforce no-phones-in-meetings.

Russian-speaker traps include: meetings that drift without explicit agendas; missing action-item capture (informal verbal agreements that don’t get tracked); confusion on table that (which means opposite things AmE/BrE); deference to senior people that prevents the facilitator from keeping time; and treating meetings as conversation rather than decision forums.

Common Russian-speaker mistakes

1. Skipping the purpose-agenda-time opening — launching into substance without the framing trio produces meetings that drift. The 90-second opening is non-optional in US business contexts.
2. Confusing table that AmE/BrE — In AmE, let me table this proposal means defer; in BrE it means discuss. This is the single highest-stakes meeting vocabulary trap for English-speakers crossing the Atlantic.
3. No named action items — We should look into that is not an action item. C1 standard is what + who + when.
4. Letting meetings run over — Soviet meeting tradition tolerated long meetings; US business tradition treats running over as failure of facilitation. Time-box and close on time.
5. Not using the standard facilitation vocabulary — parking lot, take it offline, circle back, loop in, sync up — fluent use marks C1. Substituting we will discuss separately, I will inform later, return to this is grammatically correct but culturally off.
6. Not making the call — Russian deference to consensus sometimes prevents the facilitator from naming a decision. American facilitation expects I’m going to make the call when the decision needs to land.
7. Confusing RACI vocabulary — I’m responsible, I’m accountable, I’m consulted, I’m informed have specific meanings in RACI. Loose use signals you don’t actually know the framework.
8. Missing the recap — meetings that end without summary or written recap produce confusion in the days following. Send the recap by EOD.

Summary

• Open with purpose + agenda + time in the first 90 seconds.
• Parking lot for off-topic items; name them and return to them.
• Table that in AmE means defer; opposite in BrE — critical trap.
• Decision frameworks: RACI, DACI, DRI, Type 1 vs Type 2 — know them and use them fluently.
• Make the call when a decision is needed; consensus is not always achievable.
• Summarize at every transition, not just at the end.
• Action items = what + who + when. Always named owner, always a date.
• Time-keep visibly: Time check, we’re at 15, halfway through.
• AmE workhorses: parking lot, take it offline, circle back, loop in, sync up, touch base, EOD/EOW/EOQ, DRI, move the needle.
• Close with a 90-second recap of decisions, action items, parking-lot items, follow-ups.

Next lesson: Hedging in professional communication — softeners, conditional offers, plausible deniability, and the line between diplomatic hedging and evasion.