← All posts
·GADUIN Researchevent-contractstrading-journalpnl-trackingperformance-metricsposition-sizingflight-delay-trading

Event Contract Trading Journal: P&L Templates & Metrics

A trading journal template for event contract traders, with P&L fields, hit rate, EV accuracy, drawdown analysis and performance metrics.

Last updated

Why a Trading Journal Is the Missing Edge in Event Contract Speculation

Most event contract traders judge their decisions from memory. After a good week they assume their approach works. After a bad one they blame luck. Neither is based on data. A trading journal turns those impressions into numbers you can measure.

Without a proper record, you can’t tell real skill from noise. A trader whose positions pay off 60% of the time over twenty trades may have had favourable conditions, or may really be pricing delays better than the market. Only a journal with consistent fields and calculated metrics can show which.

Record every event contract trade: route, cost basis, position size, outcome and realized P&L. Every analysis below is built on that data. For a wider look at trading event contracts for profit, see How to Profit Trading Flight Delay Event Contracts.

The Core Fields Every Event Contract Trade Entry Needs

A basic trade log needs eight fields. Every metric later in this article is calculated from them.

1. Route / Asset. The route and flight number (e.g., JFK–LHR BA 175). For shipping contracts, record the vessel name and port pair.

2. Entry Date & Time. The exact time you opened the position. This lets you compare your entry timing with the data available then: ATFM restrictions, weather alerts, aircraft rotation status.

3. Cost Basis per Unit. The price you paid per share, in US cents. It’s also the most that share can lose.

4. Position Size. The number of shares you hold. Multiply by cost basis per unit to get the total you put in: position size × cost basis per unit.

5. Your Delay Probability Estimate. Your own estimate of the chance of a delay when you entered, as a percentage. You need this field to track EV Accuracy.

6. Contract Threshold. The delay threshold set in the contract (e.g., 15 minutes). You need it to compare different contracts.

7. Settlement Outcome. The outcome the market settled on: On time, Delayed or Cancelled. These are three separate outcomes on a flight, train or ship market, so log Cancelled as Cancelled, never as a very long delay. On a count market (ship transits through a chokepoint in a week, or an airport’s flights in a day), record Yes or No: whether the count came in above the threshold set when the market opened.

8. Realized P&L. The net result in USDT: (settlement value − cost basis per unit) × position size. Settlement value is $1.00 for the outcome that happened and $0 for every other outcome. Record gains as positive numbers and losses as negative.

Fill in every field. Each missing value makes every metric built on it less reliable.

Context Fields That Make Your Journal Actionable

Core fields tell you what happened. Context fields tell you why, so you can break results down by cause of delay.

Weather Flag at Entry (Y/N). Was there significant bad weather at the origin, destination or hub when you opened the position? Compare this flag with the IATA delay code to see whether your weather-driven positions do better than your average.

ATFM Slot Restrictions (Y/N). Were EUROCONTROL Air Traffic Flow Management restrictions in force on the route when you entered? EUROCONTROL publishes ATFM delay data that you can check against your positions. If ATFM-flagged trades keep doing better, that data is giving you a real edge.

Aircraft Rotation Risk (Y/N). Is the inbound aircraft coming from a route that’s often late? Reactionary delay from aircraft rotation is one of the main causes of late arrivals. For trading several positions on knock-on delays, see Cascade Delay Trading: Multiple Event Contract Positions.

IATA Delay Code. The IATA delay code given for the flight, when you can find it (airlines mostly use these codes internally). Examples: code 11 for late check-in, code 81 for ATC en-route capacity restrictions, code 71 for weather at the departure airport. Comparing your flags before entry with the actual codes shows which signals really predict delays.

Trade Notes. Free text for anything unusual: crew shortages, aircraft swaps, gate changes, or other information that affected the trade.

