← TradeChrona Help CenterBest Practices
Interpret sample size before calling something a pattern
Use the displayed sample and date range to judge whether a comparison is useful, incomplete, or overly broad.
Browse this article
CategoriesGetting StartedAccount & BillingConnecting PlatformsNinjaTrader SetupTradovate SetupTopstepX SetupDashboardCalendar & Daily JournalAccounts & Prop-Firm RulesTrade LogAnalyticsAI MentorBacktestingStrategy BuilderBest PracticesTroubleshootingSecurity & PrivacyFrequently Asked QuestionsRelease NotesOn this page
What this article helps you do
Avoid treating a handful of trades as a stable conclusion.
Before you start
- A filtered Analytics, Backtest, or AI Mentor result.
Follow these steps
- 1
Read the exact number of trades or sessions.
- 2
Check whether the records use consistent tags and definitions.
- 3
Check whether one unusual trade dominates the result.
- 4
Compare a relevant date range rather than combining unrelated market conditions automatically.
- 5
Use out-of-sample or later data when validating a strategy idea.
- 6
Label a result as preliminary when the evidence remains limited.
What you should see
The user understands how much data supports the displayed comparison and what remains uncertain.
Common mistakes
- Using an arbitrary universal minimum for every setup.
- Combining unrelated accounts only to increase the count.
- Ignoring missing tags or incomplete journal answers.