Direct answer
To verify information about “slippage questions,” confirm that the claim uses a consistent definition of slippage, clearly states measurement timing and inputs (expected price, executed price, and timestamps), and separates stable mechanics from variable conditions (market movement, spreads, execution method, and transaction costs). Then reproduce the stated calculation using the same assumptions, and test whether the claim still holds when timing or costs vary within reasonable ranges.
Mechanics and definition
Slippage generally refers to the difference between an order’s intended (expected) execution price and the actual executed price. In verification terms, the key is operational: what exactly counts as “expected” (for example, the price observed at order placement) and what counts as “executed” (the fill price), and whether the measurement uses comparable timestamps.
A useful way to keep the discussion factual is to write the claim as inputs and outputs:
- Inputs: expected price, executed price, direction (buy/sell), and the time reference used to define “expected.”
- Output: slippage magnitude (often absolute difference) and sometimes slippage in price terms per unit.
- Assumptions: whether costs are included (spread/commission/fees) or excluded, and whether the claim assumes constant liquidity.
If the claim mixes concepts (for example, using “spread widening” as if it were “execution slippage”), verification should flag that mismatch before doing any math.
Evidence and reproducible verification steps
Use a reproducible checklist that does not depend on live prices.
-
Confirm definitions and scope Check that the source defines slippage consistently and explains the measurement basis: expected price reference, fill price reference, and timestamp alignment.
-
Reconstruct the calculation Assuming the source provides the numbers needed, recompute slippage using the exact method described. State your own calculation explicitly (e.g., executed minus expected for buys, and the opposite sign convention if the source uses sells).
-
Audit the assumptions If the source excludes or includes costs, replicate the same rule. If it mentions “during news” or “volatile periods,” treat those as condition descriptors, not proof of causation.
-
Test sensitivity to variable conditions Where exact execution details are unavailable, perform a sensitivity check. For example, vary the expected-price reference within a small time window to see whether the conclusion depends on a fragile timestamp.
-
Look for failure of internal consistency A common failure mode is comparing numbers that come from different moments (expected price from one time reference, executed price from another). Another failure mode is using “average slippage” while ignoring that costs and spread changes can dominate the observed difference.
Limitations and risks, and what to verify next
Several limitations can make slippage information easy to misinterpret:
- Market and execution conditions vary: slippage is not a fixed property; it changes with volatility, liquidity, and order timing.
- Historical relationships do not establish future results: even if slippage behaved a certain way in the past, it may not repeat.
- Data quality and comparability: different sources may measure “expected” differently or use different time references.
- Incomplete information: without order timestamps and fill details, any computed slippage may be approximate.
Next verification question to ask: does the claim provide enough operational detail (definitions, timestamps, and inputs) to reproduce the stated slippage calculation under the same assumptions? If the answer is no, treat the claim as descriptive rather than verifiable.