NAV-06 · Lesson 10

Group Standard and Field Exercise

Turning nine lessons of individual settings into one document the whole group works from, then proving it on the ground.

Reading: about 10 minutes · Field drill: about 2 to 3 hours

Bottom Line Up Front

Everything so far has been about your device. This lesson is about the fact that a position only has value when it moves between people — and two members with correctly configured devices set differently produce coordinates that are individually right and collectively useless.

Two deliverables come out of this lesson. A written group standard that anyone can be handed and comply with, and a capstone exercise that tests whether it actually works when walked rather than read.

Recall Check · L06

From Lesson 06, because the standard has to encode it: what is the rule when the device and the ground disagree?

A. Stop moving, work through the cheap explanations first, and re-establish position by terrain if none of them fit.
B. Take the midpoint of the two positions and continue, which bounds the error while keeping the team moving.
C. Trust the device unless its accuracy figure has degraded, since terrain interpretation is the less reliable of the two.
D. Continue to the next planned checkpoint, where a second comparison will show which of the two sources was wrong.

1. What the standard has to decide

A standard is not a statement of good practice. It is a short list of decisions already made, so nobody is deciding them in the field. If a line in your document does not remove a decision, it is commentary.

Decision	From	What must be written
Map datum	Lesson 03	The datum, and the map series it matches. The single highest-consequence line in the document.
Coordinate format	Lesson 03	The internal standard, plus what you accept from outside and who converts.
North reference	Lesson 03	True, grid or magnetic, and why — so a new member can match it rather than guess.
Units and elevation reference	Lesson 03	Distance, elevation, angle units, and whether elevation is above sea level or above ground.
Waypoint naming	Lesson 05	The convention, with two worked examples. Examples do more work than the rule.
Precision by task	Lesson 07	How many digits for a routine check, a rendezvous, an evacuation.
Reporting sequence	Lesson 07	Warn, frame, digits, read-back. Written as a script somebody can read aloud.
Emissions postures	Lesson 08	The postures, their triggers, and what each does to sharing, sync and recording.
Verification standard	Lesson 06	Where verification is mandatory, and the disagreement rule in one sentence.
Fallback	Lessons 01, 09	The PACE legs by name, and what every member carries on paper regardless.

Keep it to a page or two. A standard nobody reads is worth less than a shorter one everybody does, and this document has to survive being handed to somebody in a hurry.

Knowledge Check

What distinguishes a line that belongs in a group standard from one that does not?

A. It cites the lesson or doctrine it derives from, so a member can check the reasoning behind it before complying.
B. It applies to every member equally, since a rule with exceptions cannot be enforced consistently across a group.
C. It removes a decision that would otherwise have to be made in the field, rather than describing good practice.
D. It can be verified by inspecting a member’s device, which makes compliance checkable rather than a matter of trust.

2. Making it hold

Publishing a standard is the easy part. Three things decide whether it survives contact with a group.

Configure together, once. Set every device in the same room, side by side, against the document. It takes an hour and it catches what a written instruction never will — the member whose menu is laid out differently, the watch that has no datum setting at all, the phone nobody had checked.

Make the settings card the compliance record. The card from Lesson 03, filled out and dated, is the evidence a device matches the standard. Re-check on a schedule and whenever anyone changes map series or region.

Decide what happens when somebody cannot comply. Some devices will not do what the standard asks. The answer is not to lower the standard; it is to record the exception, name what that member does instead, and make sure everyone knows which devices are which.

The most common failure

A standard is written, everyone agrees, devices are configured — and eleven months later somebody replaces a handheld, sets it up from the box, and joins a movement. Nothing in the document catches that, because the document was a one-time event rather than a process.

Build in the trigger: a new or reset device is configured against the standard and its card filled out before it goes on a movement. One line, and it is the line that keeps the other ten alive.

Knowledge Check

A group publishes a standard and configures every device together. What is the most likely way it degrades over the following year?

