Once a week, make a top-down pass in this order: scan the dashboard's Needs attention queue and your project cards, open each affected client's catalog to check import health and warnings, clear the content waiting for review, then confirm every channel is live. A short pass — often under an hour — and problems get caught before they waste spend.
Why a fixed weekly order beats poking around#
When you manage many clients, your scarcest resource is attention. A fixed order means you always start where the platform is already pointing — the clients that need you — and never open a healthy account "just to check." Renable surfaces problems for you; the routine is about reading those signals in the right sequence so nothing slips between one weekly visit and the next.
The whole pass is designed to be top-down. The dashboard tells you which clients need you; each later stop is a drill-in on only those clients. A client with no signal usually doesn't need a visit this week — with one blind spot to watch: a project whose end date has lapsed stops importing silently, with no warning raised to surface it (see Stop 2). Its only tell is a freshness line frozen at an ever-older "imported {time ago}", which looks the same as a healthy unchanged feed. So once a month, do a full-roster sweep in the Projects directory (/projects) and check end dates, so a silently-deactivated client can't hide behind a clean-looking card.
The pass at a glance#
- Dashboard — read the Needs attention queue, then filter your project cards to Issues and Flagged to see which clients are affected.
- Catalogs — for each affected client, open the catalog and read its health strip and warnings on the Activity tab.
- Content — clear whatever's waiting for review on each affected project's Content page.
- Channels — confirm every channel is still Live and its last run succeeded.
The rest of this guide is one section per stop.
Stop 1: The dashboard — who needs you this week#
The dashboard (the app home, at /) is a status-now rollup across every project in the organization. Start here every week.
- Read the Needs attention queue at the top. It lists the organization's open warnings and errors, most pressing first — one working list across all your clients, not per-project. A warning here is a problem that's live right now, not a note about something you did.
- Below the queue, filter your project cards. The mode selector switches between Starred, Flagged, Issues, and All. Flip to Issues to see every client with open errors or warnings, and Flagged to see clients with flagged content — content that failed an automatic quality check.
- Read each card's signals. A card shows its open issues (errors and warnings), any flagged content, unpublished drafts, and a freshness line — either "import failing", when it last imported, or how many new products arrived this week.
- Note the draft reminders below the queue. These flag entities with unpublished changes (most often a catalog or channel) — a common way a fix silently never went live, because nothing takes effect until you publish. The same notices appear on each project's Overview, and entities with a pending draft carry an Unpublished badge there and in the project's Catalogs and Channels lists.
- Skim Changes to know about on the right. It's a curated recent-changes list across all your clients: what teammates published, who worked through content review, channels going live for the first time, and only the remarkable feed changes — an unusually large share of a catalog arriving, leaving, or changing price. Routine day-to-day feed churn is deliberately left out, so anything listed here is worth a glance.
Star your key clients. The Starred filter is your own per-user shortlist. Star the accounts you always want at the top and the dashboard opens to them each week — the queue and digest stay organization-wide, so starring only reorders your own cards, never what your colleagues see.
Want the full roster instead? The Projects directory (/projects) lists every project (archived ones too, via the Show archived filter), with an Attention column showing the same issues-and-flagged signal per row. Use it when you'd rather scan the whole client list than the attention-first cards.
Stop 2: Each affected catalog — import health and warnings#
For every client that showed a signal, open its catalog and check the feed is importing cleanly.
- Open the project, then open the catalog from its Catalogs tab.
- Read the health strip at the top of the catalog page — it's always visible. A healthy feed shows a green light, "Last import {time ago}", and the product count. A problem shows "Needs attention — N warnings".
- Open the Activity tab to see what each import did and to read the warnings underneath it. Warnings dedupe on their text, so one line telling you it hit 500 products replaces 500 separate alarms — and you can drill straight down to exactly the affected products.
The full mechanics — reading a run's statistics, tracing why one value came out the way it did, and what each warning means — live in Feed runs, warnings, and tracing a value. For the routine, you only need the health strip's one-line read and the warnings list.
A client suddenly went quiet — no imports at all? Check the project's end date first. If it lapsed more than about a week ago, Renable treats the whole project as inactive and silently stops import, enrichment, and export for every catalog and channel in it, with no separate warning. See What is a project.
Stop 3: Content awaiting review#
For each affected project, clear the content waiting for a human look.
- Open the project's Content page (from the Products section, click See content).
- Scan Aimée's confidence and approval status per product. Switch to gallery view when you want to eyeball images quickly, table view when you want to move through rows with the review hotkeys.
- Approve what looks right. You don't have to review everything — by default, unapproved content is used in your templates and channels exactly like approved content, so a review pass is a quality check, not a gate that holds ads back.
The approval flow, the hotkeys, and the bulk actions are covered in Reviewing and approving content. For an agency working many accounts in one sitting, Review content quality across clients is the faster cross-client pass.
Stop 4: Channel status — confirm ads are still flowing#
Last, confirm the outgoing feeds are actually generating and uploading. This is where ad delivery quietly breaks even when the feed data is fine.
- On each affected project's Overview, read its channel cards. Each shows Live (green), Preparing, or — when something needs attention — a color-coded count of open channel events. A channel that stopped uploading, or whose latest run failed, is the one to open.
- Open a channel to its Activity tab to see its render history — each run's status, counts, and any required-field warnings.
- If a channel's feed generates fine but products still aren't delivering, the rejection is usually on the ad network's side. See Products disapproved by Google for the fix path.
Or ask Aimée#
Two parts of this routine are worth handing off:
- Investigate a warning. Every warning on the Activity tab carries an "Ask Aimée to investigate" action — one click and she looks into what caused it and what to do about it, instead of you tracing it by hand.
- Wait for an import. After you publish a fix, you don't have to sit and watch. Ask Aimée to wait for the import to finish and report back the real counts and warnings when it's done.
You can also ask her why a specific product isn't in a feed — she'll follow that one product end to end and tell you exactly which step dropped it.
FAQ#
I manage 40 clients — do I really open every one each week?
No. The point of starting at the dashboard is that it surfaces only the clients that need attention — the Needs attention queue, the Issues and Flagged card filters, and the directory's Attention column all point at the same accounts. A client with no signal usually doesn't need a weekly visit. The one exception is a silently-deactivated project — a lapsed end date stops its imports with no warning to flag it — which is why the routine adds a monthly full-roster and end-date sweep in the Projects directory. That catch is what makes "skip the quiet ones" safe.
A warning says it affected hundreds of products — do I fix each one?
No. Warnings dedupe to a single line and drill down to the affected list. Fix the cause once — at the source feed, or with a single rule that covers the whole group. See Bulk-fix a whole category with one rule.
Do I have to approve all content before ads can run?
No. Unapproved content is used by default, so nothing is blocked waiting on your review. Reviewing is a quality pass. (You can tighten this per placeholder if a client needs stricter editorial control — see Reviewing and approving content.)
I fixed something last week but it never took effect — why?
Almost always an unpublished draft. Edits to a catalog or channel stay in a draft until you Publish, and imports process your last published configuration. The dashboard's draft reminders exist to catch exactly this — a fix that was made but never published.