Introduction

The base drill asks the brain to do a significant thing: scan ahead, commit to a destination out loud, carry the ball without watching it, and count any lapse in that discipline honestly. For most players in the 9–12 band, this is a full cognitive load — well above what the match currently demands of them.

By the 13–16 Development band, that capacity has expanded. The base drill's working-memory demand — gate sequence, no-repeat rule, call-before-entry — should be manageable without conscious effort for a player who has trained it. When a skill is automatic, it is not being trained; it is being confirmed. Dual-Stream Spotter re-introduces the training edge by adding a second simultaneous information stream: a partner calls single digits at irregular intervals, and the player holds a running total while the full gate discipline continues unchanged.

This creates a dual-task architecture the base drill does not attempt. The player now manages two concurrent demands — visual-perceptual (gate scanning and commitment) and auditory-cognitive (number tracking and accumulation) — neither of which can be paused while the other is processed. It is closer to the real cognitive environment of a match, where a player carrying the ball must read the gate ahead, hear a teammate's call, and decide which piece of information takes precedence.

The number-tracking task does not replace any element of the base drill. It adds to it. Gate calls are still made from 3m, with the ball moving, by colour and position name. Blind entries are still counted. The no-repeat rule holds. The block structure is identical. The dual-task is the single new constraint — but it changes the cognitive character of every run.

Setup

The field setup is identical to the base drill:

   [Y]                          [R]
    •  •                      •  •          R = red gate (×2)
                                            B = blue gate (×2)
              [B]                           Y = yellow gate (×2)
               •  •
                                            each gate 1.5m wide,
   [R]                  [HOME]              scattered orientations,
    •  •                ▪    ▪              ≥4m between gates
                        ▪    ▪
                                  [Y]
              [B]                  •  •
               •  •

         ← — — —  12–15m × 12–15m  — — — →

Six gates, three pairs, home square at centre — all as in the base drill. Any surface with at least 12m × 12m works: garden, park, pitch, or indoor hall.

Partner position: the caller stands outside the playing area at one end. A clear, fixed calling position keeps the acoustic challenge low at Levels 1–2 (one sound source, predictable direction). From Level 3 the partner rotates around the perimeter so sound arrives from different directions, adding a spatial tracking component.
Number protocol: the partner calls single digits, 1–9 (no zeros at base levels — zero is reserved for the Level 5 "discard" signal). Numbers are called between gate entries, ideally during the approach, not as the player is entering a gate. The partner records every number called on a notepad or phone so the player's end-of-run report can be verified.
Reporting: the player reports the running total aloud at the end of each run, before stepping into the home square. The partner confirms or corrects. One-digit accuracy is the standard; systematic errors are diagnostic.
Pre-brief: before Run 1, player and partner spend 60 seconds agreeing the protocol — how fast, where the partner stands, what signals are used — so the communication rhythm is set before the timer starts.

Description

While running the full base drill — call-before-entry, blind-entry count, no-repeat rule — the player also tracks a running total of single digits called by the partner. One run is 60 seconds, continuous:

Start in the home square. Partner prepares to call. Timer starts on first touch.
Gate calling proceeds as in the base drill: 3m minimum call distance, ball moving, colour and position name.
Partner calls a number (single digit, 1–9) during the run — ideally 2–4 times per 60-second run at Level 1. The player adds it to the running total mentally. Neither the carry nor the gate-call stops to process the number.
Blind entries are counted aloud as normal. The count does not interact with the running total.
At 60 seconds, the player reports the running total aloud to the partner before stepping into the home square. The partner confirms or corrects.
Record both numbers — blind entries, and number accuracy (correct/error, and by how much if incorrect).

Block structure is the same as the base drill: 3 blocks × 4 runs, 90-second rest between blocks (record, re-randomise from Level 2, discuss accuracy with the partner).

There is no instruction on when to integrate the called number. The player discovers their own approach across sessions — some integrate immediately during a steady-state carry, some defer to the moment of gate entry, some process during the return carry after a gate. All are valid. The point is not to prescribe the strategy but to create the conditions where the player must develop one. Coaching on strategy comes only after three full sessions of the player having found their current approach — and even then, as a question: "When in the run do you find it easiest to take in the number?"

Progressions

