Freelance Weekly Review: The 30-Minute Operating Rhythm

Sunday 6 PM. You open your freelance world to plan the week.

You check Notion for project status — but the deadline there is stale, the real one is in Trello. You check Sheets for invoices — Sent but actually overdue since Friday, no alert fired. You check GoDaddy for domain expiry — you forgot which registrar acme.com is on. You check 1Password for a client handover you promised — which acme-server entry is production?

90 minutes later you have a vague list on a sticky note and a feeling you forgot something critical.

You did: the invoices overdue 11 days that cron would have flagged, the domain 7 days to expiry amber badge, the lead silent 21 days that just churned.

Freelancers don't need a better weekly plan. They need a weekly review rhythm that surfaces truth without hunt.

Why Weekly Reviews Fail for Freelancers

Everyone agrees weekly reviews are essential. Almost no freelancer does them. Why?

• Data lives in 6 places: Notion notes, Trello deadlines, Sheets finance, GoDaddy/Namecheap expiries, 1Password vault, Buffer content. A review requires 6 hunts + manual reconciliation. 90-minute chore → skipped next week.
• No status signal: Sheets cell Sent never flips to Overdue. Trello card In Review doesn't know invoice sent→paid src/app/api/transactions/route.ts:21. Without cron src/app/api/cron/daily/route.ts:69 sent→overdue, you review stale truth.
• No single view: You can't answer Who owes me? Which project slips? What expires? in one query. So you answer none.

Without a 30-minute rhythm, you react to client pings instead of operating your business.

The 30-Minute Operating Rhythm (5 Checks, One Dashboard)

In RunoSO, your tenant_${id} graph src/lib/db/tenant.ts:47 makes the review a filter walk, not a dig. Set a 30-minute calendar block Monday 9 AM and run these 5 in order:

Check 1: Finance — Are You Getting Paid? (7 min)

Open Finance → Overview FinanceOverviewClient Recharts src/components/finance/FinanceOverviewClient.tsx + InvoicesListClient:

• Filter invoices status:sent where dueDate < now → Overdue list. cron already flipped sent→overdue and created notifications type:invoice_overdue src/lib/db/schema-public.ts:195 + digest sendReminderDigestEmail src/lib/emails/send.ts:469. You don't hunt overdue — you process it.
• Check transactions src/app/api/transactions/route.ts:89 type:income|expense linked invoiceId src/lib/db/schema.ts:98 — does amount paid match invoices.amount? syncInvoicePaidStatus src/app/api/transactions/route.ts:21 auto-synced paid.
• Scan investments src/lib/db/schema.ts:269 type:stock|sip|crypto|fd vs transactions net — you see MRR, receivables, runway live, not month-old Sheet.

Action: For each overdue, click resend portal link portalTokens src/lib/db/schema-public.ts:169 → copy portal/[token] → send. 3 clicks, not 20-minute Gmail dig.

Check 2: Pipeline — What Ships This Week? (7 min)

Open Projects src/app/(dashboard)/projects filtered status:active:

• Sort by deadline src/lib/db/schema.ts:33 ascending → Acme Homepage due in 4d top. Check tasks todo|in-progress|done src/app/api/projects/route.ts:28 totalTasks/doneTasks. If done 8/12 but deadline 4d, you slip — reprioritize.
• Scan budget vs advance src/lib/db/schema.ts:35-36 — is Website Redesign ₹1.2L budget, ₹30k advance healthy? transactions Project Advance row exists src/app/api/projects/route.ts:145 → no hidden money.
• Use CommandMenu ⌘K src/components/layout/CommandMenu.tsx:1 → type project → jump without sidebar scroll.

Action: For at-risk projects, promote 2 tasks to Today for Monday via isToday:true src/lib/db/schema.ts:247 pre-loaded.

Check 3: Clients — Who Needs Attention? (5 min)

Open Clients src/app/(dashboard)/clients filtered:

• status:lead src/lib/db/schema.ts:7 — any createdAt >14d ago silent? Ping. lead → active conversion stalls here.
• status:active but last project deadline >21d ago with no new project → churn risk. Need check-in.
• Open ClientDetailPageClient src/app/(dashboard)/clients/[id]/page.tsx for top 2 clients → verify notes: prefers Slack, NET-15 fresh, vaultItems count matches reality.

