Field Notes / Feedback

Corrections matter Beginner confusion welcome Private notes allowed

Send the correction, confusion, or proof that helps the next person.

Use this page to turn one real-world note into a cleaner page, a safer planning route, or a stronger trust warning for the next visitor.

Start with the page, say what helped or confused you, and name the next move Double-D should make before someone else trusts the wrong thing.

Fastest useful route Pick the note type, name the page, and explain the trust gap or proof in plain language. The form now starts immediately below.

Field Notes Form

Start here while the problem is still fresh.

Phone visitors should reach the real workflow quickly. Fill this out like you are talking to the next person who will use the page: one page, one problem, one next move.

Pick the note type honestly. Name the exact page or section. Tell Double-D what should change next.

Feedback Rules

What kind of note are you leaving?

Double-D should not mix official facts, experience, beginner confusion, and requests into one blurry pile. If you are unsure, read these note types after you draft the problem in the form above.

Source correction

A rule, date, permit step, or official link needs fixing.

Use this when the page should point to a stronger agency source, show a reviewed date, or remove wording that sounds too certain.

Beginner confusion

The page still leaves a new person unsure what to do next.

Use this when the guidance is technically true but still too dense, too vague, or too intimidating for the person it is supposed to help.

Community field note

You learned something useful in the real world.

Use this for experience that can improve planning, preparation, expectations, or safety, while still staying separate from official regulation claims.

Missing guide request

You need a page, checklist, or route we do not cover yet.

Use this when the gap matters enough to block trust, planning, or a better outdoor decision for the next visitor.

What Happens Next

Notes should improve pages, not disappear into a vague promise.

Your note should be specific enough that someone else can understand what happened, what page it affects, and what would make the next trip easier.

1

Name the page and the problem.

Say what page you reviewed, what helped, what confused you, or what should be corrected before someone else trusts it.

2

Classify the note honestly.

Source correction, beginner confusion, field note, and missing guide request each need a different follow-up and a different trust threshold.

3

Make the next visitor safer or clearer.

Good notes lead to a page improvement, a wording fix, a stronger source path, or a clearer warning about what still needs checking.