CARS: a four-part framework for clearer team communication

Executive overview

Most workplace miscommunication happens not because people are unclear about what they want, but because they omit the context, prior attempts, and stakes that would let the other person act immediately. CARS — Context, Attempts, Request, Stakes — is a four-part structure you can apply to any written or spoken message to eliminate back-and-forth.

Clear roles and responsibilities can substitute for context and attempts entirely — but only if they already exist.

Context: give only what's needed to act

• Set the scene with the minimum information the other person needs to respond.
• Anticipate the questions that would block their reply and pre-answer them.
• Exclude chronology, apologies, and irrelevant detail — especially common for extroverts.
• Example: "I have an invoice to send to John Doe Inc. for $1,200 for VIP service 123" — not a story about how the day started.

Attempts: show what you've already tried

• Document every step you've already taken so the recipient doesn't repeat them.
• The more thorough this section, the faster the other person can move forward.
• When delegating up (to a boss, client, or peer), make this section exhaustive — it demonstrates you've exhausted your options.
• When delegating down (to a direct report or assistant), leave it blank unless there's a critical detail they need to know.

Request: be specific about what you want

• State exactly what action you want: create, decide, approve, review, or fix — and by when.
• Avoid yes/no questions ("Can you make the invoice?") when you need action, not capability confirmation.
• Avoid vague prompts like "tell me what you think" — name the actual outcome: approval, feedback, a decision between two options, devil's advocacy.
• For people with short attention spans, put the request at the top as a subject line or at the bottom as a TLDR.

Stakes: explain why it matters

• Define what happens if the request isn't fulfilled — or why fulfilling it is valuable.
• Concrete example: "We're hiring at end of month — the careers page needs to be ready in two weeks."
• If you can't identify a meaningful stake, reconsider whether the request is worth making.
• Stakes as a delegation threshold: set a dollar-value floor (e.g. $500) below which team members resolve issues independently. Raise the threshold as trust is earned.
• Log decisions made under the threshold — coach on bad ones, celebrate good ones, then raise the floor.