A Record Needs the Full Ledger
A tracked record should show every issued customer-facing MLB selection in the stated window. That means wins, losses, pushes, odds, units, grading rules, and date range.
Leaving out losses, changing the sample after the fact, or mixing research results into the public total makes the record harder to trust.
Separate Market, Tier, and Model Boundaries
MLB moneyline, totals, first-five markets, props, and other research streams should not be treated as one interchangeable bucket unless the service clearly explains that reporting choice.
Customers should know which product or tier generated the pick and whether the performance belongs to a live customer-facing process.
Use Results as Evidence, Not a Promise
A tracked record helps customers evaluate process and accountability. It does not guarantee that future selections will win or that any customer will profit.
The strongest reporting gives enough context for a customer to understand both the upside and the risk.
Read One Ledger Row Before the Headline
A useful hypothetical row might read: MLB, full-game moneyline, Team A +125, one unit risked, issued before first pitch, result loss, net -1 unit. A winning row at the same price would show +1.25 net units, not +2.25: the returned stake is not profit.
Check that postponed or void selections have an explicit status and that a rescheduled game is handled consistently. When a report gives a recent window, do not call it lifetime performance. Your own ledger should use the price you actually obtained rather than assuming the published selection price was still available.
Key Takeaway
ESA's reporting standard is to keep customer-facing MLB production results separate, track the complete sample, and avoid treating historical results as a guarantee.