Tickets and Licences

The per-worker compliance wallet, with expiry chasing.

Tickets and Licences

What it is

One wallet for every ticket, licence and certification your people hold, white cards, high-risk licences, EWP, trade tickets, grouped by the person and sorted so whoever is closest to lapsing is at the top. It is what you reach for when a principal contractor asks at the gate, and what Base reads when it chases a renewal. The safety or compliance person keeps it.

Before you start

  • The Tickets & Licences module must be on for you (Settings → Team Modules). It is on by default for a new business.
  • Adding, verifying or removing a ticket needs the Tickets edit permission.
  • A ticket belongs to a worker by name. Crew from the Crew Roster and a subcontractor's workers can both hold them.
  • For renewals to be chased for you, turn on the Compliance Chaser pack in Automations.

How to

Add a ticket

  1. Press Add ticket.
  2. Type the Worker name and Ticket type (both required), and the Number, Issuer / RTO and expiry date if it has one. Blank means it does not expire.
  3. Press Save.

The ticket appears under its holder with an expiry badge: days left, green past 30 days, amber inside 30 and inside 7, red once expired.

Add a ticket from a photo

  1. In chat, attach a photo of the card or licence and say "add this to the wallet".
  2. Check what the assistant read and let it file it.

The ticket lands marked AI so you can see it was read from a photo rather than typed.

Verify a ticket

  1. Press Verify on a ticket you have sighted and checked.

It is marked verified with your name against it. The Unverified count at the top drops.

Find and print

  1. Type into the search to filter by worker, ticket type, number or issuer.
  2. Press Print snapshot for a printable compliance snapshot of the wallet as shown.

Remove a ticket

  1. Press the bin on the ticket and confirm.

What happens on its own

  • A daily sweep reads every expiry. When a ticket crosses 30 days out, then 7 days out, then expires, it raises an event once for each crossing. Entering a new expiry date after a renewal re-arms the sweep automatically.
  • With the Compliance Chaser pack on, the assistant acts on those events: it works out who holds the ticket, writes a renewal request saying what is needed and by when, and sends it by email or text (or queues it for your approval when auto-send is off). Expired items are escalated.
  • The counts at the top (Expired, ≤ 7 days, ≤ 30 days, Unverified) update as the wallet changes, and the page refreshes when the assistant or the sweep touches a ticket.

Things that surprise people

  • Without the Compliance Chaser pack this is a register, not a reminder. The sweep still records each crossing; nobody is told.
  • The same sweep also watches subcontractor insurances, licences and compliance documents recorded on their engagements. Those do not appear in this wallet.
  • A ticket with no expiry is never chased.
  • Verified means a person sighted it. Base does not check tickets against any register.
  • Removing a ticket is permanent; there is no archive.