Content language · English
Weekly Job Search Review: Metrics Before Mood
A weekly job search review is not journaling about how the market “felt.” It is a short ops meeting with yourself: open the board, compute a few rates from your rows, audit whether Applied meant Gate-pass, then write scale / change / stop decisions that change next week’s hours. If you leave with vibes and a color-coded spreadsheet, you held a status meeting. Status meetings are how pipelines rot politely.
This article is the “why + shape” of that ritual. The filled one-pager shape lives in the Command Kit’s Weekly Command Review worksheet; the longer operator checklist is also mirrored in Weekly Command Review: Scale, Change, or Stop.
Why weekly beats daily panic
Daily refresh feels like work. It rarely reallocates channels. Conversion math needs a week of sample: Screen/Applied by channel, Loop/Screen, signal events per hour, stale and cold clears. Check those every morning and you overfit noise. Skip them for a month and you invent a narrative about “the market” while one dead board lane ate sixty percent of your hours.
Protect the same weekday every week—Sunday evening or Monday morning, whatever you can defend like a Screen. Cap the review itself at 30–40 minutes. Overrun usually means board hygiene failed mid-week. Fix hygiene; do not romanticize long retrospectives.
Inputs open before the clock starts
- Kanban with locked stages:
Sourced → Applied → Screen → Loop → Offer → Closed - Channel tags on every Applied (job_board, company_site, referral, recruiter_inbound, community, outbound_hm)
- Conversion worksheet or equivalent rates (see Job Search Funnel Metrics)
- Touch log, Targeting Map (A/B cap), Evidence Bank notes, same-day interview debriefs
If stages are creative (“recruiter liked me,” “onsite vibes”), your funnel is fiction. Onsite or video is a format under Loop—not a new stage. Autorejects are not Screens. Stale and Cold are timer states with next_action rules—see Stale & Cold Pipeline Rules.
The review spine (eight blocks)
- Funnel snapshot — counts this week, open WIP, Stale, Cold.
- Rates — Screen/Applied, Loop/Screen, Offer/Loop, signal/hour vs prior week. From your sheet only. No invented industry benchmarks.
- Channel scoreboard — Applied n, Screens, Screen rate, decision column.
- Quality Gate audit — any Applied without Gate pass? Failures caught before send? Which
resume_version? - Targeting Map — demote/cut, promote/add, A+B count vs cap (≤12 is a workable starting rule).
- Outreach & stale clear — touches, meetings, stale cleared, cold-closed, next outbound focus.
- Interviews & evidence — Screens/Loops, debriefs same day?, top gap to fix.
- Decisions + one sentence — channel, targeting, evidence, time budget—each with owner action + date.
Operator rule: A cut is only real when (a) sample is adequate or the lane is toxic, (b) hours move to a better lane, (c) next week’s touch log shows the stop. Writing “stop job_board” while Monday Easy Apply continues is a slogan, not a command.
Scale, change, stop — in plain language
Scale means more hours where the rate holds—usually warm referral or community paths that produce Screens or human replies without inventing metrics. Change channel means the mix shifts: board becomes supporting volume under Gate, not the default identity of the hunt. Stop means pause a lane and free WIP—cold HM with zero replies across a fair sample, a Priority C ego spray, a resume_version that keeps failing Gate.
Do not stop a channel on n=3 “because vibes.” Guideline: ≥10 Applied in-channel across 2–3 weeks before a stop for rate reasons—unless the lane is clearly toxic (scam, unethical). Premature stops feel decisive and usually fail the behavior test the next morning.
Gate audit is not optional decoration
If Applied includes ungated spray, Screen/Applied lies, and your weekly “strategy” becomes spray harder. An Application Quality Gate protects the denominator and anyone who might put their name on you. Three Gate fails on the same resume version → freeze Applies; repair evidence and targeting first. Volume is not a strategy when the packet is broken. Proof still lives under the hood—an Evidence Bank keeps bullets as views over ACH rows, not adjective spam.
What a good Sunday produces for Monday
Monday should inherit Sunday’s writing. If you scaled referrals, the calendar shows warm touches—not more board tabs. If you changed motion, Gate and packet change before volume returns. If you stopped outbound_hm, the touch log shows zero new cold HM, not “just one more batch.” Loop weeks shift time budget toward prep and same-day debriefs without abandoning Gate.
Save the one-pager with week number and date in your zone (Asia/Shanghai for this site’s SAMPLE season). Compare weeks in writing. “Feels worse” is not a row.
What this review is not
- Not a hire guarantee. Process control ≠ outcomes.
- Not a Notion aesthetic project. Core uses HTML and XLSX; other kits use the formats listed on the product cards.
- Not fake conversion claims. SAMPLE files in kits are fictional samples, not testimonials.
- Not a substitute for the full Command Loop—Gate, locked stages, rates, then weekly command.
Minimal install
- Lock stage vocab and channel tags on the board.
- Put a 40-minute Weekly Review on the calendar.
- Run Gate before the next real Applied.
- Leave Sunday with written scale/change/stop and one sentence for next week.
That is the weekly job search review: metrics before mood, decisions before Monday, hours that match the page you signed. Core is listed as a $19 one-time digital download on jobhuntkit.top. No outcome promises—only a cleaner operating system for the hunt.