IdealSync by Dorian GorskiSave my blueprint

A clean IdealSync playbook · by Dorian Gorski

Weekly operations review

One numbers pack, four reviews (stock, ads, listings, customers), three agreed actions with owners, and a check on last week. 9 tasks, 4 departments, 3 automations.

Make this fit my business →

Preview freely. Sign in to save your own version. No private client information appears in this template.

  1. T1 · Operations

    Refresh the weekly numbers pack

    Sales by SKU, ad spend and sales, sessions and conversion rate, days of stock cover, returns rate

    Ops Manager1 calendar day assumed
    After: Flow start
  2. T2 · Operations

    Check last week's actions actually landed

    Last week's three actions, their owners and their status

    Ops Manager1 calendar day assumed
    After: Flow start
  3. T3 · Supply Chain

    Review stock cover and reorder flags

    Days of cover per SKU, open purchase orders, supplier lead times

    Demand Planner1 calendar day assumed
    After: T1
  4. T4 · Marketing

    Review advertising performance

    Spend, ad sales, ACOS and TACOS by campaign, top search terms

    PPC Manager1 calendar day assumed
    After: T1
  5. T5 · Marketing

    Review listings and buy box health

    Content change log, buy box percentage, suppressed or stranded listings

    Brand Manager1 calendar day assumed
    After: T1
  6. T6 · Operations

    Review customer feedback signals

    New reviews, rating movement, return reasons, support ticket themes

    Ops Manager1 calendar day assumed
    After: T1
  7. T7 · Operations

    Agree the top three actions

    Findings from each review, money at stake per finding

    Ops Manager1 calendar day assumed
    After: T2, T3, T4, T5, T6
  8. T8 · Operations

    Assign owners and due dates

    The three agreed actions

    Ops Manager1 calendar day assumed
    After: T7
  9. T9 · Operations

    Log the decisions and what changed

    Decisions, owners, expected effect, the numbers they were based on

    Ops Manager1 calendar day assumed
    After: T8

Why we build it this way

End the review with an owner and an action.

A dashboard surfaces a signal; an owned task makes a response possible.

Bring the completion receipt back to the next review, including what did not work.

Design guidance from the IdealSync method. Adapt and validate it for your operation.

The next run should teach you something

Confirm the data. Give the response an owner. Do the work. Record the result. Improve the next run.

Save my starting blueprint →