Run Your Friday Notion Weekly Review in Twenty Minutes
A shrug is not a review
It is Friday at four and the honest answer to how the week went is a shrug. You have the bank tab, the invoice tab, three project pages, and a task list, and none of them agree with each other. The twenty-minute Notion weekly review below is built to end with three decisions instead of a tidier page.
The reason most weekly reviews die by week three is that they ask you to reflect. Reflection is pleasant and produces nothing you can act on Monday. A review you can finish in one sitting is a review you will still be running in February. A fixed list of questions asked in the same order produces a short list, and a short list is something you can finish.
The 20-minute Notion weekly review, by the clock
| Minutes | Question | Where the answer lives |
|---|---|---|
| 0 to 3 | What cash came in? | Finances, Type is Income and Paid On is this week |
| 3 to 6 | What is late? | Tasks, the Overdue view |
| 6 to 10 | Which project is slipping? | Projects with Hours Logged above zero, sorted by effective rate |
| 10 to 13 | Where did the hours go? | Tasks grouped by Project plus your calendar |
| 13 to 16 | How long can I last? | Weekly Reviews: cash on hand, monthly burn, runway |
| 16 to 18 | What did I avoid? | Your own judgment, typed in one line |
| 18 to 20 | What is the one thing for next week? | One task row, created before you close the laptop |
Take money first
Start with cash received, not invoices sent. Sent-but-unpaid invoices are a hope, and a review built on hopes teaches you to trust the wrong number. Pull cash received from the ledger for the week, then look at what is owed. Anxiety about a month usually drops once both numbers are in front of you, even when neither number is good.
Two numbers settle most Friday nerves: what actually landed and what is already overdue. A month that felt bad because of one invoice going unpaid reads differently once the second number has a name attached to it.
Five questions worth writing in full
- How much did I actually receive, and from whom?
- What was due this week and did not ship?
- Which project's effective rate fell below the rate I quote?
- What did I avoid all week?
- If nothing new arrived, how many months could I keep going?
The clock covers seven steps; these five are the ones to write in full sentences, because they are the ones you will reread on Monday. Write the answers on the same page as the numbers. Numbers without a sentence get forgotten by Monday, and sentences without numbers become a diary.
If a question takes more than three minutes, the answer is not in Notion yet. Write "missing" in the cell and fix the database that should have answered it during the following week.
Answer the avoidance question honestly
The "what did I avoid" line is not a confession; it is a routing instruction. If the same task appears there twice, either delete it as not worth doing or make it the first task on Monday. Two minutes, one sentence, no analysis.
Put the numbers in properties, not paragraphs
Create a Weekly Reviews database with nine properties: Week Of, Revenue This Week, Cash on Hand, Monthly Burn, Runway, Hours Worked, Energy, Bottleneck, and One Thing Next Week. One row per Friday. Energy is a select with three options: Good, Fine, Drained. It costs one click and it is the cheapest diagnostic in the system. Three drained weeks with healthy runway means the problem is not money, and no amount of invoicing fixes it. The only formula is runway:
`` if(prop("Monthly Burn") == 0, 0, round(prop("Cash on Hand") / prop("Monthly Burn") * 10) / 10) ``
The multiply-and-divide around round() is not decoration. Notion's round() returns whole numbers, so without it a runway of 5.5 displays as 6, and a business with six weeks of runway does not round to comfort.
Cash on hand is what is in the bank on Friday, including the tax money you have set aside, because it is still your cash and the bill is still coming. Monthly burn is your last three months of total outgoings divided by three. Quarterly tax payments belong in the month they leave the account, which is exactly why a three-month average is steadier than one month. The full method is in how to calculate freelance runway.
Three readings, three decisions
The review earns its twenty minutes only if a number changes what you do next week. Three readings cover most weeks:
| Reading | What it means | Action this week |
|---|---|---|
| Runway under 3 months | One slow month from a real problem | Chase the oldest receivable, raise the next quote, cut one subscription |
| Effective rate below target on two projects | Scope or revision problem, not a speed problem | Add a revision limit or a change-order clause to the next contract |
| Same bottleneck three reviews running | A process problem, not a bad week | Change one workflow step and check the same field next Friday |
The third reading is the one people miss, because it requires reading your own past reviews. Sort the Weekly Reviews table newest first and check whether your bottleneck line has said the same thing for a month.
None of these actions is a strategy. They are the smallest correction that keeps next Friday cheaper than this one, and they are the reason the review earns twenty minutes instead of demanding two hours.
Keep the system honest
A review page that no other database touches becomes fiction within a month. The numbers you type in should come from the same Finances and Projects tables that run your week, which is why the rollup setup exists. Rollups keep the review reading live records instead of last week's memory. If a number looks wrong on the review page, fix it at the source database rather than in the review row.
Do this today
- Create
Weekly Reviewswith the nine properties above and setWeek Ofto this Friday's date. - Paste the runway formula and type in this week's cash on hand and your three-month average monthly burn.
- Create the actions for the readings you just got, then put a recurring Friday block on your calendar for the review itself.