Skip to content

METHODOLOGY

How the calculator turns a rule table into a date.

A useful legal-adjacent tool should make its assumptions visible. If a result depends on a fact the calculator did not ask for, the correct product behaviour is to request that fact or return “needs official check”—not silently invent an answer.

On this page

1. You answer the facts 2. The engine selects a rule 3. Date logic is applied 4. The result exposes the rule and source 5. Ambiguous cases stop instead of guessing

1. You answer the facts

The tool asks only for facts used by the selected state pathway: role, agreement, reason, notice date, service and an optional proposed date.

2. The engine selects a rule

Versioned data matches the jurisdiction, actor, agreement type, ground and rule effective period.

3. Date logic is applied

Service is resolved first, then clear days, calendar days, weeks or months are counted with any verified adjustment.

4. The result exposes the rule and source

Every calculated result includes its rule ID, source authority and last-verified date.

5. Ambiguous cases stop instead of guessing

Partial, special or unsupported pathways return an official-check state.

Sample versioned rule

{
  "id": "qld-form13-without-grounds-2026",
  "jurisdiction": "QLD",
  "actor": "tenant",
  "form": "Form 13",
  "minimumPeriod": { "value": 14, "unit": "days", "counting": "clear_days" },
  "fixedTermConstraint": "later_of_period_or_agreement_end",
  "source": "Queensland Residential Tenancies Authority",
  "verifiedAt": "2026-09-07"
}