b2KIT

Year Progress Tracker

Visualize how much of the current year, quarter, month, and week has elapsed.

Tested tool guide Tested browser tools Checked August 16, 2026

What Year Progress Tracker does, with a checked example

How far through the year are we, really? This tool places any date inside four nested periods - the year, the quarter, the month, and the week - and returns each one's elapsed percentage plus days remaining. Every figure is a simple ratio: position within the period divided by the period's length in days. The denominators are what vary: 365 or 366 days for the year, 90 to 92 for quarters, 28 to 31 for months. The surprise most users hit: the current day counts as elapsed, so January 1 reads about 0.3 percent, not zero, and quarter lengths are not equal - they run 90 to 92 days.

Worked example

A concrete input and expected output from the current implementation.

Input

2026-10-22

Expected output

Year: 80.8% elapsed, 70 days remaining. Quarter (Q4): 23.9% elapsed, 70 days remaining. Month (October): 71.0% elapsed, 9 days remaining. Week: 57.1% elapsed (Thursday, day 4 of 7, weeks counted from Monday).

October 22, 2026 is day 295 of a 365-day year, so 295/365 = 80.82%; it is day 22 of the 92-day fourth quarter (22/92 = 23.91%) and day 22 of October's 31 days (22/31 = 70.97%). Q4 ends on December 31, which is why year and quarter both show 70 days left. The date is a Thursday, so the week figure assumes Monday-start weeks; a Sunday-start calendar would show day 5 of 7, about 71.4%. The day counts as fully elapsed, so a moment-based tool would read between 80.5% and 80.8% during October 22.

How the result is produced

1

Ratio math per period

Each percentage is a ratio: a date's position in a period divided by that period's length in days. Position counts day of year, day within the quarter, day of month, or day of week. Lengths are the calendar lengths, which differ: 365 or 366 days in the year, 90 to 92 in a quarter, 28 to 31 in a month, always 7 in a week.

2

Reconciling countdown

Days remaining are the period length minus the current day, so the two readings always reconcile: 295 elapsed plus 70 left equals the 365 days of 2026. The current day counts as elapsed, not remaining, which is why readings step at midnight rather than the evening before, and why a date never shows 100 percent until its final day begins.

Good uses

  • You manage a yearly goal - sales quota, savings target, or reading list - and want the calendar to audit your pace: at 80.8% of the year, progress under 80.8% means you are behind.
  • You plan around a quarter-end report and need the exact count of days left before the close - 70 on October 22 - to schedule submissions, reviews, and sign-offs.
  • You face a year-end deadline such as tax filing or benefit enrollment and want a countdown, plus a month-level view for nearer deadlines like an expiring data cap.

Limits and checks

  • Week progress depends on where the week starts. October 22, 2026 reads 57.1% on a Monday-start calendar (Thursday is day 4 of 7) and 71.4% on a Sunday-start one, so the week figure is only meaningful with the convention attached.
  • Leap years shift every percentage after February 28. In 2028 the same date is day 295 of 366 (80.6%), not 80.8%, because February gains a day. Year-over-year comparisons of percentage done are only exact during January and February.
  • The current day counts as elapsed and the clock used is your device's. January 1 therefore opens at about 0.3% rather than zero, the year reads 100% from the start of December 31, and if the tool factors in time of day, values creep upward through the day instead of stepping at midnight.

Common questions

Why doesn't January 1 show 0 percent?

Because the day you are in counts as elapsed. January 1 is day 1 of 365, so the year opens at 1/365, about 0.3 percent, and reaches 100 percent at the start of December 31 rather than at the stroke of midnight. Read every figure as 'done by the end of today.'

Which time zone does it use, and is my date uploaded?

The tool uses the date and time from your own device, so the percentages reflect your local clock; two people at the same moment in different time zones can see different readings near midnight. Computation happens in the browser on your machine, and no date, time, or other data is sent anywhere.

References and verification

The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools