Home Framework Library APE

APE

Action-Purpose-Expectation

Three slots. The one to use when the message is short and the clock is running.

Communication & Storytelling Free Framework 3 Steps

What is APE?

APE has three slots: Action, Purpose and Expectation. It is the smallest framework that still improves a prompt, built for the messages you write twenty times a week and think about for thirty seconds.

The interesting slot is Purpose, and it is the one no other short framework has. Purpose asks why this message exists — not what it says. "Request five days off" and "get approval before sprint planning so nobody has to chase me for cover" produce different emails from the same facts: the second one volunteers the cover plan, because the purpose demanded it. Stating why is how you get a model to include the thing you would have forgotten.

Best used for
Emails task assignments internal communications team updates

Where APE Came From

A deliberately small acronym

APE has no documented inventor and no history before prompting — it is one of several three-slot structures that appeared once people noticed that most everyday prompts fail for the same three reasons: no stated deliverable, no stated reason, no stated finish line. Any page claiming a specific origin story for it is inventing one.

Why three and not six

The design trade is explicit. A six-slot framework produces better prompts and gets used less, because filling six fields for a two-line email feels absurd — and it is. APE is sized to be used on the messages nobody would otherwise structure at all. A framework that is skipped scores zero however good it is on paper.

What it is really competing with

Not CO-STAR. APE competes with typing the request straight into the box, which is what happens to internal email, Slack messages and meeting agendas. Judged against that baseline rather than against a larger framework, three slots is a large improvement for almost no effort.

The 3 Slots, One at a Time

Each slot is a decision. Leave it out and the model still makes it — just without you.

A
Action
The deliverable, as a verb plus an artefact.

Action is the same slot RACE has, and it fails the same way: naming a topic rather than an artefact. "Something about the schedule change" could be an email, a Slack post or a meeting agenda, and the model will pick one without telling you.

Weak Write something about time off.
Strong Write an email to my manager requesting five working days off, 10-14 March.
P
Purpose
Why this message exists and what it must achieve.

The slot unique to APE, and the reason it beats other three-slot frameworks. Purpose is not the topic restated — it is the outcome. It routinely makes the model include something you did not ask for and did want, because the purpose implied it.

Weak To ask for holiday.
Strong To get approval before sprint planning on the 3rd, so nobody has to chase me for cover arrangements afterwards.
E
Expectation
Length, shape, tone and what must not appear — all of it.

With only three slots, Expectation carries everything the other two do not. That is a lot, and it is where APE prompts are won or lost. Treat it as a checklist: how long, what shape, who reads it, what to leave out.

Weak Keep it short and professional.
Strong Under 120 words in three short paragraphs — the request with dates, the cover plan, then the confirmation. My manager is direct and reads on a phone, so lead with the dates. No apologising, no "I hope this finds you well". Do not invent a reason for the leave.

One Task, Before and After

The task: Ask a manager for five days off. 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.

26 Without APE · weak
Write an email asking for time off.

Seven words. You will get a polite, padded, three-paragraph email that apologises twice and omits the cover plan.

59 With APE · workable
Action: Write an email to my manager requesting five working days off, 10-14 March.

Purpose: To get approval before sprint planning on the 3rd, so nobody has to chase me for cover arrangements afterwards.

Expectation: Under 120 words in three short paragraphs - the request with dates, the cover plan, then the confirmation. My manager is direct and reads on a phone, so lead with the dates rather than context. Keep it plain: no apologising, no long preamble, no 'I hope this finds you well'. Name Priya as cover for the billing migration and Tom for the on-call rotation, and confirm the release notes will be finished before I go. Do not invent a reason for the leave and do not offer to be reachable.

One hundred and twenty-four words of prompt for a hundred-word email. That ratio is the honest catch with APE, and it is discussed below.

Why 59 is a good score for APE, and why chasing higher is a mistake

