A clearer prompt can improve an AI response, but it cannot guarantee accuracy or supply knowledge the tool does not have. Treat prompting as defining a task and its acceptance checks. If a result remains wrong, the tool, source material or task may be the problem; adding more instructions is not always the answer.
Specify four useful things
State the task, the relevant background, the intended reader and the output format. A role can help set tone, but it does not create professional expertise. Google’s Workspace prompting guidance similarly emphasises task, context and format and recommends refining results.
Weak request: “Write an email.”
More useful request: “Draft a 120-word email asking the organiser to confirm the workshop venue. We have the date and time, but no room number. Use a polite tone. Do not invent an address or booking reference.”
The second request gives you something concrete to inspect: does the draft ask for the missing venue, keep the supplied details and avoid inventing information?
Separate source material from instructions
Label a supplied passage as source material and state what the assistant may do with it. For example: “Summarise the passage below. Use only facts in the passage. List any question it does not answer.” This reduces ambiguity, but you must still compare the summary with the source.
Do not paste confidential records merely to improve context. Replace personal details with placeholders and use an approved workplace service when handling work material.
Three templates to adapt
Study practice
“Using this syllabus section, explain the concept at my course level. Give two practice questions and keep the answers separate until I attempt them. Identify any point the source does not explain.”
Check the explanation against the textbook. These are practice questions, not predictions of what will appear in an exam. Follow your institution’s rules for assessed work.
A factual service complaint
“Draft a concise complaint using these facts: [dates], [what was ordered], [what happened], [resolution requested]. Leave identifiers as placeholders. Do not invent legal deadlines, compensation rights or promises made by the business.”
Verify the actual complaint route before sending. Do not let an assistant add an escalation threat to an authority that does not cover your issue.
Editing your own paragraph
“Make this paragraph clearer for a beginner. Preserve the meaning, numbers and qualifications. Show any sentence whose meaning you changed. Keep technical terms that are necessary and explain them briefly.”
Refine a specific failure
Instead of “make it better”, describe the problem: “The second paragraph adds an unsupported date; remove it” or “Keep the example but shorten the introduction.” Start a fresh conversation if previous assumptions keep contaminating the result. Iteration is an option, not a rule that every task must remain in one long chat.
Check before using the result
- Does it answer the actual request?
- Are names, numbers and quotations faithful to the source?
- Do links open and support the nearby claim?
- Did it turn uncertainty into certainty?
- Does the wording sound appropriate in your language and setting?
Keep a template only when it repeatedly helps your task. Record which checks still require your attention. A good prompt makes the work easier to review; it does not remove the need for review.
Reviewed on 27 October 2026. Added safer templates and removed exaggerated claims about prompting and exam prediction.
Techleez Editorial Team
The Techleez publishes practical digital guides. For our scope, use of AI assistance and corrections process, read our editorial policy.
More from this author →
