PREP Framework: State the Point, Then Support It
PREP helps you give a short spoken argument: state the Point first, support it with one Reason and one Example, then restate the same Point so the room can follow the claim without hunting for it.
Framework Card
- Name:
- PREP Framework
- Goal:
- State a conclusion first, support it with one reason and one example, and restate the same point so a short spoken answer stays followable.
- Flow:
- Point → Reason → Example → Point (restated)
- Best For:
- Impromptu or Q&A answers when the claim already exists; Short briefings that need the conclusion before the support; Tightening a rambling opinion into one position
Why it matters
In a meeting, the question is often already on the table: delay the launch or not, fund the hire or not, keep the vendor or switch.
What happens next is familiar. The speaker starts with background, then a caveat, then a story, then another caveat. People wait for the recommendation. Some stop listening. Others reconstruct a point the speaker never said out loud.
That matters when the audience already has context and only needs your position in a short window: a Q&A, a two-minute update, an impromptu ask from a manager. If the conclusion is buried, the support never gets a chance to land.
PREP is a way to reverse that order. Say the claim. Prove it once. Close on the same claim. It is not a personality fix and it is not a promise that the room will agree.
What it is
PREP is a four-beat communication pattern: Point, Reason, Example, Point (restated).
Production content often credits Brian Tracy with popularizing this speaking loop. The method itself is small:
| Beat | Job |
|---|---|
| Point | State the conclusion or recommendation first. |
| Reason | Say why that point holds. |
| Example | Give one concrete illustration or piece of evidence. |
| Point (restated) | Repeat the same claim so the close matches the opening. |
The first Point is the answer. The last Point is not a new thesis. If the close changes the recommendation, the loop failed.
PREP assumes you already have a position. It organizes how you say it. It does not invent the judgment underneath.
How it works
A useful PREP is one claim, one rationale, one illustration, same claim at the end.
1. Point: lead with the conclusion
Name the recommendation or stance in a sentence the audience can repeat. "I recommend we delay the launch by two weeks." "We should keep the current vendor for this quarter." Avoid opening with history, mood, or a list of options.
2. Reason: justify that Point only
Give the rationale that makes this Point the one you are willing to stand on. One clear reason beats three half-reasons. If you need a stack of grouped arguments, you are closer to a pyramid than to PREP.
3. Example: make the Reason checkable
Point to one fact, incident, or comparison the audience can inspect: last week's defect rate, a customer conversation, a missed SLA. The example should prove the Reason, not entertain. If you lack an example, say what is known and what is assumed. Do not invent one.
4. Point restated: close the loop
Say the original Point again in the same direction. A short "so" sentence is enough. Do not smuggle in a second recommendation, a new scope, or a softer version that undoes the opening.
The four beats are the method. They are not a script you must read word for word, and they are not a playbook for choosing which decision is right.
How it compares
When another lens fits better, or when you need a complementary view, these frameworks do different jobs. They are not interchangeable labels for the same question.
Related communication lenses
| Framework | What it helps you see | How it differs from PREP |
|---|---|---|
| SCQA Framework | A narrative from shared situation and complication to the question and the answer | Builds context and tension before the answer. PREP states the answer first for a short spoken loop. |
| Pyramid Principle | A governing thought with grouped supporting arguments | Holds many reasons in a hierarchy, usually for memos and longer talks. PREP is one reason and one example. |
| STAR Method | One past experience as Situation, Task, Action, Result | Tells an incident in time order. PREP is a claim with support, not a story of what happened. |
Related frameworks on MyFramework
| Framework | What it helps you see | How it differs from PREP |
|---|---|---|
| SCQA Framework | Situation, Complication, Question, Answer as a story spine | Sanity related item. Same contrast as above: narrative problem-to-answer versus point-first spoken argument. |
PREP is the lens for a short spoken argument that starts and ends on the same Point. Other methods help when the question is mainly a story the audience must inhabit, a pyramid of reasons, or one past incident.
When to Use This Framework
- Q&A and impromptu asks: Someone puts a decision question on you and the room expects a stance, not a tour of your notes.
- Short executive updates: Leaders want the conclusion first and the reasoning only as far as it supports that conclusion.
- Claim-style interview answers (secondary): You are stating a strength, a recommendation, or a lesson as a position. If the interviewer asked for one past incident, STAR is the closer fit.
Example
A concrete example makes the structure easier to reuse when you are under uncertainty.
Example: product meeting Q&A
A product lead is asked, live: should we ship the checkout rewrite this Thursday as planned?
A PREP-shaped answer might sound like this:
Point: I recommend we delay Thursday's ship by one sprint.
Reason: The rewrite still fails the payment-retry path we already promised finance, so a Thursday ship would export a known break into production.
Example: In yesterday's staging run, 14 of 40 retry cases never posted the capture. That is the same path that caused last quarter's reconciliation tickets.
Point (restated): Delay Thursday. Fix the retry path, then ship.
Implication (not a finished plan): The room heard a stance, a reason tied to a promise, and one checkable failure. PREP did not design the sprint. It kept the recommendation from disappearing under a status tour.
Example: weekly executive briefing
An operations manager has three minutes in a standing meeting. The question on the slide is whether weekend overtime should continue.
Point: We should stop weekend overtime on the packing line this week.
Reason: Overtime is no longer covering the backlog. It is covering a sorter jam that weekday maintenance can fix.
Example: Saturday's extra shift cleared 200 orders and created 180 more because the jam recurred at 11:00. Monday's mechanic slot is already booked and unused overtime budget is the constraint, not labor supply.
Point (restated): Stop the weekend overtime this week and use the mechanic slot. Do not buy another Saturday.
Implication: The update is usable because the close matches the opening. A story about "how hard the team worked" would have been a different method and a weaker briefing.
Takeaway
What PREP can help with
- Putting a recommendation where listeners can hear it before the support
- Keeping one spoken claim from dissolving into background
- Pairing a reason with one illustration so the claim is inspectable
- Closing on the same point so the takeaway is stable
What PREP cannot replace
- A narrative path to the answer: If the audience lacks the situation and the tension, SCQA (Situation, Complication, Question, Answer) is built for that sequence.
- A multi-reason written architecture: Grouping several supporting arguments under a governing thought is the Pyramid Principle's job.
- A past-incident story: Situation, Task, Action, Result (STAR) tells what you did in one event. PREP states a position.
- Missing judgment or missing evidence: Clean structure will not repair a Point you do not believe or an Example you do not have.
- A facilitated group conversation: Moving a room from facts to feelings to meaning to a decision is ORID's job, not PREP's.
Honest scope: PREP organizes a short spoken argument. It does not choose the strategy, write the memo, or tell the incident.
Frequently asked questions
PREP is for saying one position clearly in a short spoken window: Point, Reason, Example, then the same Point again. It is most useful when the audience already has enough context to hear a conclusion first.
No. It makes the argument followable. A clean PREP with a weak Reason or a fake Example is still a weak answer. The method organizes a claim you already have.
SCQA walks the audience through Situation, Complication, Question, then Answer. Use it when people need the problem story before they can accept the answer. PREP skips that narrative and leads with the Point. The two are easy to mix up because both "structure a message." They sequence the conclusion differently.
STAR is one past incident in order. PREP is a current claim with a reason and an illustration. In interviews, STAR fits "tell me about a time." PREP fits "what is your recommendation?" or "why this approach?"
A Point you can quote, a Reason that actually supports it, one Example that makes the Reason checkable, and a close that repeats the same Point. If the close is a new idea, or the example is a second speech, you no longer have PREP.