Fifty-nine sits in the "workable" band, well below the 86 the four-slot RACE example reaches. That gap is structural, not a failure of the example. With three slots there is simply nowhere to put the things the scorer rewards most:

Role0 / 8

APE has no persona slot at all. For an internal email that is correct — you are writing as yourself, and telling a model to be a "senior communications professional" would make the email worse.

Examples0 / 10

Nothing invites a sample. You can force one into Expectation, but at that point the prompt is longer than the email.

Reasoning0 / 8

No slot asks the model to think first, and a hundred-word leave request does not want deliberation. Points you should not want.

This is the clearest case on any of these pages that the score is not the goal. A 59 that took forty seconds to write and produced a usable email on the first try has done its job. Pushing the same prompt to 85 means adding a role, an example and a reasoning instruction — roughly tripling the effort to write a note your manager will read in eight seconds. If a task genuinely deserves that, you should not be using APE.

Copy-Paste Prompt Template

Replace the bracketed placeholders with your specific details.

Action: [One deliverable — a verb plus an artefact, with the specifics: dates, names, numbers]

Purpose: [What must be true after this is read. Not the topic restated — the outcome]

Expectation: [Length, shape, who reads it and how they read, and what must not appear]

When APE Fits — and When It Does Not

Reach for it
  • Internal email, Slack messages, meeting agendas, handover notes — the daily traffic.
  • Anything where you would otherwise type one line into the box and accept what came back.
  • Requests, where saying why you are asking changes what the message needs to contain.
  • Learning your first framework. Three slots is the version people actually keep using.
Use something else
  • Published or customer-facing writing. No tone slot, no audience slot. Use CO-STAR.
  • Analysis and decisions — nothing asks the model to reason. Use ReAct or SCQA.
  • Anything long. Past roughly 400 words of output, Expectation cannot carry the whole brief.
  • Work where a persona genuinely changes the answer. Use RACE or RTF instead.

10 Ready-Made APE Prompts

Every prompt below was produced by the Frompting generator with APE 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.

Email: requesting time off 82
You are an email drafting assistant.
Your task is to compose a concise, professional request for time off addressed to the user’s manager.

The email should first state the specific dates and amount of leave being requested, then explain briefly why the time off is needed, and finally indicate the desired outcome (e.g., approval, confirmation of coverage, or next steps).

Write the email in a polite, business‑formal tone, keeping the total length between 150 and 200 words. Ensure the message is clear, includes a courteous opening and closing, and uses proper email formatting (subject line, greeting, body, sign‑off).

[MANAGER_NAME]: provide the manager’s name for the greeting.
[LEAVE_DATES]: specify the start and end dates (or number of days) of the requested time off.
[REASON_FOR_LEAVE]: give a brief reason for the request (optional, can be generic if not disclosed).

If any of the placeholders above are unknown, state your assumption and proceed, or ask up to three clarifying questions before drafting.

Quality criteria:
1. Clarity – the request, reason, and expected response are unmistakable.
2. Professional tone – respectful language and appropriate email etiquette.
3. Brevity – stays within the 150–200 word limit without unnecessary detail.

Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader.
218 words · scores 82/100 solid
Meeting agenda: weekly team sync 77
You are a professional meeting facilitator tasked with drafting a concise agenda for a weekly team sync.

Create a clear, actionable agenda that guides the meeting flow, ensures all participants know why each item matters, and defines the desired outcomes for each discussion point.

The agenda should be formatted as a markdown list with time allocations, brief descriptions, and expected results for each item. Keep the total length to approximately 150–200 words.

Include placeholders for any details not provided:
[MEETING_DURATION]: total length of the sync (e.g., 30 min, 1 hour)
[PARTICIPANTS]: list of team members or roles attending
[KEY_TOPICS]: specific subjects or projects to cover
[OUTCOME_EXPECTATIONS]: what the team should achieve by the end of each item (e.g., decisions, action items, updates)

If any of these placeholders are unknown, state your assumptions clearly and ask up to three clarifying questions before finalizing the agenda.

