Quick Answer: A run of did-not-find logs on a cache that is genuinely still in place usually comes down to four things: coordinates that drifted or were averaged badly, seasonal vegetation change that hid the container, a hint that made sense to you and to nobody else, and difficulty ratings that set the wrong search expectation. Three consecutive DNFs is the standard threshold for going to check - and when you do, take a photo of the hide so future checks take five minutes instead of an afternoon.

You hid it. You know exactly where it is. Three people in a row say it has gone.

Usually it has not, and the reason is on your side of the listing.

Why do coordinates drift when the cache has not moved?

Consumer GPS accuracy varies with sky visibility, and woodland is the worst case. Under a full canopy, position error routinely exceeds ten metres, which means the finder is searching a circle several times larger than the one you think you set.

Coordinates taken on a single visit inherit that visit’s error. If you recorded them on an overcast day under trees, you baked a systematic offset into the listing that every finder now has to overcome.

Averaging works but only if it is done properly - multiple readings across different times, ideally on different days, with the device stationary. A ten-second average is not an average.

Phone compasses add a second error on top of the first. Magnetic interference from nearby metal, vehicles, and power lines sends the arrow off by a large margin at exactly the moment the finder is closest.

Seasonal canopy makes this a moving target. A cache with acceptable accuracy in March, before leaf-out, can be genuinely hard to reach accurately in August, and then acceptable again in November.

The fix is to re-average on a clear day with the leaves off, and to check your posted coordinates against a fresh reading whenever you do a maintenance visit. A two-metre correction converts a frustrating hide into a fair one.

How seasonal change hides a cache you have not touched

Vegetation is the biggest single cause of seasonal DNF clusters. A hide that is obvious in April is behind a wall of nettles and bramble by August, and the finder is standing two metres away looking at green.

Late summer is peak concealment. Growth is at maximum, undergrowth is dense, and ground-level hides in particular become genuinely unreasonable rather than merely difficult.

Then the opposite problem arrives. Once leaves drop, a cache that was well camouflaged becomes visible to non-cachers, which is when containers actually go missing rather than merely being unfindable.

Ground movement matters too. Heavy rain, animals, and falling branches all shift small containers a metre or two without removing them, and a metre is enough when the search area is already dense.

Leaf litter buries flat containers completely in autumn. A cache sitting on the ground under a beech tree can be under several centimetres of leaves within a fortnight.

The practical response is a seasonal note in the listing. A line saying the hide is considerably harder between July and October, or that it is easier once leaves are down, sets expectations and prevents both frustration and unnecessary maintenance trips.

Hints, ratings, and the curse of knowledge

A hint written by the person who hid the cache is almost always too vague, because they cannot un-know where it is. Terms like near the base or under cover mean something specific to you and nothing to anyone else.

The test is whether the hint narrows the search area meaningfully. If a finder standing at ground zero could apply your hint and still have ten candidate spots, the hint has done nothing.

Good hints constrain height, material, or direction - roughly waist height, on the north side, behind the stone rather than the timber. These are unambiguous and still leave the find satisfying.

Difficulty and terrain ratings are a contract with the finder. A hide rated as easy that requires ten minutes of systematic searching will generate DNFs from people who reasonably concluded it was gone after three minutes.

Under-rating difficulty is far more damaging than over-rating it. A finder expecting a hard search will persist; a finder expecting an easy one will log a DNF and move on, and the cache acquires a false reputation.

Container size in the listing matters more than people credit. Someone searching for a small container will not spot a micro, and the difference between those two expectations is most of the search.

And read your own DNF logs for a pattern. When several people describe searching in the same wrong place, the listing is pointing them there - which is a listing problem with a fifteen-minute fix.

5 Mistakes Cache Owners Make Without Noticing

Mistake 1: Never revisiting after the initial hide. A cache is a physical object in weather. Containers crack, logs soak, and camouflage degrades, and no listing update substitutes for going and looking.

Mistake 2: Ignoring DNFs until someone posts a needs-maintenance. Three consecutive DNFs is the widely used threshold for a check. Waiting for a formal maintenance request means the cache spends weeks in a broken state.

Mistake 3: Not photographing the hide. A photo kept privately turns every future maintenance check into a five-minute job rather than an afternoon of searching your own cache - which is a genuinely common and embarrassing outcome.

Mistake 4: Writing the listing for people who already know the area. Local landmarks, informal path names, and parking descriptions that assume familiarity send visitors to the wrong approach entirely.

Mistake 5: Leaving the hint unchanged as the site changes. A hint referencing a fallen log is worthless once the log has rotted away, and hints referencing vegetation date badly within a single season.

The one that catches nearly everyone is the third. Cache owners routinely cannot find their own hides after two years, and the fix is one photograph taken on the day.

FAQ: DNF Logs and Cache Maintenance, Answered

How many did-not-find logs before I should check my cache?

Three consecutive DNFs is the widely used threshold. Two experienced cachers in a row is also worth acting on, particularly if their logs describe searching the right area.

Why are my coordinates off when I have not moved anything?

Coordinates taken in one visit under tree cover inherit that visit’s GPS error, which can exceed ten metres. Re-average across multiple readings on a clear day with leaves off, and check them on every maintenance visit.

Why does my cache suddenly get DNFs in late summer?

Vegetation. Growth peaks in late summer and a hide that is obvious in spring can be behind dense undergrowth by August. Add a seasonal note to the listing rather than moving the cache.

How do I write a hint that actually helps?

Constrain height, material, or direction - waist height, north side, behind stone not timber. A hint that leaves ten candidate spots at ground zero has done nothing, and hint writers systematically underestimate this.

What is the single most useful maintenance habit?

Photograph the hide when you place it and keep it privately. It turns every future check into a five-minute visit instead of a search for your own cache.

TL;DR:

• Most DNFs on a healthy cache come from coordinate error, seasonal vegetation, a vague hint, or a difficulty rating that set the wrong expectation.
• Re-average coordinates on a clear day with leaves off, and recheck them every maintenance visit.
• Late summer growth is peak concealment - add a seasonal note rather than relocating the cache.
• Hints must constrain height, material, or direction; under-rating difficulty causes more DNFs than over-rating it.
• Check after three consecutive DNFs, and photograph the hide the day you place it.

The cache is usually fine. The listing is what is broken.