Strategy & approval

A Strategy turns selected opportunities into a small set of concrete actions you can review, edit per-item, and approve as a whole — after which each action becomes a work item.

A strategy is the approval-oriented workspace between opportunities and work. The default is a small "next best actions" plan, not dozens of tasks across twelve weeks.

Building one

1
Select opportunities
On Mission Control or Opportunities, tick the opportunities you want to act on and choose Create strategy.
2
Give it a title and objective
One line each — what this push is and the outcome it's for.
3
Review the items
RankOut drafts one action per opportunity: a planned action, an expected outcome, and an effort / risk read.
4
Edit per item
For each item you can adjust the planned action, expected outcome, effort and risk, target date, target URL and target keywords, dependencies, and — importantly — the implementation method.
5
Set the implementation method
WordPress Connector, GitHub PR, manual, or content-first. This decides how RankOut will implement that action.
6
Submit for review
Submitting moves the strategy to a review state with an optional comment.
7
Decide
A reviewer approves, rejects, or requests changes. On approval, every action becomes a work item on the Plan & Work board.

The strategy builder with a list of editable action items and their implementation methods — Approve the strategy as a whole; edit any individual action first.

Implementation method: WordPress Connector: RankOut will draft a precise tool call against the live WordPress site and, on approval, apply and validate it.
Implementation method: GitHub PR: RankOut will draft a file change and open a pull request for a human to merge.
Implementation method: manual: RankOut drafts the change and a person applies it, then marks it done.
Content-first: The action needs a content asset drafted and approved first (see Content Engine); implementation follows once the draft is signed off.

Approval permissions matter here. Submitting a strategy and deciding on a strategy are separate permissions from building one — see Team, roles & permissions.