Congressional trading backtest
A methodology-first backtest page for readers asking whether congressional stock trades beat the market, and for analysts who need the assumptions before trusting any strategy chart.
Short answer
A congressional trading backtest should separate transaction-date performance from filing-date public availability. Congressional Trader frames backtests around event date, benchmark, return window, amount-range handling, and look-ahead-bias controls before interpreting any strategy result.
Backtest input map
A credible Congress backtester starts by naming the assumptions before ranking a strategy.
Transaction or filing date
Transaction-date tests measure historical performance. Filing-date tests model what a public observer could know.
SPY first
A broad market proxy gives a simple alpha baseline before deeper sector-relative analysis.
30d / 90d
Short windows match the live leaderboard metrics and keep assumptions visible.
Range-aware
Public filings report amount bands, so exact portfolio-return claims should be avoided.
Sample purchase disclosures
R-OH · House
Disclosure delay: 13 days
R-OH · House
Disclosure delay: 13 days
R-OH · House
Disclosure delay: 13 days
R-OH · House
Disclosure delay: 13 days
What a congressional trading backtest has to control
A simple chart can overstate the signal if it assumes investors knew about a trade on the transaction date. Public filings often arrive later, so a backtest must separate historical trade performance from public-copy performance.
Congressional Trader treats a backtest as an assumptions problem first: choose the event date, benchmark, return window, transaction type, amount handling, and sample-size threshold before interpreting results.
- Transaction-date tests ask how the reported trade performed after it happened.
- Filing-date tests ask what a public observer could have monitored after disclosure.
- Amount ranges should stay as ranges instead of fake exact position sizes.
- Small samples should be labeled before they become leaderboard claims.
Transaction date versus filing date
The transaction date is useful for measuring whether the disclosed purchase later outperformed. The filing date is more important for any strategy that claims a public reader could act on the information.
Both views can be useful, but mixing them quietly creates look-ahead bias. A credible Congress backtester should make the date choice visible.
How to read benchmark-relative returns
A broad benchmark such as SPY helps separate market drift from stock-specific outperformance. For deeper analysis, sector-relative benchmarks can be better when a lawmaker repeatedly trades one industry.
The page should be read as research methodology, not as investment advice or proof of illegal conduct.
- Use purchase-only views when measuring copy-style upside.
- Read sales separately because they can reflect liquidity, tax, or diversification needs.
- Pair return windows with disclosure delay before judging whether the signal was actionable.
Related paths
FAQ
Can public congressional filings be backtested?
Yes, but only with clear assumptions. A transaction-date backtest and a filing-date backtest answer different questions because public disclosure is delayed.
What is look-ahead bias in congressional trade backtests?
It happens when a strategy acts as if the public knew about a trade before the filing was public. Filing-date tests are a cleaner way to evaluate public-copy workflows.
Why not calculate exact portfolio returns?
STOCK Act filings usually report amount ranges, not exact sizes or full portfolio weights. Exact portfolio-return claims would add false precision.
Is this an investment strategy?
No. The methodology is for research, monitoring, and understanding disclosure data limits. It does not recommend buying or selling securities.