Write better AI prompts
Learn how to write incident descriptions that get better results when Logiqc AI fills in the rest of your form.
A few simple habits make a real difference to the result you get, first time.
This article covers why it matters, giving AI enough detail, and phrasing dates correctly.
Logiqc AI can only work with what you give it. A short, vague description leaves it guessing, and if it guesses wrong or leaves something out, you'll usually end up making a follow-up correction to fix it.
Beyond the extra step, a vague description also means more time spent reviewing and correcting fields afterwards, and a less complete, less consistent incident record overall. A clear, detailed description gets you a more accurate result the first time, with less back-and-forth before you can submit.
The AI only has what you've given it to work with. You can edit your description as many times as you like before you run it, that part's free: include what happened, who was involved, where and when, and any immediate action taken, before you select Fill in this form using AI.
Q: Does a better description actually use fewer credits?
A: A single fill-in request costs the same whether your description is detailed or vague. The saving comes from not needing a second request to fix what the first one got wrong or left out.
Q: Why should I avoid relative dates like "last Tuesday"?
A: Relative dates can be interpreted differently depending on when the request is made. An explicit date removes the ambiguity and gives Logiqc AI clearer information to work from.
Give AI enough detail
A description that states what happened, who was involved, and the details that must be included will almost always get you a better result than a one-line entry.
Helpful description
"A client slipped on a wet floor near reception at 10:30 am on Tuesday 21 July. Staff assisted immediately and placed a warning sign in the area."
Less helpful description
"Client fell over near reception."
| Description style | What typically happens | Requests needed |
|---|---|---|
| Vague, one line | AI guesses at missing details or leaves fields incomplete | Often two: the original, plus a follow-up to fix it |
| Relative dates, like "last Tuesday" | AI may not have the exact date needed for the response | Often two, if the date needs clarifying |
| Detailed, with explicit dates | AI has what it needs the first time | Usually just one |
Be explicit about dates and times
Be specific with dates and times so Logiqc AI has clear information to work from. Phrases like "Tuesday last week" or "this morning" can be interpreted differently depending on when the request is made.
See these tips in action
See these tips applied in the related articles: