Lock one active target
Start each cycle by aligning mission text, reports, and map. Pick one target label and keep every mark tied to it until the shot is ready. If report feed and command text disagree, pause and rebuild before placing geometry mark.
Do not carry two active candidates at once. One pending candidate should either move to load-ready conversion or be discarded fully before you open another. If the active command changes, archive the previous geometry and start again as a fresh task state.
Put each report line on its own report point
Use the report point named in the active report and keep that identity visible on the map until the target is resolved. If the geometry starts from the wrong symbol, every derived line is misleading even if it looks clean. A quick read of the report text is safer than reusing an old marker.
Use separate marks for separate reports while you build candidate geometry. This prevents a bearing from one report and a distance from another report from being mixed after a fast mission update. Remove marks that are no longer tied to the active target before you begin final conversion.
Match each report to the right map tool
For each report, use the bearing tool when that report gives a direction, and use the distance tool when the same report gives only radius. The output shape is different, so treat each as a separate constraint. Mixing these shapes before verification causes false crossings in tight corridors.
Use the red line only for the final Nest-to-target measurement. Red is the geometry that feeds the ballistic input, while exploratory marks remain temporary map work. Reusing an exploratory red line can send an obsolete range or bearing into the calculator.
Build one candidate from independent constraints
A valid candidate needs at least two independent constraints, for example two bearings or one bearing plus one distance arc. Build your own cross-check point only when the two constraints converge on one place and that place still makes sense in the active objective. After that point is identified, confirm the anchor points are still active in the current command context.
If the constraints disagree, do not force a candidate point. Keep the uncertain mark separate, wait for another report if needed, and rebuild from the latest report set. This is faster than correcting a target created from conflicting information.
Validate the candidate before conversion
Before conversion, trace each constraint back to its report point and confirm that same report point still belongs to the same objective text. If an anchor no longer exists in the current feed, the candidate must be dropped and remade. Keep a copy of which constraints were valid when the candidate was accepted so you can compare after any command update.
Reduce active marks to only what supports the current candidate. Keep additional scouting marks outside this working set because they can be useful for context but confusing during final measurement. This keeps the red Nest-to-target line easy to trace.
If command context changes while you validate, stop and rebuild from the latest state. A partial patch over old geometry blends one shot plan into another and usually causes false confidence when the correction step starts. The safe choice is to clear previous assumptions before recomputing.
Create one final IRON NEST-to-target line
When the candidate is approved, draw one red line from IRON NEST to the candidate point. Read bearing and range from that line only and keep the pair in one clipboard state. If either value changes, redraw the same line immediately.
Clear every old red line before computing. A red line from scouting or another target must not remain beside the current firing measurement. Keep only the current line active on the clipboard before opening the ballistic calculator.
Run compute once from live conversion and current load plan
Use the final range and bearing from the red line for the calculation. Confirm shell type and charge before computing, then generate one card for that exact combination. This card belongs to the same target and current firing setup.
If the card does not match the current target and load, go back before loading. Treat any old card as an obsolete result and never mix it with a new measurement. If the inputs are mixed, discard the card and rebuild from the map.
After firing, if correction is needed, begin again from the map and conversion. The same sequence prevents accidental edits after the turret is already in motion. Corrections should replay map proof, candidate, and red-line conversion in order.
Use report + candidate context to choose correction
Correct misses by first checking whether target candidate identity still matches the last report line and map point. Then verify the report-to-target geometry and recompute from the same live inputs. The same chain, not a guessed offset, must drive the correction attempt.
Do not patch one value while holding old context. If range, bearing, shell type, or charge changed at any stage, clear the old result chain and rebuild from first principles. Use a fresh candidate proof before touching turret settings again.
Each reset removes one hidden dependency. A rebuilt solution is easier to trust than a patch on stale geometry. Finish one correction before opening the next.
Common miss patterns and recovery
Most misses come from mismatched inputs rather than a broken targeting formula. Run a quick three-part check: active command text, active marks, and active card. If any one belongs to a different firing cycle, rebuild immediately.
Avoid adding quick offsets when the conversion geometry has changed. If the red line or the card is not current, any turret edit can hide the real break in the chain. In that state, return to the map and rebuild before any value adjustment.
Stay with one candidate target for one correction cycle. Expanding too early makes it hard to separate a map error from a loading error under pressure. If you need a second candidate, close this cycle and open a fresh one only after the current reports change.