# Site register

One register per site: who is on it, what tickets they hold, when each runs out — and the training matrix ready to hand to the auditor or the main contractor.

- Its page on this site: [Site register](https://kasq.uk/tools/site-register)
- In the app: [open Site register](https://app.kasq.uk/v3/#tool=strikes)

## In the office

Put the crew on it by hand or upload the list you already have — Excel, CSV, Word or PDF. Then drop each person's certificates on their card, a folder at a time: KASQ reads the course and the expiry date and shows you what it read; fix anything it got wrong. Sixty days before a ticket runs out it turns amber; when it runs out, red. The folder comes out whenever you want it: a training matrix as Excel, with the certificates themselves beside it. Strikes go in only if you tick the box that time; it is never ticked for you.

## On site

Print the code and hang it in the cabin. The crew scans it and reads the 3 Strikes board in their own language — what the rules are and where they stand. A site code, if you turn one on, keeps the board to the people you give it to.

## What it never does

A cell in a spreadsheet is a note about a certificate, not the certificate: KASQ shows the courses a training matrix carries but does not write them in. It never confirms a card with the scheme that issued it — 'read' and 'confirmed' are never the same word.

## What it counts

What one run counts against a plan's monthly questions is on [the tool's page](https://kasq.uk/tools/site-register) and in the [tools overview](https://kasq.uk/docs/product/tools.md), both written from the same table as the [plans page](https://kasq.uk/plans).