Once you’ve logged 50–100 trades, these fields let you answer questions like: Do ATFM-flagged positions pay out more often than unflagged ones on the same route? For which data to check before you open a position, see Pre-Trade Research: 5 Data Signals Before Buying a Flight Delay Event Contract.

Google Sheets Template: Layout and Formulas

A Google Sheet with three tabs covers most event contract tracking. No programming needed.

Tab 1, Trade Log: one row per trade, with these column headers in this order:

Route | Entry Date | Cost Basis/Unit | Position Size | My Prob Estimate (%) | Contract Threshold | Outcome | Realized P&L | Weather Flag | ATFM Flag | Rotation Flag | IATA Code | Notes

Keep the column order fixed and add each new trade as a new row. Don’t merge cells or use colours in place of data, because formulas can’t read colours.

Tab 2, Performance Dashboard: calculated automatically from Tab 1. The hit-rate formulas below assume every row is a position on Delayed.

  • Hit Rate: =COUNTIF(TradeLog[Outcome],"Delayed")/COUNTA(TradeLog[Outcome])
  • Average P&L: =AVERAGE(TradeLog[Realized P&L])
  • EV Accuracy gap: =AVERAGE(TradeLog[My Prob Estimate])-COUNTIF(TradeLog[Outcome],"Delayed")/COUNTA(TradeLog[Outcome])
  • Max Drawdown: from a running cumulative P&L column, find the deepest drop from any earlier peak
  • Sharpe-like Ratio: =AVERAGE(TradeLog[Realized P&L])/STDEV(TradeLog[Realized P&L])

Tab 3, Asset Roster: a summary by route. Use SUMIF for total P&L per route and COUNTIF for the number of trades per route. It shows which routes make money and which lose it.

The same template works for shipping contracts (replace Route with Port Pair) and rail contracts (use the train service code). Only the description of the asset changes. The fields and formulas stay the same.

Performance Metrics That Tell You Whether You Have an Edge

Five metrics from your trade log are enough to tell whether you’re consistently profitable or just lucky.

Hit Rate. The percentage of trades that settle in your favour. Read it against your average cost basis. At 0.30 per unit, where the market gave the outcome a 30% chance, a 35% hit rate has positive expected value. At 0.50, you need more than 50% to break even.

EV Accuracy. The difference between your average probability estimate at entry and your actual hit rate. Near zero means your estimates are well calibrated. A steady positive gap means you overestimate how often delays happen. A negative gap means you underestimate it.

Sharpe-like Ratio. Average realized P&L divided by its standard deviation. It works like the Sharpe ratio in portfolio management and measures return per unit of P&L volatility. A higher number means steadier results.

Max Drawdown. The biggest cumulative loss from a P&L peak to a later low, in USDT or as a percentage of the money you put in. BTS On-Time Performance data can give you a baseline delay rate by route to compare your hit rate with.

ROI by Asset. Total realized P&L divided by total cost basis, per route. It shows your best markets and the routes to drop from your list.

None of these numbers means much from a small sample. Wait for at least 30 settled positions before drawing conclusions from any of them.

EV Accuracy: The Calibration Metric Most Traders Skip

Most traders track hit rate. EV Accuracy shows whether your hit rate matches the probabilities you estimated when you entered.

For example, over 20 trades your average estimate at entry was 62%, and your actual hit rate was 45%. The EV Accuracy gap is +17 percentage points: you kept thinking a delay was more likely than it turned out to be. With estimates that far off, you’ll lose money even when a well-calibrated trader would make it.

The direction of the gap tells you what to look at:

  • Positive gap (you overestimate how often your positions pay out): your data sources may show a worse on-time record than the route really has, or you’re not allowing enough for good weather.
  • Negative gap (you underestimate how often your positions pay out): you may be too cautious and passing on contracts priced well below how often delays actually happen.

Don’t fix this by nudging your estimates at random. Find the routes or conditions that cause the gap. Filter your journal by Weather Flag = Y or ATFM Flag = Y and compare EV Accuracy within those groups.

