TattvaDocs
Use casesPerformance marketing

Target vs landing

"Where are we landing this month?" — a quick month-end projection that accounts for sale days, ordinary days and weekends.

Planned

This use case needs definitions that aren't in the Library yet (monthly targets). Until your data analyst adds them, Tattva can't answer it as shown here.

The question: "Given how we're trending, and knowing how many sale days, ordinary days and Sundays are left, where do we land this month?"

The simplest forecasting question, and the one asked most often. Mid-month: "What's our projected landing against target?" The maths is simple once you account for the calendar (sale days vs ordinary days vs weekends). Ask Tattva and stop doing the back-calculation by hand.

Who asks

  • The performance-marketing lead, daily in the second half of the month
  • Finance, for the weekly finance review
  • Founders, weekly during sale months

Frequency

Daily in the second half of the month; weekly before that.

Data you need

  • orders: daily revenue and units
  • targets: monthly target per product and overall
  • A calendar table: which dates are sale events and which are public holidays
  • Day-of-week patterns (weekend lift, Monday dip) per product, or enough history to compute them

How to ask it

  • "Where are we landing this month against target? Break it down by product."
  • "At the current run rate, adjusted for the remaining sale days and weekends, what's projected month-end revenue?"
  • "How much faster do we need to run for the rest of the month to hit target, by product?"

What you'll get back

A landing projection (figures made up):

Overall: 7.6M projected against an 8.0M target — landing 5% short.

ProductTargetActual to dateDays leftProjected landingvs targetRun rate needed to recover
SKU-A4.0M2.5M113.6M−10%+18% on current daily
SKU-B2.5M1.9M112.7M+8%on track
SKU-C1.5M0.8M111.3M−13%+25% on current daily

A good projection uses:

  • day-of-week patterns from the last six months (for example, Sundays well above ordinary days);
  • sale-day lift from comparable past sales;
  • the recent trend, so one bad day isn't projected across the whole month.

If revenue settles only after returns, recent days in the actuals are marked Provisional in the Compute card: part of them is estimated.

The logic

For each product:
├── Compute the daily run rate to date (last 7 days, calendar-adjusted)
├── For each remaining day in the month:
│   ├── Tag the day (ordinary / weekend / sale / holiday)
│   ├── Apply that day type's usual multiplier
│   └── Add the projected revenue
├── Add actuals to date → projected landing
├── Compare with target → gap
└── If the gap is below your threshold → compute the uplift needed to recover

How to make it recurring

  1. Click Save as tracker on the answer. It runs daily.
  2. Edit the question and set the Classification rule to Relative delta on your revenue metric with critical if Δ > 5. A run is Critical when the figure moved more than 5% since the previous run. The rule doesn't compare with the target, so read the narrative for the projected gap.
  3. Add the team's Slack channel on the Delivery tab.

Trackers have no time-of-day setting. Each question shows its next run time; click Run now when you want a fresh projection before a meeting.

Pitfalls

  • Wrong calendar. If a sale day isn't in the calendar table, the projection misses its lift. Keep the calendar up to date.
  • Trusting early days. Day 3 of the month is not a reliable base. Wait until around day 10 before leaning on it.
  • Ignoring the recovery rate. The gap tells you how far off you are; the run rate needed tells you what to do each day. The second is the one to act on.
  • Confusing a projection with a commitment. It's the best estimate from the current trend, not a forecast to promise anyone. Use it to decide whether to spend more.
Target vs landing — Tattva Docs