Quick answer
These AI workflow before after examples all turn on one fix: rewrite your one-line request as four lines — who the AI is, what the finished thing is, which facts it may use, and what shape the answer comes back in. Same tool, same document, better output.
The AI workflow before after examples in this guide all start the same way. Someone types one line into a chat box, gets back something that reads fine and helps nobody, and quietly decides the tool is overrated. The tool was not the problem. The one line was.
A one-line ask is a request. What the model needs is a brief. The gap between the two is four short lines you already know how to write, because you write them every time you hand work to a colleague:
- Who is doing this — the job title and seniority the answer should sound like.
- What the finished thing is — a deliverable, not a topic.
- Which facts are allowed — the text you pasted, and nothing invented around it.
- What shape it comes back in — table, three sections, five bullets, 200 words.
Below are ten desk tasks, each shown twice: the ask most people actually type, and the rewrite that produces something sendable. Steal them directly. The pattern underneath is more useful than any single one of them.
One thing to notice as you read these AI workflow before after examples: the after column is rarely longer than three sentences. This is not about writing more. It is about writing the three or four facts the model cannot guess.
Will this work for you?
Why one-line prompts fail at work
A one-line prompt is not wrong, it is under-specified. The model has to guess your role, your reader, your format, and which facts count — and it guesses the average of everything it has ever seen. The average of every meeting summary on the internet is a neat recap that assigns nothing to nobody.
That is also why the same prompt gives you a different answer on Tuesday. You never pinned down the variables, so they float. If you have hit that already, the AI Execution Loop is the wider system this article sits inside — Think, Structure, Execute, Refine. What follows is the Structure step, done ten times on real work.
The same task, asked two ways. Only the input changed.
Most professionals reach for a longer prompt when the answer disappoints. Length is not the fix. A 200-word request that still never names the reader produces the same fog, slower.
There is a second cost nobody counts. The bad answer is not free — you read it, judge it, and then spend ten minutes rewriting it into the thing you wanted. Across a week that is most of an afternoon spent editing drafts you should never have received.
The Four-Line Rewrite, explained
The Four-Line Rewrite is the approach we teach at PromptPeakAI for turning an ask you already typed into a brief the model can work from: rewrite it as four lines — who the AI is, what the finished thing is, which facts it may use, and what shape the answer takes. It is the same four ideas as Role, Goal, Context and Format, applied as a repair job rather than a blank page.
Four lines, written in this order, then the source text pasted underneath.
Name the role, not the tool
Write the job title of the person whose desk this work normally lands on. “You are a senior operations manager” changes vocabulary, assumed knowledge, and what the answer bothers to explain. Seniority matters more than industry — a director writes shorter than an analyst. There is more on this in the guide to writing a role that lands.
Name the finished thing
“Help with the report” is a topic. “A one-page status update for my director, covering progress, risks and asks” is a deliverable. If you cannot picture the document at the end of the sentence, the model cannot either.
Fence the facts
This is the line almost everyone skips, and it is the one that stops invented numbers. Say where the facts come from and what to do when they run out: use only the text below, and write NOT STATED for anything missing. That single instruction is the difference between a draft you check and a draft you cannot trust. It works because it gives the model a legal answer for a gap — see negative constraints for why banning things outperforms asking nicely.
Name the shape
Columns, word count, number of sections, tone. “A four-column table: task, owner, deadline, dependency” removes every layout decision from the model. The format line is what makes output pasteable instead of re-typeable.
You are a [job title, seniority level]. Produce: [the finished deliverable, in one phrase]. Use only the [transcript / email / table] pasted below. If a detail is missing, write NOT STATED. Do not estimate, assume, or add anything that is not in the text. Format: [exact shape — columns, sections, word count, tone]. --- [paste your source text here]
An AI chat input box with the four-line rewrite template pasted in, source text visible below it, before pressing send.
Crop to the composer area only. Hide the sidebar, chat history, account name and email address.
File: four-line-rewrite-pasted-into-chat.png · Alt: "A four-line rewritten prompt pasted into an AI chat input box"You should now have four lines, in that order, with your real source text pasted underneath the separator.
AI workflow before after examples: meetings and reports
These first three AI workflow before after examples cover the tasks that eat Monday mornings. In each pair, the before is a real thing people type and the after is the same request with the four lines added. Nothing else changed — same tool, same source document, same day.
Example 1: the meeting transcript
Forty minutes of recording, half of it small talk, and you need to know who owes what by Friday.
✕ The ask most people type
"Summarise this meeting transcript and give me the action items."
✓ The Four-Line Rewrite
"You are an operations director. Produce an action table from the transcript below. Use only the transcript; if an owner or date is not spoken aloud, write NOT STATED — never assign one yourself. Format: four columns — action, owner, stated deadline, blocked by."
The fenced facts line is doing the work here. Without it the model helpfully assigns owners based on who talked most. The full walkthrough lives in the guide to turning a transcript into minutes.
Example 2: the weekly status
Your director reads eleven of these before lunch. Yours needs to be skimmable in twenty seconds.
✕ The ask most people type
"Write my weekly status report from these notes."
✓ The Four-Line Rewrite
"You are a delivery manager writing upward to a director who has not followed the detail. Produce a one-page weekly status. Use only the notes below; flag anything unclear as NOT STATED rather than smoothing it over. Format: three headed sections — shipped, at risk, needs a decision — maximum 40 words each, no adjectives."
“Writing upward to a director” is the whole trick. Naming the reader, not just the writer, is what strips the filler out.
Example 3: the executive summary
A sixty-page document landed and someone wants the gist by 2pm. This one is better as a template you keep.
You are a chief of staff summarising for a board that will not read the source. Produce: a five-bullet executive summary, plus one line naming the single decision this document is asking for. Use only the document below. Where the document is vague, say so explicitly rather than resolving it. Write NOT STATED for anything absent. Format: five bullets, maximum 25 words each, plain language, no adjectives. Then one line beginning "Decision required:".
Examples 4 to 7: money, vendors, scope
This is where the fenced-facts line stops being good practice and starts being self-defence. Every task below involves numbers somebody will act on.
Example 4: the budget variance
Actuals versus budget, and a non-finance audience who needs the story, not the spreadsheet.
✕ The ask most people type
"Explain the variances in this budget table and write it up for leadership."
✓ The Four-Line Rewrite
"You are a financial controller writing for department heads with no finance background. Produce a variance note covering every line over 10 percent. Use only the table and the notes column below — do not infer causes that are not written there; write CAUSE NOT STATED instead. Format: one paragraph per line item, cause first, then the number."
“Do not infer causes” is the line that saves you. Plausible-sounding reasons for a spike are exactly what a language model is best at inventing. The longer version is in writing a financial narrative for leadership.
Example 5: the vendor shortlist
Three proposals, twenty pages each, and a comparison that has to survive being questioned.
You are a procurement lead preparing a shortlist paper for a decision meeting. Produce: a comparison matrix of the three proposals attached. Assess only on: price, implementation timeline, support commitment, security certifications. Use only what each proposal states in writing. Where a proposal does not address a criterion, write NOT STATED — do not score it, and do not fill the gap from the vendor's website. Format: one row per vendor, one column per criterion, plus a final column listing what is missing from that proposal.
Example 6: the scope audit
The client keeps adding “quick” requests by email and nobody has checked them against the signed scope.
✕ The ask most people type
"Is anything in this email thread outside our original scope of work?"
✓ The Four-Line Rewrite
"You are a project manager protecting a fixed-fee engagement. Produce a scope-delta list. Compare only the email thread against the statement of work pasted above it; quote the exact SOW wording that does or does not cover each request. Format: a table of request, SOW clause or NONE FOUND, minor or major."
Asking for the quoted clause is a verification trick worth stealing everywhere: it forces the model to point at the evidence instead of asserting a conclusion.
Example 7: the RFP answer
Sixty questions, most of which your team has answered before in slightly different words.
You are a bid manager answering a public-sector RFP. Produce: a draft answer to the question below, using our previous answers pasted underneath as the only source of fact. Do not invent capabilities, certifications, client names, or numbers. If our previous answers do not cover part of the question, write GAP — NEEDS INPUT and name exactly what is missing. Format: 150 words maximum, second person, no marketing adjectives, no superlatives.
That GAP instruction turns the draft into a to-do list for the humans. More on the whole cycle in the guide to writing RFP responses.
Examples 8 to 10: people and clients
The last three carry reputational weight. A wrong number in a variance note is embarrassing; a wrong sentence in a review is a formal problem.
Example 8: the performance review
Six people, a deadline, and a pile of notes you took across the year.
You are a line manager writing a mid-year review for a direct report. Produce: a draft review with three strengths and two development areas. Use only the notes and feedback pasted below. Every point must cite a specific incident from those notes. If a competency has no evidence in the notes, write NO EVIDENCE RECORDED rather than writing something general. Format: for each point — the behaviour, the example, the impact. No personality descriptions, no comparisons to other team members.
“No personality descriptions” is a negative constraint with a legal reason behind it. Reviews describe behaviour and impact, not character. The manager-side detail is in writing performance reviews fairly.
Example 9: the sales follow-up
A good discovery call, and a follow-up email that usually reads like it was sent to everyone.
✕ The ask most people type
"Write a follow-up email to this prospect after our call."
✓ The Four-Line Rewrite
"You are an account executive following up with a finance director who raised two specific objections. Produce a follow-up email. Use only my call notes below — reference their exact words about budget timing, and do not restate our product features. Format: under 120 words, one clear next step, no bullet lists."
Example 10: the client delay notice
You are late. The email has to say so without either grovelling or hiding it.
✕ The ask most people type
"Write an email telling the client the project is delayed. Make it professional."
✓ The Four-Line Rewrite
"You are an agency account director emailing a client who has already been patient once. Produce a delay notice. Use only the facts below; do not promise a recovery date that is not in my notes. Format: new date first, one sentence of cause, then what we are doing about it. Under 100 words. Apologise once, in the first line, and not again."
“Apologise once and not again” is the sort of instruction you only write after reading an AI draft that apologised five times. Lay the ten AI workflow before after examples side by side and one line does most of the work in each — usually a different one:
| The task | The line most often missing |
|---|---|
| Meeting transcript | Fence the facts, so owners are not invented |
| Weekly status | Name the reader, not just the writer |
| Executive summary | Name the shape, including a word ceiling |
| Budget variance | Ban inferred causes explicitly |
| Vendor shortlist | Force NOT STATED instead of a guessed score |
| Scope audit | Demand the quoted clause as evidence |
| RFP answer | Name the gap rather than filling it |
| Performance review | Require an example behind every claim |
| Sales follow-up | Name the reader and their actual objection |
| Client delay notice | Cap the apology and lead with the new date |
What the four lines change, dimension by dimension.
An AI chat response showing a completed four-column action table generated from a pasted meeting transcript, with NOT STATED appearing in at least one cell.
Crop to the response area only. Redact all real names, company names and dates in the table.
File: structured-table-output-from-rewrite.png · Alt: "A four-column action table produced by a rewritten prompt, with NOT STATED in one cell"When the rewrite still goes wrong
The four lines fix the common failures, not all of them. Three things go wrong often enough to be worth naming.
| What you see | Why it happens | The fix |
|---|---|---|
| Still reads generic | The reader was never named | Add who receives this, not just who writes it |
| It invented a figure | The gap had no legal answer | Require NOT STATED for anything absent |
| It forgot the rules mid-chat | Instructions faded across turns | Paste the four lines again before the next ask |
That third row is worth understanding rather than memorising. Anthropic’s engineering write-up on effective context engineering for AI agents, published in September 2025, describes the effect as context rot: as the number of tokens in the window grows, the model’s ability to accurately recall information from that window drops. It is not the model ignoring you. It is attention thinning out across a long conversation.
The practical consequence is small and slightly annoying: on turn four or five, re-anchor. One short block does it.
Reapplying my rules from the start of this chat before you answer: - Role: [paste your role line again] - Source: use only the text I pasted. Missing details are NOT STATED. - Format: [paste your shape line again] Now: [your next request]
Match the symptom to the line you left out.
If the answer is close but not right, resist the urge to start again. Change one line, re-run, and see what moved — the method for that is in refining output without starting over.
What the rewrite cannot fix
Four lines make the output usable. They do not make it true, and they do not make it yours. Three things stay on your desk permanently.
The Four-Line Rewrite does not do any of this for you:
- Judging what matters. The model weights every line of a transcript equally. Deciding that one throwaway comment was the real risk is your job, and it always will be.
- Verifying the facts. NOT STATED stops invention; it does not confirm that what your source document says is correct. If the numbers are wrong going in, they are wrong coming out, now formatted beautifully.
- Owning the send. Your name is on the email. A review, a variance note, or a delay notice that gets challenged is challenged with you, not with the tool.
There is also a category of task where the rewrite is simply the wrong instinct — anything where the thinking IS the deliverable. A strategy call, a difficult conversation, a decision between two options you genuinely have to weigh. Structure the input all you like; the judgment is not in there.
Most professionals overcorrect once, hand something over that needed a human, and then settle into the right split. It is worth reaching that point deliberately rather than by accident. If you want the wider verification habit, the guide to fact-checking AI research covers the checking pass properly, and why AI invents things covers the underlying mechanism.
Which plan you actually need
None of this requires a subscription. Every rewrite above is plain text into a chat box, which the free tier of every mainstream assistant handles. Paid tiers raise upload and length limits; they do not unlock the method.
| What you are doing | Free plan | Paid plan |
|---|---|---|
| Pasting a transcript or email | Fine | No advantage |
| A long report to summarise | Usually fine | Higher upload limits help |
| Three vendor PDFs at once | Often hits a limit | Worth it for this |
| Everyday rewrites all week | Fine | Only for message limits |
The real constraint is not price, it is what you are allowed to paste. That depends on your account type, not your plan tier. OpenAI’s help centre for ChatGPT account and data questions states the boundary plainly: content from business offerings is not used to train models, while content from individual accounts may be unless you opt out — and specific prompts cannot be deleted from your history afterwards. Other vendors draw the line in the same place.
Your own drafts, public documents, anonymised examples.
Client names, internal metrics, salary figures, staff names.
Credentials, personal data, unreleased financials, anything under NDA.
Redaction is easier than it sounds: swap identities for roles before you paste, and the output comes back in the same terms.
- Client and vendor names become Client A, Vendor B.
- Colleagues become the finance director, the project lead.
- Real figures become [FIGURE] when the number itself does not change the writing.
Pick one task from the ten above — ideally the one you will do again this week — and rewrite it four lines at a time. The second one takes a minute. By the fifth, you stop thinking about the structure and just write briefs instead of asks.
Then keep them. The genuine compounding effect of AI workflow before after examples is not the ten on this page, it is the four or five you write yourself for the tasks that actually recur on your desk. A saved note with your own role line and your own format line, ready to paste, is worth more than any prompt list — because it already knows who you are and who you write for.
Rewrite your next prompt in four lines
- Name the role: the job title and seniority the answer should sound like. Name the deliverable: the finished document, not the topic. Fence the facts: use only the pasted text, and write NOT STATED for gaps. Name the shape: columns, sections, word count, tone. Paste your source underneath and send it once, unedited. Save the four lines as a note so the next run takes a minute.