Reviewers Role Regarding Maintenance
Reviewers do periodic sweeps to check for abandoned, unmaintained and long-disabled caches. This is a housekeeping duty, and is necessary to keep the game "clean & tidy".
Responding to a "Did Not Find" log
A DNF is a cache owner's nightmare, but is a reality, and needs to be dealt with. You, as the cache owner need to be the judge, and decide what to do. The obvious "first prize" is to quickly check on your cache, and if it's there log a note of reassurance, or replace it if it's missing. But that's not always possible within a short time frame, especially for more remote caches.
If you can't get there quickly, you need to decide whether to disable the cache (to avoid others having the same disappointment), or to "wait and see..."
Consider the difficulty of your hide - some challenging hides have many DNF's which aren't a cause for concern.
Consider the previous "found" history of your cache - if everybody's been finding it easily, it's probably gone.
Consider the experience and determination of the cacher - would you have expected them to find it.
Consider the risks pertinent to that location - eg if it's a high muggle spot, it's probably been stolen.
Try contacting the cacher and find out more - to help decide whether it's still there or not. Maybe they were looking in the wrong place.
If you think it's still there - you could wait and see, but there could be the risk of frustrating other cachers.
If you think it's gone - temporarily disable the cache.
When you can't find a cache, consider when to log a DNF versus when to log a note. We recommend that you only log a DNF if you got to the location, searched for the cache properly, and couldn't find it. Writing DNF’s or Notes are as important as Found logs. These notes provide a cache owner with up to date information on the status of their cache and any possible problems. Don’t ever be too embarrassed to log a DNF.
If your cache has gone missing, and it had a travel bug or geocoin in it - it's common courtesy to drop the traveller's owner an apologetic note, and mark it as "missing".
Responding to criticism of your cache
Yes, criticism happens, but obviously relative to the quality of the cache experience you've created. Great caches are rarely criticized, and lame caches - well, they get what they deserve. You need to decide how to react, but our advice is to remember that it's only a game - don't take it to heart, and don't overreact. Consider what's been said with an open mind - maybe he/she is right. Sometimes the "finder's" experience is very different to the "hider's" intention. A simple issue like battling to find the right road could cause a negative experience, and can be easily solved. You can learn from criticism too. Also consider from who it comes - some cachers are naturally arrogant and offensive. Should you feel that the criticism is unwarranted, then you have a choice of actions.
- You could ignore it, and move on.
- You, as the cache owner, could delete the offending log - that's your right, but doesn't win you any friends.
- You could ask the cacher to amend their log, and tone it down - sometimes works.
If you disagree with a log, is to let it stand, but post a note for everyone to see politely countering the offending opinions, and move on.
Obviously rude logs should be deleted by default, but always follow this up with an email to the logger explaining your actions and keep a copy of the original log. Keep it polite.
Keep your listing up to date
Things change, and you need to update your listing when necessary. If you replace a muggled cache, or change anything at the location - did the co-ords change? If so, change them using a "co-ords change" log entry. Is it still the same size? Does a new hide affect the hint? It's very frustrating to search for what you think is a regular size cache, but has been replaced with a micro, and the old hint is irrelevant and misleading. Remember to update!
Controlling your listing
As the cache owner, you control the quality and validity of logs on your cache listing. Groundspeak tries to have the minimum of rules so that we can all play the game with as much flexibility as possible. For example - When finding remnants of a muggled cache, some cachers will log a find, most won't. Some cache owners will allow such logs, and some won't. But there are some generally accepted norms and practices, which aren't Groundspeak rules. Generally, one find per cache listing, and log a find only if you've signed the logbook. However you choose to deal with logs on your caches, please be courteous and patient. Even if others don't play the game the way you'd like them to.
Reviewers (and Groundspeak) are not log policemen. They will only take action regarding a log if it violates the Groundspeak Terms of Use - like bad language, attack on another cacher, etc.
Temporarily disabling a cache
This is the cache owner's way of telling others "don't hunt my cache right now - it's got a problem", and avoiding frustration. There could be many reasons for disabling a cache, the common one's are:
- It's had multiple DNF's and needs to be checked.
- There have been reports of environmental damage, and you need to check.
- It's been muggled and needs to be replaced.
- It's temporarily inaccessible - eg: road washed away, construction in the area, high water levels, etc.
When disabling a cache, it's good to explain why in the disable log. This lets the community know what the issue is, and how long it's likely to be unavailable. When re-enabling the cache, it's also good to write something encouraging - like "Replaced and back in action. Enjoy!!"
Archiving a cache
When a cache is archived, it disappears from searches and lists, but is still available to view, and keeps all the history of its logs. There is no "stigma" with archiving a cache, and it's sometimes the right thing to do. There are various reasons for archiving a cache:
- The location was a poor choice, and it keeps getting muggled.
- The location has changed, and is no longer suitable for a cache.
- There are unforeseen safety or environmental or other considerations.
- Our initial hides are often amateurish, and we outgrow them. If it can't be upgraded, archive it and do better next time.
So, if a cache is not working properly, or not up to your growing standards and you can't correct it, then archive it and move on. But always make sure there are no cache remnants left - we don't want to leave geo-litter lying around.
Owner Maintenance log
When you maintain your cache, or do a routine check on it, always log an "Owner Maintenance" log. There are two main reasons:
- It reassures others that your cache is being cared for, and is likely to be in good shape if they hunt it.
- It removes the "needs maintenance" icon from your listing.
Needs Archived
NA logs are emailed to reviewers, and reviewers will react on them. This is an extreme measure, and should only be used as a last resort when reviewer intervention is deemed necessary. This could be for a variety of reasons:
- The cache violates the guidelines, eg: trespassing, breaking laws, illegal hide, etc, etc.
- The cache is abandoned, has a problem, and NM logs have elicited no response from the owner.
NA logs don't make friends, so use them with great care. They can be abused - we've seen NA logs for caches which someone couldn't find, and that's how they've expressed their frustration!! If you get an NA log on one of your caches - don't overreact, leave it in the hands of the reviewer.
The caches in this series are:-
- GC3QACA - Geocaching Etiquette - Hiding a Geocache
- GC3QE60 - Geocaching Etiquette - Submitting a new Cache
- GC3E5N1 - Geocaching Etiquette - The Cache Hunt
- GC3Q7RH - Geocaching Etiquette - Online Logging
- GC3729Y - Geocaching Etiquette - The Compleat Geocacher