arXiv’s q-fin sections and SSRN publish thousands of papers a year. Reading them linearly — abstract, introduction, literature review, model, results — is how an afternoon disappears into a paper that a 10-minute triage would have rejected. This is the reading order we use to process 5,000+ papers, and the framework behind our scoring system.

The two axes that decide everything

Before any technique: know what question you’re asking. Almost every judgment about a quant paper collapses onto two independent axes:

  • Math complexity — how much theoretical machinery the paper runs on: stochastic calculus and PDEs at one end, descriptive statistics at the other.
  • Empirical rigor — how seriously the claims were tested: real data, out-of-sample discipline, transaction costs, robustness checks.

These are independent. Elegant theory with zero data (“Lab Rats” in our quadrant system) is valuable for pricing engines and dangerous for trading claims. A simple idea tested brutally (“Street Traders”) is often more tradeable than a beautiful one tested never. The most common reading error is letting the math axis stand in for the rigor axis — difficulty is not evidence.

The 10-minute pass, in the right order

Read sections in order of information per minute, not page order:

1. Abstract (1 min): extract exactly two things — the claim, and whether it’s a theory claim or a performance claim. Performance claims (“Sharpe of 2.1”) set up the rest of the triage; theory claims redirect you to a different standard entirely.

2. The data section (3 min): this is the real abstract. Which instruments, which dates, which source, which frequency? Three instant filters: Does the sample end years ago (why?)? Is the universe survivorship-clean (the bias that manufactures alpha)? Is the data purchasable by anyone, or proprietary — reproducibility starts here.

3. The main results table (3 min): go straight to it. Look for what’s missing before what’s present: transaction costs, turnover, out-of-sample columns, a max drawdown. A returns table without turnover is unpriceable — see our cost framework. Check the number of observations against the number of things tested (the multiple-testing problem).

4. The methodology’s one load-bearing paragraph (2 min): every paper has one — usually where the signal is defined or the estimator chosen. Find it and ask the question from our Monte Carlo audit: is each parameter assumed or measured?

5. Skip entirely on the first pass: the literature review, the robustness appendix (note that it exists — its absence is data), and the conclusion, which restates the abstract with more confidence than the results earned.

Ten minutes in, you can place the paper on both axes and decide: read deeply, mine for one idea, or close.

Red flags that end a read early

  • Backtest starts when the data conveniently starts — sample-period-as-modelling-assumption, never acknowledged.
  • Performance claims with no costs and no reply to the obvious objection. Fixable by you, but the omission signals what else was skipped — run it through the backtest checklist.
  • Accuracy above 60% on daily direction of liquid instruments — almost always look-ahead leakage or an illiquid universe.
  • One spectacular equity curve, no error bars, no subperiods. A single path is one draw from a fan — see it interactively.
  • “Novel” + “AI” + no baseline. A deep model beating no sensible benchmark is an ablation, not a result.

Red flags that aren’t

Symmetry demands the opposite list. Don’t discard a paper for: modest Sharpe ratios (0.7 honestly measured beats 2.5 with leakage); negative or null results (the rarest and most trustworthy findings in the field); simple methods (simplicity survives out of sample better than complexity — a finding that recurs across our machine-learning hub); or prose quality (some of the best empirical work reads terribly).

Where the deep read goes, when a paper earns it

Deep reading is reverse engineering, not comprehension: reconstruct the pipeline — data → transformation → signal → portfolio → evaluation — until you could reimplement it. That’s precisely what our flowcharts draw for each paper, and why they exist: the pipeline diagram is the paper’s skeleton, and most flaws are visible in the skeleton. If the paper matters enough to trade on, the next step is the reproduction checklist — because the read-through is the cheapest gate, not the last one.

Browse triaged papers: by topic · highest empirical rigor first · The scoring rubric: score guide →