File a no-trade (null) ticket

Desk seat: Ops / Journal / Reporting

Next to this. The later review is the missed-trade log. The full template is the no-trade ticket skill.

The problem

A session with no order still needs a ticket, filed next to the missed-trade log. A blank page is not a record.

What the agent does

Writes a null ticket with a fixed reason code when the desk does nothing. The missed-trade log is the later review, not this ticket.

Copy-paste prompt

File a no-trade ticket for this session. Paper lane. Do not draft an order.
Date: [date]
Instrument: [e.g. BTC]
Session: [session name]
Map state: [trend, correction, neutral, or blank]
Reason, one code: [NO-SETUP, OUTSIDE-MAP, RULE-BLOCK, EVENT-RISK, ALREADY-IN, or OTHER]
What I saw, in one sentence: [paste]
Order drafted: no
Review date for the missed-trade log: [date, or blank]
Leave any field I left blank. Do not add a trade. Do not give buy/sell/hold advice or price targets; label facts vs. inferences and cite sources.

Works with

Grok, ChatGPT, Claude, Gemini, or any similar assistant.

Linked tools

Notion: A DIY journal, watchlist and review database
Airtable: A structured journal that automations can write to

Linked roles

Journal Keeper

Limitations

A null ticket records that no order was drafted. It is not a claim that standing aside was the right call. Review the pass later, on the missed-trade log. AI can be wrong, so verify before relying on any output.

Source

No-trade ticket skill pack

Related use cases

Pick one commitment for next week: Long improvement lists never stick.
Run your desk on a schedule: Run the routine on a schedule and review the output.