Job & Site Register
The pack holds deep per-discipline logs - drying readings, stormwater inspections, chemical applications, injuries. This is the job those belong to: site, client, dates, what had to be permitted or notified before starting, who was on site and who signed it off at the end. On a regulated job the records are worth what the sign-off makes them, so a folder of readings with nobody's name at the end of it is the first thing queried. It asserts no permit requirement - it flags what YOU listed as needed with nothing recorded against it.
Your database
Fields
| Field | Type |
|---|---|
| Job number | text |
| Client | text |
| Site / address | text |
| Scope of work | text |
| State | select |
| Started | date |
| Finished | date |
| Permits / notifications needed | text |
| Obtained — reference and date | text |
| Who was on site | text |
| Records kept for this job | text |
| Signed off by, and when | 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.
Does it know which permits my work needs?
No. What must be notified, to whom and how far ahead is jurisdictional, differs per discipline and changes. You list what your job needs; the register tells you which of those you have nothing recorded against.