How to Write a TOK Claim That Is Not Generic
This page turns the video into a StudyIB lesson note you can scan before drafting. Use it to test whether your TOK reasoning is actually specific, comparative, and examiner-facing.
What This Video Covers
The Generic Claim Problem
Many TOK claims sound generic because they try to be true everywhere. A stronger TOK claim has a condition.
Generic ≠ Simple
A claim can be simple and still be strong. The problem is not short wording.
Claim As A Testable Idea
Think of a TOK claim as a testable idea about knowledge. It should make a statement about how knowledge is produced, trusted, interpreted, or limited.
The Three-Part Claim
Use three parts: knowledge action, condition, and consequence. What happens to knowledge, under what condition, and why does that matter?
Bad Claim: Evidence Is Important
Evidence is important is too broad. It is true, but it does not tell us what kind of evidence, which area of knowledge, or what problem is being tested.
Better Claim: Evidence Builds Trust
A stronger claim says evidence can increase trust when the method for collecting it is transparent. Now the claim has a condition that can be tested.
Before You Draft
Do not treat this as a paragraph to copy. Treat it as a planning and diagnostic tool: check whether your claim has a condition, a knowledge mechanism, a limit, and a reason the example matters.
If you want more annotated TOK examples, examiner-style feedback support, and planning tools, use the TOK Bundle Link.