Skip to main content

​
Overview

Playbooks let you save the way your scanner is configured without changing the layout of your dashboard. Think of a playbook as a reusable behavior preset: it remembers the supported filters, panel settings, and scanner voice preferences you are using right now, then lets you apply that same setup again later with a single click. This is important because there is a big difference between how your scanner looks and how your scanner behaves. Your layout controls structure: which panels are visible, where they sit, how large they are, and how your workspace is arranged on screen. A playbook controls behavior: the active scan settings, panel-specific preference snapshots, and supported voice/alert state that determine what the scanner is focusing on. That separation is what makes playbooks so useful. You can keep a layout that already works for you and switch the scanner’s operating mode instantly, without rebuilding the page or loading a completely different dashboard.

​
How Playbooks Work

When you create a playbook, the scanner takes a snapshot of the current supported Mission Control state for your active layout. That snapshot includes the playbook-capable panel preferences the system is designed to carry forward, along with the associated voice preferences. In practical terms, that means a playbook can preserve things like the filters you are scanning with, selected timeframes, thresholds, sector selections, and scanner voice behavior, depending on the panel. Once saved, that playbook becomes a named, reusable preset in your personal scanner workspace. You can:
  • Save the current scanner state as a new playbook
  • Apply an existing playbook to the current layout
  • Overwrite a playbook with your latest scanner state
  • Delete playbooks you no longer use
  • Restore layout defaults when you want to remove playbook-driven behavior and go back to the baseline state for the current layout
Applying a playbook does not swap you into a new layout. Instead, it copies the playbook’s supported behavior settings onto the layout you are already using. That means your panel placement, overall geometry, and workspace structure stay intact while the scanner’s operating profile changes underneath it.

​
What Playbooks Save, and What They Do Not

A good way to understand playbooks is to think of them as behavior snapshots, not layout snapshots. A playbook is designed to save the parts of the scanner that affect how it scans and how certain panels behave. This can include supported filter state, timeframe selections, thresholds, sector selections, and scanner voice preferences. These are the settings that change the character of the scan. A playbook is intentionally not designed to rearrange your workspace. It does not replace your layout, move your panels around, resize them, or turn the feature into a layout-cloning system. That boundary is deliberate. Layouts and playbooks solve different problems:
  • Layouts define your workspace structure
  • Playbooks define your scanner behavior
That separation makes the system much easier to use. If you want a different workspace arrangement, use layouts. If you want the same workspace to behave differently for a different scanning job, use a playbook.

​
Why Playbooks Matter

Playbooks are powerful because they remove repetitive setup work from the scanning process. Many users don’t want to rebuild filters, reset panel preferences, and reconfigure scanner behavior every time they switch from one kind of market read to another. Playbooks turn those repeated setup patterns into one-click workflows. They are especially valuable because they keep your mental model clean. Instead of asking, “Do I need a new layout for this?” you can keep one layout you already like and simply apply a different playbook. That makes the scanner feel faster, more flexible, and easier to trust. Your screen stays familiar, but the scanner’s focus changes instantly. They also improve consistency. If you discover a setup that works well for a specific use case, you can save it as a playbook and reuse it exactly, instead of trying to recreate it from memory. That is useful for anyone who has multiple scanner routines, multiple market conditions they watch for, or different workflows throughout the trading day. In other words, playbooks help turn the scanner from a configurable tool into a repeatable operating system. They let you move from “I need to set this up again” to “I already have a saved operating mode for this.”

​
Real Scanner Workflow Example

In a live scanner, speed and repeatability matter. Users often shift between different modes of analysis:
  • An intraday scanning mode focused on shorter timeframes and tighter thresholds
  • A swing-oriented mode with broader timeframes and different filtering logic
  • A sector-focused mode that changes what the scanner emphasizes
  • A quieter or more active voice/alert mode, depending on what they want the scanner to surface
Without playbooks, changing between those modes means manually editing multiple controls and hoping nothing important gets missed. With playbooks, the scanner can jump directly into the right mode while the workspace itself stays stable. That is a better experience because users usually want continuity in the dashboard they have already built. They want their familiar panel arrangement, but they also want the freedom to tell the scanner, “Now behave like my intraday setup,” or “Now switch to my higher-timeframe review mode.” Playbooks are what make that possible.

​
Restore Layout Defaults

One of the most useful parts of the feature is the ability to restore layout defaults. This gives users a clean way to remove playbook-applied behavior from the current layout without disturbing the layout itself. That matters because playbooks are meant to be layered on top of your existing workspace. The restore action acts as the inverse of apply: it clears the playbook-managed behavior and returns supported settings to the layout’s default baseline, while leaving panel placement and overall geometry unchanged. This gives users confidence to experiment, because applying a playbook never feels permanent or risky.