The call-before-entry rule and blind-entry count hold at every level. The dual-task is structural from Level 1 — not a progressive addition.

Level 1 (baseline — dual-task introduced): as described. Partner calls 2–3 numbers per run, stands fixed at one end, gate layout fixed. Mastery signal: number total accurate (±0) across a full block while blind entries hold at or near the player's solo base-drill average.
Level 2 (higher call frequency + layout variability): partner calls 4–5 numbers per run; gate layout re-randomised at each between-block rest. Working memory now holds gate sequence, running total, and the new gate positions — three concurrent memory tasks.
Level 3 (spatial sound variability): partner rotates around the perimeter, so numbers arrive from different directions. The player locates the sound source in their peripheral auditory field without turning to look — training the match skill of processing teammate calls in motion without losing visual orientation.
Level 4 (timing collision): partner deliberately calls a number at the moment the player is mid-entry on a gate — the cognitively densest point. The player completes the entry (gate commitment is irreversible once called) while holding the new digit. Any gate abandonment after a mid-entry call counts as a blind entry — if called, enter.
Level 5 (discard signal + fatigue): 5 down-ups or a 10m sprint before each run. The partner introduces a "zero" call mid-run: on hearing "zero!" the player discards the entire running total and restarts from zero on the next number. Inhibition control, working-memory restart, and scanning discipline all under physical fatigue. Base-drill Level 5 constraint cards can be layered for the maximum version.

Coach guidance

Look for:

Blind entries increasing when a number is called — head drops, call abandoned, gate entered without announcement. The number is winning the attention competition; expected early, resolves with reps.
Number total drifting off by more than ±1 per run — poor integration, either not hearing, failing to add quickly, or losing the total when a gate commitment competes for working memory. Ask whether the error is in the arithmetic or the hearing; the player can usually name which.
The player stopping the carry to integrate a number — inhibition control isn't holding. The prompt is not to stop stopping; it is "what happens if the ball keeps moving while you add the number?"
Communication rhythm — early sessions often see acoustic collisions between the player's gate call and the partner's number call. Establish between-gate timing quickly; from Level 2, deliberate collisions are part of the constraint.

Cues (partner, between blocks): "What did you do when the number arrived during a gate approach?" — "Which number were you on when you lost the total?" — "When in the run did the two streams feel most manageable?"

Cues (coach, if present): "Both streams are live — what's your strategy for the next run?" — "The gate discipline dropped after the number call. What's the sequence you want?" — "One stream improved, one didn't. Which failure is more informative to you?"

Praise:

Both streams accurate on a run: "Gate discipline held AND the total was right — that's dual-task integration working."
Naming the specific cause of a number error: "You named exactly which gate call cost you the total — that's the cognitive diagnosis, not just the score."
Maintaining the carry through a number call without pausing: "The ball kept moving when the number arrived. The integration is starting to happen in the background."

Don't fix yet: early-session accuracy errors on the running total; the initial blind-entry increase versus solo base-drill sessions; the player talking themselves through the total aloud during the carry (working memory externalised — it disappears as the process becomes internal; don't suppress it).

Watch points

Calling gates from progressively shorter distances when a number arrives — shortening the call window to buy processing time. Redirect: "What's the minimum call distance you can hold when the number arrives? Find that number in the next run — don't let it go below three metres."
Reporting the total confidently but incorrectly — the player has reconstructed a number from memory rather than tracking it live. Redirect: "How sure were you of that total? On a run where you're uncertain, can you tell the difference between 'I tracked it' and 'I reconstructed it'?"
Treating the two metrics as competing — improving one by letting the other slip. Redirect: "Which stream did you prioritise that run — and what made you choose that one over the other?" Explicit attention allocation is the target; unexamined trade-offs are not.
The partner calling unpredictably in volume or tempo, creating load that isn't progressive or intentional. Redirect (to partner): establish a consistent call frequency per run at each level and only increase it once the player has stabilised. Uncontrolled variability is noise, not a constraint.
The player laughing, commenting, or showing frustration mid-run in response to a call — losing the composure that keeps both streams active. Redirect, after the run: "You broke off mid-run. What happened in that moment — was it the number or something about the gate sequence?" The mid-run break is expected and not worth addressing during the rep.