Send in form before or after placing?

[+Phil&Phil2008]

Question answered.

Edited March 30, 2008 by Phil&Phil2008

[+Cardinal Red]

You know that some caches get published very quickly? You know that some cachers are obsessed with being FTF? They rush out the door the instant the brand new listing pops up.

 

When you submit the cach page indicating the cache is in place and ready to go, don't you think it's pretty obvious that's the way you should do it? Unless you want to send a potential FTF hound on a wild goose chase. Great fun.

 

No question is so difficult to answer as that to which the answer is obvious. — George Bernard Shaw

[Motorcycle_Mama]

Wow that's a lot of extra spaces and stuff.

 

Anyway, the cache should be in place BEFORE you submit the cache for review.

 

Whoops ... too slow!

Edited March 29, 2008 by Motorcycle_Mama

[Keystone]

One of the first things you should do when thinking about hiding a cache is to read the listing guidelines. In this section of the guidelines, you will find the answer to your question:

 

Your cache should be in place and ready to hunt at the time your cache page is submitted for review. If for any reason it is not ready, please either disable your cache page so that it won’t be seen by the reviewer until ready, or include a “note to reviewer” to explain your special circumstances (for example, waiting for a permit from a land manager).

[+Phil&Phil2008]

Hahahha... I guess you 2 are right.. alright I'm dumb.. thanks!

Edited March 30, 2008 by Phil&Phil2008

[Mushtang]

After.

[+edscott]

Note that you can do the cache page beforehand, just do not check the box that puts it on the reviewer's list of caches to be approved. This gives you the opportunity to place the cache, read the page again to be sure it is how you want it, then check the box and let 'er go.

[+FireRef]

Even having read the guidelines, the problem that comes up with this is that if you place the cache, then it gets rejected for some reason you have no idea about (like not allowed in that area by something the reviewer knows, or more likely, there's a part of a multi cache in the area too close). You have to go back and move it. It seems like, although I'm not sure how this would work, it would be better to get approval for the site first, and then go place it.

 

Again, I know this isn't what the guidelines say. From what I remember, reviewers have said before that they are willing to answer questions, like "is this site ok for a cache", sometimes. Am I correct?

[+gof1]

I have found that if I have a question about a location the local reviewer is always happy to answer it.

It also helps to solve any puzzle caches or multis in the area before you hide a cache, but that isn't always easy.

[+keehotee]

the problem that comes up with this is that if you place the cache, then it gets rejected for some reason you have no idea about (like not allowed in that area by something the reviewer knows, or more likely, there's a part of a multi cache in the area too close). You have to go back and move it.

 

But you have to place your caches so they're within easy maintenance distance anyway....so where's the problem?

What do you do if a cacher posts a Needs Maintenance log - just archive it and not bother because it's too far to go?

[Motorcycle_Mama]

To the OP, please don't edit your question after you've gotten responses. It makes it difficult for people searching for the same question later on.