For the basics of calculating EV, see Expected Value (EV) for Event Contract Traders. For finding markets where the price is out of line with historical delay rates, Finding Mispriced Flight Delay Contracts explains how to screen for them.

Drawdown Analysis and Sizing Discipline

Use the drawdown data from your journal to set your position sizes, in three steps.

Step 1: Set a drawdown limit. Choose the largest loss you’ll accept over a rolling 7 days, as a percentage of the money you’ve put in. −15% is a common starting point.

Step 2: Automate the alert. In the Performance Dashboard, use conditional formatting to highlight the rolling 7-day P&L column when it goes past the limit. Then you don’t have to check it by hand every day.

Step 3: Cut size after a breach. When you hit the limit, halve the size of new positions until your running P&L gets back to the peak before the drawdown. This only applies during the drawdown. Once you’re back at the peak, return to normal sizing.

The maths behind this is in Risk of Ruin in Event Contract Speculation: How Much to Risk Per Trade. If you ignore drawdown limits, a run of losses can wipe out your capital faster than wins can rebuild it.

Sizing based on hit rate needs a stable estimate from at least 50–100 trades in your journal. A sizing formula applied to 10 trades gives you mostly noise.

The Weekly Review Ritual: From Data to Better Decisions

A journal is only useful if you review it regularly. A weekly review turns the data into changes in how you trade.

For each losing trade:

  • Did my ATFM or weather flag before entry match the actual IATA delay code?
  • Did I lose because of something I hadn’t flagged, or was it a low-probability outcome I’d estimated correctly?
  • Would I take the same position again with the same information?

Across the whole week:

  • Has the hit rate on my main routes moved more than 5 percentage points from the previous 30-trade average?
  • Is the EV Accuracy gap getting bigger or smaller?

Asset Roster review (monthly): Drop any route with negative cumulative P&L over 30 or more settled positions and replace it using delay-rate data. Best Flight Routes to Trade on GADUIN explains how to find routes that are consistently delay-prone.

Basis risk check: Flag routes where your position’s outcome and the actual delay don’t line up cleanly, for example because of threshold mismatches or data lag. Basis Risk in Event Contract Hedging explains how to spot and measure this in your journal.

The review doesn’t need to be long. If your dashboard is up to date, 20 minutes is enough.

Notion Alternative: Tracking Event Contracts in Notion

If you prefer Notion, you can build the same structure with linked Notion tables. The core fields map to Notion property types:

  • Route (Text)
  • Entry Date (Date)
  • Cost Basis / Unit (Number)
  • Position Size (Number)
  • My Prob Estimate (Number, percentage display)
  • Contract Threshold (Text: the threshold in the contract, e.g., 15 min)
  • Outcome (Select: On time / Delayed / Cancelled, or Yes / No for count markets)
  • Realized P&L (Formula field linked to cost basis and position size)
  • Weather Flag (Checkbox)
  • ATFM Flag (Checkbox)
  • IATA Code (Text)

Rollup for Asset Roster: Create a linked Route database, then roll up Realized P&L by route with Sum. That gives you the same per-route P&L view as the Asset Roster tab in Google Sheets.

Useful filtered views: “Open Positions”, “Settled, Positive P&L”, “Settled, Negative P&L”, “Last 30 Days”.

Notion’s main weakness here is formulas. Standard deviation and the Sharpe-like ratio are hard to build in Notion. Export the database to CSV once a month and calculate those in a spreadsheet. You can use both: Notion for entering trades on your phone and checking positions, Google Sheets for the analysis.


Risk Disclosure: Event contracts on GADUIN are financial instruments. All trading involves risk of loss, including loss of the full amount allocated to a position. This article is for educational purposes only and does not constitute investment advice. GADUIN is not available to US persons. Past performance data recorded in a personal trading journal does not guarantee future returns.

Look up flight status by flight number. The methodology explains scheduled, estimated and actual times.