How to Write a Clear Prompt for ChatGPT
A beginner-safe AI workflow for write a clear prompt for chatgpt, with a copyable prompt, source boundaries, missing-information rules and line-by-line verification.
By the end: You will run a grounded AI task using real source material, verify every consequential claim, and keep a reusable prompt plus human-review process.
You will run a grounded AI task using real source material, verify every consequential claim, and keep a reusable prompt plus human-review process.
Key terms before you start
These definitions make the steps easier to follow and help distinguish controls, files and concepts that can look similar at first.
What you need before starting
- Access to ChatGPT
- The real source material required for the task
- Permission to use that material
- A person who can verify/approve consequential facts
Step-by-step tutorial
Every step is shown below. Work through them in order and use each checkpoint to confirm the result before moving on.
Open a new ChatGPT conversation
Start a new chat so unrelated earlier instructions do not accidentally shape the workflow.
A clean conversation makes the task/source boundary easier to audit.
Treat the claim as unsupported; open the source yourself and correct/remove it.
Collect the authoritative input first
Prepare the real verified source text you are allowed to use.
Do not ask the model to reconstruct private/current facts that should come from a document, database or person.
Strengthen the source-only/missing-information rule, delete unsupported content, and verify the revised output. Do not keep a plausible guess.
Define the output format
Ask for a structured draft with requested headings and specify headings/fields/order.
A defined structure makes comparison/review easier.
Restate the exact schema/headings and show a tiny structural example without adding fake factual values.
Paste or attach the source after the instructions
Place the source under a clear SOURCE: label or attach the document, depending on the interface.
Separate instructions from source text so quoted source language is less likely to be mistaken for an instruction.
Treat the claim as unsupported; open the source yourself and correct/remove it.
Run the prompt without asking for extra creativity
Send the request.
For factual extraction/rewrite, creativity is not the goal.
Restate the exact schema/headings and show a tiny structural example without adding fake factual values.
Check every number and date
Compare numbers, dates, prices, percentages and deadlines back to the source one by one.
These details are easy to alter accidentally and often consequential.
Treat the claim as unsupported; open the source yourself and correct/remove it.
Check every proper name and product/service name
Compare spelling and identity with the source.
A plausible wrong name is still wrong.
Strengthen the source-only/missing-information rule, delete unsupported content, and verify the revised output. Do not keep a plausible guess.
Check citations/quotes if present
Open cited sections/links and verify they actually support the statement.
Never assume a citation is valid because it is formatted convincingly.
Strengthen the source-only/missing-information rule, delete unsupported content, and verify the revised output. Do not keep a plausible guess.
Record reusable prompt only after it works
Save the prompt template plus required inputs and review checks.
A repeatable workflow includes validation, not just reusable wording.
Re-run the same verification after every material revision. Human review is not a one-time step.
Re-test when source/model/process changes
If the input format, policy, model or business process changes, run validation examples again.
A workflow proven on one version is not permanently proven.
Strengthen the source-only/missing-information rule, delete unsupported content, and verify the revised output. Do not keep a plausible guess.
If a factual sentence cannot be traced to the allowed source, remove it or mark the information missing.
Concrete examples
Copyable example
You are helping me write a service page.
Task: Rewrite the supplied text into a 300-word service page.
Audience: Small-business owners who already have a WordPress site.
Facts: Use only the SOURCE below.
Tone: Direct and professional.
Do not invent prices, testimonials, statistics, dates or features.
If a necessary fact is missing, write [MISSING: what is needed].
Output headings:
1. Service
2. What is included
3. Who it is for
4. Next step
SOURCE:
[paste verified source text here]Troubleshooting
Strengthen the source-only/missing-information rule, delete unsupported content, and verify the revised output. Do not keep a plausible guess.
Restate the exact schema/headings and show a tiny structural example without adding fake factual values.
Treat the claim as unsupported; open the source yourself and correct/remove it.
Re-run the same verification after every material revision. Human review is not a one-time step.
The process remains current.
How the topic comes up in practice
Short excerpts from public discussions that directly relate to the task. Use the source link for the complete context.
“Break things into lists or bullets to reduce ambiguity.”
detailed prompting guide ↗
“Good prompting is just good structure.”
prompt structure ↗
Continue with these tutorials
Documentation and references
Use these primary and supporting sources to verify current controls, browser behavior and product-specific details.