What's changed in Unpaid Wages Claim

Versions that passed Trilly's checks, newest first.

1. Version 2.0.2 · 25 Oct 2026
   • A shift longer than 24 hours, a negative or enormous number of hours, or a date in the far future or distant past now gets a plain message naming the row, instead of the calculation hanging your computer.
   • A shift before your city's rows in the rate table is named in a note (the state or federal minimum was used, and a city's rate is usually higher), where before it was priced at the state rate without saying.
   • The demand letter says the shift table is attached only when you've said yes to the table file; otherwise it offers to send the working and the answer offers you the table.
   • Since 2.0.1, the calculation script asks the AI to name which of five options (daily hours, leave year, holiday entitlement, vacation hours, the shift table file) came from you, and refuses them otherwise. That's a check on what the AI reports, not proof.
   • A very large or non-ASCII pay period, or a pay period start more than ten years from your first shift, now gets a plain message instead of an error or a very long wait.
   • The "how many days before the last safe date to file" setting is now a reminder before the last safe date, a backstop, since filing follows the day after the reply date; and an edge-case line about job sites, which only concerned job applications, is gone.
2. Version 2.0.1 · 25 Oct 2026

   A pay period of 0 days, or a payslip whose period ends before it starts, now gets a plain message instead of the calculation never finishing.

   What else changed in version 2.0.1

   • A US shift dated before your state or city rates in the table is named in a note, since only the federal minimum could be used for it.
   • A casual retail shift over 9 hours in Australia now says plainly that its overtime isn't priced, and the UK count says when time clocked in before a shift counts as work, and how to turn that off.
   • The pay-by date in a demand falls on a working day, and the claim is filed straight after it passes unpaid, with the reminder before the last safe date kept only as a backstop.
   • The versions you paste in follow the method step by step, since a pasted copy has no script.
   • Since 2.0.0, "How you'd like things done" asks how the claim form is filled in (fill it in for me, a copy-ready sheet or step-by-step help) instead of whether to keep your career file up to date; your career file still changes only after your yes.
3. Version 2.0.0 · 25 Oct 2026

   Starts with the count from your own payslips and rosters: you're owed this much over this many shifts, ranked by cause, each with a shift, the rate in force that day and the working.

   What else changed in version 2.0.0

   • Prices every shift with a calculation script that works offline, at the rate in force on its own day; for apps that can't run code, the same method is written out step by step.
   • Adds casual loading to penalty rates the right way, checks unpaid time and uniform deductions against the minimum wage, puts overtime on the regular rate, and repays minimum wage arrears at today's rate where the rules say so.
   • Counts each time limit from the right day, including a series of deductions and a time limit that changed this year.
   • Your browser helper can fill in the labour agency's claim form and stop before Submit; with Gmail connected it finds your payslip emails, and with Google Calendar it adds each reminder after your yes.

   This update asks for more Now runs code on your computer; Uses a new tool: Email; Now takes actions in your accounts; Can read a new connected app: Email; Can use a new connected app and create things in it: Calendar; Now uses a browser helper on websites.

4. Version 1.0.0 · 22 Oct 2026

An update that needs more access than yours waits for your yes.

When a skill updates · Follow changes in a feed reader

Feedback and fixes