Build Log
A Useful Audit Changes the Release
An audit has value when it changes the product in response to evidence. Today’s review converted a focused set of observed defects into release work, while keeping the remaining checks explicit.
Start with the observed system
The review checked 52 public HTML routes, 31 sitemap URLs, their extensionless apex canonicals, a missing-route response, the Queensland calculator flow, and the flagship 2027 rankings article. Those checks established that the published structure, core calculator flow, and primary information pages were working before any repair was proposed.
The point was not to produce a long list of possible improvements. It was to separate faults that could be reproduced from ideas that needed more evidence. That kept the response focused on the things the release could actually correct: moved official sources, accessible controls, readable supporting copy, mobile navigation behaviour, and meaningful aggregate outcome signals.
Repair the defects, not the story
Two official-source links were updated after the review found that the former Western Australian page returned an error and the ACT page had moved. The repaired destinations stay attached to the calculator’s source material, so readers can follow the same public record used by the product.
The school-holidays option now has an accessible name and description. Supporting text was brought into the shared contrast treatment, inline links are visibly underlined, and the mobile menu was changed to a full overlay rather than leaving the page’s call to action visible beneath it. These are small implementation changes, but they reduce avoidable friction for real visitors.
The release also records calculation completion, calendar export, print, leave-request copy, and share-link creation as aggregate events. Those events deliberately exclude a visitor’s state, leave balance, selected strategy, and generated plan. Measurement should help assess whether the tool is useful without turning a personal leave plan into analytics data.
Keep the next checks visible
A repaired release is not proof of every quality claim. The audit remains a record of a point in time: automated checks and screenshots do not replace later keyboard, screen-reader, current-source, or field-data checks. The project keeps those limits in the Editorial Standards instead of hiding them behind a passing score.
The practical result is a narrower and more useful maintenance loop: inspect the live system, correct reproducible defects, retest the changed routes, and wait for enough new evidence before making a broader content decision. Readers can see the repaired Western Australia source path, use the calculator, or compare the current 2027 rankings.