Why track when tests are due?
Every test that comes due again is a job that books itself.
- For
- Remind owners when a device is due a test, and fill your diary.
- When
- After every test you do
Try it
100 devices tested every 12 months: 9 come due each month.
Due a month = devices on your list ÷ months between tests, rounded up.
Write the next due date on every test.
Worked out
| Devices | Every 6 months | Every 12 months | Every 24 months |
|---|---|---|---|
| 50 | 9 | 5 | 3 |
| 100 | 17 | 9 | 5 |
| 200 | 34 | 17 | 9 |
| 400 | 67 | 34 | 17 |
Easy to get wrong
- No due date on the certificate.
- A reminder a week before, too late.
- The list lost with an old phone.
- Waiting for them to call you.
The tool for it
Questions
Which devices need a test?
It depends on the device and the place. Check the rule where you work.
How often are they tested?
It’s set for each kind of device; type in the gap. Check the rule where you work.
When do I send the reminder?
About a month before it’s due, so they can book you.
What goes on a test certificate?
The device, where it is, the result, the date and the next due date.
Who keeps the certificate?
Give the owner a copy and keep one with the job.
What if it fails?
Write down why, quote the fix, and test again after.
Can I remind them by text?
Yes, with the device, the date it’s due and how to book.