Venue-Specific Impact-Decay Calibration for Live Slippage Control

2026-03-03 · finance

Venue-Specific Impact-Decay Calibration for Live Slippage Control

Date: 2026-03-03
Category: research
Focus: Practical modeling framework to separate temporary vs. persistent impact by venue and convert it into routing/participation controls.

Why this matters

Most desks estimate one global slippage curve, then wonder why costs explode when routing mix changes. Impact decay is not universal:

If you fit one decay kernel for all venues, you overtrade “slow-decay” venues and underuse “fast-decay” venues.

Modeling target

For parent order slices indexed by (i), model signed future price move after each child fill:

[ \Delta p_{i,\tau}=\alpha_{v,s,t}+\beta_{v,s,t},q_i^{\delta},G_v(\tau)+\Gamma_{s,t},M_i+\epsilon_{i,\tau} ]

Use a two-part view:

  1. Transient component (decays): execution footprint you may recover by waiting
  2. Persistent component (does not decay quickly): likely information/toxicity cost

Calibration pipeline (desk-operational)

  1. Event table: child fill timestamp, side, size, venue, fee/rebate, queue metrics, top-of-book state.
  2. Horizon grid: (\tau\in{1s,5s,15s,30s,60s,180s}) markouts (mid-based + executable-based).
  3. Regime stratification: volatility terciles × spread state × session bucket.
  4. Kernel family per venue:
    • power-law: (G(\tau)=(1+\tau/\theta)^{-\kappa})
    • stretched exp: (G(\tau)=\exp(-(\tau/\theta)^\nu))
  5. Hierarchical shrinkage: venue-symbol cells borrow strength from venue-level priors to avoid noisy small-sample fits.
  6. Walk-forward refit: daily incremental + weekly full refit; freeze parameters intra-session except alert-triggered fallback.

Key metrics to store

Converting model to execution decisions

1) Venue routing score

[ \text{Score}_v = -\widehat{\text{NetCost}}_v + w_r,\widehat{\text{Recovery}}_v - w_u,\widehat{\text{Uncertainty}}_v ] Route marginal flow to highest score under risk caps.

2) Participation throttle

If realized recovery < model P10 for N consecutive windows, reduce POV cap (e.g., 12% → 8%) and widen inter-slice gap.

3) Cooldown logic

For slow-decay venues (high (t_{1/2}), high (\pi)), add mandatory cooldown between aggressive clips, unless urgency state is critical.

Monitoring & drift alarms

Trigger alerts when any holds for >15 min:

Fallback policy:

Failure modes (seen in production)

Minimum implementation checklist

References


Bottom line: model impact decay by venue, not globally. The edge is not just lower average slippage; it is faster detection of regime breaks and safer automatic throttling before costs compound.