Introduction

The base Weak-Foot Dribbling Gauntlet makes the weak foot reliable under physical variety. This variation makes the weak foot reliable under cognitive load — which is the match-relevant test.

In a match, the weak foot never operates in silence. While controlling the ball, a player is simultaneously reading a pressing defender, checking a teammate's run, deciding whether to turn or play forward, and managing the pressure of the moment. None of those concurrent demands appear in the base gauntlet. They are all present here — represented, at their simplest, by a flash signal the player must read and call while dribbling through Zones A and B.

The flash works through inverse design: the only way to catch it is to look up. Looking up is the easy path; watching the ball is the path that costs a missed flash. The player discovers eyes-up weak-foot carrying as the solution to the problem, not as an instruction from outside.

Two process numbers are tracked: rescue touches (weak-foot compliance, from the base drill) and missed flashes (eyes-up compliance, new here). A session improves when both numbers fall. A run where both rise is information — usually attentional overload that resolves with a brief single-task reset.

Setup

Identical to the base drill. Four zones in sequence: Slalom (Zone A) → Gate Maze (Zone B) → Turn Box (Zone C) → Finish Gate (Zone D). Same dimensions throughout.

Additional — the caller's position:

The caller stands beyond Zone D, at or just behind the finish gate, facing the player throughout the run.
Fingers 1–5 are visible to the player from the moment they enter Zone B.
The caller can read the player's head position — seeing both when the player looks up and when the player is ball-watching.
The caller never interferes with the player's path.

If the space is narrow, the caller can stand to one side of Zone D rather than directly beyond it — sightline from Zone B is the requirement, not exact position.

Flash cards (solo alternative): 5 numbered cards (1–5), each on its own sheet. Before each run, prop one card face-up at the Zone D end, visible from Zone B. The player reads it during Zone B and calls the number aloud. No caller required — the solo version is fully self-directed.

Description

The two rules:

Every touch is taken with the weak foot — strong-foot touches are rescue touches, counted aloud the moment they happen.
The player must call the flash number aloud at any point during Zone B — not before, not after.

One run:

Zone A — Slalom: dribble through all 5 markers with the weak foot, alternating inside and outside surfaces. The caller does not flash during Zone A — this zone is motor load only, letting the player settle before the cognitive demand begins.
Zone B — Gate Maze: as the player steps into Zone B, the caller raises a number (1–5) to head height and holds it. The player dribbles through any 3 of the 5 gates (no-repeat rule from the base drill applies) AND must call the number aloud at any point during Zone B — after the first gate, the second, or mid-turn, whenever they look up and read it. The caller drops the hand only after hearing the call clearly. Exiting Zone B without a call is a missed flash — one count, logged at the end of the run.
Zone C — Turn Box: enter the box, execute one named weak-foot turn (announced before entering Zone B), exit through the opposite side. No flash in Zone C.
Zone D — Finish: weak-foot strike or roll through the finish gate.
Count and log: at the end of each run, the player says two numbers aloud — rescue touches and missed flashes. The caller confirms both. These two numbers are the block's tracked data.

Turn-announcement timing: the player announces their Zone C turn type before stepping into Zone B, not at Zone C entry. Announcing the turn while fresh trains working memory to hold the intention through the flash challenge. A player who forgets the announced turn in Zone C is showing working-memory saturation — a useful diagnostic, not a failure.

Block structure: 3 blocks × 5 runs, 90 seconds rest between blocks. During rest: log both numbers for the block and — from Level 2 — re-randomise Zone B.

Two-number ledger:

Block 1 — Rescue touches: ___ / ___ / ___ / ___ / ___   Missed flashes: ___/5
Block 2 — Rescue touches: ___ / ___ / ___ / ___ / ___   Missed flashes: ___/5
Block 3 — Rescue touches: ___ / ___ / ___ / ___ / ___   Missed flashes: ___/5

Session improvement: either number falls from Block 1 to Block 3, or across sessions. Both falling simultaneously is the indicator that dual-task integration is occurring.

Progressions

Because this variation's Level 1 already corresponds roughly to the base drill's Level 4, the progressions begin from that higher baseline and continue into territory the base drill does not reach.

