LUFT host analysis · shipped 4 August 2026

Your two amendments are live.

Both changes from your email are now on datahub.uktgdata.com/luft-host-analysis, implemented exactly as you described them, and switched on by default. This page shows what each one does, with screenshots taken from the live report today.

Amendment 1 — future Scheduled data is excluded

You asked: "Exclude Scheduled data in the future from calculations — i.e. Scheduled calls for tomorrow and beyond are excluded. So August's Scheduled to Completed right now would be [sum of completed calls from 1st to 4th August ÷ sum of scheduled calls from 1st to 4th August]."

That is exactly what it does now. Every table on the report — the three funnel tables, the three drop-off tables, and the three cost tables — only counts calls dated up to and including today. Calls booked for tomorrow onwards are out of every calculation until their day arrives. Your worked example is the live number:

Aug Scheduled → Completed, before

13%

14 completed ÷ 111 booked for the whole month

Aug now, amendment 1 on

30%

14 completed ÷ 46 scheduled 1st–4th Aug

July, for reference

48%

completed months are untouched

Scheduled to Completed with amendment 1 on

Live today, amendment on. The outlined August column counts only 1st–4th August. Grand total 30%. Every other column is a completed month and is exactly as it was.

Scheduled to Completed with amendments off

The same table with the amendment switched off — the old behaviour, kept one click away for comparison. August falls back to dividing by all 111 booked calls: 13%.

The cost tables get the same treatment on both sides of their fractions: August's ad spend is divided by the calls scheduled so far (46), not the whole month's bookings, so £-per-scheduled-call stays honest when the future calls leave the count.

Amendment 2 — part-month wage for the current month

You asked: "For current month, the forecast Host Wage is divided by total days in the current month and multiplied by today's date (e.g. today would be ÷31 ×4)."

Implemented as written. Every Host wage figure in August's column is the forecast wage ÷ 31 × 4 today; tomorrow it becomes ÷ 31 × 5, and by the 31st the factor reaches 1, so a finished month is never scaled down. Hovering any August wage cell on the report shows the factor applied ("Part-month: × 4/31 days passed").

The Host wage band of the Cost breakdown table, live today. August (outlined) shows each host's forecast wage ÷ 31 × 4 — team total £175 for the four days so far, against £1,979 before the amendment. Past months keep their full figures.

Host wage, August column	Before	Now (÷31 ×4)
Rachel	£155*	£20
Nicole	£128	£17
Lisa	£672	£87
Whole team	£1,979	£175

*Rachel's "before" here already reflects amendment 1, which trims her forecast to calls taken so far; amendment 2 then applies your day-count factor on top.

The toggles

Both amendments sit behind switches at the top of the report, on by default. Click either chip to flip that amendment off and see the old numbers; click again to bring it back. Nothing else about the report changed.

The report header with the two amendment toggles

The top of the live report. The outlined bar holds the two switches — one per amendment. A tick means it's on. The wage chip shows the current factor (÷31 ×4 today) so you can see the day-count it's using at a glance.

What we checked before shipping

Completed months cannot move. We captured every number on the report before the change and compared after, in both toggle states: only the current month and current week differ; March–July are identical to the digit. With both toggles off, the whole page matches the pre-change report exactly. The day-count factor has its own automated tests, including your ÷31 ×4 example, a 30-day month, and February in a leap year.

Where to see it

datahub.uktgdata.com/luft-host-analysis — both amendments on by default.

August's funnel now reads calls-to-date (30% Scheduled → Completed today), and August's wages are day-counted (÷31 ×4). The toggles at the top let you compare against the old behaviour any time.

Screenshots taken from the live report on 4 August 2026; the blue/red outlines and badges were added on top for this page. Shipped as pull request #329 the same day.