ERA
Three slots, and the third one decides the order of the first two.
What is ERA?
ERA is three slots: Execution, Results, Audience. It is the shortest reporting framework here, built for the update somebody reads on a phone between meetings — and its one structural idea is that the third slot, which looks like an afterthought, is actually the instruction for the other two.
Status updates are almost always ordered by effort. The writer lists what they did in the order they did it, because that is how the week is stored in their head, and the item that changes what somebody else has to do ends up third. On a phone, third is unread. The Audience slot exists to reorder the update: once you have written down who reads this and what they will do with it, the lead is usually not what took the most work. A measurement error that invalidates three months of reported figures is a smaller piece of work than the feature that shipped, and it is the one that belongs first.
Where ERA Came From
A modern reporting convention with no author of record
ERA has no documented inventor. It is a compression of standard status-reporting practice into three slots, and belongs to the same undocumented pool as TAG, SCOPE and TOAST. Note the acronym is heavily taken elsewhere — ERA is a statistic in baseball, an equal rights amendment, and a geological division — so searching the three letters is unproductive.
It is deliberately smaller than PPP
The obvious comparison is PPP, and the difference is scope rather than quality. PPP has three slots too, but one of them is Past — a comparison against what you committed to — and another is a Proposal, an explicit ask. ERA has neither. It is for the update where nothing needs deciding and somebody just has to know what happened, which is most weeks.
Why Audience is a slot and not a preamble
Because it changes the output rather than framing it. Every other element of a short update — what leads, what gets cut, how much explanation a number needs — follows from who is reading and what they will do next. Making it a required slot is what stops the writer defaulting to chronology, which is the failure mode of every status update ever sent.
The 3 Slots, One at a Time
Each slot is a decision. Leave it out and the model still makes it — just without you.
Facts, briefly, and with the omissions included. A list of completed items with no mention of the thing that did not start is technically true and functionally misleading, and it is the commonest small dishonesty in status reporting. Naming the unstarted item costs one clause and buys the rest of the update its credibility.
Not activity restated as achievement. If a result is not yet significant, say so in the same sentence as the number, because a figure quoted without its caveat will be repeated without it. And include the results you did not want: a fix that reveals earlier figures were wrong is a result, and usually the most important one.
The slot that governs the other two. Name them, name what they already know so you can skip it, and name the decision this feeds. Then let that decide the lead. A director who needs to know whether a test can be called and whether an earlier decision was built on bad numbers should not have to reach paragraph three for the second one.
One Task, Before and After
The task: A 150-word project update read on a phone between meetings. 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 a quick update on the project this week.
Eight words. You get three chronological paragraphs about what was worked on, with the measurement error that invalidates three months of figures mentioned last.
Write a short project update using Execution, Results, Audience - a deliberately compressed format for people who will read it on a phone between meetings. Execution - what was actually done this week: the new checkout flow went live to 50% of traffic on Tuesday; the analytics fix that was blocking measurement shipped Thursday; the third planned item, the saved-cards work, did not start. Results - what happened as a result: checkout completion in the treated group is 71.2% against 68.9% in control, on 4,100 sessions, which is not yet significant. The analytics fix revealed that 6% of sessions were being double-counted, so all prior conversion figures are slightly overstated. Audience - this goes to a product director and two engineering leads who already know the project and will not read past the first screen. They care about whether the test can be called and whether the double-counting changes any earlier decision. Write the update as a short email of 150 to 180 words - two short paragraphs and one line, no headings and no bullets. Lead with the double-counting finding rather than the test result, because it is the item that changes what somebody else has to do. Work out the lead before you write: a result that is not yet significant is less actionable than a measurement error that invalidates earlier numbers, and reports ordered by effort rather than by consequence are why updates stop being read. For example, the opening should read like this: ``` The analytics fix shipped Thursday and immediately showed 6% of sessions were double-counted, so every conversion figure we have quoted since January is slightly high. ``` Ensure the update states plainly that the test cannot yet be called, and prioritise what changes someone else's decision over what took the most effort. Do not use status labels, do not describe the week as productive, and do not add any item that is not in the three sections above.
Ninety-two. The lead is the whole decision: a not-yet-significant test result is less actionable than a double-counting bug that makes every earlier number wrong.
Ninety-two, and nothing checks whether the right thing led
One check is out of reach, and the single decision that makes a short update useful is unmeasured:
No persona slot, and none wanted — this update is from you to people who will ask you about it on Monday. A persona writes claims you did not make.
The whole framework, and completely invisible. An update that leads with the feature that shipped scores exactly as well as one that leads with the measurement error invalidating three months of figures. On a phone, only the first paragraph is read, so this is the only decision that reliably matters.
A list of three completed items reads as complete. So does a list of two completed items and one that did not start. Only the second is true, and no rubric knows what you left out.
The test worth applying to any short update: what in here changes what somebody else has to do? That is the lead, regardless of how much work it represented — and ordering by effort instead is why status updates stop being read.
Copy-Paste Prompt Template
Replace the bracketed placeholders with your specific details.
Audience: [WRITE THIS FIRST even though it is last in the acronym — who reads it, what they already know, and what decision this feeds] Execution: [what was actually done — INCLUDING what did not happen] Results: [what followed, with the caveats in the same sentence as the numbers. Include results you did not want] [Lead with whatever changes what somebody ELSE has to do — not with what took the most effort] [150-200 words, no headings, no bullets, no status labels. It is read on a phone]
When ERA Fits — and When It Does Not
- Weekly updates where nothing needs deciding and people just need to know.
- Anything read on a phone between meetings.
- Fast-moving projects where a full report every week would not be read.
- Updates to people who already know the context and need only the delta.
- Quick summaries after a conference, a research round or a short piece of work.
- Updates where you need a decision. Use PPP, which has a Proposal slot.
- Reporting against commitments — ERA has no Past slot, so there is no trend.
- Bad news that needs handling carefully. Use SCIPAB or PPP; three slots is too blunt.
- Formal reports and post-mortems. Use 5W1H.
- Audiences who do not already know the project, since ERA assumes context.
10 Ready-Made ERA Prompts
Every prompt below was produced by the Frompting generator with ERA selected — not written by hand for this page. Each is scored by our prompt checker; the median is 80/100. Click one to open it, then copy.
A two-paragraph website project update 69
You are a concise project‑status writer. Write a brief update about a website project in exactly two paragraphs. In the first paragraph, describe the recent work that was completed, the tasks or milestones that were finished, and any notable actions taken. In the second paragraph, summarize the outcomes of that work, include any measurable results or impacts, and indicate who will benefit from or needs to know this information. [PROJECT_NAME: the name or identifier of the website project] [RECENT_MILESTONES: specific tasks or milestones completed in the last reporting period] [KEY_RESULTS: any metrics, improvements, or deliverables achieved] [PRIMARY_AUDIENCE: the stakeholder group that will read this update] If any of the placeholders are unknown, state your assumption clearly and ask up to three clarifying questions before drafting the update. Deliver the update in plain text, two paragraphs, each no longer than 120 words. Ensure the writing is clear, professional, and focused on the facts described. Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader.
A sprint summary for the wider team 75
You are a concise sprint‑summary writer. First, gather the essential details of what was done during the sprint: the sprint name or identifier, the start and end dates, the primary objectives, and the key activities completed. Next, translate those details into clear outcomes: list the main deliverables finished, any measurable results or metrics achieved, and note any blockers or incomplete items that need attention. Finally, tailor the summary for its readers: specify the intended audience (e.g., product team, leadership, cross‑functional stakeholders) and highlight the information most relevant to them. Produce a brief sprint summary of **150–200 words** that: - Presents the execution facts in a logical, chronological order. - Summarizes results with concrete outcomes and any quantitative indicators. - Addresses the audience’s interests, using a tone appropriate for the specified readers. **Quality criteria:** clarity, brevity, and relevance to the audience. **Boundary:** avoid technical jargon and keep the language straightforward. If any of the required details are unknown, state your assumptions explicitly and ask up to three clarifying questions before drafting the summary.
A brief update on a hiring round 80
You are a concise business communicator tasked with drafting a brief update on a hiring round. The update should be a single paragraph of 120–150 words, written in a professional yet approachable tone. It must clearly convey: 1. What actions have been taken and what is currently being executed in the hiring process. 2. The outcomes achieved so far, including any metrics or notable developments. 3. Who the update is intended for and why it matters to them. The audience for this update is: [AUDIENCE: specify the role or group, e.g., senior leadership, investors, hiring team]. Include any known details such as the company name, the position(s) being filled, and the current stage of the hiring round. If these are unknown, insert placeholders: [COMPANY], [POSITION(S)], [CURRENT STAGE]. Quality criteria: - Clear, factual language with no jargon. - Logical flow that naturally moves from actions to results to relevance for the audience. - No promotional language or unverified claims. Exclude any internal process details that are not relevant to the external audience. If any required information is missing, state your assumptions explicitly and ask up to three clarifying questions before completing the update.
A short progress note for a client 72
You are a professional progress‑note writer. Create a concise progress note that: 1. Summarizes the actions taken or work performed for the client. 2. Describes the outcomes or results of those actions, including any measurable impact or key observations. 3. Identifies who will read the note and what they need to know from it. The note should be written for **[AUDIENCE: role or stakeholder who will receive the note]**, be no more than **150 words**, and use a clear, professional tone. **Quality criteria**: - Include the client’s name (**[CLIENT NAME]**) and the date of the update (**[DATE]**). - Highlight the most important result(s) in a way that the audience can quickly grasp the significance. - Keep language direct and free of unnecessary jargon. **Boundary**: Do not add background information unrelated to the current update or any promotional content. If any of the required details are unknown, state your assumptions clearly and ask up to three brief clarifying questions before drafting the note.
A conference summary for colleagues 66
You are a concise conference summarizer. First, describe the conference you attended: include the conference name, dates, location, and the main activities or sessions you participated in. Next, highlight the key outcomes: summarize the most important insights, announcements, or takeaways, and note any actionable items or implications for your team. Finally, tailor the summary for your colleagues: consider their roles and interests, and frame the information in a way that is immediately useful for them. Write the summary in plain prose of **150–200 words**, using short paragraphs and bullet points only if they improve clarity. Quality criteria: - Accurate and specific details about the event. - Clear emphasis on actionable insights. - Tone that is professional yet approachable for internal colleagues. If any essential details (e.g., conference name, specific sessions, or colleague roles) are unknown, state your assumptions explicitly or ask up to three brief clarifying questions before completing the summary.
A brief budget review update 92
You are a concise business communicator. Write a brief update on a recent budget review. The update should: - Summarize the actions taken and the process followed in the review. - Highlight the main findings, any variances, and the implications for the organization. - Address the intended readers, focusing on what they need to know and any required next steps. The update is for [AUDIENCE: specify the role or group, e.g., senior management, finance team, project stakeholders]. Include any key numbers or percentages only if you have them; otherwise note that the figures are pending. Deliver the update in plain text, no more than 180 words. Quality criteria: 1. Clear and logical flow from actions to findings to reader relevance. 2. Use specific, concrete details where available; avoid vague language. 3. Maintain a professional tone appropriate for the audience. Do not include unrelated background information or detailed methodological explanations. If any essential details (such as exact budget figures, review period, or audience specifics) are missing, state your assumptions explicitly and ask up to three clarifying questions before finalizing the update. 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.
A customer research round summary 82
You are a concise business analyst tasked with drafting a short summary of a recent customer research round. First, describe the research activities you performed, including methods (e.g., surveys, interviews, focus groups) and any notable constraints or timeline details. Next, present the key findings, highlighting the most significant insights, any surprising results, and the implications for the business. Finally, tailor the language and emphasis for the intended reader, ensuring the tone and level of detail match the audience’s needs. The summary should be no more than 150 words, written in clear, professional prose. Quality criteria: - Accurately reflects the described research methods and findings. - Prioritizes the most impactful insights. - Uses language appropriate for the specified audience. If any of the following are unclear, state your assumptions and ask up to three brief clarifying questions: the specific research methods used, the most important insights to highlight, and the primary audience for the summary. [RESEARCH_METHODS]: list the methods employed in the round. [KEY_INSIGHTS]: the top findings to emphasize. [AUDIENCE_TYPE]: who will read this summary (e.g., executives, product team, marketing). 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.
A compliance audit update 91
You are a concise business communicator tasked with drafting a brief update on a compliance audit. Prepare a short written update (≈150 words) that clearly conveys: 1. What actions were taken to conduct the audit, including any methods or tools used. 2. The main findings and any immediate implications or next steps. 3. Who the update is intended for and why it matters to them. The update should be clear, factual, and written in a professional tone suitable for an executive audience. Ensure it is free of jargon, uses plain language, and highlights any critical issues without unnecessary detail. [AUDIT SCOPE]: specify the area or process being audited. [AUDIT DATE]: indicate when the audit was performed. [RECIPIENT ROLE]: define the primary audience (e.g., senior manager, compliance officer). [KEY FINDINGS]: list the most important results or issues discovered. If any of the above information is unknown, state your assumption and proceed, or ask up to three clarifying questions before completing the update. Do not include any background information beyond what is requested, and keep the total length to roughly 375-495 words. 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.
A note on a partnership discussion 87
You are a concise business communication specialist. Your task is to draft a brief note summarizing a partnership discussion. First, outline the essential elements to include: the purpose of the meeting, the main topics covered, any agreed next steps, and any key concerns or benefits highlighted. Next, produce the note in a clear, professional tone, limited to **[WORD COUNT: 150‑200]** words, formatted as a single paragraph followed by a brief bullet list of action items (no more than three bullets). Finally, tailor the language for **[AUDIENCE: e.g., senior executive, potential partner, internal team]**, ensuring the message is appropriate for their level of familiarity with the partnership and decision‑making authority. **Quality criteria:** - Accuracy: reflect the discussion facts without adding unverified details. - Clarity: use straightforward language and avoid jargon. - Relevance: focus on points that matter to the specified audience. **Boundary:** Do not include speculative future scenarios or unrelated background information. If any critical details (e.g., names of parties, specific agreements, tone preferences) are missing, state your assumptions clearly and ask up to three clarifying questions before finalizing the note.
A campaign's first-week update 78
You are a concise campaign analyst. Write a brief update covering the first week of the campaign, organized as follows: 1. Describe the actions taken and tactics employed during the initial week. 2. Summarize the key performance results observed so far. 3. Tailor the tone and focus of the update for the intended readership. [CAMPAIGN_NAME: specify the name or brief description of the campaign] [PRIMARY_GOALS: list the main objectives the campaign aims to achieve] [KEY_METRICS: identify the most important metrics to report (e.g., impressions, clicks, conversions, engagement rate)] [INTENDED_AUDIENCE: define who will read this update (e.g., senior leadership, marketing team, client)] Produce the update in 120–150 words, using clear, professional language. Ensure the information is accurate, the tone matches the intended audience, and the key metrics are highlighted prominently. Do not include any filler or unrelated details. 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.
Scores range from 66 to 92. 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.
ERA vs the Alternatives
The bigger sibling and usually the better choice when something needs deciding. PPP compares against commitments and ends in an ask; ERA does neither and is shorter for it.
For when the update is really a request. SCIPAB opens a decision; ERA closes a week.
For the formal record. 5W1H is a completeness checklist for a document that will be scrutinised; ERA is three paragraphs on a phone.
The same compression instinct applied to your own achievements rather than a project's state.
For saying it out loud. If the update is a two-minute item in a meeting rather than a message, PREP handles it better.
Five Ways People Get ERA Wrong
The defining ERA failure, and the reason status updates stop being read. The item that took the most work is rarely the item that changes what somebody else does. Write the Audience slot first and let it decide the lead.
A list of completed items with no mention of the unstarted one is technically true and reads as complete. One clause fixes it and buys the whole update its credibility.
A result quoted without "not yet significant" will be repeated without it, and by the time it reaches a decision nobody remembers the qualifier existed.
"Shipped the analytics fix" is Execution. "The fix revealed 6% double-counting" is a Result. Confusing them produces an update that is entirely about what you did and says nothing about what is true.
Amber tells the reader nothing they can act on and is usually chosen to avoid committing to a judgement. Say the judgement.
There is no Proposal slot. If a decision is required, ERA will bury the ask in a sentence and you will be writing the same update again next week.
ERA Questions
What does ERA stand for?
Execution, Results, Audience — a three-slot structure for a short status update.
Why is Audience one of the slots?
Because it decides the other two. Once you have written down who reads this and what they will do with it, the correct lead usually turns out not to be the thing that took the most work — which is what the framework exists to prevent.
How is ERA different from PPP?
PPP has a Past slot, which compares against what you committed to, and a Proposal, which is an explicit ask. ERA has neither. Use ERA when nothing needs deciding and PPP when something does.
How long should an ERA update be?
Short enough to read on one phone screen — 150 to 200 words is usually right. If it is longer, you probably needed PPP or a proper report.
Should I include things that did not get done?
Yes. A list of completed items with the unstarted one omitted is technically true and reads as complete, which is the small dishonesty that eventually costs an update its credibility.
What should lead the update?
Whatever changes what somebody else has to do. That is often a small finding rather than a large delivery — and on a phone, the first paragraph is the only one you can count on.
Generate a ERA Prompt Instantly
Skip the manual template — Frompting applies ERA to your topic in one click.
Try it FreeFramework Details
| Name | ERA |
| Stands for | Execution-Results-Audience |
| Domain | Communication & Storytelling |
| Steps | 3 |
| Access | Pro |