A pre-trade checklist creates a deliberate pause before an idea becomes an order. It brings together the setup, exits, size, account exposure, market conditions, and your readiness to act. This lesson turns those checks into a practical routine rather than a vague reminder to be careful. You will work through a sample ticket, identify conditions that require waiting, and verify what happened after submission so that an unchecked assumption does not become an unintended position.
The idea
A pre-trade checklist is the final check between a market idea and an order. Your trading plan contains the overall method; the checklist confirms that this particular trade follows it. It is most useful when the questions are specific enough to answer before you click. Begin with the setup. Can you state the entry reason in one sentence? Are the required conditions present, or are you anticipating them? Check the instrument, timeframe, and session so that you do not apply a rule to the wrong market context. Next, check the invalidation point and intended exit. Confirm the stop and target, or the management rule if you use a different exit method. Calculate position size from the planned loss allowance, stop distance, contract value, and costs. Check required margin separately from the potential loss. Review account exposure. An additional position can duplicate an existing risk, especially across related instruments. Check scheduled news, market opening or closing times, and any holding costs relevant to your expected duration. Read the order ticket carefully: instrument, direction, quantity, order type, price conditions, expiry, and attached exits. A correct idea entered with the wrong units is still an incorrect trade. After submission, verify the order status and attached protection rather than assuming that clicking completed every step. Include your ability to follow the plan. Fatigue, distraction, frustration after a loss, or an urge to recover money can change decisions. The checklist should contain clear reasons to wait. It is a decision aid, not a ritual that makes a trade profitable or removes market risk. Design checks that can fail A useful checklist must allow the answer “not ready.” If every question is phrased so vaguely that any trade can pass, the list offers little protection from mistakes. “Does the setup meet the three recorded conditions?” is more testable than “Does this feel like a good trade?” Separate mandatory conditions from observations. A news event may be something to note under one tested method and a reason not to enter under another. Your plan determines the rule; the checklist applies it consistently. Do not invent exceptions simply because the price is moving quickly. Pre-submission and post-submission checks Before the order, confirm what you intend to send. Afterwards, confirm what the platform accepted and executed. These are different questions. A correct ticket can still be rejected, partially filled, or executed at a different price. Include an interruption rule. If a call, browser issue, or distraction breaks the process, restart the relevant checks rather than relying on memory. If you are unsure whether an order was sent, inspect its status before submitting another. A few seconds of verification can prevent duplicate exposure.
Apply the idea
Use this example as a template for a demo trade. Adapt the questions to the method you are testing. 1. Setup: What exact condition has occurred, and what evidence would cancel the idea? 2. Entry: Is the instrument correct? Is this a long or short position, and why does the chosen order type fit? 3. Exit: Where does the idea fail? How will the position close if it succeeds, fails, or takes too long? 4. Size: Have I checked units, contract multiplier, stop distance, costs, and the planned account loss? 5. Exposure: What existing positions share this risk? Is the combined exposure still within my rules? 6. Conditions: Is there relevant news, an unusually wide spread, or a market closure to consider? 7. Readiness: Can I monitor or manage the position as the plan requires, and am I able to accept the planned loss? 8. Verification: After submission, is the order pending or filled, and are the intended exits attached? For a hypothetical calculation, an entry at $100 and stop at $98 create $2 of planned loss per unit. Ten units create $20 of gross planned loss, before costs or execution differences. If $20 is the entire allowance, those costs mean ten units may already be too large. If one required condition fails, pause. Do not change the checklist merely to make the current trade pass. Record a skipped trade just as you would an executed one; it helps show whether your rules are practical. Afterwards, compare the ticket, actual fills, and your notes. Separate a rule-following loss from an avoidable mistake, and a rule-breaking profit from a sound process. Update unclear checklist wording during review, rather than while trying to justify an entry. Run a deliberate error test in demo Prepare a written practice ticket, then compare it with the platform before submitting. Look specifically for a wrong symbol, an incorrect quantity unit, a buy/sell reversal, a stale entry price, or a missing exit. The purpose is to catch a mismatch, not to place a trade quickly. Next, describe what you would do in three situations: the spread is wider than your plan permits; the smallest allowed position exceeds the loss allowance; and a submission produces no clear confirmation. Write an action for each, such as waiting, skipping, or checking order history. Do not solve the problem by quietly changing the limit. After a completed demo trade, review which check would have caught any mistake. If the checklist already contained it, investigate why it was skipped. If the wording was unclear, rewrite that item at the review stage. Keep a record of successful decisions not to trade. They show whether the checklist is being used as an actual decision tool rather than as a form filled out after entry.
Key takeaway
A useful checklist catches mistakes before an order and confirms what happened after submission. It connects setup, exits, size, account exposure, market conditions, and readiness in one repeatable pause. Make every question concrete and keep the list short enough to use. A failed condition is a reason to wait, not a reason to loosen the rule for this trade. Review compliance separately from profit or loss. The checklist improves consistency and error detection; it cannot predict the next move or guarantee a profitable result.
