Have you ever asked an AI assistant for help and received an answer that wasn't quite what you needed?
A prompt is the message you use to tell an AI what you want it to do.
When an answer misses the mark, adding impressive-sounding words is less useful than identifying the specific problem and revising your request.
Using fictional examples, this guide walks through how to spot a mismatch, ask for a correction, and keep a useful prompt for next time.
First, identify what went wrong
When an answer feels off, it can be tempting to rewrite the entire prompt immediately.
Start by putting the situation in which you'll use the answer alongside the part that concerns you.
Check whether the answer changes what the reader is expected to do
Imagine you're sending participants a short notice about a neighborhood cleanup.
The organizer's notes say:
The cleanup takes place at the park at 10 a.m. on Saturday.
Participation is optional, and no advance registration is needed.
The organizers will provide work gloves.
The notes give a day and time, but not a calendar date or the park's name.
Before sending a real notice to first-time participants, confirm the date and the park's exact location with the organizer.
For now, let's focus on how the answer handles the information in the notes.
Suppose you give the AI the notes and ask:
Turn these notes into a short notice for participants.
The following answer was written by the editors as a teaching example; it is not a measured AI response.
The cleanup will take place at the park at 10 a.m. on Saturday. All participants must attend. We will provide gloves.
The answer is brief, but the notes say participation is optional, while the response makes it sound mandatory.
Because this mismatch could change what the reader thinks they must do, it matters more than a stylistic preference.
The response also omits the fact that registration is not needed.
Whether that detail must stay depends on the purpose of the notice; here, first-time readers need it to decide how to participate.
Say what to change and what to keep
You could continue the conversation with this correction:
Participation is optional, not mandatory.
Change the wording that makes attendance sound compulsory, and include the fact that no advance registration is needed.
Keep the day, time, location and glove information, and make the notice brief.
Here's an illustrative revision:
The cleanup will take place at the park at 10 a.m. on Saturday. Participation is optional, and no advance registration is needed. The organizers will provide gloves.
Compared with the notes, the revision restores the participation condition while keeping the day, time, location and glove information.
This is a teaching example, not a guarantee that the same prompt will always produce this response.
Even after a correction, check the answer against the original source.
Separate different kinds of mismatch
In the cleanup example, we checked participation and a missing detail.
Other answers may be factually sound but too long or unsuitable for their audience.
- Facts: Does the answer conflict with the source?
- Omissions: Is anything the reader needs to make a decision missing?
- Format: Does a paragraph, list or table fit the intended use?
- Audience: Is it appropriate for the person who will use it?
You don't have to fix everything at once.
Start with the issue that prevents you from using the answer, then check the remaining concerns in turn.
Compare the source and response in another task
The same approach works when you're organizing a handover rather than writing a notice.
Imagine these fictional shipping notes are being passed to the next person on duty:
Packing is complete.
The shipping label has been created.
Pickup has not yet been requested.
The person responsible gives the notes to an AI and asks it to summarize the shipping status for a handover.
Summarize these notes for the next person handling the shipment.
Packing is complete. The shipping label has been created. Pickup has not yet been requested.
Suppose the response is:
Shipping preparations are complete. Pickup has been requested.
The notes say pickup has not been requested, but the response says it has.
If the next person relies only on the answer, they may not realize a pickup request is still needed.
Separate completed work from work that remains
The first priority is not to make the answer shorter; it is not to turn an unfinished task into a completed one.
A follow-up request could be:
Keep the status of each task exactly as stated in the notes, and separate completed work from work that is still needed.
Make it clear that pickup has not yet been requested.
The editors' illustrative revision is:
Complete: packing and creation of the shipping label.
Still needed: request pickup.
The revision retains the completed items and shows that the pickup request remains.
It is a teaching example, not an observed model output.
For a real handover, check with the responsible person whether pickup was requested after the notes were written.
The cleanup notice and shipping handover have different purposes, but both begin by checking whether the facts the reader needs have been preserved.
Add missing context from the intended use
Your first prompt can be short.
If the answer is unsuitable, return to the actual use case and consider what the AI was not told.
Name the audience and purpose
The same cleanup notes could become a record for the organizer or a notice for people attending for the first time.
The record might focus on decisions, while the notice needs readers to find the time and participation requirements quickly.
You could add:
Write a notice that helps first-time participants understand when and where to go and whether they need to register.
This simply explains who the message is for and what they need to decide.
More detail about the audience cannot reveal a calendar date that is missing from the source.
For missing facts, return to a reliable source or someone who can confirm them.
Put instructions and source material in separate sections
Separating what the AI should do from what it must not change makes the request easier to review.
Turn the notes below into a notice for first-time participants.
Do not add information or make participation sound mandatory.
Include the day, time, location, participation requirements and glove information.Notes:
The cleanup is at the park at 10 a.m. on Saturday.
Participation is optional, and no advance registration is needed.
The organizers will provide work gloves.
The AI may still fail to follow a condition, so check each one before using its answer.
Make revision requests specific
You can ask an AI to make an answer better, but that leaves the AI to infer what better means.
If you already know which part is wrong, identify the passage and the change you need.
Point to the wording you want changed
In the cleanup example, the problem is the sentence saying all participants must attend.
“All participants must attend” makes participation sound mandatory.
Change it so that participation is clearly optional.
Also check the other details against the original notes.
The quotation marks identify the exact wording to revise.
You can then compare the relevant passage before and after the change.
Check the effect on the rest of the answer
Even when you ask for one small change, an AI may rewrite other parts as well.
Tell it what should remain, then check both the correction and the details you asked it to keep.
Dates, amounts, deadlines and participation requirements can affect what people do, so compare them with the source.
Choose an output format you can check
The content of an answer matters, but so does the form in which you'll use it.
Imagine you need to check who is responsible for tasks after a meeting.
Sato will review the flyer draft by Wednesday.
The venue booking is incomplete, and no one has been assigned to it yet.
Ask for a format that separates known information from missing information:
Organize the tasks from the notes into a table with task, owner and deadline columns.
If the notes say an item is undecided, mark it as undecided; if an item is not mentioned, do not guess and mark it as not stated in the notes.
Keep any task status from the notes with the task name.
Here is a table created for the example:
| Task | Owner | Deadline |
|---|---|---|
| Review flyer draft | Sato | Wednesday |
| Book venue (incomplete) | Undecided | Not stated in notes |
The table makes it easy to see that the owner has not been decided and that the notes do not give a deadline.
A well-formatted table is not proof that the information is correct.
Compare it with the notes, including whether unfinished work has been labeled complete.
Don't fill gaps with guesses
You can ask the AI to mark a missing item as not stated rather than inventing an answer.
Not mentioned in a note is not the same as actually undecided.
The notes explicitly say the venue owner is undecided, but they say nothing about the deadline, so the deadline is marked as not stated.
Even when the AI writes not stated, verify that the information really is absent from the source.
For an important decision, review the relevant passage yourself and ask the person responsible if necessary.
Show an example, but specify what to copy
A short sample can help describe the tone or shape you want.
For a friendlier cleanup notice, you might provide a different notice and ask the AI to imitate only its tone.
Use the sample's warm, concise tone to write a cleanup notice.
Do not use any date or location from the sample; use only the cleanup notes for the facts in the notice.Tone sample:
We're holding a weekend book club. First-time visitors are welcome to join us.
The sample contains information about a book club, so the request specifies that only the tone should be used.
Afterward, check that details from the sample have not slipped into the cleanup notice.
When shortening, decide what must stay
A word or character limit is not the only consideration when a notice must be brief.
Tell the AI which details the reader needs in order to act.
Imagine putting the cleanup notice on a board with limited space.
The cleanup will take place at the park at 10 a.m. on Saturday. Participation is optional, and no advance registration is needed. The organizers will provide gloves.
For this notice, the day, time, location, optional participation and lack of a registration requirement should remain.
The glove information is useful too; if it cannot fit, the organizer must decide whether to place it elsewhere.
Shorten the notice for a bulletin board.
Keep the day, time, location, optional participation and the fact that no advance registration is needed.
Keep the glove information if it fits; if not, tell me separately that it was omitted.
Separate the bulletin-board text from any omitted information.
The editors' illustrative result is:
Cleanup at the park, Saturday at 10 a.m. Participation is optional; no registration is needed. Gloves are provided by the organizers.
Omitted information: none.
The shortened version keeps the participation details and glove information along with the day, time and location.
We have not specified an actual character limit, so we cannot yet say it fits the board.
Rather than assuming brevity and completeness conflict, first see whether you can satisfy both.
If the board has a strict limit, include it in the request and verify the final length using the destination's counting rules.
Some destinations may count punctuation, numbers or line breaks differently.
Consider another way to deliver details before removing them
If essential information genuinely will not fit, reconsider where and how the notice is delivered before deleting an important condition.
For example, participation details could stay on the board while the glove information appears in a separate, more detailed notice.
But that only helps people who actually receive the second notice.
Decide what goes where after checking who will receive each message.
Compare alternatives using consistent criteria
The same prompt can produce different answers on different runs.
When comparing prompts for your own work, keep the source material and review criteria consistent and record what you changed.
Use the same source and criteria
Here are two requests against the same cleanup notes, with fictional answers prepared to illustrate the comparison.
Turn these notes into a short notice for participants.
The cleanup will take place at the park at 10 a.m. on Saturday. All participants must attend. We will provide gloves.
Turn these notes into a short notice for first-time participants. Say that participation is optional and registration is not needed, and retain the day, time, location and glove information.
The cleanup will take place at the park at 10 a.m. on Saturday. Participation is optional, and no advance registration is needed. The organizers will provide gloves.
For this exercise, the criteria are that the participation requirements are clear and the day, time and location remain.
Response A sounds mandatory and omits the registration detail.
Response B retains the optional participation and registration details as well as the day, time and location.
B meets these particular criteria, but the fictional examples do not measure whether either prompt is generally better in real use.
Don't generalize from a single result
A repeated run may produce a different answer, so one comparison cannot establish that a wording always works better.
Different sources and goals also require different conditions.
A work note for cleanup staff, for example, needs more than the criteria used for a participant notice.
Record what you compared and the conditions under which the result was usable so that you can check it again for another purpose.
Separate changes to the request from changes to the source
If you change both the prompt and the source at once, it is harder to tell which change affected the answer.
Suppose the organizer says the cleanup will now start at 11 a.m.
First update the source and give the new time to the AI.
An earlier response based on 10 a.m. is no longer suitable, however polished it looks.
When revising the request, also check whether the source is current.
Reorganize the conditions after several revisions
A long conversation can make it difficult to remember which conditions were added and which no longer apply.
If the answer keeps drifting, collect the current purpose, source, conditions and desired format in one place.
For the cleanup notice:
- Purpose: Tell first-time participants about the event and how to participate.
- Source: Day, time, location, optional participation, no registration and provided gloves.
- Conditions: Do not add facts or make attendance mandatory.
- Format: A short notice.
Using this summary in a new request can make it easier to see exactly what you supplied.
It does not mean a new conversation is guaranteed to be more accurate.
In either case, compare the result with the source.
Save a useful request for next time
Once you have a request that works for your purpose, consider saving the request and its review criteria as well as the finished text.
For another cleanup notice, checking optional participation and registration could be useful again.
But hard-coding this event's day and place into a template risks carrying old information into the next notice.
Replace the changing details every time, and check that no previous details remain.
Check what you are allowed to enter
Before using an AI service for work, check your organization's rules and the service's settings for personal information, confidential business material, credentials and other sensitive data.
Don't paste information whose use you cannot confirm merely because it is convenient.
For practice, use fictional material that is safe to share instead of real names or private details.
Decide when an answer is usable
If you never define what makes an answer ready to use, revisions can feel endless.
Return to the original use case and choose a few checks that matter before sending it.
Check the reader's next action
For the cleanup notice, a first-time participant needs to understand when and where to go and whether registration is needed.
For this fictional exercise, the checks are:
- Day, time and location: Saturday at 10 a.m. at the park are stated.
- Participation: Attendance is optional and no registration is needed.
- Source agreement: No conditions absent from the notes have been added.
These are editorial checks for this specific example.
Another notice may need different checks, such as a contact address or what to bring.
Check that one fix didn't introduce another problem
Suppose a shorter version instead says:
Cleanup at the park, Saturday at 10 a.m. Participants must register.
The day, time and location remain, but the original notes said registration was not needed.
You cannot use the result just because it is shorter.
Separate what improved from what still needs fixing, then correct the participation requirement while retaining the useful brevity.
Also remember that a response can match the notes while the notes themselves are out of date.
Check the latest conditions with the organizer rather than asking the AI to guess.
Stop and verify when you cannot decide
Filling an unknown gap without checking it can produce a plausible notice that sends readers in the wrong direction.
If you don't know whether the event date changed, confirm it with someone who does before sending the text.
That is separate from improving a prompt, but it is part of producing an answer you can actually use.
Check before you use the result
Prompt improvements do not guarantee that every AI response will be correct.
A fluent answer can still contain changed facts or additions that were not in the source.
Before using it, check:
- Source: Do important facts and numbers match?
- Omissions: Is anything needed for the reader's decision missing?
- Additions: Has anything not in the source been presented as fact?
- Purpose: Does the form fit the audience and use?
- Information handling: Are you permitted to enter and share the information?
If you cannot verify a point, don't use it as-is; return to the source or ask the person responsible.
Rather than searching for a perfect first prompt, start by identifying what makes an answer unusable, stating the needed conditions, and checking the result against the source.