A steady edge says the winning lineups of a tournament held a band more often than the field, slate after slate. On Power, you can turn many of these rows into a build setting in two clicks. The report shows each change before it writes anything.
Which rows have an action
Only a steady edge has an action, and only when a build setting can hold its band. A finding shows Apply, and a table row shows a menu button in its last column.
A steady fade has no action. A row writes its own band, so a fade would push every lineup toward what the winners avoid. A row within noise or a thin sample is no reason to change a build. See Read a measure.
Apply to my build
- Click Apply on a finding, or the menu button on a table row.
- Choose Apply to my build.
- Read the change and its warnings at the top of the dialog.
- Pick a slate. The list shows the open slates of the report's site, sport, and format, with their lock times and games.
- Click Open the workspace.
- In the workspace, read the bar From your Game Plan report over the grid.
- Click Apply on the bar to write the change to the build tab on screen, or Dismiss to drop it.
A built tab keeps its lineups. The toast tells you to rebuild to use the change. When a playbook is armed on the tab, the toast says the playbook writes over the change when it runs.
The change waits only in this browser tab. A reload drops it, so apply it before you leave the workspace.
A rule that needs more games than a slate holds leaves that slate off the list, and a line under the list counts the slates it left out.
Save to a playbook
- Click Apply on a finding, or the menu button on a table row.
- Choose Save to a playbook.
- Read the change and its warnings.
- Pick one of your playbooks of the same site, sport, and format, or pick New playbook and type a name.
- Click Save to with the playbook's name, or Create the playbook.
Every later run of the playbook uses the change. A save to a Stack IQ playbook moves it to manual stacks when the row writes a stack rule, and the dialog says so first. When the playbook changed after the list loaded, the save stops and asks you to save again. See Playbooks.
What each row changes
| Row | The setting it writes |
|---|---|
| Salary left | The band's two edges as the salary range. $0 sets both ends to the salary cap. $2,000+ has no action. |
| Total ownership | The band's edges as the lineup's ownership range. Classic only. |
| Players under 10% owned | Force low ownership: at least the band's low count of players, at 10% owned. Classic only. MLB refuses it beside a Team Stack. |
| FLEX position | The FLEX seat's position. NFL and CFB classic. |
| QB teammates, bring-backs, game stack, QB with his own RB, and the NFL stack type | NFL position rules. A number is exact, and 3+ or 2+ is a floor. |
| Stack type in another sport | The exact shape: each block at its size, and 1 or fewer players from every other team. A shape of 3 or more blocks has no action. CFB has no stack action. |
| NHL line and power play stacks | A center and teammates from one of his lines 1 to 3, or from one power play unit. The band counts the center: 2 asks for at least 1 teammate, and 3+ for at least 2. |
A sport with a points cap has no salary actions. A row not in this table has no action.
Read the warnings
Each warning names the rules the change replaces. A stack rule turns the Correlation dial off. A position rule replaces only the rules of its own kind.
- A strict stack shape needs a slate with enough teams to seat it. If not, the build stops with no lineups.
- An ownership band can sit outside a slate's projected ownership, and the build then stops with no lineups. On a slate with no ownership projections, the ownership settings do nothing.
- A salary range can build fewer lineups than you ask for on a small slate.
- Late swap reads these settings only when Build settings in the Swap sheet names the build tab that holds them. The sheet starts at Defaults. See Run a late swap.
In Hero Chat and an AI agent
On Power, ask Hero Chat about a report in a slate's workspace, and it can propose the same change. A card shows the change, and nothing changes until you confirm. A connected AI agent can save a row to one of your playbooks. Both follow the same rule: a steady edge only.
Related articles
Was this article helpful?