New Notion Feature! Native Progress Bar Crash Course

Notion’s latest update adds native progress bars—either a progress bar or a progress ring—so users can turn a numeric value into a visual indicator without building custom UI. The key shift is that progress visuals now live inside Notion’s native “number → bar/ring” formatting options, driven by a single number property (from a database field or a formula). That makes progress tracking faster to set up and easier to maintain, especially when the underlying logic already produces a percentage or a count.

The walkthrough starts with a habit tracker that uses five checkbox fields per day. A formula sums the checked values (true/false converted to 1/0) into a single count, then Notion’s display settings convert that number into a bar. Because the result is a raw count rather than a percentage, the “divide by” option is used to normalize the value against the total number of habits (five). The presenter also notes a common pitfall: converting to a percentage format doesn’t automatically mean the displayed value is a clean percentage—users can choose to hide the numeric output and keep only the bar for a cleaner look.

Next comes a more structured project manager example using two linked databases: one for projects and one for tasks. Tasks carry a status (not started, in progress, done) plus a deadline date, and a relation connects each task to its project. From that relationship, rollups compute completion rates by grouping tasks by status. Those rollup outputs are then fed into separate formula properties that convert each status share into a percentage suitable for progress bars. The formulas use a floor-based cleanup to avoid rounding up edge cases like 99.8% to 100%, which would prematurely show completion.

The tutorial then tackles capping progress at 0–100%. A date-range database calculates “today’s position” within a start/end window using date arithmetic (days between now and the start, divided by the total days in the range). Because real-world date ranges can be entirely in the past or future, the computed value can exceed 1 (over 100%) or drop below 0. An if-statement clamps the result: values under 0 become 0, values over 1 become 1, and everything else passes through. Once clamped, the value can be converted into a native progress bar.

Finally, a calendar-cover use case shows how to track progress within a single day. A formula checks whether the calendar date matches today; if it’s in the past, it returns a full 24-hour completion value, and if it’s in the future, it returns 0. For today, it converts the current time into a decimal hour fraction using minutes/60, then normalizes by dividing by 24 to produce a day-progress ratio. The result is a calendar where past dates show complete bars, while today’s bar advances as the day goes on.

Overall, the update turns progress visualization into a formatting choice backed by simple numeric outputs—counts, rollups, and time-based calculations—while still supporting the practical guardrails users need (rounding control and 0–100% clamping). That combination makes progress bars more approachable for everyday dashboards and more reliable for date- and status-driven workflows.