# How To Write Caveats For Optimized Results Slug: how-to-write-caveats-for-optimized-results. Canonical: https://tradingtune.com/blog/how-to-write-caveats-for-optimized-results ## Summary Gives language for describing optimized settings without overstating what the historical test shows. ## Key facts - A good caveat names the window you tested, the range you swept, and what the test cannot tell you about unseen data. - A caveat is stronger when it points at a range and the neighboring settings than when it points at a single number. - A setting that stands apart from its neighbors, or sits at the edge of the tested range, should be flagged as unverified. - Caveat language works when it names the range tested, the split used, and the specific thing left unverified, in plain words a reader can check. ## Outline - Writing Caveats That Match What A Backtest Actually Shows (#writing-caveats-that-match-what-a-backtest-actually-shows) - Setting Up The Sweep And The Walk-Forward Split (#setting-up-the-sweep-and-the-walk-forward-split) - What Changes As You Move Across The Range (#what-changes-as-you-move-across-the-range) - Reading The Illustrative Sweep Table (#reading-the-illustrative-sweep-table) - When An Optimized Setting Falls Apart Out Of Sample (#when-an-optimized-setting-falls-apart-out-of-sample) - Turning This Into Your Own Validation Habit (#turning-this-into-your-own-validation-habit) - Why Caveat Language Matters For Every Optimized Result (#why-caveat-language-matters-for-every-optimized-result) - Sources (#sources) ## Code snippets - Anchor: #pine-snippet-1