General Information

When will my Geocache be published?

In Arizona, we have 3 Volunteers who review and publish geocaches.  We strive to begin review of geocaches within 7 days.  Typically, it is much sooner.  If some of your geocaches are published by one reviewer and some are still unpublished, please be patient.  The other reviewer will get to them as schedules permit.  If for some reason one reviewer gets behind, it is possible that another reviewer will help out. 

Please do NOT contact us via the messaging system. If you're corresponding regarding a cache you currently have in the review queue, communicate via Reviewer Notes so that the correspondence stays associated with the appropriate cache. Reviewer Notes are automatically removed when the cache is published, along with any photos attached to them.

For general correspondence, please contact us via the instructions in our profiles which are linked from the top right corner of this page. If you are corresponding regarding a geocache, always include the GCnumber. If you're going to send an email via Geocaching.com, please check the "I want to send my email address along with this message" box.

Include a complete Reviewer Note about your geocache

We ask all cache hiders to provide basic information in a Reviewer Note about their cache. In your Reviewer Note, please clearly and completely describe your cache in detail. Please include three categories of information including WHERE, WHAT, and HOW.

WHERE - Always explain the property your cache is placed on - both the ownership and the property use. Any cache should have permission as described in the Guidelines. (http://www.geocaching.com/about/guidelines.aspx#permission) Just because property does not have obvious No Trespassing signs does not mean that it's open to geocache placement without obtaining permission. For example, many HOAs have green space trails or parks. We expect you to comply with the Guidelines, include documented permission from HOA management in your Reviewer Note, and include in the cache description that permission has been granted. If your cache is adjacent to a residence, please get consent from that resident, even if your cache is located on property that is otherwise acceptable, since you're essentially inviting people to visit this location at all hours of the day and night.

WHAT - Clearly and completely describe the cache container, including physical dimensions, material, shape, contents, and how it is identified as a geocache. Just saying a "plastic container" or a 'Metal box" is incomplete.  Some containers are self explanatory like a 30 cal ammo can, a bison tube, a preform, a keytainer, or a magnetic nano but others need a complete description in your Reviewer Note. We want to know exactly what you've placed in case there is some question in the future by Law Enforcement or a property owner.

HOW - Explain how and where your cache is hidden. Please be specific any about camouflage and any attachment method to any object or the ground. For example, it might be a bison tube hung with a wire hook over a palo verde limb about 5 feet off the ground. If your cache is on a sign post, or near a sign, please tell us what the sign says.

If you need to include a picture, please upload the image to a Reviewer Note as additional information. Photos are not a substitute for a written Reviewer Note.  When the cache is publishes, the image will be archived and not visible to the public.

Coordinate Check

If you want to confirm the availability or limitations of a specific location before placing your geocache, please create a cache submission, title it COORDINATE CHECK ONLY, and submit it for review. This will allow us to use our complete toolkit to determine any proximity conflicts or other limitations. The cache submission will then be returned to you for any necessary changes and edits.

Cache Owner Responsibilities

Health Score

• To help improve the overall caching experience, Geocaching HQ created an algorithm to calculate a hidden Health Score for each geocache.

• A low Health Score provides an indication that the cache may need attention from the owner.

• The goal is to improve the overall geocaching experience and avoid frustrations due to missing or broken caches.

• The algorithm isn't perfect; it cannot read and interpret the text within a cache page - however it does take the following aspects of a page into consideration:

1.    Did Not Find logs (DNF)

2.    Needs Maintenance logs (NM)

3.    Needs Archived logs (NA)

4.    Last find date

5.    Difficulty and terrain rating

• If the Health Score of a cache is calculated below a dynamic threshold, an automatic alert email is sent to the cache owner by Geocaching HQ.

• A Community Volunteer Reviewer may follow up to perform further actions on the cache page.

• Neither Geocaching HQ or the Community Volunteer Reviewer can assess the true status of a cache; it is the responsibility of the cache owner, as part of cache maintenance.

• If there are a multiple DNFs logs on a cache - the community may not know if the cache is missing or is simply hard to find.

• If a cache page has several posted DNFs - and the cache owner knows that the cache is in definitely in place - they should reassure the community by posting a Note log.

e.g. "There have been a few DNFs, however it is a clever hide! I checked on it this morning. Check the hint!"

• If a Community Volunteer Reviewer does not see a posted response from a cache owner on their cache page after several DNF/Maintenance requests, it may be Disabled.

• If a cache owner knows with certainty that their cache is in place and ready to be found, they may Enable the cache page, with an explanatory note.

• If a cache owner is unable to definitively confirm the status of their cache, the cache page should remain Disabled and a Maintenance visit should be scheduled.

• An Owner Maintenance log should only be posted after a maintenance visit has occurred.

• Only when a cache is confirmed to be in place and ready to be found should a cache page be Enabled.

The number of "false positives" flagged with this process are minimal compared to the number of abandoned caches that this process will remove from the game.

Disabled Caches 

If the cache owner intends to keep the cache in the game, they should:

• At least monthly post ongoing status updates on the cache page using a Write Note log

• Confirm when a maintenance visit has been completed using an Owner Maintenance log

• Use the Enable option when it has been confirmed the cache is ready to be found

A Reviewer may Archive the cache if the cache owner has not posted an update within 14 days.

Requirements for Different Cache Types

Multi-Caches

A Multi-Cache can have physical or virtual stages. When you submit a multi-cache for Review, include a Reviewer Note stating the process of how your multi-cache could be completed.

Puzzle/Mystery/Wherigo caches

• We need to know how your puzzle/mystery cache is solvable, please include this information in a Reviewer Note.

• When using a third party coordinate checker (Certitude, for example), please include the keyword or coordinates needed to pass the checker along with a screenshot of the "success" screen.

• Jigidi has expressed concern with the use of their platform for the presentation of complex puzzles in geocaching puzzle caches because geocachers are seeking ways to shortcut the solution in manners not allowed by Jigidi's Terms of Use. When you incorporate a Jigidi (or other online puzzle) as part of your puzzle cache, please include two screenshots with your Reviewer Note - one showing the puzzle at least 90% (but less than 100% completed) using the number of pieces that your submitted cache uses, and the second showing the completed puzzle with the completion message and the side panel with the details.

• Please do not put your 'posted' coordinates in areas where people should not search such as freeways, private residences, railroads, off-limits locations, or other areas where access is restricted.  Lakes and street corners are fine.  I know your cache page says the cache is not at the posted coordinates, but people do search those coordinates.  We have many new cachers who are using cell phones and may not look at the cache page.  If you have any questions about a location, feel free to ask one of us.

Challenge Caches

Before submitting a Challenge Cache, please click here to read the article in the Geocaching Help Center.

The challenge requirements should be simple, and easy to explain, follow and document. A long list of rules or restrictions may prevent publication.

A challenge cache needs to appeal to and be attainable by a reasonable number of cachers. Arizona's Reviewers consider the "reasonable number of cachers" to be TEN (in addition to the cache owner); qualifying cachers must reside within Arizona. Please provide an accurate name list of the geocachers who qualified in a Reviewer Note.

Challenge cache owners must demonstrate that there are plenty of qualifying caches to meet the challenge at the time of publication.

Please do not submit a challenge cache in an area where a very similar or identical challenge cache already exists.  

Event Stacking

•  

  • An event must be a minimum of 20 miles distance or 3 hours before or after another event. This is a regional rule to prevent event stacking. A registered series of events can also be rejected as unique events, even if the distance is over 30 miles, if it is essentially the same group traveling from event to event.

  • The intention of an event is to be central; a social gathering for and with geocachers.

  • A CITO is a work event and the emphasis in the description needs to be on the type of work expected of the attendees. This is also the reason that GCHQ recommends we allow a stacking exception where a regular social event closely preceeds or follows (not both) an associated work event. The event anticipating a stacking exception must make it clear that it is associated with the CITO and in support of the CITO.

•  

  • Only 2 events within 50 miles of the primary Mega Event site the day before, or the day after a Mega event, with a minimum of 3 hours between events.

  • No events, other than by the Mega organizer within 50 miles on the day of the event.

Power Trails

Please note - YOU will be the one responsible for the maintenance and upkeep of your cache as outlined in the Guidelines. If you are not going to be able to regularly visit and maintain your cache as required then please do not submit these caches. Your prompt attention to any log that indicates things could be amiss will be greatly appreciated by all geocachers. The rule is; if you can't fix it straight away then "Disable" it until you can, see this Help Center Article.  

You, as the Cache Owner, may not ask “the community” to maintain caches on your behalf. In certain circumstances, you may designate other cachers to assist in maintaining. These other cachers must be active local cachers, local to the area where the cache is placed. However – you – as the cache owner - remain primarily responsible for all maintenance.

To help assure maintenance of this geocache power trail is performed the following wording needs to be placed on each cache page in a prominent location:

To assure this cache Power Trail remains active and available for all who seek these caches, this cache (and the others in this trail) is maintained by the cache owner (Name). (As appropriate – please add) These additional local cachers will assist with the cache maintenance: Name/Link, Name/Link, Name/Link.

Cachers are encouraged to communicate any caches requiring attention by placing a Owner Attention Requested note on this cache page.

Plan your power trail wisely.  Check for minimum distance.  Geocaches must be at least 0.1 miles (528 feet or 161 meters) apart.

Proximity to public structures

The guidelines specifically state "a geocache is problematic due to its proximity to a public structure. Examples include highway bridges, major roadways, dams, government buildings, schools, military installations, hospitals, airports and other areas defined in the Regional Geocaching Policies Wiki."

Highways and Guardrails

• On divided highways and other highways posted at 65 mph or higher, caches should be at least 100 feet back from the fog line and a parking coordinate for legal parking should be provided.

• For most other highway, maintain at least 60 feet back from the fog line.

• No guardrail caches on roadways with speed limits over 40 mph.

Military Installations

No geocaches allowed on or near military installations. Cache listing can be reviewed when:

1. A major roadway is in between the military installation and the geocache container. A major roadway is defined as a road with at least four traffic lanes.

2. There’s at least a 250 feet buffer between a geocache container and the military base’s boundary when a major road does not exist.

Railroad Property

Geocaches placed within 150 feet of an active railroad tracks, including spur lines, are considered to be on property belonging to a railroad and trespassing is prohibited by Federal Regulations.

Schools, Playgrounds, and Airports

• Generally - should some one seeking a cache be visible from the school or airport buildings, parking areas, and/or playgrounds or playing fields - We consider the cache to be "too close".

• This restriction applies even with verifiable permission - as this permission can not be clearly communicated to all "stakeholders" of the location.

Universities and Colleges

Generally geocaching is allowed on University and College campuses (with permission) where the general public is allowed to visit unrestricted.  Geocaches are not allowed to be placed near or on student housing property.

Restricted Areas

Arizona State Parks

Website

Geocaching is allowed in Arizona State Parks but you are required to get permission from the State Park manager prior to placing and submitting your cache. There is more information on the State Parks Frequently Asked Questions page

Arizona State Trust Land

Website 

Geocaching is allowed.  Cache page description must indicate the geocache is on Arizona State Trust Land, make it very clear that a pay permit must be obtained from the Arizona State Lands Dept (ASLD) before entering, and provide a link or a clear explanation about how to obtain that required permit. 

Cache owner shall provide a complete Reviewer Note as described above.

ASLD Parcel Viewer

Bullhead City Parks

Website 

All new geocaches placed in any parks or property owned by Bullhead city must receive permission prior to placement. All permission requests must be sent to the Recreation Manager.

Bureau of Land Management - Arizona

Website 

BLM's Geocaching Rules

• Identify proposed cache locations to the local BLM office before placing a cache

• Do not place caches at archaeological sites

• Obtain a BLM permit for any competitive events, contests for prizes, paid participation, or caches hosted by commercial business

• Advise BLM if you observe any misuse or abuse of a cache location

Cibola National Wildlife Refuge

Website  

No geocaches allowed.

Chandler City Parks

Geocaches placed in Chandler City Parks must comply with Chandler’s policy on geocaching which can be found in this document.

Cochise County

No geocaches allowed inside or outside of drainage structures. 

Coronado National Memorial

Web: http://www.nps.gov/coro/index.htm

No new geocaches are allowed.

Glen Canyon National Recreation Area

Web: http://www.nps.gov/glca/index.htm

No new geocaches are allowed.  There are a number of existing geocaches in the park.  The park reserves the right to archive any or all of the geocaches at any time.  Rangers will normally gather any geocache if they come across it.

Golf Courses

No geocaches are allowed on any Golf Courses unless permission is given by the golf course manager.

Grand Canyon National Park

Web: http://www.nps.gov/grca/index.htm

Any new geocaches are not allowed.

Events taking place in Grand Canyon National Park are required to have an approved special use permit prior to submitting the event for review.

Special Use Permit: https://www.nps.gov/grca/learn/management/sup.htm#CP_JUMP_2220836

Imperial National Wildlife Refuge

Web:  https://www.fws.gov/refuge/imperial/

No geocaches allowed.

Ironwood Forest National Monument

Web:  https://www.blm.gov/visit/ironwood

Geocaches allowed with permission.

Kofa National Wildlife Refuge

Web: https://www.fws.gov/refuge/kofa/

No geocaches allowed.

Lake Mead National Recreation Area

Web: http://www.nps.gov/lake/index.htm

Any new geocaches are not allowed.

Little Free Libraries 

Little Free Libraries are growing in popularity and geocachers are increasingly wanting to use them for geocache placement.

They are publishable with the following considerations:

• The libraries are privately owned and usually on private property so permission must be obtained from the library owner.

• The cache page should not be promotional of the Little Free Library movement. 

• They can use the term Little Free Library on the cache page.

• The www.littlefreelibrary.org website sells the library boxes and solicits donations, so it should not be included on cache pages.

• The logbook should be placed in a container within the library, and not just be paper "floating" around.

Maricopa County Parks

Web: https://www.maricopacountyparks.net/things-to-do/activity/geocache/

No geocaches are allowed in any Maricopa County Park without explicit written permission from the Park Supervisor prior to cache placement.

1. Adobe Dam Regional Park

2. Buckeye Hills Regional Park

3. Cave Creek Regional Park

4. Estrella Mountain Regional Park

5. Lake Pleasant Regional Park

6. McDowell Mountain Regional Park

7. San Tan Mountain Regional Park

8. Spur Cross Ranch Conservation Area

9. Usery Mountain Regional Park

10. White Tank Mountain Regional Park

Mesa Parks

Web: https://www.mesaparks.com/parks-facilities/parks/park-rules-regulations

The City of Mesa allows the placement of caches within the parks and facilities managed by Mesa Parks, Recreation, and Community Facilities as long as they are in a “safely accessible location” and participants follow all park rules especially regarding hours of operation and not disturbing natural resources or park guests.

Native American Reservations

Web: https://www3.epa.gov/region9/air/maps/az_tribe.html

Geocaches in Native American Reservations is not allowed without written permission from the tribal counsel.

1. Ak-Chin Reservation

2. Camp Verde Reservation

3. Cocopah East & West Reservation

4. Colorado River Reservation

5. Fort Apache

6. Fort McDowell Reservation

7. Fort Mohave Reservation

8. Fort Yuma Reservation

9. Gila River Reservation

10. Havasupai Reservation

11. Hopi Reservation

12. Hualapai Reservation

13. Kaibab-Paiute Reservation

14. Navajo Reservation

15. Pascua-Yaqui Reservation

16. Salt River Pima-Maricopa Indian Community

17. San Carlos Reservation

18. Tohono O’odham / San Xavier Reservation

19. Tonto Apache Reservation

20. Yavapai-Apache

21. Yavapai-Prescott Reservation

Native American Ruins

No geocaches are allowed on any Native American ruins.

Phoenix Preserves & Parks

Web: https://www.geocaching.com/p/?u=cityofphx

Placing geocaches in the listed Phoenix Preserves & Parks is only permitted in specific instances.  You must have explicit written permission from a park ranger prior to placement. The cache must be within the trail corridor of specific trails. Include the name of the approving ranger as well as their title, contact information, and a clear photo of their approving document in your Reviewer Note when submitting your cache for review.

See CITYOFPHX profile page (linked above) for their geocache guidelines

1. Buffalo Ridge

2. Casa de Montanes

3. Deem Hills

4. Echo Canyon/Camelback Mountain

5. Lookout Mountain

6. Ludden Mountain

7. North Mountain/Shaw Butte

8. Piestewa Peak

9. Pitcher Hill

10. Phoenix Sonoran Preserve

11. Shadow Mountain

12. Stoney Mountain

13. South Mountain

14. Union Hills

Picacho Peak State Park

Website 

Any new geocaches are subject to a permit process and approval by the park manager before they can be placed. Information and permit application can be found at their website.

Pima County Parks

Geocaching is not allowed in Pima County parks without prior written permission from the Pima County Natural Resources, Parks and Recreation.

Shopping Malls

Permission from the Mall's Management Office is required before geocaches can be placed on mall property.

Town of Gilbert Parks

Web: https://www.gilbertaz.gov/home

Geocaches and events are generally permitted in town parks and shall comply with the restrictions and prohibitions listed in Chapter 15 - Special Events.

Tucson Mountain Park

Website

Geocaches are no longer allowed to be place on Tucson Mountain Park.

Wildlife Watering Facilities

No geocaches within 1000 feet from a wildlife watering facility allowed.  Wildlife rely heavily upon these water sources especially in dry desert areas and will stay away from areas where human activity is present. 

AGFD Wildlife Waters Interactive Map 

Wilderness Parks

Arizona Wilderness Parks List

Geocaches not allowed in Wilderness Parks.