Why Is ChatGPT Bad at Some Tasks?
ChatGPT struggles with factual accuracy, following precise instructions, and remembering context across sessions. Understanding why helps you use it better and avoid common mistakes.
Updated 4 min read
ChatGPT is bad at tasks that require precise facts, strict rule-following, or memory across sessions. It generates text by predicting what a plausible response looks like, not by checking a database of verified information. That makes it useful for drafting, summarizing, brainstorming, and explaining, but unreliable for tasks where accuracy or consistency is critical. Tools like fenbs help by keeping a separate record of verified facts, lessons, and project rules that every connected assistant reads before acting.
None of these weaknesses mean ChatGPT is useless. They mean it needs to be used with the right checks in place. Knowing where it fails most often lets you apply those checks where they matter.
Unreliable facts and fabricated details
ChatGPT can state an incorrect fact with the same confidence it uses for correct ones. This is sometimes called hallucination: the model generates text that sounds right but is not. It happens most often with specific numbers, dates, citations, people's statements, and technical details outside its training data.
The model cannot tell you when it is uncertain in real time. It does not have access to live data unless a web search tool is enabled, and even with search enabled, it can misread or misquote a source. Anything that matters should be checked against a primary source before you use it.
Asking ChatGPT to tell you when it is uncertain can help at the margins. "For any claim you are not confident about, say so rather than stating it as fact" sometimes surfaces hedges that the default response omits. It does not prevent hallucination, because the model does not have reliable access to its own confidence level, but it can prompt acknowledgment of gaps it would otherwise paper over.
Weak instruction-following
ChatGPT often drifts from precise instructions as a conversation continues. Ask it to always respond in bullet points, use a specific format, or avoid a certain phrase, and it may comply for a few turns before reverting. Longer conversations and more complex instructions increase the drift.
This is not defiance. The model weights recent context more heavily as a conversation grows, and an instruction from the beginning of the conversation gradually loses influence. Short, clear prompts at the start of each session, with a reminder when instructions are not followed, help more than long instruction sets buried in an initial message.
No memory between sessions
Unless you have ChatGPT's optional memory feature turned on, each new conversation starts completely fresh. ChatGPT does not know what you discussed in previous sessions, what decisions were made, or what the ongoing project is. If you paste in a long recap at the start of every session, you are doing manually what a proper context system would do automatically.
Even with memory turned on, the feature is limited in what it retains and is personal to your account. It does not give teammates or other AI apps access to the same project context, and it cannot distinguish between a standing rule and a one-time preference.
Difficulty with complex reasoning chains
ChatGPT performs well on straightforward reasoning tasks but struggles when a problem requires many steps in sequence, each depending on the previous one. It can lose track of constraints, make an error early that compounds into a wrong final answer, or take a shortcut that seems plausible but skips a necessary step.
Breaking complex tasks into smaller, sequential steps with a review at each stage produces better results than asking for everything at once. Treat ChatGPT's output on complex reasoning tasks as a draft to review rather than a final answer.
What these weaknesses mean in practice
For most everyday tasks, the weaknesses above are manageable. Drafting a document, explaining a concept, brainstorming options, or summarizing a text are all within ChatGPT's strengths. The problems arise when you take its output directly into high-stakes use without checking. A legal argument built on a fabricated case citation, a financial model using wrong figures, or a project plan based on a misunderstood constraint are all real risks.
The answer is not to avoid ChatGPT but to understand which output needs verification and which does not. A compelling draft headline probably does not need checking. A specific regulation number definitely does. For comparisons with other tools, see ChatGPT alternatives and Claude vs ChatGPT.
Record what ChatGPT gets wrong so it does not happen twice
fenbs keeps a Lessons learned record: what went wrong, what the correct approach is, and what to check next time. When a connected assistant reads the project context, it reads the lessons first. You can also write standing rules in Decisions and rules, such as "always verify population figures against the US Census Bureau site." Create a free account and start recording lessons after your next session.
Create a free accountFree for one person · No credit card · Works with Claude, ChatGPT, Cursor and more
How to track ChatGPT's limits with fenbs
- Create a free account at fenbs.ai.
- Add the project you use ChatGPT for most. Write the goal and the tasks.
- In Decisions and rules, write the standing checks that apply: which facts must be verified, which sources are authoritative, which formats are required.
- When ChatGPT produces a mistake you catch, record it in Lessons learned: what it got wrong, what the correct answer was, what to check next time.
- Connect ChatGPT from Integrations. Before each session, your assistant reads the rules and lessons first.
fenbs does not fix the model. It gives you a place to record what you have learned about working with it, so the same mistakes are less likely to happen again.