Quality criteria:
- Logical sequence that flows from updates to decisions.
- Time allocations that fit within the overall meeting duration.
- Each agenda item includes a concise purpose and a measurable expected outcome.

Do not include any extraneous commentary beyond the agenda itself.
190 words · scores 77/100 solid
Slack message: a process change 89
You are a concise internal communications specialist.
Your task is to craft a Slack announcement that informs the team about a change to an existing process.

The message should:
1. Clearly state what the new process requires from the team.
2. Explain why this change is being made and why it matters.
3. Describe the result that is expected once the change is adopted.

Write the announcement for **[AUDIENCE: e.g., the product development team, all staff, etc.]** and reference the specific process **[PROCESS: e.g., code review workflow, expense reporting, etc.]** that is being updated. Include any relevant deadline **[DEADLINE: e.g., “effective from March 15”]** if applicable.

The output must be a single Slack‑compatible message of 120 words or fewer, using a friendly yet professional tone.

Quality criteria:
- The three parts are logically ordered and easy to scan.
- Language is clear, action‑oriented, and free of unnecessary jargon.
- The call to action is explicit and includes any required next steps.

Exclude any unrelated background information or lengthy explanations.

If any of the placeholders above are unknown, state your assumption and ask up to three clarifying questions before finalizing the message.
191 words · scores 89/100 strong
Follow-up email after an interview 84
You are a professional email writer who crafts concise, courteous follow‑up messages after job interviews.

Write a follow‑up email that:

- Begins by thanking the interviewer for the opportunity and referencing the interview on [INTERVIEW_DATE: date of interview].
- Clearly restates the position you discussed, [POSITION_TITLE: job title], and expresses continued enthusiasm for contributing to [COMPANY_NAME: company].
- Highlights one specific topic or project mentioned during the interview that aligns with your skills, such as [KEY_TOPIC: brief description of the discussed topic].
- Politely asks about the next steps in the hiring process and offers to provide any additional information needed.

The email should be addressed to [INTERVIEWER_NAME: name of the interviewer] and signed with your full name and contact information. Keep the total length between 120 and 180 words.

Ensure the tone is professional yet warm, avoid overly formal language, and use clear, direct sentences.

If any of the placeholders above are unknown, state your assumption for each and ask up to three clarifying questions before finalizing the email.

Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader.
199 words · scores 84/100 solid
Reminder: an unpaid invoice 81
You are an email copywriter tasked with drafting a concise reminder about an unpaid invoice.

Write a professional email that (1) clearly states the required payment action, (2) explains why timely payment is important, and (3) specifies the expected outcome (e.g., payment by a certain date or a reply confirming receipt).

The email should be addressed to **[RECIPIENT NAME]:** the name of the person or organization receiving the reminder. Include the invoice details: **[INVOICE NUMBER]:** reference identifier, **[INVOICE AMOUNT]:** amount due, and **[DUE DATE]:** original due date. Sign the message with **[SENDER NAME/COMPANY]:** the sender’s name or business.

Target length: 150–200 words.

Quality criteria:
- Clear, single‑sentence call to action.
- Brief justification for prompt payment.
- Polite yet firm tone appropriate for **[FORMALITY LEVEL]:** (formal or semi‑formal).

If any of the placeholders above are unknown, state your assumption and proceed, or ask up to three clarifying questions before finalizing the email.

Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader.
177 words · scores 81/100 solid
Out-of-office auto reply 82
You are an expert copywriter specializing in professional email communications.

Create a concise out‑of‑office auto‑reply message that will be set in an email client.

[RECIPIENT TYPE]: specify who will receive this reply (e.g., clients, internal colleagues, general contacts).
[ABSENCE DATES]: provide the start and end dates of the absence.
[ALTERNATE CONTACT]: give the name, role, and email of a person who can be contacted in your stead.

The reply should (1) clearly state the period you are unavailable, (2) explain briefly why you are away, and (3) tell the sender what to expect regarding response timing or who to contact for urgent matters.

