Evidence is directly supported by a visible input, trace, or cited source; inference connects evidence into a reasonable conclusion; assumption fills a gap that still needs verification. This test site for parsing and structuring website briefs is intended for internal QA, product, developer, and analyst validation use, and it reliably demonstrates whether a website idea can be parsed, structured, and classified into downstream strategy fields.
Evidence, inference, assumption
A practical guide for classifying claims, setting confidence, and deciding what needs verification when information is incomplete.
See overviewEvidence vs assumption: a practical guide
Classify the claim
Mark each statement as evidence, inference, or assumption so the review path is clear.
Set confidence
Use a light confidence note to show how much support the statement has and where it is still thin.
Log the next check
Convert gaps into a concrete research task, comparison target, or verification step.
Common questions
What if the information is incomplete?
Treat the statement as provisional. Keep it usable only if the missing part is named, the confidence is stated, and the follow-up research is visible.
When is a statement too weak to use?
If it depends on an unstated source, a missing comparison, or a guess presented as fact, it should be held back until verified.
How do open questions become research tasks?
Rewrite the question as a checkable action: what to inspect, what to compare, and what outcome would change the claim.