---
name: list-top-3-5-recommendations-for-next-7-days
description: "Turn the week’s facts into a short work list. Give each step an owner and a clear check."
category: Content Factory — Promote
stage: Promote
definitive_article: /social-amplification
status: complete
---

# List top 3–5 recommendations for next 7 days

A report should help you choose what to do next. This guide turns the week’s findings into a short list of useful steps. Start with last week’s list and what really got done.

**The path:** Prior actions → current evidence → ranked next steps → checked handoff.

**Use this when:** The campaign’s analysis and budget review are ready for the next agreed planning period.

## Inputs
- Current decomposition, period comparison and budget-review findings with source links and uncertainty notes.
- The business goal, current constraints and available capacity; last week’s recommendations and actual execution evidence.
- The real receiving owner, report/tracker destination and scope to create tasks or deliver the report.

## First-run prompt

> Review the prior actions against actual completion evidence, then rank the best supported next steps for this goal. Use up to three to five concise items with exact object, real owner, due date and acceptance measure. Keep predicted effects separate from observed results, and create or deliver only what the existing scope allows.

## Steps
1. Read last period’s list before writing a new one. Record whether each action was performed, partly performed, blocked, declined or still unknown. A task being assigned or checked complete is not enough without its relevant output evidence.
2. Compare predicted and observed effects only where the action actually happened and the measurement window is suitable. Record a wrong prediction as a lesson; do not invent a cause to make the prior advice appear right.
3. Draft candidate actions from the current findings. Link each to the changed metric or specific gap. Include useful verification or tracking repairs; not every week needs a new ad, a kill or a budget increase.
4. Rank by likely effect on the stated goal, evidence strength, urgency, cost and available owner capacity. Select up to three to five meaningful actions. Use fewer if the evidence supports fewer instead of padding the report.
5. Write each item as a clear verb and exact object, with the actual assigned owner, due date, input and acceptance test. Name the budget or authority dependency only when it is real; carry out work already authorized without asking again.
6. State the expected direction or test hypothesis and its assumptions. Use a numeric forecast only when supported by a model or comparable evidence. “Expect CPA down 20%” is not a default sentence to fill in.
7. Tag the action by its real purpose: stop, continue/scale, test, repair or verify. An all-verification week may be correct when the data is broken. Keep proposed actions separate from already performed work.
8. Deliver through the agreed report route and create tracker items only within existing scope. Read back any created item or delivered report, then save the next review date and links needed to judge the list next time.

## Definition of done (QA checklist)

- [ ] Prior actions have evidence-qualified execution states.
- [ ] Every new item traces to a current finding and the business goal.
- [ ] The short list has no filler and fits real owner capacity.
- [ ] Each item has an object, actual owner, date and measurable acceptance test.
- [ ] Predictions, assignments, completed work and report delivery are separate states.

## Example(s)

**Fictional teaching example:** Last week’s form fix was completed and checked; the proposed new ad never launched because its budget was not assigned. This week’s list has two justified items: the site owner checks that the repaired form still records valid submissions, and the campaign owner closes the expired failed ad under the existing stop rule. Each has a due date and evidence test. No third item is invented to fill the title, and no 20% cost improvement is promised from two noisy days of data.

## Handoff and Content Factory context

The named actual owners receive the exact tasks through the existing tracker/report process. The next cycle of [compare current vs last period performance](https://local-service-spotlight.github.io/task-library/?task=compare-current-vs-last-period-performance#task-compare-current-vs-last-period-performance) checks the resulting evidence, not merely the recommendation list.

This task is in Promote within the [Content Factory](https://blitzmetrics.com/content-factory/). Produce gathers real source material; Process makes useful assets; Post places and checks them; Promote distributes suitable work within its own scope. Use the proof and checked posts from earlier stages; a Promote task does not automatically redo all four stages. Use the actual next step above; catalog neighbors are not prerequisites.

## When this runs

Use the campaign’s agreed weekly planning day and next-seven-day horizon. Friday is a source example, not a new required schedule. A recurring delivery or task-creation job needs a real configured trigger and destination.

## First-run setup and continuity

Open the supplied task file and its linked source. Verify the project’s real inputs, account, access and output folder before work. This Markdown file is a guide; it does not install an app, connect an account, supply a subscription or create a schedule. Carry out work already authorized; do not ask for the same approval again. Keep any unsupplied destination or new action outside that scope clearly pending.

Save source IDs, versions, decisions, checked outputs and next owner in the project tracker. Before a retry, check the saved state and other workers’ changes. A model name does not guarantee memory or a running timer. Repeated work needs an actual configured trigger and durable state; one-off work can be started by the prompt above.

Keep agent media muted with volume zero before playback. If mute cannot be verified, use captions, metadata or still frames. State the limit: silent visual checks do not prove spoken-word accuracy or audio quality. Do not start sound through the user’s speakers unless explicitly asked.

## Write up the real run

For every actual attempt, [write its meta article](https://blitzmetrics.com/meta-article-prompt/) with this recipe and revision, trigger, steps performed, output evidence, measured result, gaps and next owner. Failed, blocked and partial attempts also get a written record. A draft can satisfy writing; publishing it follows the existing job scope.

Keep one stable execution ID across retries and edits. A separately scoped child task may have its own ID linked to its parent. Writing the parent’s meta record is part of that run, not an endless new chain. The [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) explains this distinction. Teaching examples are not real executions and must not enter the run count.


<!-- factory-layer:start -->

## Factory chain (do not treat this as isolated)

- **Phase:** Promote
- **Importance:** 5/5 `●●●●●` — frequency 4, revenue 5, gating 3 (runs every factory cycle or weekly; ads/revenue path)
- **Suggested previous station:** `compare-current-vs-last-period-performance`
- **Suggested next station:** `use-dollar-a-day-to-influence-media-coverage`
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Organic metrics CSV (or Ads Manager export), pixel ID, creative filenames, kill/scale log. Next week's ranking starts from this file.

## Model routing (same factory, any engine)

- **This task's lane:** `computer` — Logged-in UI (Meta Ads Manager, Descript, GSC, wp-admin when REST is blocked). Requires a supported browser tool and the right account access.
- **Single-engine path:** Use the capable AI app you already have. Check its required tools and access before starting. Pass the actual result and proof to the next task.
- **Optional multi-engine:** A tested local model may draft; a stronger model may review facts and voice. Use supported tools for approved actions. Pick models from observed quality and cost; a model name does not prove it can run this task.
- **Never** store the working state in one vendor's memory. Files in the Content Library are the bridge.

<!-- factory-layer:end -->
## Definitive article & links

- Canonical article: https://blitzmetrics.com/social-amplification
- Exact task: [List top 3–5 recommendations for next 7 days](https://local-service-spotlight.github.io/task-library/?task=list-top-3-5-recommendations-for-next-7-days#task-list-top-3-5-recommendations-for-next-7-days)
- Writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Metrics, Analysis, and Action](https://blitzmetrics.com/maa/)
- [Goals, Content, and Targeting](https://blitzmetrics.com/gct-business-strategy/)
- [Social Amplification Engine](https://blitzmetrics.com/social-amplification/)

## Review and evidence still needed

The source contributor status is preserved. It is not certification of this draft or proof of account access, completed work or a live outcome. The worked example teaches the method and is explicitly fictional.
- Actual owners, deadlines and task-delivery authority are not supplied by a guide.
- A predicted result stays a hypothesis until the action and its measured outcome are observed.