Advanced Notion Rollups & Formulas for System Automation

Notion rollups can’t be stacked directly—but a practical workaround makes multi-level performance metrics possible, especially for numbers. The system being built uses daily-to-weekly rollups for things like sleep averages, then mirrors those rollup results with formulas so monthly views can aggregate again. That approach sidesteps Notion’s limitation on “rollup of a rollup,” while still producing clean, usable monthly statistics.

The walkthrough starts with a set of advanced automation upgrades inside the “alignment zone” and then drills into three rollup/formula techniques. First, an automated “task progress bar” replaces a more manual progress assessment. It calculates progress from two rollups in the project database: remaining actions (count of unchecked “done” tasks linked to a project) and completed actions (count of checked “done” tasks). A formula then turns those counts into a percentage so the progress bar updates automatically as tasks are checked off. The tradeoff is accuracy: every task is weighted equally, so a trivial task counts the same as a major deliverable, and the percentage can look misleading when new tasks get added midstream. Still, the progress bar functions as a management trigger—near 90–100%, it signals that more tasks may need to be added or the project may be ready to close.

Second, the project “active” checkbox is automated using a formula instead of manual toggling. The formula checks the project’s status field: if status is “active,” the checkbox becomes true (checked); otherwise it’s false (unchecked). That reduces clutter and makes goal-level rollups cleaner because the goal outcomes can count active projects automatically. The tradeoff is speed: changing a checkbox is one click, while switching a status may take extra interaction—so the automation is applied where it matters most (projects) rather than where it would slow down daily task checking.

Third—and most important for the rollup-of-rollup problem—the system demonstrates how to mirror numeric rollups. In the weekly review, sleep time is rolled up from daily tracking. Since that rollup can’t be rolled up again to the monthly review, a formula property is added that mirrors the weekly rollup value and rounds it to a tidy decimal format using a Notion-specific rounding pattern (multiplying/dividing by powers of 10). Once the weekly value is represented as a formula (not a rollup), the monthly database can roll up the formula across linked weeks and compute an average for the month.

The workaround works well for numbers, but the transcript flags a limitation for text. Mirroring rollups that produce text (like “pillars” linked through a hierarchy) ends up as unusable URLs, and there’s no equivalent “two text” conversion to strip the URL into readable text. The presenter invites community solutions, but the current conclusion is that the mirroring technique is functional mainly for numeric rollups.

Overall, the upgrades emphasize a consistent theme: automation reduces manual upkeep, but each method carries costs—field clutter, interaction speed, and measurement fidelity. After trying these alternatives for weeks, the system’s final design choice is left open, with the next phase shifting toward a “vault” series aimed at knowledge management and distillation into reusable knowledge products.