Build Log

A Distribution Claim Needs a Chain of Evidence

A useful distribution programme starts with a claim that can be checked, a route that answers it, and measurement that does not turn a leave plan into analytics data.

Start with the signal, not a keyword list

The pre-promotion baseline showed small but relevant Victorian demand: five impressions for victoria public holiday and four for maximise annual leave 2027 victoria. That is direction, not proof of a mature search opportunity. The response was therefore narrow: clarify the existing Victoria public-holidays page and the national 2027 rankings page rather than create a family of near-duplicate pages.

The public record behind the local example was checked again before release. Business Victoria and the Fair Work Ombudsman list Melbourne Cup Day on Tuesday 2 November 2027. The state page now explains the useful bridge without overstating it: where the holiday applies, booking Monday 1 November joins the weekend to Cup Day for four days off using one annual-leave day. A non-metro council can arrange an alternate local holiday, and workplace approval still sits outside the calculator.

Keep attribution useful and bounded

The site already preserves only standard campaign fields in the analytics page location. It lowercases and sanitises values, caps them at 80 characters, and excludes every non-allowlisted query parameter. That permits a future owner-controlled distribution link to distinguish a platform and stable post identifier without collecting names, account handles, leave balances, locations, or shared-plan data.

The supporting distribution pack records three reusable, non-personal destinations and a review path at days 0, 14, 30 and 90. The success question is not raw traffic. It is whether Australian campaign sessions become engaged use, completed calculations, calendar exports, copied requests or created share links. Cloudflare request counts remain delivery observations, not a substitute for people or outcomes.

Repair the route that people will actually see

Mobile review exposed a 320-pixel overflow in the Victoria public-holiday table. The release did not treat a desktop rendering as sufficient. It introduced a new immutable stylesheet only for the two changed pages, with mobile table sizing that kept the Victoria table within the usable width. A new filename matters because a query-only CSS version cannot reliably invalidate long-lived edge caches.

The final checks ran at the source, mirror and public layers. The authoring release and Git-backed mirror matched across 100 files by SHA-256. Integrity checks covered 53 HTML documents, 31 canonical sitemap URLs, structured data, internal links, optimiser parity across all 16 state-year tables, and the UTM privacy contract. Public probes then checked both changed routes, the immutable stylesheet, and a deliberately missing route that returned the branded page with a genuine HTTP 404.

What was and was not distributed

The website release made the pages and the distribution copy available. It did not send outreach, publish on third-party services, buy promotion, or claim a result before a campaign exists. That separation is deliberate: a prepared message, a tagged destination, and a measurement plan are controls. They are not evidence of attention, authority, or conversion.

Readers can inspect the Victoria 2027 page, compare the national rankings, or use the calculator. The public Editorial Standards and Privacy Policy describe the source and data boundaries that frame those routes.

All Build Log entries →