
Our method
The standard itself: how long we use gear before we write, which conditions we record, how timed results are reported, and what counts as a failure.
This page is the standard itself, not a description of one. It sets out how we test survival gear at rationalsurvivor.com: how an item enters the queue, how long it is used before we write a word, which conditions get recorded, how timed results are reported, and what we refuse to test at all.
Rational Survivor is a new publication. That means most of our tests run on a single sample, and a single sample can only support certain kinds of claim. Where that is the case, the article says so in the same sentence as the result rather than in a footnote.
Everything below is checkable against what we publish. If a piece on this site breaks one of these rules, tell us — the last section explains exactly how to make that stick.
Seven commitments
Seven commitments. Every gear piece on this site is held to all of them.
Commitment 01
Each category has a minimum use period, stated in the article. Below that threshold, the piece is labelled a first look and carries no verdict.
Commitment 02
Temperature, precipitation, wind, elevation, water source, operator state. A result without conditions is an anecdote.
Commitment 03
Median, slowest attempt, number of attempts, number of failures.
Commitment 04
A failure that happened once is reported as having happened once, and it stays in the article afterwards.
Commitment 05
When it is one, it says one.
Commitment 06
Boil times, bleach ratios, food spoilage windows and carbon monoxide distances come from published agency guidance, linked to the source.
Commitment 07
Our figures carry conditions. Agency figures carry links. They never share a sentence without attribution.
The reasoning behind these, and the wider rules on sourcing and corrections, sit in our editorial policy. Finished tests are collected under gear tested.
An item enters the queue when it maps to a task we already teach, not when a press release lands.
Those tasks come from the drills in our guides: make one gallon (3.8 L) of doubtful water safe to drink in under 30 minutes, get a self-sustaining flame in rain, carry 72 hours of supplies 3 miles (5 km) on pavement, keep a medical device running through an eight-hour night. If a product does not address a task like one of those, it does not get tested — however well it sells.
Where the gear comes from.
Before the first use, we write down the manufacturer’s claims verbatim — rated temperature range, flow rate, runtime, capacity, duty cycle, service interval. The test is then run against that claim. This matters because a product that never claimed to work at 10 °F (-12 °C) should not be criticised for failing there, and a product that did claim it should be held to it.
Most gear works on day one in a kitchen. The useful information arrives later. These are the floors we hold ourselves to before an item can carry a verdict or appear in a recommendation.
If we have not met the floor, the article says so at the top and is published as a first look: observations, specifications, claims recorded, no verdict and no place in any recommendation.
A time or a result means nothing without the conditions attached to it. The following are recorded at the test site, at the time, on paper or in a phone note before the session ends — never reconstructed from memory afterwards.
The corollary matters as much as the list. A condition we did not record is never implied later. If we did not measure wind, the article says wind was not measured — it does not say "in calm conditions".
Timed tasks are where gear writing usually goes wrong, because one lucky attempt makes a better headline than five honest ones.
How a task is run.
How it is reported.
We do not re-run a task until a number looks good and then print that one. If a session produces an ugly spread, the ugly spread is the result.
Failure is defined before testing starts, in four classes, so that the definition cannot move to suit the outcome.
Three rules govern what happens next. A failure is written down at the time it occurs, not reconstructed later. A failure is never deleted because a replacement unit worked — if a manufacturer sends a replacement, the original failure stays in the article and the replacement is reported as a second sample. And a failure is never traded away: we do not remove findings in exchange for units, access or advertising.
Most tests on this site run on one unit. That is the honest position for a new publication, and pretending otherwise would undermine everything else on this page. So the sample size appears in the article, next to the result.
What a sample of one can legitimately show:
What a sample of one cannot show:
So one broken sample is written as "this unit failed under these conditions after this much use", never as "this model is unreliable". The two sentences look similar and mean entirely different things.
For the same reason, we do not publish scores out of ten. A single number conceals exactly what the conditions section exists to reveal. A recommendation here is always scoped: for this task, at this temperature, for a person carrying this load. Where a question genuinely needs a fleet of units and several years to answer, the honest answer is that we do not know yet, and that is what we will write.
There are two kinds of number on this site and they are never blended.
Agency figures carry a link to the primary source. Our measurements carry conditions, a spread and a sample size. If a sentence contains both, it attributes both.
Safety-critical figures are never ours. We do not derive them from our own testing, and we do not round, simplify or "update" them. These come from published guidance:
When published guidance changes, the guidance wins over our older article. The page is corrected in place and carries a dated note saying what changed and whether the advice changed with it. Manufacturer claims are a third category again, always labelled as claims — including certification marks, which we report by the standard’s name rather than restating as our own finding.
A testing standard is defined as much by its limits as by its protocol. We do not run the following, and we will not imply that we have.
If you are deciding where to start rather than what to buy, start here is the better page — the editorial line on this site is that skills beat stockpiles, and most of our drills need no new gear at all.
A published standard is worth little without a route to enforce it. If a result here is wrong, we want to know, and corrections take priority over everything else in the inbox.
Write to hello@rationalsurvivor.com with Correction or Challenge at the front of the subject line, and include:
What happens then:
What we will not do: remove an unfavourable finding because a brand asked, swap a spread for a flattering best attempt, quietly delete a page instead of correcting it, or treat "our lab says otherwise" as evidence without the conditions and sample size behind it.
Full routes and response times are on the contact page, and the standards this testing protocol sits inside are in our editorial policy.
See the results
Every published test carries its conditions, its sample size and its failures. If a piece breaks one of these rules, tell us.