What's in here

What CACHE POINT is for

It does five jobs, one per module:

• Lists every cache you have, by codename, with its priority and status. (Module 01)
• Tracks what's inside each one — quantities, weights, rotation dates, how it's preserved. (Module 02)
• Records how to find it again using a careful step-down system, kept locked away from the safe records. (Module 03)
• Keeps an inspection history so you know each cache is still good and dry. (Module 04)
• Stores your container and concealment know-how, plus a desiccant calculator. (Module 05)

Doctrinal basis: TC 31-29/A (Special Forces Caching Techniques), FM 31-21, ST 31-205, FM 3-05.130, and MIL-STD-2073-1E preservation methods.

The codename / location split

This is the single most important idea in the program. Information about your caches comes in two flavors:

• Safe to share — the codename, the priority, whether it's a food cache or a medical cache. Knowing a cache called RAVEN exists tells an outsider nothing useful.
• Almost never shared — the actual location and how to dig it up. This lives only in the Access Sheet (Module 03) and prints only as a hand-delivered Access Card.

CACHE POINT enforces this split for you. The Registry Summary you can hand to the whole group. The Access Card you guard like cash. Each printout is stamped with a sensitivity level so nobody mixes them up.

What's on your screen

1. A — Top bar. COMMAND SUITE returns you to the WATCHMAN home menu. The gear (⚙) opens Settings.
2. B — Module list. The five numbered modules plus Print Outputs, this User Manual, and the Demo sandbox (RETURN TO LIVE when you are inside the demo). The counter at the bottom shows how many caches you've defined.
3. C — Main work area. Whatever module you click on opens here. This is where you add caches, log contents, and so on.

Your first 15 minutes

Do these in order and you'll have a real, working cache record:

1. Open Module 01 — Cache Registry and click + ADD CACHE. Give it a codename (any word — RAVEN, ANCHOR, a color, a tree). Pick a method (Burial, Concealment, or Submersion), a priority, and a status. Save.
2. Still in Module 01, scroll to Compartmentalization and tag who is allowed to know about this cache. At minimum, tag one Recovery-authorized person. (Members come from your ROSTER module.)
3. Open Module 02 — Contents Inventory, pick your cache from the dropdown, and add a few items. Don't aim for perfect — get the big things in.
4. Open Module 03 — Access Sheets, pick your cache, and fill in how to find it. This is the sensitive one. Take your time and be precise.
5. Open Print Outputs, look at the Registry Summary, and print it. That's your safe, share-with-the-group sheet.

Cache Registry

This is the master list. Every cache starts here. The codename is the only name that ever leaves this program safely, so pick something memorable but meaningless to outsiders.

The fields that matter most

Contents Inventory

Pick a cache from the dropdown, then list what's inside it. Each item records quantity, unit weight, rotation date, and how it's preserved. The module totals the weight for you — useful for knowing whether one person can carry a recovered cache out.

Two flags worth knowing

Access Sheets

This is the locked-vault module — the only place exact locations live. It follows the three-tier reference system from caching doctrine so the find narrows in deliberate steps rather than a single map pin.

How the step-down works

1. General Area — the broad zone (a valley, a stretch of road). Means nothing on its own.
2. IRP — an obvious landmark you go to first (a bridge, a lone tree, a trail junction).
3. FRP — the precise feature right next to the cache. From the FRP you use a pinpointing technique (distance and bearing, pace count, etc.) to reach the exact spot.

Condition Log

A cache you never check is a cache you're guessing about. Each time you inspect one, log it here: the date, what you found, and when the next inspection is due. The Inspection Schedule output then sorts every cache by what's overdue.

How often to inspect

Container & Concealment

Three layers live here: your group's standing operational notes (the procedures you've settled on), per-cache container assignments (what you actually used for each cache), and a doctrinal reference library (the source facts your procedures rest on).

The desiccant calculator

Moisture is the slow killer of buried caches. Enter your container volume and the tool estimates how much desiccant you need to keep the inside dry. Pair it with a moisture indicator card so you can see at a glance, on inspection, whether the seal held.

Print Outputs & the Binder

The Outputs screen turns your records into paper. Each output carries a sensitivity stamp telling you how far it can travel:

Printing the full binder

At the top of Outputs is PRINT FULL BINDER. It assembles a cover sheet, the Registry Summary, the Inspection Schedule, and every cache's Contents Manifest into one continuous print job — each section on its own page — ready to drop into a 3-ring binder.

Saving, backups & settings

Everything you enter saves automatically to this device, in this browser, under the key ao_cache_point_v1. Nothing is sent anywhere. That privacy is the point — but it also means this device is your only copy unless you make a backup.

1. In Outputs, scroll to Data Management.
2. EXPORT ALL DATA (JSON) downloads a single file with everything in it. Keep it somewhere safe and offline.
3. IMPORT DATA (JSON) restores from that file on a new device or after a reset.

The gear (⚙) in the top bar opens Settings, where you can switch between the dark tactical display and a light field-manual look. Your choice is shared across the whole WATCHMAN suite.

Hover any acronym

Anywhere you see a word with a dotted underline, hover your mouse over it (or tap it on a touchscreen) and a plain-language definition appears. It works across every screen, including this manual. Try it now: hover OPSEC or TC 31-29/A. The full list is in the glossary below if you'd rather read it on paper.

Glossary

Common questions

Is my data sent anywhere?

No. Everything stays in this browser on this device. That's also why you must export your own backups.

Can I share the Registry Summary with my whole group?

Yes — that's exactly what it's for. It contains codenames only, no locations.

Where do the member names come from?

The compartmentalization roster pulls from your ROSTER module. Add people there and they become selectable here.

What if I move or lose a cache?

Update its status in Module 01 (Recovered or Compromised). The change flows through every output so your records stay honest.

Why are Access Cards rendered one at a time?

By design. Bulk-rendering every location at once is the most dangerous thing the program could do, so it makes you select a single cache deliberately.

Demo sandbox

CACHE POINT ships with a demo sandbox — a separate copy pre-loaded with a worked example: three caches in different states (an active buried long-term cache, an active concealment medical cache, and a planned E&E cache), inventoried contents with rotation dates and ESDS/VCI flags, a complete Access Sheet with IRP/FRP route and pinpointing data, and a condition log with inspections on record.

Opening and leaving. In the live module, click DEMO in the sidebar under this manual. Inside the demo, that same slot reads RETURN TO LIVE and takes you back. An amber banner across the top of the demo tells you which copy you are in at all times.

Your real data is safe. The demo keeps everything in separate storage slots — including its own sample roster, so the compartmentalization dropdowns work without touching your real ROSTER. Nothing you do in the demo can reach your real caches.

Resetting. The ↻ RESET DEMO button (top bar and amber banner) wipes any changes and restores the sample scenario, sample roster included.

How to use it. Open the RAVEN cache and read its Access Sheet against Section 7 of this manual — that is what a complete sheet looks like. Check the condition log entries for the inspection rhythm. Then open Print Outputs and generate the binder — the OPSEC split between what prints and what stays memorized is easiest to understand from the finished product.