Write the message in a friendly yet professional tone, keeping it under 120 words. Ensure the text is ready to copy‑paste into an email auto‑reply field without additional formatting.

Do not include any disclaimer unrelated to the out‑of‑office purpose. If any of the placeholders above are unknown, state the assumption you are making or ask up to three clarifying questions before finalizing the reply.

Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader.
195 words · scores 82/100 solid
Thank you email after a client meeting 75
You are an expert business communication writer.
Write a concise thank-you email to a client following a recent meeting.

The email should:
- Begin with a brief opening that thanks the client by name and references the meeting date.
- Summarize the main points discussed, highlighting any key decisions or topics.
- Express appreciation for the client’s time and input, and convey enthusiasm for the partnership.
- Clearly outline the next steps you will take or expect from the client, including any agreed-upon deadlines or deliverables.
- Close with a courteous sign-off that includes your full name and title.

The email is intended for a professional business audience and must be 445-585 words in length.

Quality criteria:
1. Professional and warm tone, free of jargon.
2. Clear, logical flow that makes the purpose and next actions unmistakable.
3. No sales-heavy language; focus on gratitude and collaboration.

Assume any missing details are typical for a standard client meeting, but first state those assumptions and ask up to three clarifying questions (e.g., client name, specific topics covered, agreed next steps) before finalizing the email.
181 words · scores 75/100 solid
Internal memo: a policy update 80
You are an internal communications specialist tasked with drafting a concise internal memo announcing a policy update.

The memo should be written for **[AUDIENCE: specify the department, team, or whole organization that will receive the memo]** and must clearly convey:

1. **What action is required** – the specific change or behavior employees need to adopt.
2. **Why it matters** – the rationale behind the update and its importance to the organization.
3. **What outcome is expected** – the desired result or compliance target, including any relevant deadlines.

The memo must be no more than **300 words**, formatted as plain text with a brief heading, three short paragraphs (one for each element above), and a closing line inviting questions to **[CONTACT: name and contact method for follow‑up]**.

Quality criteria:
- Clear, actionable language with no ambiguity.
- Persuasive justification that aligns the update with organizational goals.
- Professional tone appropriate for internal corporate communication.

Exclude any unrelated background information or unrelated policy details.

If any of the placeholders are unknown, state your assumption and proceed, or ask up to three clarifying questions before drafting the memo.
179 words · scores 80/100 solid
Declining a meeting invitation 87
You are a professional communications specialist.
Your task is to craft a concise, polite message that declines a meeting invitation.

The message should:
- Clearly state the decision to decline and propose an alternative if appropriate.
- Explain briefly why the decline is necessary, emphasizing respect for the inviter’s time.
- Indicate any next steps or expectations, such as a follow-up email or a suggestion to reschedule.

Write the message for a [RECIPIENT ROLE: e.g., manager, colleague, client] who sent the invitation on [INVITATION DATE: e.g., March 3, 2024] for a meeting scheduled on [MEETING DATE/TIME: e.g., April 10 at 2 PM]. The sender of the decline is [YOUR NAME/ROLE: e.g., Alex Rivera, Project Lead]. Keep the tone courteous and professional, and limit the total length to under 540 words.

Quality criteria:
1. Polite and respectful tone throughout.
2. Clear articulation of the decline, reason, and any suggested next action.
3. No ambiguous language; each sentence should convey a single, precise idea.

Exclude any mention of the APE framework or its components. If any of the placeholders above are unknown, state your assumption and proceed, or ask up to three clarifying questions before drafting the final message.

Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader.
220 words · scores 87/100 strong
Handover note before annual leave 88
You are a professional internal communications specialist.
Your task is to draft a concise handover note that an employee can send to their team before taking annual leave.

The note should clearly state:
- What specific responsibilities, projects, or tasks the employee will be handing over, including any critical deadlines or deliverables that fall during the leave period.
- Why these handovers are important for maintaining workflow continuity and meeting team objectives.
- What the employee expects from the recipients (e.g., who will cover each item, any required approvals, and how progress should be reported).

