Three Notion Rollups for Freelancers That Replace Guessing
Links do not count themselves
You added the relation, so a project knows its client and a task knows its project. Without a rollup, that knowledge just sits there. Three Notion rollups for freelancers turn it into the numbers you open the app for: how far along the work is, what the hour really paid, and how long the cash lasts.
The word rollup sounds technical. It is one job: look at the rows linked through a relation and reduce them to a single number. Depending on the property you point it at, the calculate menu offers counts, sums, averages, dates, and percentages. The four a one-person business actually needs are covered below.
How a rollup works, in three steps
- The relation has to exist. A rollup reads through a relation, so without one there is nothing to roll up. If the relation itself is fuzzy, the client and project linking guide covers it.
- Add a property, choose Rollup, pick the relation, pick the property on the other database, then pick the calculation. Notion fills the cells for every linked row.
- Put a formula property on top when the rollup is only half the answer, which is the case for two of the three below.
The calculation menu matters more than it looks. Count all counts every linked row regardless of blanks. Count values counts only rows where the chosen property has a value, so choosing a property that is usually empty gives you zero and a false sense that nothing is linked. Sum adds numbers and needs a number property to point at.
The three Notion rollups for freelancers you will use
| Rollup | Lives on | Relation | Property | Calculate | Formula on top |
|---|---|---|---|---|---|
| Tasks Total | Projects | Tasks | none | Count all | none |
| Tasks Done | Projects | Tasks | Done | Sum | Progress |
| Billed | Clients | Invoices | Income Amount | Sum | none |
Done and Income Amount are themselves formulas, and this is where the system starts paying compound interest. A formula produces a number, a rollup adds that number up, a second formula divides it. Each step is simple; the chain answers a question you could not answer before.
Progress: set the format, not just the formula
First, the flag on Tasks:
`` if(prop("Status") == "Done", 1, 0) ``
Call it Done and hide it once Tasks Done works, because it is plumbing. Then the percentage on Projects:
`` if(prop("Tasks Total") == 0, 0, prop("Tasks Done") / prop("Tasks Total")) ``
Set the number format to Percent. Notion's percent format takes the raw ratio between 0 and 1, so 0.5 displays as 50 percent. If you add the percent format to a formula that already returns 0 to 100, a finished project shows 5,000 percent, and every number in the workspace becomes suspect.
Two honest limits. Progress counts tasks, not effort, so a project with one enormous task looks 9 percent done when the hard part is finished. And it only counts tasks you actually created in Notion. Neither is a formula bug; the fix is process, such as splitting large tasks into real pieces.
Effective rate: never average the rates
The effective hourly rate is a project-level number, not a rollup of task-level ones:
`` if(prop("Hours Logged") == 0, 0, round(prop("Budget") / prop("Hours Logged"))) ``
The tempting version is a rollup that averages some rate property across tasks. Skip it. An average weights a one-hour task and a twenty-hour task identically, so it tends to describe the calendar rather than the money. Budget divided by hours logged is the number that matches the bank. Compare it with the client's quoted rate, and read client profitability when it sits below that rate.
Runway: a division on the review row, not a rollup
Runway does not belong in a rollup, and pretending otherwise is how people end up with a monthly burn that is actually total spending. Runway is cash on hand divided by average monthly burn at one moment in time. Put two number properties on the Weekly Reviews database and do the division there:
`` if(prop("Monthly Burn") == 0, 0, round(prop("Cash on Hand") / prop("Monthly Burn") * 10) / 10) ``
The multiply-by-ten trick is required because round() returns whole numbers. Without it, 5.5 months shows as 6. A rollup across all your review rows would sum the months instead of describing this one. The weekly review setup covers what to type into those two fields and when.
Where rollups stop
A rollup cannot filter the rows it reads. There is no way to tell it "count my open tasks" and have it understand the adjective. The workaround is the 1/0 flag formula from the progress section: roll up the flag with Sum, and only the rows that match contribute anything. That is not a limitation of your setup; it is how rollups are built as of the versions tested, and the flag pattern is the accepted fix.
If your version offers a Percent checked calculation, it does the same ratio in one step when the source property is a checkbox rather than a number. Use whichever your version exposes. What you should not do is trust a 5,000 percent result or a number that reads zero because the relation cells were never filled.
Do this today
- Add the
Doneflag formula on Tasks and hide the property after theTasks Donerollup displays a number. - Add
Tasks TotalandTasks Doneon Projects, add the progress formula, and set the format to Percent before trusting either figure. - Add the runway formula on Weekly Reviews and type in this Friday's cash on hand and average monthly burn, then check the one-decimal result.