Identify the active reporting source
Read the current order before touching geometry. Pick one active report and confirm its source marker is visible on the map with the same source label. A spotter bearing belongs to its own source, not the Nest.
If the source label is not visible, pause and recover the report context before drawing any line. Work with one reporting source at a time until its constraint is either accepted or discarded. This avoids mixing an older report into the final firing measurement.
Draw each report line from its origin
Once a source is active, draw its line or radius from that exact source only. Do not connect to the Nest until the active reports identify a usable target point. If the report gives a distance, keep the radius tied to its named source.
If the report gives a bearing, its line is still part of locating the target and is not yet turret input. Add a second independent report only when its source is clear and current. The goal is a candidate target point, not the final firing line.
Create a candidate from at least two constraints
Use line-line or line-circle intersections from the active reports to form one candidate point. If the point is not clear, do not convert it yet. Keep candidate construction local to the current command target and avoid using prior mission geometry.
A candidate point is valid only for the current reports and should not be reused as a permanent value. Continue to the final measurement only after the candidate is stable, and keep only one target active while preparing the shot. Finish that firing cycle before plotting another target.
Convert once from IRON NEST
After candidate is set, draw one fresh measurement from IRON NEST to that point. This is the bearing and range used for turret data, never the report line directly. Use the fresh measurement to read both bearing and range together.
These two values are then the only map values that enter the calculator for that target. If the candidate changes before loading, confirm it again and redraw the line from the Nest. Updating only bearing or only range is a common way to preserve a wrong-origin measurement.
Verify target point before turret transfer
Before turret transfer, check that the selected point still matches the latest active reports. If one report point no longer exists in the visible context, redraw the candidate first. Do not transfer turret values from a stale candidate while report context changed.
Confirmed reports protect the firing solution from an obsolete target point. If the map has become cluttered, clear extra notes and rebuild the candidate from the current reports you can identify with confidence. A clean restart is faster than trying to repair a line with an uncertain origin.
Use a correction-first workflow
When a correction is needed, trace each map line back to its current source first. Confirm both the named source and target point before making turret edits. Then redraw the Nest-to-target measurement and rerun the calculator if the range changed.
If only the turret settings changed, return to the same sequence and keep the current report lines intact. A correction is more reliable when treated as a complete sequence rather than an isolated angle change. This keeps origin mistakes from being repeated in the next cycle.
Check both origin meanings
A report line should point to where the spotter measured; a firing line should point from the Nest to the candidate. These are different jobs, and they can produce different endpoint behavior if mixed. A quick self-check is to reverse-extend each line in your head.
If reversal reaches a different source than expected, the line is being used in the wrong role. Only the Nest-derived reversed-free line drives turret input; report lines stay for locating and validating the target. Keep these roles distinct for every loop.
Finish with one verified final transfer
Before load, run a final one-pass check: active target, source verification, candidate point, Nest line, and card match. If any step is out-of-date, rerun from that step before loading. Do not split this check across multiple cycles, because split checks are the first route to stale origin reuse.
A single continuous check is easier to audit and easier to recover. If you get the check right once, each shot starts cleaner. Keep this pattern for both first-round fire and correction shots.
Know what this flow is not
This topic is about using the correct origin, not memorizing mission-specific coordinates or universal target solutions. Treat every point as temporary until the current mission and reports confirm it. If a mission update changes map symbols or report behavior, repeat the process with the latest reports.
The workflow stays useful even when the map presentation changes. Do not build a fixed route from a single example shot. A memorized route can become wrong when a mission or game build changes.