The problem with shooting at a spot
The standard arrow consistency check after fletching is to use a 3-spot target: shoot one arrow at each face and compare the impact locations across all three. If all three land in the same relative position on their respective faces, the arrows are consistent with each other. If one arrow’s impact location is noticeably offset from the others, that arrow is flagged for nock rotation or culling.
Shooting the same arrow repeatedly at the same face does not test consistency between arrows — it only confirms that the arrow is consistent with itself, which is always true and tells you nothing. The variation you care about is between arrows, and that only shows up when you shoot different arrows and compare where they land.
The problem is that the archer is inside this measurement. Every arrow that goes through that bow was launched by the same person, with the same form variability, the same timing inconsistencies, the same slight grip variation. The group you observe is not the arrow’s group — it is the combined group of the archer and the arrow, with no clean way to tell them apart.
When an arrow lands a quarter inch outside the main cluster, was it the arrow or was it you? You suspect it was the arrow. You cannot confirm it. You shoot it three more times and two of them are fine, so you keep it. That arrow may still be the worst one in the set and you have no method to know.
Shooting at a spot is a two-dimensional problem. Impact position is a vector — it has both a horizontal component and a vertical component. Each shot produces a point on a two-dimensional plane. Separating arrow error from archer error in two dimensions simultaneously requires a large number of shots and statistical methods most archers do not apply. In practice, it means the arrow test is heavily contaminated by the thing it is trying to exclude.
Why a line changes the problem
A vertical line on a target face reduces the measurement to one dimension. The only variable that matters is where the arrow lands horizontally relative to the line. Left, right, or on it. Vertical position is irrelevant and deliberately ignored. The two-dimensional problem has been collapsed to a one-dimensional measurement, and in doing so the signal-to-noise ratio of the arrow test improves dramatically.
The deeper reason this works is what a line does to shot-calling. When you shoot at a spot, you know the pin broke somewhere in a 360-degree circle around the target — you might call it “a little high and left” or “pulled it slightly right,” but your spatial confidence in that call is limited. Your ability to account for your own error is coarse.
When you shoot at a vertical line, your shot call has only three valid answers: the pin broke left of the line, right of the line, or centered on the line. That is a categorical judgment, not a spatial one. Humans are significantly better at making categorical left-right judgments than at estimating precise 2D angular deviations. The shot call becomes reliable enough to actually use as a filter.
That is the key mechanism. You are not just measuring where arrows land. You are filtering the measurement by whether the shot was centered — and only counting the shots where you confidently called center. Those shots have near-zero known archer contribution in the horizontal plane. Whatever horizontal deviation remains at the target is the arrow.
Test distance
Twenty to thirty yards is the correct range for DIAG. The reasoning is grounded in what the method depends on: the shot call. DIAG’s power is entirely in filtering called-center shots — if the filter degrades, the test degrades with it. At 50 or 70 meters, wind, hold fatigue, and timing pressure all erode shot-call reliability. The filter becomes noise. Shorter distance restores it.
The angular error that separates a biased arrow from a consistent one scales linearly with distance — an arrow that is off at 20 yards is proportionally more off at 70 yards. You do not need to verify that the geometry holds at distance. Physics guarantees it. Test where your shot call is most reliable, not where the deviation is largest.
For indoor competition prep, 18–20 yards is appropriate and conveniently close to tournament distance. For outdoor prep, 20–30 yards — indoors if possible to eliminate wind as a confounding variable.
Why horizontal first
Modern compound bow systems are inherently stable in the vertical direction. Nocking point height, rest height, and cam timing are all set during the initial bow build, and once correct they produce consistent vertical arrow flight across a well-matched set. Vertical inconsistencies between arrows do exist, but they are usually small and they are rarely correctable through nock rotation — a small nock orientation change has almost no effect on where an arrow lands vertically.
Horizontal deviation is where compound systems are finicky, and where nock orientation does its work. The dynamic spine oscillation that drives left-right arrow exit is sensitive to small asymmetries in the arrow — nock concentricity, insert seating, minor shaft straightness variation. Rotating the nock changes how that asymmetry aligns with the cam and rest at the shot, and can meaningfully shift the arrow’s horizontal landing position. This is the adjustment that DIAG’s first pass is designed to exploit.
Testing horizontal deviation first — with the vertical line — gives you the dimension where nock tuning has leverage. The nock orientations you lock in during the first pass are then held fixed for the second pass, which tests the dimension where nock tuning has little leverage and arrows either pass or are pulled.
Setting your pass criterion
Before you shoot a single arrow, decide what passes. This is the maximum deviation from the line you will accept on a called-center shot. Any called-center shot that lands beyond that threshold is a fail for that arrow at that nock orientation.
The right threshold comes from your competitive goal. If you are chasing a 90x game indoors, your arrows need to be consistent to roughly ¾″ at test distance. Work backwards from the X ring at your tournament distance: that is the tolerance the shot has to live inside, and your arrows have to contribute a small enough fraction of that budget that the remaining error is yours to control.
Tighter goals require tighter criteria. An archer satisfied with clean scoring hits has more budget than one chasing X’s at distance. Setting the criterion before you start matters because it removes the temptation to make a judgment call arrow-by-arrow after seeing results. If the threshold is ¾″, every called-center shot beyond ¾″ fails, regardless of how close it was. The criterion is a commitment to objectivity, not a grade on a curve.
The procedure — vertical pass
Set up a tall target face — two sheets of paper stacked top to bottom works well — with a single vertical line running full height through the center. Each arrow is assigned its own position along that line, spaced roughly 4 inches apart vertically, numbered top to bottom before you start. The spacing just needs to be enough that each arrow’s holes do not crowd the neighboring arrow’s data. Aim each arrow at the vertical line, at its own designated height.
Shoot the full set in order — arrow 1 through 12 — each to its assigned column, all aimed at the same vertical line. Call each shot before looking. Then pull and repeat the same sequence. Two or three full passes through the set gives you enough called-center data per arrow to see a pattern.
The reason for sequential cycling rather than exhausting one arrow before moving to the next is fatigue and condition management. If you shoot all of arrow 1’s trials first and all of arrow 12’s trials last, arrow 12’s data is systematically collected later in the session — when your hold muscles are more fatigued, your form has drifted slightly, and any ambient conditions have shifted. That is a bias applied to arrow 12 that arrow 1 did not experience. Cycling through the full set on each pass distributes fatigue and conditions evenly across all arrows. Any systematic drift in the session affects every arrow equally, and drops out of the comparison.
For each arrow, only called-center shots count toward its horizontal baseline. If you called left and it landed left — that was you. Discard it. If you called center and it landed right of the line — that is the arrow. Log it: which arrow, which direction, approximate distance from the line.
What you are looking for across the set: do all called-center shots land on the line, or does each arrow have its own consistent offset? Arrows with consistent offsets may be nock-rotatable into agreement. Arrows with random scatter on called-center shots have an internal inconsistency — likely nock concentricity or insert variation shot-to-shot — and are a different problem from a directional bias. Arrows that reliably land on the line at their correct nock orientation are your reference arrows.
Nock rotation — using the bias rather than fighting it
When an arrow consistently lands left or right of the line on called-center shots, it has a directional bias at that nock orientation. Before culling it, try rotating the nock 90 or 180 degrees and repeating the test. A bias that comes from a slightly off-center insert or a minor shaft bend will rotate with the nock — the direction of the bias will change predictably as the orientation changes. Find the nock rotation where the bias is minimized or eliminated, and that is the arrow’s tournament orientation. Mark it.
An arrow whose bias does not change with nock rotation — it consistently lands in the same direction regardless of how you orient the nock — has a fixed bias source that is not in the nock. Likely candidates are a slightly off-center insert, a tip that is not perfectly on-axis, or an insert not fully bottomed. These are more work to diagnose and may or may not be worth the time depending on how far off the arrow is.
Nock rotation is the tuning step of the first pass — and only the first pass. The orientation you lock in here carries forward into the second pass. Any nock change made after the first pass is complete invalidates the horizontal characterization and requires restarting from the beginning. This is why the two passes have different objectives: tune in the first pass, pull in the second.
The horizontal pass — pull, don't tune
After the vertical-line pass you know where each arrow lands horizontally on called-center shots, and each arrow is locked into its correct nock orientation. But you have deliberately ignored vertical deviation throughout. An arrow that lands exactly on the vertical line on every called-center shot might still be landing two inches high or two inches low relative to the rest of the set. You have not tested that yet.
Rotate the line 90 degrees. Now it is a horizontal line. The one variable that matters is where each arrow lands vertically relative to the line. Your shot call has three answers: pin broke high, low, or on the line. The same filtering logic applies: only called-center shots count toward the arrow’s vertical characterization.
The critical difference from the first pass is what you do with arrows that fail. In the first pass, a biased arrow is a candidate for nock rotation. In the second pass, nock rotation is not an option — rotating the nock to correct a vertical bias would undo the horizontal orientation that was established in the first pass and invalidate that work entirely. An arrow that passes the first pass and fails the second is pulled from the set. The nock orientation that was correct in one plane cannot be independently corrected in the other without restarting the full procedure.
An archer who wants to rescue a failing arrow can restart DIAG from the beginning with a different starting orientation — but that is a deliberate choice to redo all the work, not a mid-procedure adjustment. The default path is simpler: tune in the first pass, pull in the second.
Why this is different from a machine test
A shooting machine removes the archer entirely and shoots every arrow under identical mechanical conditions. This is the gold standard for arrow characterization. It is also not available to most archers, and it misses one thing DIAG captures: how the arrow behaves with the human archer’s specific bow and specific draw cycle. A machine finds the arrow’s intrinsic consistency. DIAG finds the arrow’s consistency in your system.
These are not the same thing. An arrow that is mechanically perfect in a machine test might interact unfavorably with your cam timing, your rest, or your arrow’s specific oscillation pattern at your draw length and weight. An arrow that passes DIAG under your shot is confirmed to be working correctly in the actual setup it will be used in. That confirmation is arguably more directly useful than a machine result for the archer doing their own sorting.
What the test does not fix
DIAG characterizes fletched arrows in their current state. It does not diagnose what is wrong with a failing arrow — it identifies that a bias exists and gives you a direction and magnitude, but not the source. The diagnostic path for a biased arrow runs through the insert-concentricity spin test, a tip replacement, and a nock-and-insert re-bedding check. DIAG tells you which arrows need that work. It does not do the work itself.
It also requires honest shot-calling. An archer who calls center on shots that were not center will contaminate their own data. If you are not confident whether a shot was center or slightly off, do not count it — discard it and shoot again. The power of the method is entirely in the filtering step. Contaminate the filter and you are back to the same noise problem that shooting at a spot creates. The method is only as good as the self-honesty of the person using it.
The practical reality is that shot-calling improves with practice. Archers who do not currently call their shots accurately will find the first few sessions humbling. That is useful information in itself. An archer who cannot reliably call left-right on a vertical line has a form consistency problem that no arrow test will fix.
The set you end up with
After both passes — vertical line for horizontal characterization, horizontal line for vertical characterization — you have a sorted set. The arrows that passed are confirmed in two dimensions. They were tested with your bow, your draw, your release. The remaining uncertainty in your groups is you. When you are shooting for score and an arrow misses the X, the confirmed arrow set tells you something important: it was not the arrow. Every miss is feedback about the shot, not a reason to suspect the equipment.
That is the actual goal. Not perfect arrows, which are achievable with enough work. The goal is known arrows — arrows whose behavior is characterized well enough that when something goes wrong, you know where to look.
Published 2026-08-17 · Axial Bowstrings