A. Members drift from the standard deliberately as they develop preferences that suit their own habits better.
B. New or replaced devices are set up from the box and join movements unconfigured.
C. Firmware updates silently revert configured settings to their factory defaults across the group at the same time.
D. The standard is lost, because documents circulated once are rarely retained by the members who received them.

3. The capstone exercise

The standard is a claim that your group can pass a position between members without corrupting it. This tests that claim.

Set it on ground you know, with a route of three or four legs and at least one section of restricted sky — canopy, a drainage, or built-up ground. Allow two to three hours.

Phase 1Configure and checkEvery device against the standard, cards filled out. Another member checks yours; you check theirs.
→
Phase 2Plan and loadBuild the route, name the points to the convention, transfer it, mark the paper map and write the grids.
→
Phase 3Walk and verifyWalk the route. Verify against terrain at three checkpoints, features before screen, every time.
→
Phase 4ReportPass each checkpoint by radio using the reporting sequence, with a read-back. Log what was sent and received.
→
Phase 5Final leg darkDevice off. Complete the last leg on map and compass, on the same plan.

Judge it on outcomes rather than effort:

Every checkpoint verified against terrain before the position was accepted. Not glanced at — three features, named, found.
Every reported position read back and confirmed, with any error caught by the read-back rather than discovered later.
Positions plotted by the receiving station landed where the sender meant. This is the one that tests the standard rather than the individual.
The final leg completed on the plan, with the step down costing a pause and not an incident.
Any disagreement handled by the rule — stopped, cheap explanations first, terrain to re-establish. If nothing disagreed, induce one next time.

The exercise has failed usefully if a position did not survive the trip between two members. That is the finding you wanted, discovered on a training day rather than on a day that mattered. Fix the standard, not the member.

Knowledge Check

Which capstone outcome tests the group standard rather than an individual’s skill?

A. Whether each member verified against terrain at every checkpoint before accepting the position the device offered.
B. Whether the final leg was completed on map and compass with the device switched off for its full length.
C. Whether positions plotted by the receiving station landed where the sender meant them to land.
D. Whether the route was built from map recon rather than generated automatically by the planning software.

4. Where this sits

The course opened with a claim: GPS is the primary, and map and compass is the emergency. Ten lessons later that should read less like a slogan and more like a consequence.

The device is faster and more precise than a paper map, and it earns its place as the primary leg. It is also capable of being confidently, silently wrong — through a datum set once and never checked, a reflection off a rock wall, a coordinate misread over a radio, or a signal that is not what it claims to be. None of those announce themselves. All of them are caught by the same thirty seconds of looking at the ground.

That is the whole course: a fix is a claim, and the ground is the authority. Everything else — the settings, the naming, the read-backs, the postures, the standard — exists to make that check cheap enough that you actually do it.

Then keep going. NAV-02 is the leg you fall back to and it needs practicing on its own terms, not just as a contingency you have read about.

What to carry out of this lesson

A line in a standard must remove a decision that would otherwise be made in the field. If it only describes good practice, it is costing a tired reader time.
The quiet failure is a replacement device set up from the box eleven months later. Write the rule that a new device gets configured before it travels.
The capstone outcome that tests the standard rather than the individual is whether a position plotted by the receiving station landed where the sender meant.
A fix is a claim, and the ground is the authority. Everything else in this course exists to make that check cheap enough that you actually do it.

Final Drill

Write the group standard. One or two pages, using the table in Section 1 as the contents list. Every line removes a decision.
Hand it to somebody who was not involved in writing it and have them configure a device from it alone. Every question they ask is a defect in the document.
Run the capstone. Log what was sent and what was received at each checkpoint.
Debrief against the five outcomes. Amend the standard where it failed, and date the amendment.
Put a review date on it, and write the rule that a new or reset device gets configured before it travels.

Return to the sheets from Lessons 01 through 09. Everything on them should now appear in the standard, or have been deliberately left out.

Answer all three knowledge checks to complete the course

← Lesson 09: Degraded, Denied, and Dead