The rule that decides whether a card shows green, orange, or red. Read this if you want to know exactly how "on Monday you should have Sunday's daily target done" gets computed for week, month, quarter, and YTD views.
One function produces a number between 0 and 1 representing how far through the current period you are. Every card on the dashboard uses the same output.
paceFactor counts only days that have fully ended — not the day in progress. Sunday = 0 days complete, Monday = 1 (Sunday done), Tuesday = 2, and so on.
This matches how a human reads the week: on Monday afternoon we don't judge you against 1.6 days of expected output; we judge you against what should have been done by the end of Sunday.
Examples for a fiscal week (Sunday–Saturday):
Apply the pace factor to the weekly goal and you get where the number should be by now: "paced target."
Weekly daily rate = weekly goal ÷ 7. For the 15,435-unit weekly goal, that's ~2,205 units/day. On Monday you should have 1 day's worth done (~2,205). On Tuesday, 2 days' worth (~4,410).
So 3,500 units on Monday ÷ 2,205 paced target = 159%. Ahead of pace → green. The old fractional-hour math would have computed ~1.7 days of pace (~3,760) and called 3,500 "behind" at 93% — which doesn't match how a person reads the week.
paceDelta = actual ÷ pacedTarget. That ratio drives color through a uniform rule:
On track or ahead of where you should be for this point in the period.
Watch. Not an emergency, but one soft day makes this a problem.
Behind. Something needs to change or there's a clear reason why.
Same thresholds apply to every pace-eligible metric, every period. No hidden neutral zone, no per-metric overrides.
Same idea, different units. All four count completed days only (floor, not fraction). No partial credit for the day in progress.
Fiscal week, Sunday 00:00 through Saturday 23:59 local. paceFactor = floor(daysSinceSunday) ÷ 7. Sunday = 0/7 (grace). Monday = 1/7. Tuesday = 2/7.
Calendar month (not rolling 4-week). paceFactor = floor(daysSinceMonthStart) ÷ daysInMonth. April 9th = 8/30 = 26.7%.
13 fiscal weeks (91 days). paceFactor = floor(daysSinceQuarterStart) ÷ 91. Day 32 of the quarter = 32/91 = 35.2%.
Fiscal year starts Oct 1. paceFactor = floor(daysSinceOct1) ÷ 365. April 20 = day 201 complete → 201 / 365 = 55.1%.
On the very first day of any period (Sunday of a fiscal week, the 1st of a calendar month, etc.), paceFactor = 0. We treat that as green by default — pacing hasn't started yet, so we don't flag early-period numbers as behind. This avoids whiplash between "just started the week" and the first real pacing check on day 2.
Pacing only makes sense for running totals. Ratios, averages, and point-in-time counts are compared to the full target, not a paced fraction.
Active subscriptions is a snapshot at the end of the week, not a cumulative number you build toward. Week goal is the target count; color compares actual to full target.
Both groups still use the uniform 75/95 color thresholds — just compared to the full-period target instead of a paced fraction. So "active subs at 92% of target" reads orange regardless of when in the period it's checked.
The number on a KPI card and the color of that number come from two different calculations, on purpose.
percentOfGoal = actual ÷ full goal. Bounded 0..~100%, always positive, intuitive. Reads as "how close to finishing this period's goal am I?"
Tuesday morning at $128K vs a $384K weekly goal → 33% of goal. Honest answer to "how much of the week's revenue is in the bag."
paceRatio = actual ÷ pacedTarget. Drives green / orange / red via the 75/95 thresholds, but is never rendered directly as a number.
Tuesday morning with 2 days of Monday-Tuesday completed: pacedTarget = $384K × 2/7 = ~$110K. Actual $128K is ratio 1.16 → green. So the card reads "33% of goal" in green — honest about progress, color says on track.
If we showed "% of paced goal" (115% in the example above) we'd get numbers that swing wildly by day of week — a Monday-afternoon read could show 250% for a metric that's cleanly on pace, which trains the eye to ignore the number. Decoupling lets the number stay stable and bounded while the color carries the pacing signal.