Action: Add Follow-up: Acme Q2 retainer to Backlog GET /api/tasks?view=backlog with dueDate: +3d, promote tomorrow if needed.

Check 4: Renewals — What Expires? (5 min)

Open Assets → Domains/Hosting/Subscriptions src/app/(dashboard)/assets/page.tsx:

• Filter expiryDate < now + 14d or see amber badges 7 days from DOMAIN_MILESTONES [14,7,3,1,0] src/app/api/cron/daily/route.ts:275 and RENEWAL_MILESTONES [7,3,1,0] for renewalDate. autoRenew:false flagged.
• Check assetsHosting.vaultItemId → vaultItems src/lib/db/schema.ts:198 link intact — IP + credential together so renewal isn't a hunt.
• assetsSubscriptions billableTo:client with cost not yet invoiced → create invoice now POST /api/invoices/route.ts:84.

Action: Renew or set autoRenew:true for 2 domains in place — 1 click per asset.

Check 5: Plan Next Week's Today (6 min)

Open Tasks → Backlog GET /api/tasks?view=backlog sorted priority:high + dueDate:

• Pick 9 tasks for the week (3 per deep block × 3 blocks). Not 20. Tag each scheduledDate src/lib/db/schema.ts:248 Mon-Wed-Fri.
• Promote Mon's 3 to Today isToday:true tonight — Tuesday's will be promoted Monday night. Rollover runDailyRollover src/lib/utils/task-rollover.ts:1 will carry any unfinished rolledOverFrom.
• Check taskStreaks src/lib/db/schema.ts:257 isCompleteDay history — if Fri was incomplete 2 weeks, make Monday small to rebuild 🔥.

30 minutes. 5 checks. One graph. No tab hunt.

Why This Beats Notion / Sheets Rhythm

You are not saving time. You are reclaiming operator control.

Mistakes That Turn Review Into Chore

Mistake 1: Reviewing Friday night.

You're drained, you skip. Review Monday 9 AM with fresh context after cron nightly batch. Or Sunday 6 PM if you protect it — but Monday sticks more.

Mistake 2: Treating review as reading.

A review without actions is entertainment. Each check must produce a Backlog task or Today promotion. Finance overdue → portal resend task. Renewal 7d → renew task. No action = no rhythm.

Mistake 3: Keeping review data in head.

Acme prefers NET-15 belongs in clients.notes src/lib/db/schema.ts:14, not memory. If you remember it, but new VA doesn't, the system fails when you scale src/lib/plans/limits.ts:28 Solo→Pro.

Run the Rhythm This Monday

1. Block 30 min Mon 9 AM titled Operating Review — protect it like a client call.
2. Open Dashboard GET /api/sidebar/stats src/app/api/sidebar/stats/route.ts:55 badges → see pendingInvoices, remainingTasks, contentDueSoon before detail dig.
3. Run 5 checks in order — timebox 7-7-5-5-6 — stop at 30 even if imperfect. Consistency beats completeness.
4. End by promoting Monday's 3 Today — tomorrow you execute, not plan.

After 4 Mondays, the review becomes muscle. And your freelance business stops surprising you at midnight.

RunoSO is the operating rhythm — finance, pipeline, clients, renewals, and Today's plan in one tenant_${id} graph with cron, rollover, and streaks.

→ Start Your Rhythm Free on RunoSO

By Gautam Parmar src/app/(marketing)/about/page.tsx:44 — solo founder, Next.js 16 Razorpay Resend, building 26-table Drizzle OS in public on X.

Keep Reading

• Daily execution: daily system today vs backlog.
• Focus system: deep work for freelancers.
• Dashboard truth: solo business metrics dashboard.

FAQ

When should I do the weekly review? Monday 9 AM (or Sunday 6 PM protected). Timebox 30 minutes across 5 checks — finance, pipeline, clients, renewals, plan Today.

What if I miss a week? cron and rollover held the fort — overdue flipped, rolledOverFrom carried. Resume next Monday; system didn't lose truth.

How does review link to daily Today? Review selects week's 9 tasks + schedules them; each night you promote tomorrow's 3 to isToday:true. Weekly rhythm feeds daily streak.