Certificate & Equipment Register
The certificates, tests and inspections a site has to be able to produce on request - equipment, competence, insurance, permits - in one register with the expiry dates you entered. The panel counts what has already lapsed and what falls due inside the window you choose, so the answer to 'is anything out of date?' is a number rather than an afternoon with a filing cabinet. It holds no schedule of its own: how often a thing must be re-certified is set by your jurisdiction, your insurer or the equipment maker, so the next-due date is the one you record.
Your database
Fields
| Field | Type |
|---|---|
| Item / person | text |
| Type | select |
| Serial / certificate # | text |
| Location | text |
| Issued by | text |
| Issued | date |
| Expires / next due | date |
| Where the certificate is kept | text |
| Notes | text |
Frequently asked
Where is this stored?
Only on this device, in your browser. Nothing is uploaded and there is no account. Export to CSV or JSON to back it up, hand it to an auditor, or move it to another machine.
Does it know my deadlines and required frequencies?
No, and that is deliberate. Inspection intervals, retention periods and review cadences are set by your standard, your jurisdiction, your certifier or your own procedure, and they change. This runs offline and cannot know if one changed last month, so it never asserts one. You enter the dates that apply to you and it does the arithmetic on those.
Will it tell me how often something needs recertifying?
No, and anything that claims to while running offline is guessing. Frequencies are set by your jurisdiction, your insurer or the manufacturer and they change. You enter the due date that applies; the register tracks it and tells you what has passed.