Content language · English
Weekly Command Review: Scale, Change, or Stop
A job search without a weekly decision ritual is a mood. Moods don’t reallocate hours. Sundays (or whatever weekday you can protect) exist so that Monday is not a random restart of last week’s spray.
Weekly Command Review is 30–40 minutes, same weekday, written output. The mandatory product of the meeting is three decisions with one-line reasons: scale, change channel/motion, or stop. If you leave with only vibes and a prettier board, you held a status meeting. Status meetings are how pipelines rot politely.
Cadence and setup
- Same weekday every week. Protect it like a Screen.
- Inputs open before you start: kanban CSV, conversion metrics worksheet, touch log, Targeting Map, Evidence Bank notes, interview debriefs.
- Timer: 40 minutes max for the review itself. Overrun usually means your board hygiene failed during the week—fix hygiene, don’t romanticize long retrospectives.
- Output: filled one-pager (digital or print) saved with week number and date in your zone.
Bring coffee if you want. Bring honesty either way.
Section 1 — Funnel snapshot
Enter counts for the week: entries into each stage, currently open, Stale, Cold.
Stages stay locked: Sourced → Applied → Screen → Loop → Offer → Closed.
Then rates from your sheet only:
| Metric | This week | Prior week |
|---|---|---|
| Screen / Applied | ||
| Loop / Screen | ||
| Offer / Loop | ||
| Signal events / hours |
Signal events = Screens + Loops + meaningful human replies that move a row. Autoresponders don’t count.
Compare to prior week in writing. “Feels worse” is not a row. Numbers are.
Section 2 — Channel scoreboard
Every Applied tagged: job_board, company_site, referral, recruiter_inbound, community, outbound_hm.
Scroll for all columns
| Channel | Applied (n) | Screens | Screen rate | Decision |
|---|
Decisions per channel: scale / change / stop.
Stop after adequate sample (guideline: ≥10 Applied in channel across 2–3 weeks) with weak Screen rate—or sooner if toxic/scam.
Change means alter motion: titles, companies, resume_version, outreach framework, Gate strictness—not “same thing louder.”
Scale means more hours only when Gate hygiene holds.
Write the decision on the scoreboard. Do not leave blanks “to see how you feel tomorrow.”
Section 3 — Quality Gate audit
- Any Applied marked without Gate pass? Correct stage or admit process drift.
- Count Gate failures caught before send—this is a health metric. Zero failures forever often means rubber stamps.
- Resume versions used this week: list IDs. Thrashing five versions in seven days is not iteration; it’s panic.
If the audit finds fake Applied rows, fix them before you trust Screen rate. Otherwise the rest of the review is fan fiction.
Section 4 — Targeting Map
- Demote / cut: names.
- Promote / add: names.
- Active A+B count (cap—often ≤12).
A map with 40 “Priority A” companies is a wishlist. Wishlists don’t get Screens; they get envy. Cut until the cap hurts a little.
Section 5 — Outreach & stale clear
- Touches sent / meetings booked.
- Stale cleared / Cold-closed.
- Next week outbound focus (one sentence).
Stale rules belong in your playbook (example patterns: Applied stale after N days without next action; Screen stale if debrief missing). Clear in the review, don’t admire the moss.
Caps still apply. A Weekly Review that “scales” outbound to 50 cold notes is how you become the reason people hate seekers.
Section 6 — Interviews & Evidence Bank
- Screens/Loops this week.
- Debriefs filed same day? Y/N. If N, that is a process bug equal to skipping Gate.
- Top gap to fix (one). Put it in Evidence Bank or mock plan—not in a vague “be more confident” note.
Section 7 — Decisions (required)
Force three written lines, for example:
- STOP job_board Easy Apply for Title X — 0 Screens / 12 gated Applied over 3 weeks; motion exhausted.
- CHANGE referral asks to ladder step 2 only on Priority A — Screens came only from warm paths with shared context.
- SCALE company_site apps on two A-targets — Gate pass quality high; Screen rate readable at small n; add +3 hours.
Optional fourth: personal constraint (visa timing, burnout cap, family week). Constraints are decisions too.
No decisions → you didn’t review. You journaled.
What a good review feels like
Slightly uncomfortable. You will kill a channel you liked. You will admit a resume version was cosplay. You will schedule fewer applications and more Evidence Bank hours. Discomfort means the ritual worked.
A bad review feels soothing: “keep doing everything,” “market is tough” as the only sentence, zero cuts, plus a new color on the kanban.
Worked fictional Sundays (contrast)
Week 2 — failed review (what not to do)
Funnel: Applied 18 (many ungated), Screens 0. Channel scoreboard blank. Gate audit skipped. Decisions: “push harder,” “update LinkedIn banner.” Result: Week 3 repeats Week 2 with more fatigue.
Week 4 — corrective review
Funnel: Applied 7 gated, Screens 2, Loop 1. Hours 11. Signal/hour up. job_board 0/9 across two weeks → stop. referral 2/2 Screens on tiny n → scale carefully with caps. Evidence gap: incident narrative weak → change Friday block to Evidence Bank. Three lines written. Week 5 hours follow the page, not the anxiety.
Your numbers will differ. The shape of the ritual should not.
Time budget inside the 40 minutes
| Block | Minutes |
|---|---|
| Pull counts + rates | 8 |
| Channel scoreboard | 10 |
| Gate + Targeting | 8 |
| Outreach/stale + interviews | 7 |
| Write three decisions | 7 |
If counts take 25 minutes, your weekly hygiene failed. Add a 10-minute Friday stale pass so Sunday isn’t archaeology.
Pairing with daily ops
Daily: Gate on each apply, next_action_date, touch log, same-day debrief if interviewed.
Weekly: rates, channels, map cuts, forced decisions.
Monthly (light): role-family strategy, floor refresh for offers, burnout check.
Do not invent a daily Command Review. You will abandon it.
Honest limits
A perfect Sunday does not create headcount. It reallocates your scarce hours toward cleaner signal. Markets freeze. Visas constrain. Levels mismatch. The review makes those constraints visible instead of mystical. No ritual guarantees interviews or offers. Beware anyone who sells guaranteed pipelines for coffee money.
Run four Weekly Command Reviews before you declare “process doesn’t work.” Most seekers never ran one with clean denominators.
Failure modes of Weekly Command Review
The vibes close. You talk yourself into “market is bad” as the only decision. Fix: require channel-level lines; market notes are annotations, not substitutes for stop/change/scale.
The museum board. You spend the slot color-coding stages and never write decisions. Fix: decisions block first if time is short; aesthetics never unblock a Screen.
The punishment review. You use Sunday to shame yourself for low volume. Fix: track signal/hour and Gate fails caught before send. Shame spikes spray.
The renegotiation. Monday you ignore Sunday’s stop and Easy Apply again. Fix: put the stop rule on a wall cheatsheet; tell one accountability human the channel you stopped.
The metrics cosplay. You copy blog benchmark percentages into “prior week.” Fix: prior week must be *your* prior week only.
Escalation path when reviews stall three weeks
If three consecutive reviews show flat-zero Screens with gated Applied ≥10 total:
- Re-read Targeting Map caps and level honesty.
- Run Evidence Bank rewrite lab on top 5 bullets with a harsh reader.
- Shift hours from job_board to referral/community with caps.
- Consider role-family reset (one family per season).
- Check external constraints (visa, location, compensation floors vs market).
Still no: the process is working as a diagnostic—the market/fit may be the blocker. Don’t “fix” by deleting Gate.
Family / burnout constraints as first-class decisions
Write hours caps in the decision section: “max 10 search hours next week.” A review that schedules 30 hours you won’t perform is another lie in the system. Burnout creates spam relapse. Treat rest as an operator constraint, not moral failure.
Templates worth printing
- Weekly Command Review one-pager (sections 1–7).
- Channel scoreboard alone on the wall.
- Gate poster next to your monitor.
- Cheatsheet: stale/cold day rules + stage vocab.
Paper reduces the chance you “forget” a stop decision when anxiety spikes midweek.
Closing the loop with next week’s calendar
Decisions that never hit the calendar die. After you write scale/change/stop, block the hours:
- Evidence Bank rewrite — Tuesday 90 minutes.
- Gated company_site apps — Wednesday 60 minutes.
- Referral ladder touches (capped) — Thursday 45 minutes.
- Stale clear — Friday 15 minutes.
- Weekly Command Review — Sunday 40 minutes.
If the calendar still shows “apply spray 3 hours daily,” you did not accept your own stop decision. Operator move: delete the spray block.
Soft note — Job Hunt Command Kit
Weekly Command Review is the spine of Job Hunt Command Kit (Core, $19 one-time—HTML, XLSX and print one-pagers) on jobhuntkit.top. No hire guarantee. If you only need a blank spreadsheet, steal this one-pager structure today.