Skip to main content

Why is month-to-date pacing always wrong in the first week?

Dashboards & Reporting Published November 17, 2026
Short Answer

Because straight-line run rate assumes revenue arrives evenly and it does not. Weekends, holidays, billing timing and job completion patterns make the first days unrepresentative. Pace against your own historical shape of the month instead: the share of a typical month's revenue that has landed by this business day. That single change removes most first-week false alarms.

Why naive pacing misfires

The usual formula takes month-to-date, divides by days elapsed, and multiplies by days in the month. It assumes every day contributes equally. In a service business the first of the month can be a Saturday, the month can open with a holiday, and invoicing can cluster around week ends. Early in the month the divisor is small, so each of those distortions gets multiplied.

The result is a projection that swings violently for the first week or so and then settles. People learn to ignore it, which means the projection is useless in the exact window where it could still change the outcome.

Curve-based pacing instead

Build a cumulative share curve: from several prior years, the fraction of the month's final revenue that had landed by business day one, two, three and so on. Then the projection is month-to-date divided by the expected share for the current business day.

It is not sophisticated, it is just correct about the shape. Businesses with heavy weekend or holiday effects see the biggest improvement, and the curve is stable enough that rebuilding it annually is plenty.

Show a range, and make the range mean something

An early-month projection carries real uncertainty and should be displayed as a band rather than a point. Derive the band from history: across prior months, how far off was a projection made at this business day. That gives you an honest, empirical range instead of an invented plus-or-minus.

The band naturally narrows as the month proceeds, which teaches the reader how much weight to put on the number without anyone having to explain it.

The part almost everyone gets wrong

Month-to-date revenue is itself incomplete, because jobs invoice late. If you build the pacing curve from restated, fully matured history but compare it against today's immature month-to-date, the projection will show you behind every single month and then mysteriously recover.

The curve has to be built from as-of snapshots, capturing what was recorded by business day five at the time, not what we now know about business day five. That requires storing daily snapshots, which is a deliberate design decision in the revenue data model and one of the more common gaps we find in existing business intelligence setups.

Topics: pacing · forecasting · run rate · month-to-date

Have a version of this question about your own business?

The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.

Related Answers

People who read this also asked

Browse the Answer Hub →

AI is easy to access. Making it useful is hard.

Bluefrog makes AI useful by integrating it with the way your business actually works — your software, your calls, your customers, your marketing and your revenue.

Technology development since 1997 · AI integration platforms since 2001