PREP
The only framework here whose output is meant to be said out loud.
What is PREP?
PREP is four slots and only three ideas: Point, Reason, Example, then the Point again. It is the shortest framework on this site, it is built for speech rather than for documents, and the repetition that looks like padding is the whole design.
PREP exists because a listener cannot scroll back. In a document a reader who loses the thread re-reads the first line; in a meeting they cannot, so the claim has to arrive twice — once before the evidence and once after it, carrying the weight the evidence gave it. That makes PREP the one framework here whose output format is a constraint rather than a preference. Ask a model for "a persuasive argument" and you will get a bulleted memo with bold headings, which is a perfectly good document and cannot be said out loud. If you want something speakable, the prompt has to say so, because nothing about the acronym implies it.
Where PREP Came From
Public-speaking pedagogy, no inventor of record
PREP belongs to impromptu-speaking training rather than to management writing, and no individual can be credited with it. Toastmasters International teaches and recommends it — it is a standard answer-shape for the unprepared speaking exercises at the heart of their meetings — but recommending is not inventing, and pages naming a founder are guessing. It is best understood as a piece of oral tradition that got written down.
It is answer-first, which is the same instinct as the Pyramid Principle
The design choice worth noticing is that PREP leads with the conclusion. That is the miniature form of what Barbara Minto argued at McKinsey in the Pyramid Principle and what SCQA arranges at length: give the answer, then support it. PREP is what that looks like when you have ninety seconds and no slides.
Why four slots for three ideas
The fourth slot is not a summary, it is a restatement — the same claim in different words, said again once the listener has a reason to accept it. Repeat it verbatim and it reads as filler. Change the words and it reads as a conclusion. That single distinction is most of the difference between PREP done well and PREP done mechanically.
The 4 Slots, One at a Time
Each slot is a decision. Leave it out and the model still makes it — just without you.
One sentence, and get the ask into it. A point with no request is an observation, and the room will treat it as one. If you need a decision today rather than at the next meeting, that belongs in the first sentence, not the last.
PREP holds one reason. If you have four, you have four PREPs or a different framework, because a listener who hears four reasons remembers none of them. Pick the one that would still stand if the other three were wrong.
The load-bearing slot, and the one people fill with a hypothetical. "Imagine if we shipped without it" persuades nobody; a thing that actually happened, with a date and a cost, ends the discussion. If you have no real example, that is worth knowing before you speak — it usually means the Reason is weaker than you thought.
Not a summary and not a repeat. Say it again in the terms the Reason and Example have just established, so the sentence lands harder than it did the first time. Then stop — the commonest PREP failure is a fifth beat where the speaker starts hedging.
One Task, Before and After
The task: A spoken opening telling three directors the launch is slipping. Both prompts below are scored by our free prompt checker — paste either in and you will get the same number, because the scoring is deterministic.
Write something explaining why the project is late.
Seven words, and the lowest starting score on this site. You get a bulleted apology with five reasons and no ask — a document, when what you needed was ninety seconds of speech.
Point: The launch moves from 14 October to 25 November, and I am asking you to approve the new date today rather than in two weeks. Reason: The payments integration failed its security review on 2 October and the remediation is four weeks of work we cannot compress. Shipping on the original date would mean launching without it. Example: We tried compressing a review like this once before, on the invoicing release in March. It went out on time, failed a customer's own audit six weeks later, and cost eleven weeks of rework - three times the delay we avoided. Point again: Approve 25 November now. The delay is six weeks; the alternative, on the only evidence we have, is three months. Write this as a spoken opening for a stakeholder meeting, 200 to 250 words in four short paragraphs, one per element, in continuous prose - no bullets, no headings, no bold. Every sentence must be sayable in one breath. The room is three directors who have already heard the October date twice and are not technical. Do not explain what a security review is; assume they know it is a gate they cannot waive. The closing point must restate the opening claim in different words, carrying the weight the reason and the example have given it - not a verbatim repeat. For example, the opening should sound like this: ``` I am asking you to approve a new launch date of 25 November, and I would like the decision today rather than in a fortnight. ``` Do not apologise more than once. Do not blame a named team or an individual, and do not promise the new date is certain.
Ninety-two from 273 words — the biggest jump on this site, from the lowest floor. Most of it comes from three instructions that have nothing to do with the acronym: say it in prose, one breath per sentence, and do not repeat the opening verbatim.
Ninety-two, and no scorer can hear it
One check is out of reach and two of PREP's three real failure modes are invisible to any rubric:
No persona slot. Here that is genuinely the right call rather than a limitation — the point of PREP is that you are saying this, in a room, in your own voice. A persona produces something you would not say out loud, which defeats the exercise.
The one thing PREP exists for, and nothing measures it. A bulleted, bolded, sub-headed answer scores exactly as well as speakable prose, and only one of them survives contact with a meeting. Read it aloud; that is the only test.
A closing point copied word for word from the opening scores the same as one that has been re-earned. To a listener the first sounds like padding and the second sounds like a conclusion.
The transferable habit is the Example slot. PREP fails softly when the Reason is weak, and the tell is that you cannot produce a real example — you reach for "imagine if". That is worth discovering at your desk rather than in the room, and it is the cheapest argument test there is.
Copy-Paste Prompt Template
Replace the bracketed placeholders with your specific details.
Point: [The claim in one sentence, with the ask inside it] Reason: [The single strongest reason — the one that would stand alone] Example: [One real, specific, checkable instance. If you reach for "imagine if", the argument is not ready] Point again: [The same claim in DIFFERENT words, carrying what the example added. Then stop] [Say it out loud: continuous prose, no bullets or headings, every sentence sayable in one breath] [Who is in the room, and what they already know]
When PREP Fits — and When It Does Not
- Answering a question in a meeting when you have had no warning.
- Explaining a delay, a decision or a refusal to people who will push back.
- Executive summaries and one-page recommendations — answer first, then support.
- Short opinion pieces and social posts, where one point beats three.
- Interview answers to opinion questions, as distinct from story questions.
- Any moment where you need to be understood once, without a second chance.
- Arguments with conditions and branches. PREP holds one point; nuance flattens it.
- Long documents. Four short beats do not organise anything past a page.
- Story questions in interviews — "tell me about a time…" wants SOAR or STAR.
- Analysis, where you do not yet know the point. PREP starts by asserting it.
- Anything with several equally strong reasons; pick one or use a different shape.
10 Ready-Made PREP Prompts
Every prompt below was produced by the Frompting generator with PREP selected — not written by hand for this page. Each is scored by our prompt checker; the median is 82/100. Click one to open it, then copy.
Arguing for more investment in support 69
You are a persuasive business strategist preparing a concise board‑room argument to secure additional investment in customer support. Your audience is the company’s board of directors. The goal is to convince them that allocating more resources to customer support will drive measurable business benefits. Deliver a spoken‑style presentation script of approximately 300 words, organized as a single flowing argument that: - Begins with a clear opening statement that captures the core claim. - Provides a logical justification for the claim, linking support investment to key business outcomes. - Includes a concrete, relatable illustration (e.g., a recent customer incident, benchmark data, or competitor case) that demonstrates the impact of strong support. - Concludes by restating the original claim and summarizing the expected upside. Quality criteria: 1. Use compelling, data‑informed language while keeping jargon to a minimum; define any technical term at first use. 2. Maintain a confident, executive tone appropriate for senior leadership, with varied sentence length for natural rhythm. 3. Ensure the argument is tightly focused—avoid unrelated topics or excessive detail. Boundary: Do not propose specific budget figures or timelines; leave those to be filled in later. If any essential detail (such as the company’s current support metrics, recent customer feedback, or competitive landscape) is unknown, indicate it with a placeholder in the form **[PLACEHOLDER: description of needed information]**. If any bracketed detail above is left unfilled, choose a sensible value from the context, state that assumption in one line before you begin, and continue — do not ask for it and stop.
A LinkedIn post on remote work structure 83
You are a persuasive content creator specializing in professional social‑media posts. Your task is to craft a LinkedIn post that argues remote work requires more structure, not less. Begin with a clear opening statement that presents the main claim. Follow with a concise explanation of why additional structure is essential. Include a concrete, relatable illustration that supports this reasoning. Conclude by restating the claim and encouraging readers to consider implementing stronger frameworks in their remote environments. Write the post for [AUDIENCE]: a brief description of the intended readers (e.g., managers, remote‑team leaders, HR professionals). Use a professional yet engaging tone appropriate for LinkedIn, and keep the total length between 150 and 200 words. Quality criteria: 1. The argument is logically coherent and easy to follow. 2. The example is specific, vivid, and directly reinforces the reason. 3. The closing reinforces the main point and includes a subtle call‑to‑action. Exclude overly technical jargon and avoid mentioning any framework names. If any of the required details are unclear, state your assumptions and ask up to three clarifying questions before drafting the post.
Explaining a late project to stakeholders 74
You are a concise business communicator tasked with crafting a persuasive explanation for stakeholders about why the project is running late. First, state a clear opening statement that directly addresses the delay and its impact on the project’s objectives. Next, provide a logical justification that outlines the primary cause(s) of the delay, referencing any relevant constraints or unforeseen issues. Then, illustrate the justification with a concrete example or anecdote that demonstrates how the identified cause manifested and affected the timeline. Finally, close with a reaffirming statement that restates the initial point, emphasizes commitment to resolving the issue, and outlines the next steps or mitigation plan. The explanation should be written for [STAKEHOLDER_GROUP: specify the audience, e.g., senior executives, client representatives, project sponsors] and be no longer than 250 words. Quality criteria: - Clear, jargon‑free language that a non‑technical audience can easily understand. - Logical flow that naturally leads the reader from the opening point through the reason, example, and closing point. - A tone that is professional yet empathetic, showing accountability and a proactive stance. Exclude any technical project management terminology that is not essential to the stakeholder’s understanding. If any bracketed detail above is left unfilled, choose a sensible value from the context, state that assumption in one line before you begin, and continue — do not ask for it and stop.
A vendor recommendation summary 95
You are an executive communications specialist. Your client needs a concise executive summary that persuades senior leadership to select a single vendor over two alternatives. Create a summary of **approximately 250 words** that follows a clear, persuasive flow: start with a decisive opening statement, provide the logical justification, illustrate the point with a concrete comparison, and close by reinforcing the recommendation. The summary must: - Be tailored for a C‑suite audience, using a professional yet direct tone. - Highlight the most compelling advantage of the chosen vendor in relation to the two competitors. - Include one specific, data‑driven example (e.g., cost savings, performance metric, implementation timeline) that supports the advantage. - End with a strong reaffirmation of the recommendation and a brief call to action (e.g., “Approve the contract by [DATE]”). [SELECTED_VENDOR]: name of the vendor you recommend. [COMPETITOR_1]: name of the first alternative vendor. [COMPETITOR_2]: name of the second alternative vendor. [KEY_ADVANTAGE]: the primary reason the selected vendor is superior (e.g., lower total cost of ownership, faster deployment). [EXAMPLE_METRIC]: a specific figure or case study that demonstrates the advantage. Produce the summary in plain text, without headings or bullet points, and ensure it reads as a single, cohesive narrative. Do not include any information beyond what is provided; if any critical detail is missing, state the assumption and ask up to three clarifying questions before finalizing. Before writing the final answer, work through the problem step by step and weigh the main trade-offs; present only the reasoned conclusion, not your working notes.
An opinion piece on AI in hiring 82
You are a concise opinion writer for a professional audience. Write a short opinion piece (≈250 words) on the use of AI in hiring that follows a clear persuasive flow: start with a strong opening statement, provide a logical reason supporting it, illustrate the point with a concrete example, and finish by restating the opening statement in a compelling way. The piece is intended for [AUDIENCE: specify the primary readers, e.g., HR leaders, recruiters, business executives]. Use a professional yet engaging tone, avoid jargon unless briefly defined, and ensure each paragraph advances the argument. Quality criteria: 1. The opening and closing statements are tightly linked and reinforce the central claim. 2. The reason is supported by a specific, realistic example that illustrates the impact of AI in hiring. 3. The writing is clear, concise, and free of filler language. Exclude any discussion of legal compliance details or technical implementation steps; focus solely on the persuasive argument about the benefits and considerations of AI in hiring. If any key details (such as the target audience’s level of familiarity with AI) are unclear, state your assumptions and ask up to three brief clarifying questions before drafting the piece.
Explaining a database choice in Slack 83
You are a concise technical communicator tasked with drafting a Slack update that explains why the team selected Postgres instead of MongoDB. Write a brief message (≈120–150 words) aimed at [RECIPIENT: e.g., the engineering or product team] that follows a logical flow: start with a clear opening statement, provide the main reason for the decision, illustrate the reason with a concrete example, and close by reinforcing the benefit of using Postgres. The update should be persuasive yet factual, use a friendly professional tone appropriate for Slack, and avoid unnecessary jargon. Ensure the message is easy to read at a glance and includes a call‑to‑action inviting questions or feedback. If any details are unclear, state your assumptions explicitly and ask up to three clarifying questions before finalizing the draft.
An interview answer on management style 83
You are a professional interview coach helping a candidate craft a concise, persuasive response to the common interview question “What is your management style?” Your task is to produce a single, polished answer that a hiring manager could read aloud in an interview. Structure the response so that it begins with a clear opening statement, follows with a brief justification, includes a concrete illustration from the candidate’s experience, and ends by restating the opening point. Keep the total length between 150–200 words. The answer should: - Use a confident, authentic tone appropriate for a senior‑level professional. - Highlight strengths that align with typical leadership expectations (e.g., collaboration, results‑orientation, adaptability). - Include a specific, brief story that demonstrates the style in action, mentioning the context, the candidate’s action, and the outcome. If any essential detail (such as the industry, the size of the team managed, or a notable achievement) is unknown, insert a placeholder in the form **[PLACEHOLDER: description of needed detail]**. State any assumptions you make explicitly, and if you need clarification, ask up to three targeted questions before finalizing the response. Deliver the answer as plain text without headings or bullet points. Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader.
The one-page case for more budget 68
You are a persuasive business writer tasked with drafting a concise, one-page case to secure a budget increase. Your audience is the [AUDIENCE: e.g., senior leadership team, finance committee, board of directors] who need a clear, compelling argument. Begin with a strong opening statement that directly states the request for additional funds. Follow with a logical justification explaining why the increase is essential, referencing the impact on [PROJECT/INITIATIVE: name or description] and aligning with organizational goals. Include a concrete illustration-such as a recent success, metric, or stakeholder testimonial-that demonstrates the value already delivered and the potential gains from the extra budget. Conclude by restating the request, emphasizing the benefits, and urging prompt approval. Produce the document in plain text, formatted as a single page (approximately 410-540 words). Ensure the argument is concise, evidence-based, and written in a professional tone. Quality criteria: 1. Persuasive and logically structured. 2. Clear and specific, with no vague statements. 3. Free of jargon and unnecessary detail. Leave out any unrelated financial history or unrelated project information. If any of the placeholders above are unknown, state your assumption and ask up to three clarifying questions before finalizing the draft.
A press talking point about layoffs 81
You are a seasoned communications consultant who crafts concise, persuasive talking points for press interviews. Your task is to produce a single, interview‑ready talking point that a spokesperson can deliver when asked about recent layoffs. The talking point must be clear, empathetic, and maintain the organization’s reputation. Assume the spokesperson will address a national news outlet and the audience includes journalists, investors, and the general public. Deliver the talking point in approximately 150 words, using a balanced tone that acknowledges the difficulty of the decision while highlighting the company’s forward‑looking strategy. The output should: - Clearly state the core message at the beginning and end. - Provide a logical reason that explains the necessity of the layoffs. - Include a brief, concrete example (e.g., a specific initiative or market condition) that illustrates the reason. - End with a reaffirmation of the core message to leave a strong final impression. Quality criteria: (1) empathetic language, (2) factual clarity without speculation, (3) a memorable closing sentence. Exclude any unverified financial figures or internal policy details; only use information that can be confirmed or is provided. If any essential detail (e.g., company name, specific reason for the layoffs, or key strategic initiative) is missing, state your assumption and ask up to three clarifying questions before finalizing the talking point.
Recommending a tool to a community 79
You are a community-focused writer tasked with crafting a concise, persuasive comment that recommends a project management tool to a specific online community. The comment should be structured as a brief argument that first states the recommendation, then explains why it is valuable, provides a concrete illustration, and finally restates the recommendation. Keep the tone friendly and supportive, and limit the comment to **395-525 words**. - Identify the community you are addressing: **[COMMUNITY_TYPE]** (e.g., developers, designers, nonprofit volunteers). - Name the tool you are recommending: **[PROJECT_MANAGEMENT_TOOL]**. - Highlight one key feature that makes the tool especially suitable for this community: **[KEY_FEATURE]**. Your output must: 1. Begin with a clear recommendation of the tool. 2. Follow with a concise reason why the tool benefits the community. 3. Include a specific example or scenario illustrating the benefit. 4. Conclude by restating the recommendation and encouraging the community to try it. Quality criteria: persuasive, easy to read, and free of jargon unfamiliar to the community. Exclude any unrelated product mentions or sales language. Before writing the final answer, work through the problem step by step and weigh the main trade-offs; present only the reasoned conclusion, not your working notes.
Scores range from 68 to 95. They are shown as generated rather than cherry-picked — a library where every entry scores in the nineties tells you it was curated, not measured.
PREP vs the Alternatives
The same answer-first instinct at document length. SCQA earns the answer by building tension first; PREP has no time for that and simply leads with it.
The persuasive cousin, aimed at readers rather than listeners. PAS builds discomfort; PREP assumes attention and spends it immediately.
The other four-slot spoken framework, for a different question. PREP answers "what do you think?"; SOAR answers "tell me about a time when…".
What to reach for when the job is to be understood rather than to be agreed with. CLEAR explains; PREP argues.
Four stages for an audience that has not chosen to listen. PREP assumes a room that already has to.
Five Ways People Get PREP Wrong
The defining PREP failure and the easiest to prevent. Nothing in the acronym says "prose", so a model gives you bullets and bold. Ask for continuous paragraphs and sentences sayable in one breath, or you have not used the framework.
"Imagine if we…" is not an example, it is the Reason repeated in the subjunctive. If nothing real comes to mind, the argument is weaker than it felt.
Four reasons is four arguments, and a listener retains none of them. Choose the one that would survive alone.
The fourth slot is a restatement, not a copy. Same claim, different words, carrying what the evidence has just added.
A claim without a request is an observation, and rooms do not act on observations. Put the decision you want into the first sentence.
PREP ends at the second Point. The instinct to add "but obviously we can discuss it" undoes the whole structure in one sentence.
PREP Questions
What does PREP stand for?
Point, Reason, Example, Point. You state your claim, give the reason for it, give one real example, then state the claim again in different words.
Where does PREP come from?
Public-speaking practice rather than management theory. It has no documented inventor; Toastmasters International teaches it as a standard structure for impromptu speaking, which is how most people meet it.
Why repeat the point at the end?
Because a listener cannot re-read. The second statement is the same claim carrying the weight the reason and example have just given it — which is why it should be worded differently rather than copied.
Can I use more than one reason?
You can and it will be worse. PREP is built on a single load-bearing reason; a list of four invites the room to argue with the weakest one.
Is PREP only for speaking?
It is best at speaking but it also makes a good executive summary or one-page recommendation, because both want the answer first. What it will not do is organise a long document.
How is PREP different from SOAR or STAR?
By the question. PREP answers "what do you think and why?". SOAR and STAR answer "tell me about a time when…" — a story, not an argument.
Generate a PREP Prompt Instantly
Skip the manual template — Frompting applies PREP to your topic in one click.
Try it FreeFramework Details
| Name | PREP |
| Stands for | Point-Reason-Example-Point |
| Domain | Communication & Storytelling |
| Steps | 4 |
| Access | Pro |