Ball Receipt Under Pressure & Intent Tracking

Ball receipt events are logged separately from pass events, giving each receiving player their own timestamped record. Crucially, receipt events are also logged for incomplete passes when the intended recipient can be confidently inferred — this enables intent-based analysis even when the pass fails. Both receipt events and the subsequent actions from that receipt can be tagged under_pressure independently, allowing analysis of chains of pressured events (e.g., pressured receipt → pressured pass).

Correct usage: treat ball receipt as its own event with its own pressure tag, not just an attribute of the preceding pass. A pressured receipt followed by a pressured pass represents three consecutive under-pressure events (pass + receipt + next pass). For incomplete passes, the receipt record is added when the intended target is "very clear" — providing intent context for turnovers and clearances. Use receipt pressure tags to identify which players consistently receive the ball already under pressure vs. those who receive cleanly.

1. Ignoring receipt events in pressure analysis: Pressure on a receipt is as analytically important as pressure on the subsequent pass — the player had no time to settle before being forced to act.
2. Discarding incomplete-pass receipt records: These tell you intent. A player who consistently aims toward pressed teammates is making a different error than one who loses the ball under direct press.