Lesson 0.4Lesson 0.4 · Meet Claude
When Not to Use Claude
The professional edge is not just knowing what Claude can do - it is knowing where to stop relying on it, and holding that line as the stakes rise.
Knowing where to stop relying on Claude is not a limitation on the skill. It is the skill.
This whole course is an argument for using Claude - widely, daily, across the practice. This lesson is where we draw the other line, and it is just as important, because the fastest way to damage your work or your name with a brilliant assistant is to trust it with the wrong thing. The boundary is not a short list of forbidden topics; it is a judgement, and building that judgement is the point of everything you have learned so far.
The line follows straight from Lesson 0.2: Claude is a plausibility engine, not a truth engine, with no professional accountability and no ability to check the world. So it is at its most dangerous exactly where a confident, fluent, wrong answer costs the most - a code ruling, a structural number, a dimension, a client's confidence, the design decision itself. 'When not to use Claude' rarely means 'never open it here'. It means 'never rely on it here unchecked'. Learn where that applies, and how hard, and you have the discipline that keeps AI-assisted practice professional.
Not 'never open it' -- 'never rely on it unchecked'. Facts: verify. Decision: yours. Data: protect.
The boundary is a judgement, not a blocklist
It is tempting to want a tidy list of topics Claude is banned from - but that is not how the boundary works, and a list would fail you the moment a real task did not match it. The honest rule is about reliance, not subject matter. You can happily ask Claude about a fire code, a structural approach or a client's programme; what you must not do is treat what comes back as settled truth without checking it, in proportion to what a wrong answer would cost. So the same topic can be perfectly fine to explore and dangerous to trust - and telling those apart, task by task, is the judgement this lesson builds.
Everything traces back to what Claude is. It produces plausible continuations, not verified facts; it cannot walk your site, phone the authority, open the actual standard, or measure anything; it carries no professional or legal responsibility, because responsibility belongs to the person who signs; and it does not truly know your client, your firm or your project unless you have put that in the context window. None of this makes it useless - it makes it an assistant with a specific shape, brilliant at some things and constitutionally unfit for others.
So 'when not to use Claude' resolves into a few honest categories. There is the check-hard zone - high-stakes facts, legal, structural and code rulings, precise measurement, confidential data - where you may use Claude but must verify or protect, hard, before anything ships. And there is the genuine no-go - the design decision itself, the professional judgement, the accountability - which is not Claude's to take at all, at any tier, however good the draft it hands you. The next two sections walk both, and the last gives you the instrument for deciding how hard to check anything in between. The goal is not caution for its own sake; it is knowing precisely where your own eyes and signature are non-negotiable.
The check-hard zone: facts, rulings, measurement, data
Start with the zone where Claude is genuinely useful but must never be trusted unchecked. The figure lays out the recurring cases; each is worth naming plainly.
High-stakes facts, unverified. Any specific number, date, name, citation or clause that matters and that you have not confirmed at its source is a hazard, because this is exactly where hallucination lives. Use Claude to find and explain such things, never to be the final word on them. Legal, structural and code rulings. Claude is not a lawyer, a structural engineer, a quantity surveyor or a building-code official, and its output is a draft or a lead, never a ruling or a signed-off calculation. It can help you understand a clause or set up a calculation; it cannot decide that your egress complies or that a beam is adequate. For anything that must satisfy the law or carry a load, the qualified professional and the primary source rule - Module 2 makes this its cardinal rule.
Precise measurement from drawings. Claude reads images and PDFs and will describe a plan usefully, but it cannot measure reliably from one, and it cannot read fine CAD linework - a dimension it 'reads' off a drawing may simply be wrong. Never take a measurement from Claude; take it from the model, the dimensioned drawing or the site. Confidential and client data. On consumer plans your conversations may be used to improve Claude unless you opt out, so pasting a client's private data, personal information or anything under an NDA without checking your plan's data settings is a real risk. Strip or anonymise identifiers, turn off training if you need to, keep genuinely sensitive work on business or API tiers with stronger terms, and when in doubt keep it out - the ground truth is in Module 10.1 and in your plan's current settings.
What unites these is not that Claude is useless on them - it is often very helpful - but that the cost of a confident-wrong answer is high and silent. In this zone, Claude drafts and points; you verify, protect and decide.
Use it here, yes - but verify at source or protect the data before anything ships.
The decision is yours - and the student's trap
Beyond the check-hard zone sits something different in kind - not a fact to verify but a thing that is simply not Claude's to do. The genuine design decision is yours. Claude can generate concept directions, lay out the trade-offs between schemes, articulate a rationale and pressure-test an idea - all genuinely useful, and Module 4 is built on it. What it cannot do is care about this client on this site, hold the accountability for the choice, or tell a truly good idea from a merely plausible one. If you let Claude make the call - pick the parti, settle the material, resolve the plan - you have outsourced the one thing that is actually your job, and you will ship work you cannot defend when a client, a peer or a court asks why. Use it to widen and sharpen your options; keep the choosing, and the owning, for yourself.
There is a second no-go that matters especially for students, and it is quieter and more corrosive. Do not lean on Claude instead of learning. The trap is real: Claude can write the essay, solve the problem, produce the analysis, and hand you a finished-looking result before you have understood any of it. Do that routinely and you hollow out the very skills - designing, researching, reasoning, writing - that you will one day need in order to judge Claude's output at all. It is a vicious circle: the less you can do yourself, the less you can tell when Claude is wrong, which is precisely when you most need to.
The way through is not abstinence but role. Use Claude as a tutor and a drafting partner alongside your own effort - to explain what you do not understand, to critique work you have already attempted, to show you a second way - not as a machine for producing answers you skip the learning of. A student who directs and judges Claude while genuinely building their own craft enters practice doubly strong. One who let it do the thinking enters unable to catch its mistakes, which is the least employable state of all.
Drawing the line: scrutiny scales with stakes
So where, exactly, is the line? The honest answer is that it moves - and the instrument for finding it is the one this module keeps returning to: scrutiny scales with stakes. The figure plots it. On one axis is what a wrong answer would cost, from trivial to severe; on the other is how hard you check, from a glance to line-by-line verification at the source. Good practice keeps you on the diagonal: cheap-to-be-wrong tasks get a light touch, expensive-to-be-wrong tasks get relentless checking, and you consciously place each task before you trust its output.
Down in the low-stakes corner sit the divergent, generative jobs - a mood-word list, a brainstorm of directions, a first draft of your own prose, a reformatted table. There is no single truth to miss and little cost if a line is off, so let Claude run and skim the result. Climbing the diagonal you pass client emails and option comparisons, which want a proper read and a sanity-check. Up in the high-stakes corner sit the things that go wrong loudly and expensively: a specification bound for site, a cost that drives a decision, a structural figure, a fire-egress clause. Here a confident-wrong answer is a genuine liability, so you verify every claim against the actual source - or you do not use Claude's output at all.
This is why 'when not to use Claude' is a judgement rather than a rule you can print on a card. The same tool that you trust loosely for a brainstorm you interrogate line by line for a code clause, and the skill is matching the two - which is exactly where your professional training gives you an edge no prompt-hobbyist has. Keep the whole of Module 0 in one hand: Claude is a brilliant intern you direct and judge (0.1), a plausibility engine not a truth engine (0.2), available in tiers none of which replace you (0.3), and off-limits as the decider and unreliable unchecked on high-stakes facts (0.4). Hold that, and you are ready to start actually working with it.
Same tool: loose for a brainstorm, line-by-line for a code clause. Match scrutiny to the cost of wrong.
Human-in-the-loop verification
The person checks and owns every high-stakes output
Claude drafts and points to sources; you confirm at the source and sign. Non-negotiable wherever a wrong answer carries real cost.
Data settings / training opt-out
Plan controls over whether chats train the model
On consumer plans, opt out and anonymise before sharing client data; business and API tiers offer stronger terms. Check current settings - they change.
Multimodal limits
What Claude can and cannot read from images and drawings
It describes plans and photos usefully but cannot measure precisely or read fine CAD. Never take a dimension from an image.
Scrutiny-to-stakes
Matching verification effort to what a wrong answer costs
Light on divergent low-stakes work, ruthless on anything bound for site, law or a load. The core professional discipline of the course.
Workshop - draw your own line
The boundary is personal to your practice, so you will draw it yourself. Take real tasks from your own work, place them on the stakes-and-scrutiny map, and turn the result into a short set of rules you will actually follow. About twenty minutes, no special tools.
Just a notebook and honesty about your own work. You can sketch the two-axis map from the figure on paper.
Goal: turn 'scrutiny scales with stakes' into your own working rules Inputs: 8-10 real tasks you might hand Claude + a notebook Time: ~20 minutes
- 1List eight to ten real tasks you could imagine giving Claude across a project - from a mood-word list to summarising a byelaw to drafting a spec to comparing schemes.
- 2For each, write down what a confident-wrong answer would actually cost - trivial, awkward, or serious - and be honest about the worst case.
- 3Place each task on the stakes-and-scrutiny map: low-cost tasks you will skim, high-cost tasks you will verify at the source line by line.
- 4Flag any task that is a genuine no-go - the design decision itself, anything you would sign for, anything needing a qualified professional's ruling - and mark that Claude assists but never decides.
- 5Flag any task involving confidential or client data, and note what you must do first: anonymise, check plan settings, or keep it out entirely.
- 6Write five plain rules for yourself - your personal 'when not to rely on Claude unchecked' - and keep them where you will see them.
You’ll walk away with
Your own stakes-and-scrutiny map of real tasks, with no-go and confidential-data tasks flagged, plus five personal rules for where you will and will not rely on Claude unchecked.
Three altitudes on the same idea
Read the band that fits you — or all three.
Your seal is the line Claude never crosses. Use it to research a clause, draft a spec or set up a calculation, but the ruling that your egress complies, the number a beam carries, the decision a client relies on - those are yours to verify and to own, because you sign and you are liable. Keep confidential project data off consumer plans without checking settings. The more a task touches law, safety or accountability, the harder your own eyes work.
Never let Claude be the final word on a fact a client or contractor will act on - a fire rating, a dimension off a drawing, a lead time, a price. It cannot measure from an image and will state a plausible figure as if it were checked, so confirm specifications and quantities at the source. And guard client information: strip names and personal details before pasting, and check your plan's data settings before sharing anything sensitive about a project or a home.
The one use to refuse is Claude instead of learning. Letting it write the essay or solve the problem before you have understood it quietly destroys the skills you will need to judge its output - and examiners and employers can tell. Use it to explain, to critique what you have already attempted, and to show a second approach, never as an answer machine. Build your own craft first; direct Claude with it, and you will always be able to catch its mistakes.
“As Claude gets more capable, the list of things you should not trust it with keeps shrinking.”
Do it yourself
Find the line.
- 1Why is 'when not to use Claude' a judgement about reliance rather than a list of banned topics?
- 2Name three tasks in the check-hard zone and say what you must do before trusting the output.
- 3Why can Claude never take the genuine design decision, however good its draft?
- 4What is the student's trap, and how do you use Claude without falling into it?
- 5How does the stakes-and-scrutiny map tell you how hard to check a given task?
The one line to carry out
Peer-reviewed journals & authoritative standards
- 01Hallucination (artificial intelligence) — Wikipedia, 2026.
- 02Privacy policy — Anthropic, 2026.
- 03Confidentiality — Wikipedia, 2026.
- 04National Building Code of India — Wikipedia, 2026.
That completes Module 0: you know what Claude is, how it thinks, which tier to reach for, and where to stop relying on it. From here we get practical - Module 1 begins with how to actually talk to Claude, prompting it well for design work.
The author
Amogh N P
Architect, interior designer, and creative polymath. Studio Matrx began in his notebooks — his vision of design made honest, useful, and open to everyone. Its Academy is written and taught in his memory, and free, forever.
More about Amogh →