In plain English
- What happened
- ChatGPT, Claude and similar tools do not permanently learn from a single correction inside one conversation. What they offer instead are standing-instruction features — custom instructions and memory in ChatGPT, and project knowledge in Claude — that reapply a written rule every time you start a new chat.
- Why it matters to your business
- A small business owner who keeps correcting the same formatting error, the same wrong tone, or the same made-up detail is not imagining it: the model has no memory of that correction unless it was saved somewhere and reloaded. Building a short file of standing rules and pasting it into the right box turns a one-time fix into a repeated one, which is the only mechanism these tools currently offer.
- Do this
- Open a blank document and start listing every correction made to AI output in the past month, worded as a rule rather than a complaint.
The frustration is common: you correct the AI on Monday, and by Thursday it has made the same mistake again — the wrong sign-off on emails, invented pricing, a tone that does not match the business. That is not a bug being ignored. General-purpose chat tools do not retain anything from a conversation once it ends, unless a separate feature is switched on to carry it forward.
What the tools actually offer
ChatGPT's custom instructions let a user write standing preferences once — how to write, what to avoid, facts about the business — and that text is reapplied to every new conversation from then on. It is not the model learning; it is a note being reread each time.
ChatGPT's separate memory feature can pick up specific facts mentioned during a conversation and carry them into future ones, and current settings let a user view, edit or delete what it has stored, or turn the feature off entirely.
Claude's Projects work differently: a user can set project-specific instructions and upload reference documents — a style guide, a pricing sheet, a list of past corrections — and every chat started inside that project draws on them.
None of these features change the underlying model. They add text to what the model reads before it answers, which is why a rule has to be written down somewhere the tool actually loads.
Turning corrections into a file
The practical version of this is a running list, not a one-off setup. Every time an output is wrong in a way that matters, write down what was wrong and what the correct version should have been, phrased as a rule rather than a complaint.
- 1
Start a mistake log
Open a single document and add one line every time an AI output needs correcting: what it got wrong, and what should have happened instead.
- 2
Rewrite each entry as a rule
Turn 'it used the wrong price' into 'always quote prices from the current rate sheet, never estimate.' Rules are easier for the tool to follow than descriptions of past failures.
- 3
Load the rules into the right feature
Paste the list into ChatGPT's custom instructions if it applies to everything you do, or into a Claude project's instructions if it only applies to one kind of work, like customer emails.
- 4
Test with the same prompt that failed before
Re-run the exact request that produced the original mistake and check whether the rule held. If it did not, the rule is probably too vague.
- 5
Review the list every few months
Rules go stale as prices, staff and processes change. A quarterly ten-minute pass to delete or update entries keeps the file useful instead of becoming clutter the tool has to wade through.
Here is a list of mistakes an AI tool has made when working on my business, along with what should have happened instead: [paste your mistake log] Rewrite this as a short numbered list of standing rules I can paste into a custom instructions or project settings box. Keep each rule to one sentence, written as an instruction, not a description of the mistake.
Reality check
None of this guarantees compliance. Custom instructions and project knowledge make a rule more likely to be followed, not certain — the model can still miss it on a long or unusual request. The last check on anything customer-facing still belongs to a person, and that does not change because a rules file exists.
This is also not a reason to buy a specialized 'AI training' product. The features that do this — custom instructions, memory, project knowledge — are already included in the ChatGPT and Claude plans most small businesses already pay for, and current vendor pages are the place to check what each plan includes before spending more.
Sources




