Quick Answer: Log a DNF when you did not find it and you are not certain why. Log a Needs Maintenance when you found the container but it is damaged, wet, or the log is full. Log a Needs Archived only when there is a real reason the cache cannot exist there anymore — the tree was cut, the wall was demolished, the area is now fenced or posted. Two or three DNFs from experienced cachers is the signal owners actually act on, so an honest DNF is more useful than a silent walk-away.

The most common mistake is not choosing the wrong log type. It is logging nothing at all.

What is the difference between a DNF and a Needs Maintenance?

They answer different questions, and the platform treats them differently.

A DNF — Did Not Find — says: I searched, and I came up empty. It makes no claim about whether the cache exists. Maybe it is gone. Maybe you were three feet off. Maybe it was a nano on a guardrail with 200 identical bolts. A DNF is a report about your search, not about the cache.

A Needs Maintenance says: I found it, and something is wrong with it. Cracked container, soaked log, missing lid, log full with no room to sign, camouflage fallen off. You had eyes on it. This log generates an attribute on the cache page and a notification to the owner.

A Needs Archived says: this cache should not be here. It is escalation. It goes to the owner and to a reviewer, and reviewers do act on it.

Why the distinction matters: DNFs accumulate into a pattern. One DNF means nothing — plenty of caches get found the next day by someone who looked six inches to the left. Three consecutive DNFs from experienced cachers is a strong signal, and most active owners check on that. If you skip the DNF because you feel embarrassed, you have removed a data point from the pattern that would have helped the next five people.

How certain do you need to be before saying it is gone?

More certain than “I looked for ten minutes.” Here is a workable threshold.

Not enough to declare it missing:

• You searched but the hint was vague and the GPS was bouncing.
• The area has multiple plausible hiding spots and you checked some of them.
• It was dark, raining, or you had kids getting impatient.
• The last find was recent and there is no obvious disturbance.

Enough to say the cache is probably gone:

• The described hiding spot is intact and clearly empty — the hint says “under the third fence post” and the third fence post has nothing under it.
• Multiple recent DNFs from experienced finders, and yours matches theirs.
• There is evidence of removal: broken magnet still stuck to the sign, a cut cable, an obviously disturbed spot.

Enough for a Needs Archived:

• The host is gone. The tree was felled, the wall was demolished, the bench was removed.
• Access changed permanently — new fence, new construction, private property signage, area permanently closed.
• The cache has been missing for months, the owner has not responded to several Needs Maintenance logs, and the account looks inactive.

When in doubt, DNF with detail. A detailed DNF that says exactly what you checked is far more useful to the owner than a confident wrong guess.

What makes a DNF log genuinely useful?

Specificity. “Couldn’t find it, will try again” is nearly worthless to an owner.

Include what you checked. “Searched the base of all four posts and the underside of the rail for about 20 minutes.” Now the owner knows whether you were in the right area, and the next finder knows where not to spend their time.

Include conditions. Heavy leaf cover, snow, standing water, high muggle traffic, GPS bouncing 40 feet under tree canopy. These explain a DNF that has nothing to do with the cache.

Include your confidence. “I’m fairly new to nanos, so this may well be me” versus “I’ve found 800 of these and the spot looks empty” tells the owner completely different things.

Note anything physically changed. Fresh landscaping, new construction, tree removal, mowing. Owners cannot see their caches from home, and this is the information they most need.

Keep it kind. The owner is a volunteer who placed a container in the woods for strangers to enjoy. A DNF is data, not a complaint.

What Nobody Tells You About DNF Etiquette

Logging a DNF does not embarrass you. It is the opposite — experienced cachers log DNFs freely because the number means nothing and the information means a lot. The people with the cleanest DNF-free records are often the ones who quietly walked away.

Do not log a DNF if you never really searched. Arriving at the parking coordinates, deciding the trail is too muddy and going home is not a DNF. It is a note, if anything. A DNF from someone who did not search dilutes the signal for everyone.

Do not throwdown. Placing your own replacement container because you could not find the original is one of the most disruptive things you can do — it creates a second cache the owner does not know about, and the original often turns up later. Log the DNF and move on.

Do not spoil it in the log. If you find it after a struggle, resist the urge to write the exact location. The whole point of the next person’s search is that it is a search.

One exception on Needs Archived: if there is a safety or permission problem — the cache is now on posted private land, or the search puts people in traffic — escalate immediately and without hesitation. That is not impatience, that is the system working.

FAQ: Geocaching Log Type Questions, Answered

If I DNF and then find it later, should I delete the DNF?

No. Leave it and add the find. The DNF is an accurate record of that visit, and the pair of logs together is genuinely useful — it tells the next struggling searcher that the cache is findable but tricky.

What if the owner asks me to delete my Needs Maintenance?

Owners can disable the attribute themselves once they have fixed the problem, and that is the normal flow. You are not obliged to remove an accurate log, but if the issue was resolved quickly, adding a follow-up note saying so is a good-faith thing to do.

How long should I wait before posting Needs Archived on an unmaintained cache?

Give the owner a real chance: a Needs Maintenance log, then several weeks to a couple of months with no response and no owner activity, and ideally a pattern of DNFs behind you. Reviewers generally prefer escalation to be the last step after the owner has clearly gone quiet, not the first.

TL;DR:

• DNF = I searched and did not find it. Log it honestly; the pattern is what helps.
• Needs Maintenance = I found it and it is damaged, wet or full.
• Needs Archived = the cache genuinely cannot be there anymore, or the owner has gone silent for months.
• Detail beats certainty: say what you checked, the conditions, and how confident you are.
• Never throw down a replacement container, and escalate immediately for safety or permission problems.

The logs are the only communication channel the game has. A specific DNF from you is what saves the next four people a wasted afternoon.