Level 1 (baseline — partner caller, fixed layout): as described. 5 gates in Zone B, 3 crossed per run, caller at Zone D, one flash per run, fixed layout across all three blocks. Two-number ledger throughout.
Level 2 (layout variability): re-randomise Zone B gates during each between-block rest. Route memory becomes unavailable; the player must read both the gates and the flash signal simultaneously in Zone B — two visual reads, one attention pool.
Level 3 (Zone A flash added): the caller also flashes a second, different number during Zone A — shown as the player reaches the third slalom marker. The player now carries two numbers across the run: the Zone A number (held through the A → B transition), then the Zone B number (read and called during Zone B). Misses are tracked per zone. Working-memory demand rises sharply; typically reached only after 4–6 sessions at Levels 1–2.
Level 4 (ball variability): each block uses a different ball (regulation, futsal, slightly soft), as in the base drill's equivalent level. The caller remains active. Three simultaneous variables: weak-foot compliance per ball type, layout re-randomisation, flash reading.
Level 5 (auditory override): the caller begins each run with a visual flash, but may at any point during Zone B call out a new number verbally — overriding the original. The player must update their call to the new number. Auditory signal overrides visual input mid-action: the highest cognitive load in the library to date. The player may also time runs against their own personal best for this variation.

Coach guidance

Look for:

Head position in Zone B. The player should visibly raise their eyes at least once during the gate maze. A player who never looks up will always miss the flash — the cognitive demand is not landing. Prompt once: "The number is there from the moment you enter Zone B." Then let the reps work.
Quality of the call. A call from Zone C's entrance does not count; a mumbled sound while exiting Zone B does not count. The call is clear and timely — audible from the caller's position, delivered while still in Zone B. Early on, accept any call in the zone; refine timing later.
Double-failure runs. A run accumulating both rescue touches and missed flashes usually signals attentional overload — the player is managing both tasks consciously and failing at both. Redirect by temporarily reducing to one task: "This run — ignore the flash. Just clean rescue count. Then add the flash back next run." This is a sequencing reset, not a regression; it teaches the player to prioritise attention.
Turn announcement. A player who forgets the announced turn type in Zone C is showing working-memory saturation from the flash challenge. Do not fix this at Zone C — prompt the announcement earlier: "What's your turn? Tell me before you step into Zone B."

Cues to give (questions where possible):

"The number is up — when you're ready."
"What did you see?"
"Head up before Zone B — the number appears the moment you enter."
"Which task did you protect that run: rescue count or flash?" (asked at rest, not during)

Praise:

"You called the number without breaking your dribble. That is the hardest thing in this variation."
"Missed flash, clean rescue count — you chose which task to protect. Now try the other."
"Both numbers fell from Block 1 to Block 3. The two tasks are starting to run together."
"You looked up and kept the ball going. That is the whole point."

Don't fix yet:

Flash-reading speed (early reps may need two seconds of looking up; this shortens naturally across sessions — do not rush it).
Turn-execution details in Zone C after high-flash-demand runs (momentary forgetting resolves without correction).
Dribble speed through Zone B during flash reads (it will slow, then pick back up as the dual-task becomes automatic — speed forced too early breaks the flash habit).

Watch points

The player pauses the dribble in Zone B to get a clean look at the flash — stopping the ball to read the number. Redirect: "The ball keeps moving. What is the smallest head movement that lets you see the number?" The player discovers that a one-second glance mid-dribble is enough, and stops stopping.
The player consistently misses the flash in Zone B but carries a clean rescue count. Redirect: "Rescue count is solid — the flash is the only remaining challenge. This run: don't count rescues at all. Just catch the flash. One task." Permission to focus on one task at a time builds the dual-task protocol slowly and without frustration.
The player calls the flash before entering Zone B — guessing from Zone A before they can see it. Redirect: "Call it when you can see it — not before. The drill is the reading, not the guessing."
Visible frustration after a run where both rescue touches and missed flashes are high. Redirect: "That run had everything happening at once — and you did not stop. Which task did you protect better: the rescue count or the flash? That is your answer for the next run." Frustration analysed becomes strategy.