Before trading through Rithmic, identify the account's effective restrictions, review the intended order and exit behavior, and know how to inspect remaining exposure if something fails. Account risk controls, order-level stops and automation monitoring serve different purposes. None guarantees a maximum loss or a successful evaluation.
Educational software guidance. Trading involves risk. Read the financial and information disclaimers.
Review the account rule
Record the provider, plan and account stage. Confirm the effective balance floor, loss calculation, quantity limits and permitted trading times. Use current account records rather than copying a percentage or a contract count from a generic guide.
The risk-settings guide shows the inspected route into View Risk Parameters. Check permissions and the selected administrative tab before interpreting a field. A personal threshold does not replace the provider's rules.
Review the order and exit plan
Distinguish a stop trigger from an execution price and a limit price from a guaranteed fill. Confirm where brackets, trailing changes and OCO cancellation are managed for the specific platform and connection. Inspect working exits after an entry; a template name alone does not establish that an order was accepted.
Use the order-types guide and bracket guide for these distinctions. Choose contract and size using the actual product specifications and account restrictions, not the headline account balance alone.
Review automation separately
- Identify every alert, strategy, copier and manual route that can submit instructions.
- Confirm the intended destination account, expiry, side and quantity.
- Distinguish alert generation, webhook delivery, order acceptance and fills in the records.
- Validate changes in a suitable provider-approved simulation.
- Establish how to stop new signals and separately inspect or manage existing orders and positions.
Pausing an alert is not a flatten command. Disabling a copier is not proof that a follower position is closed. Follow the exact control scope in the flatten guide.
Keep an incident record
For a problem, record timestamps with timezone, platform versions, exact responses and the relevant account and order identifiers privately. Compare positions, working orders and fill history before retrying an uncertain request. A missing acknowledgement can require reconciliation rather than an immediate duplicate submission.
Common questions
Is there a universal percentage to risk per trade?
No. This operational checklist does not prescribe a suitable loss allowance. Account rules, product exposure and personal circumstances differ.
Does a simulation prove live behavior?
No. It can validate parts of a workflow, but execution conditions, account permissions and provider rules may differ.
Are server controls enough for unattended automation?
Do not treat their existence as proof that every failure is covered. Review the configured conditions, monitoring and recovery procedure for the actual system.
Is closing the trading application an emergency exit?
No. Closing a display does not establish that server-held orders or positions have been closed. Inspect the actual account state through an authorized connection.