What Claude Isn’t Good At
Setting realistic expectations so you know when to double-check
Knowing the edges
Understanding what Claude struggles with is just as important as knowing what it’s good at. This isn’t about losing trust in the tool — it’s about knowing exactly when to slow down and double-check its work.
It can sound confident and still be wrong
This is the single most important thing to remember. Claude can state something incorrect in the exact same confident, well-written tone as something correct. It’s not lying on purpose — it’s generating text that sounds right based on patterns, and sometimes that text doesn’t match reality.
Watch out: Never assume something is true just because Claude said it clearly and confidently. Confidence in tone is not the same as accuracy.
Facts, numbers, and dates need checking
Claude can get specific facts wrong — a date, a statistic, a person’s title, a company’s founding year. It’s especially worth double-checking anything that will go in front of a client, a regulator, or leadership. Treat Claude’s facts the way you’d treat a fact a new hire told you: probably fine, but worth a quick verification for anything important.
It doesn’t know your company’s private details
Claude doesn’t automatically know your internal policies, your specific client history, or information behind your company’s login screens — unless you provide that information in the conversation, or your company has connected specific tools to it. If you ask a question assuming it “just knows” your workplace, you may get a generic or made-up-sounding answer.
It can’t take real-world action on its own
By default, Claude can’t send an email, book a meeting, or make a purchase for you. It can draft the email or suggest the meeting time — but a human (you) presses send. This is a safety feature, not a limitation to work around.
Recent events may be outside what it knows
Claude’s knowledge comes from what it learned during training, plus anything you tell it in the conversation. Without a live web search feature turned on, it may not know about very recent news or changes.
| Situation | What to do |
|---|---|
| A specific number, date, or statistic | Verify it against your own source before using it |
| A question about your company’s private policy | Paste the policy in, don’t assume Claude already knows it |
| Something that needs to be sent or submitted | Have Claude draft it — you review and send it |
| Very recent news | Check a live source; don’t assume Claude has seen it |
Key idea: Use Claude as a fast first draft and a thinking partner — not as the final word on facts that matter.
Try it: Next time Claude gives you a specific fact, date, or number you plan to use, spend 30 seconds confirming it against a source you trust before sending it along.