> ## Documentation Index
> Fetch the complete documentation index at: https://docs.synscribe.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Weekly planning flow

> The weekly execution beat inside a cycle — produce, publish, index, audit.

The weekly beat that runs inside a monthly cycle. Once the month is planned
([3.2 Monthly planning](/sops/monthly-planning)), the work executes week by week: produce
content, publish it, index it, and audit it against the Definition of Done.

> **Source note:** the standalone SOP page for the weekly flow is empty; the cadence below is the
> team's weekly status-report practice, consolidated here.

## The Monday health review

Every Monday the team walks every client account's health. The review answers the same five questions
for each account:

1. Where are we in the billing cycle?
2. What was planned for this billing cycle?
3. Are we on track on the deliverables?
4. What are the key blockers or hiccups that could stop us delivering?
5. How satisfied is the client?

The week's plan falls out of that. Each account gets a week-by-week deliverables grid showing what was
planned for each week and where the account actually sits against it. That "where are we vs plan" read
is the point of the Monday pass: it catches an account drifting behind before the cycle's review makes
it obvious.

## The weekly beat

Each week inside a cycle moves content through the same loop:

1. Produce the week's landing pages and blog posts against the tagged keyword plan. See
   [3.5 Content production & Definition of Done](/sops/content-production-dod).
2. Publish. Set posts and pages live; see [how-to: 2.5.1](/platform/publish-set-live-url).
3. Index. Submit to Google Search Console and the sitemap, and run IndexNow; see
   [how-to: 2.5.3](/platform/index-gsc-sitemap).
4. Audit. Run the technical SEO audit and confirm each page meets the
   [Definition of Done](/sops/content-production-dod#definition-of-done).

> The Month-1 flow shows this loop in its daily form. See
> [3.1 Week 2](/sops/onboarding-month-1#week-2-—-publish-&-collect-data) for the fully worked
> publish, audit, and index sequence that a normal week compresses.

## Handoffs

Publishing on the weekly schedule is often shared with the BPO teammate. Define the schedule in
`#bpo` and record a Loom for any new flow. See [3.14 Roles & handoffs](/sops/roles-handoffs).

***

## Related

* [3.2 — Monthly planning flow](/sops/monthly-planning): sets the month this week executes.
* [3.5 — Content production & Definition of Done](/sops/content-production-dod): the produce and audit steps.
* [3.6 — The Quality Gate](/sops/quality-gate): the ranking check the weeks build toward.
* [3.1 — Onboarding Flow, Month 1](/sops/onboarding-month-1): the weekly loop shown day by day.