The note is intended for: [RECIPIENT: specify the team, manager, or individual who will receive the handover].

The employee will be away from: [START DATE: when leave begins] to [END DATE: when leave ends].

Output format: a brief email-style message of 340-450 words, using short paragraphs and bullet points for the handover items.

Quality criteria:
1. Clear and actionable items with assigned owners.
2. Reasoning that connects each handover to its impact on team goals.
3. Explicit expectations for follow-up and reporting.

Exclude any unrelated personal details or unrelated project information.

If any of the placeholders above are unknown, state your assumption and proceed, or ask up to three clarifying questions before finalizing the note.
208 words · scores 88/100 strong

Scores range from 75 to 89. 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.

APE vs the Alternatives

CO-STAR Context, Objective, Style, Tone, Audience, Response

The upgrade when the message leaves the building. Twice the slots, twice the effort, and a materially higher ceiling — Style, Tone and Audience are exactly what APE lacks.

RACE Role, Action, Context, Expectation

Swap Purpose for Role and Context when perspective matters more than reason — a technical document rather than a request.

RTF Role, Task, Format

The other three-slot option. Choose RTF when the output shape is the hard part, and APE when the reason for writing is.

TAG Task, Audience, Guardrails

Three slots again, weighted differently. TAG trades Purpose for an explicit audience and an explicit list of what to avoid.

PREP Point, Reason, Example, Point

Not a prompt framework so much as a structure for the message itself. Useful inside APE’s Expectation slot when you want the email to argue rather than inform.

Five Ways People Get APE Wrong

1
Restating the Action as the Purpose

"Action: ask for time off. Purpose: to ask for time off." Both slots are now one slot. Purpose is the outcome you need — approval before a specific date, or nobody chasing you afterwards.

2
Leaving Expectation as "short and professional"

With three slots, Expectation is carrying length, shape, tone and exclusions at once. Two adjectives cannot do that. Give it a word count and a shape.

3
Using APE on work that deserves CO-STAR

The framework is fast because it is small. Reaching for it on a customer announcement because it is quicker produces something that reads as though it was written quickly.

4
Forgetting the reader inside Expectation

APE has no audience slot, so if the reader matters you must say so in Expectation. "My manager is direct and reads on a phone" changes the whole message.

5
Writing a prompt longer than the output

A hundred and twenty words of prompt for a hundred-word email is defensible once, as a template you reuse. Doing it fresh every time is slower than writing the email.

APE Questions

What does APE stand for?

Action, Purpose, Expectation. Three slots: what to produce, why it exists, and what finished looks like.

Is APE too simple to be useful?

It is the smallest framework that still helps, which is the point. Judged against the real alternative — typing one line into the box — three slots is a large gain for almost no effort. Judged against CO-STAR it looks thin, but nobody fills six fields for a Slack message.

What is the difference between Purpose and Action?

Action is what to produce. Purpose is what has to be true afterwards. "Write a reminder about the unpaid invoice" is the Action; "so it gets paid this week without damaging the relationship" is the Purpose, and it is what stops the model writing something curt.

Why does the worked example only score 59?

Because APE has no slot for a role, an example or a reasoning instruction — 26 of the 100 available points are structurally out of reach. For a short internal email that is the right trade, and the section above explains why chasing a higher number here makes the prompt worse rather than better.

Can I add a fourth slot?

Then you have RACE or TAG, both of which are already tuned four- and three-slot structures. Use one of those rather than growing APE, or you end up with a private framework nobody else on your team knows.

Generate a APE Prompt Instantly

Skip the manual template — Frompting applies APE to your topic in one click.

Try it Free

Framework Details

Name APE
Stands for Action-Purpose-Expectation
Domain Communication & Storytelling
Steps 3
Access Free
Steps at a glance
A Action
P Purpose
E Expectation