Ever arrived at a geocaching GZ (ground zero) only to find the cache missing, the location flooded, or a brand-new fence blocking the path? Frustrating, right? As a cache owner, there's nothing worse than getting those "Did Not Find" (DNF) logs knowing you could have prevented them. That's where the often-overlooked cache owner note becomes your most powerful communication tool.
Cache owner notes aren't just a feature—they're your direct line to the geocaching community. Whether you're dealing with temporary relocations, seasonal challenges, or simply updating maintenance status, these notes bridge the gap between you and the finders. They transform potential frustrations into smooth, enjoyable experiences for everyone hunting your caches.
In this comprehensive guide, I'll walk you through everything you need to know about cache owner notes—from the basics to advanced strategies. You'll learn how to craft effective messages, when to post them, and how they can transform your geocaching game.
Cache owner notes are special messages you can post on your cache listing that appear differently than regular logs. They're visible to everyone searching for your cache and serve as official updates from the owner. Think of them as your cache's "news ticker" or "status board."
Unlike regular "Found It" or "Did Not Find" logs from finders, cache owner notes carry special weight. They're stamped with your name and carry the authority of the cache owner. When geocachers see that orange-tinted note on their app or website, they know it's important information directly from the source.
These notes aren't just another comment box. They have specific characteristics that make them unique:
Direct Visibility: Cache owner notes appear prominently in the cache's logbook, making them hard to miss. Finders see them right alongside their own logs, ensuring critical information isn't buried.
No Log Type Constraints: Unlike regular logs that require a specific type (Found, DNF, Write Note), owner notes can be posted regardless of the cache's status. Whether the cache is active, disabled, or archived, you can still communicate with finders.
Permanent Record: These notes stay on your cache page indefinitely, creating a communication history that helps future finders understand the cache's journey.
Notification Triggers: When you post a cache owner note, it can trigger notifications to watchers of your cache, spreading your message quickly to interested geocachers.
Knowing when to post a cache owner note is just as important as knowing how. Let's break down the most effective scenarios.
The Missing Cache: If you receive a DNF and know the cache is still there, post a note immediately. Example: "Cache is definitely in place—I checked it yesterday. Look for the small camo tape on the oak tree at GZ. The container might have shifted into the leaves."
Damaged Container: Found your cache waterlogged or cracked? Post a note explaining the situation and your repair timeline: "Container damaged in last weekend's storm. I'm cleaning it out and will have a new one in place by Friday. Thanks for your patience!"
Missing Logbook: If the log is full or missing, let people know they can sign a temporary slip: "Logbook is full! New one arriving this weekend. Feel free to sign a piece of paper and I'll add it to the new book."
Construction or Landscaping: If a new fence, construction, or landscaping blocks access, post immediately: "Cache temporarily relocated 50 feet north due to new fence. Check the updated coordinates. Old spot is now a muggle zone!"
Seasonal Access Issues: Many caches become inaccessible during certain seasons. A note can save wasted trips: "Note: This cache is only accessible during low tide. Check tide tables before heading out. I'll update when conditions improve."
Private Property Changes: If access permissions change, communicate clearly: "Landowner has restricted access to weekdays only. Please respect their property and avoid weekends."
Weather Impacts: After heavy snow, flooding, or landslides: "Trail washed out after the rains. Please use the alternate trailhead at N 45° 12.345 W 122° 34.567. The original path is unsafe."
Wildlife Activity: In areas with active wildlife: "Warning: Bear activity reported in this area. Cache is still active but please hike with caution and carry bear spray."
Vegetation Growth: Summer brings overgrowth: "Cache location now has dense poison ivy. I've moved it to the edge of the clearing. New coordinates posted."
Disabled for Maintenance: When you disable a cache for repairs: "Cache disabled for maintenance. Container needs replacement. Will be back online within two weeks. Sorry for the inconvenience!"
Archiving with Alternatives: If you must archive but want to guide finders: "This cache is being archived, but I've placed a new one nearby at N 45° 12.345 W 122° 34.567. Check out GC12345 for the replacement!"
Event Cancellations: For event caches: "Event canceled due to severe weather forecast. Refunds being processed. I'll reschedule for next month."
Special Events: "Special event this Saturday—first 20 finders get a special pathtag!"
Photo Contests: "Photo contest: Best creative log photo wins a trackable! Tag me in your photo."
Challenge Updates: "New challenge added to the cache: Find 5 other caches in this series to unlock the final bonus."
Writing a good cache owner note is an art. You want to be clear, helpful, and engaging without being overwhelming. Here's how to do it right.
Geocachers are often reading notes on their phones while standing in the woods. Get to the point quickly.
Bad: "Hey everyone, I just wanted to let you all know that there have been some changes in the area recently that might affect your ability to find this particular cache, so please be aware of that."
Good: "Cache temporarily relocated due to construction. New coordinates: N 45° 12.345 W 122° 34.567. Old location is now a construction site."
Vague notes create more questions than answers. Include precise information.
Instead of: "Cache might be hard to find right now."
Use: "Cache container is smaller than expected. It's a black bison tube attached to the underside of the third branch on the pine tree. Look carefully!"
Tell finders exactly what they need to do.
Example: "Trail is closed for maintenance. Alternate access: Park at the church lot (N 45° 12.345 W 122° 34.567) and follow the blue blazes for 0.3 miles. This adds 10 minutes but avoids the construction zone."
While the note interface is basic, you can still improve readability:
Help finders understand what they're getting into.
Example: "This is a high difficulty cache. You'll need to solve the puzzle first (hint: it's a Caesar cipher). The final location requires scrambling over some rocks. Bring sturdy shoes!"
When appropriate, offer a way to reach you.
Example: "If you're stuck, message me for a hint. I usually respond within 24 hours."
Even experienced cache owners make these mistakes. Here's what to watch out for.
The Problem: Overloading finders with paragraphs of text.
The Fix: Break long updates into multiple notes over time. Focus on one issue per note.
The Problem: Posting notes for every minor thought.
The Fix: Only post when the information affects the finder's experience or cache accessibility.
The Problem: Leaving up outdated warnings that no longer apply.
The Fix: Always post a follow-up note when you fix an issue: "Update: New container installed! Cache is back to normal. Thanks for your patience."
The Problem: "Cache might be wet" doesn't help anyone.
The Fix: "Cache is wet due to rain. Bring a towel to dry it off before signing, or bring your own pen as the ink might be smeared."
The Problem: Posting notes but not realizing who gets notified.
The Fix: Remember that people watching your cache (and the area) get notifications. This is great for spreading important info quickly.
Most platforms allow you to edit or delete your own notes:
Important: If you edit a note, consider adding "EDIT:" at the beginning so finders know the information has been updated.
Think of your notes as a timeline of your cache's life. Strategic posting creates a narrative that helps finders understand the cache's history.
Example Timeline:
For puzzle caches, owner notes can provide subtle nudges without giving away the solution.
Example: "Several finders have mentioned the final coordinates are within 50 feet of the posted coordinates. The puzzle solution involves simple substitution."
Use notes to create interactive experiences:
Challenge Cache: "First to find this month gets to choose the theme for next month's challenge!"
Multi-cache: "Update: Stage 2 has been moved to the large oak tree. Check the updated waypoint."
Bonus Cache: "Found all 10 caches in this series? Message me for the bonus coordinates!"
Plan your notes around the calendar:
Spring: "Snow is melting—cache might be wet. Bring a towel."
Summer: "Poison ivy is thick around GZ. Stay on the trail."
Fall: "Leaves cover the cache area. Use the hint!"