Dot 5 / Feedback
Give feedback that improves the next result
Keep the conversation useful with corrections, changed priorities, and a quick check on what comes next.
Steering is part of the conversation
You can return with an ordinary sentence. You do not need to rewrite the whole request:
- “That’s too much detail” — ask for the three things that matter next.
- “My priority has changed” — explain what now comes first and what should wait.
- “What’s finished and what’s blocked?” — pick up the work where it stands.
- “What information or access do you need?” — find the missing piece together.
Dot uses selected conversation context and saved notes. They are not a perfect transcript or a guarantee that every fact will be recalled. Restate a key decision, point to the current source, and ask it to revise any affected work. OpenAI’s tasks and memory guide.
ChatGPT memory and dot’s own saved notes are separate. Searching or recalling relevant earlier work does not mean every conversation is available. Name the thread, current source, or decision you mean. If you are stuck, try When your dot needs steering.
Check whether the result helps
A helpful review is more precise than “great” or “try harder.” Compare the output with the outcome, format, sources, and boundaries you agreed on. Was it complete? Was it grounded in the supplied information? Did it make uncertainty visible? Did it stop at the right point?
Check substance before polish. A beautifully formatted list is still a problem if it assigns a deadline that no source supports.
For important actions, ask dot to show the result or confirmation, and check it before relying on it.
Correct one thing with an example
Instead of “this summary is too vague,” try:
Keep the opening to two sentences. For each unresolved item, include the source, the last known owner, and the next decision. If the owner is missing, say so. Do not infer one from who attended the meeting.
This gives the helper a rule, an output shape, and a boundary. If the problem is factual, identify the reliable source and ask for the affected conclusions to be revisited.
You can change direction whenever you need to. When you are trying to improve a recurring result, one clear correction at a time makes it easier to see what helped.
Keep your own brief current
If you use a starter brief, treat it as an editable working document. After a useful correction, revise the relevant section. You can also keep steering in conversation; a brief is optional. A small version note such as “Changed the review window to the past two weeks” can help you remember the current arrangement.
On this site, “training your Dot” means providing instructions, examples, and feedback. The builder composes a document from your answers; it does not train or fine-tune a model.
Product memory is a separate topic. OpenAI says turning off ChatGPT Memory stops sharing with a Dot but does not delete information it already received. Official privacy FAQ. Do not treat a corrected brief as proof that retained information has been erased.
Make your review rhythm realistic
For a first test, inspect every result. Once the task is familiar, decide what you will check on each run and when you will revisit the whole arrangement. Review again when sources, responsibilities, or permissions change.
Ask for a short completion note: what was reviewed, what was produced, what is uncertain, and what needs you. Decide which issues deserve an interruption and which can wait for the next check-in.
Try this now
Choose one output and write:
- One thing that meets the standard.
- One thing that needs to change.
- One example showing the change.
- One small test that would show whether it improved.
Repeat the same bounded task with the revised instruction and compare the results.
Common mistakes
Correcting only tone. Check the evidence and decisions as carefully as the wording.
Giving contradictory preferences. “Include every detail” and “keep it very short” need a priority rule. Ask for a short summary with a separate detail section.
Assuming improvement is permanent. Keep checking. New information can expose a new misunderstanding.
Put the five dots together
Context, connections, responsibilities, boundaries, and feedback are questions you can return to as needed. You can start before you have all the answers. Write a starter brief if it helps, or try a message from the Small-Business Follow-Up recipe.
Official references
Source check: October 14, 2026. A source check is not hands-on testing.