I feel like a jerk... in General geocaching topics Posted April 18, 2011 A reviewer, I am told, DOES NOT receive maintenance logs, therefore, a multitude of MN logs is just a number of logs. The NA log is necessary to As I understand it, reviewers do NOT receive notifications for "Needs Maintenance" logs; the only logs they get notifications for are "Needs Archived". Reviewers can also, as I understand it, pull up lists of caches which are disabled, and a reviewer who's doing his or her job correctly will periodically do a check for those, and archive them if the owner has had the cache disabled for too long. Our local review is good about that - when a cache has been left disabled for too long, s/he archives it with a public note saying something to the effect of "Since this cache has been disabled for so long, I'm archiving it to keep it from showing up in searches. If the owner wishes to correct the situation, please contact me." S/he is also really fair with "Needs Archived" requests due to lack of maintenance or too many DNFs - usually what happens is the reviewer disables it, and gives the CO 30 days to replace or fix it. If the CO doesn't take care of it, then it gets archived. My rule of thumb is usually if the cache needs maintenance, and there are no prior NM logs, then I post a NM and put the cache on my watchlist. If I see that another cacher (not the CO) has fixed things, or that I was mistaken, I delete my NM log. If it doesn't get fixed, but the cache is still findable, I either don't do anything more, or (if the cache is close enough to me and accessible enough) I may take care of the issue myself (replace a logbook or pencil, that sort of thing). If the NM issue was that the cache is supposed to be easy but suddenly started getting a lot of DNFs, and/or it's verifiably missing, and the CO has been on the site within, say, the past year, then I post a NM, wait a month or so to see if they respond... if they don't, THEN I'll post a NA. I won't don't a NA as my first action unless: 1) the cache appears to be missing, or has some other "fatal" issue, and CO hasn't been on the site for a couple of years - especially if s/he has other caches that have been archived due to non-responsiveness 2)the cache appears to be missing and there's a previous NM log that's been ignored for a month or more 3) the cache is placed in violation of a Groundspeak rule (for example, on the grounds of a school).