Show the working. Keep it reviewable.

RooBucks is operated and maintained by the RooBucks team. The team is responsible for selecting sources, defining calculator scope, implementing formulas, writing explanations, maintaining tests and reviewing updates.

External professional review is not implied. A calculator or policy has received independent professional review only when its page says so explicitly. Material legal and regulatory wording remains subject to the launch review described in the General Information and Calculator Disclaimer.

RooBucks uses the highest suitable source available for each claim, rate or rule. A lower-ranked source should not override a higher-ranked source without a documented reason.

1. 1

   Legislation and official government material

   Acts, regulations, regulator guidance, tax schedules, revenue-office rules and official calculators.

2. 2

   Official standards and primary datasets

   Standards bodies, central banks, public statistical agencies and original technical specifications.

3. 3

   Authoritative specialist sources

   Recognised industry, academic or professional material where no suitable primary source exists.

4. 4

   Provider information and market examples

   Public product terms, quotes and examples used only for their stated purpose and date.

5. 5

   Editable assumptions

   Clearly labelled example values that users can replace with figures relevant to their situation.

Source links should appear close to the assumption or limitation they support. A source is recorded with the applicable date or period where timing matters. Linking to a source does not mean it endorses RooBucks.

A calculator begins with a defined user question, inputs, outputs, formula, units, inclusions, exclusions and failure states. RooBucks uses the simplest model that answers the stated question without creating false precision.

Core calculation logic is kept separate from the interface where practical so it can be tested directly. Values are calculated at useful precision and normally rounded only for display. Validation rejects missing, impossible or unsupported inputs instead of silently inventing a result.

Default values are editable examples, not claims about a typical person, market price or expected future outcome. Projections state the assumptions that remain constant and identify material matters they leave out.

Depending on the calculator's risk and complexity, verification includes:

• unit tests for formulas, thresholds, rounding and invalid inputs;
• boundary tests immediately below, at and above regulated thresholds;
• browser tests for live interaction, errors, reset behaviour and result presentation;
• desktop and mobile viewport checks, including narrow-screen overflow;
• linting, type checking and a production static build; and
• dated model notes for complex calculators and external services.

Automated tests protect known behaviour but cannot prove that a policy interpretation is correct. High-impact calculators also require documented comparison with official or independent reference results. That manual release-check matrix is a separate launch-readiness task and is not yet represented as complete.

A second reviewer should verify source links and effective dates for an annual tax-year rollover and other material regulated-rule changes. Legal wording and regulatory implications require appropriately qualified review.

Date-sensitive configurations are versioned rather than silently overwriting prior periods. Australian tax-year updates add a new immutable configuration, retain earlier supported years, add tests for changed thresholds and move the current-year setting only after the sources have been checked.

An automated validation fails when the configured tax year has not rolled forward after 1 July. The annual review also covers income-tax brackets, Medicare settings, HELP thresholds, offsets, super guarantee rates and contribution caps.

Other regulated calculators record their supported period or source-check date where available. A meaningful last-reviewed date should change only when the formula, assumptions, sources or substantive explanation have actually been reviewed—not merely because the site was rebuilt.

RooBucks writes in plain Australian English and answers the user's question before adding background detail. Content should distinguish facts, assumptions, examples, estimates and opinions; avoid unexplained jargon; and place important limitations close to the relevant result.

Pages should not promise certainty, disguise an estimate as an official determination, manufacture testimonials or ratings, or add filler for search engines. Titles, descriptions and structured data must accurately describe the visible tool. Material claims should be specific, sourced and maintainable.

A useful report identifies the page, inputs, actual result, expected result, applicable date and supporting source. Do not send sensitive personal information. The Contact page currently contains a pre-launch placeholder address that must be replaced with a monitored inbox before launch.

RooBucks aims to review reports within five business days once that inbox is active. Potential issues are triaged by their effect on user decisions, breadth, regulatory sensitivity and likelihood. The review should reproduce the issue, check the source and applicable period, and determine whether the formula, copy, assumptions or scope need correction.

A confirmed calculation bug should be fixed at its source and receive a regression test. Relevant explanations, source links, review dates and known limitations should be updated with it. If a safe correction cannot be made promptly, the affected feature should be clearly limited or withdrawn until it can be trusted.

RooBucks currently has no advertising or affiliate tracking. If commercial links are introduced, they must be clearly disclosed near the link. A commission must not change a formula, hide a relevant alternative or determine an undisclosed ranking. Calculators must remain useful without following a commercial link.

This policy will be updated when the source, testing, review, correction or commercial processes materially change. The visible review date will be updated at the same time.