Work Order Register
The pack inspects and writes up. This is the queue: who reported what and when, the priority in your own wording, who it was assigned to, the date you promised and whether it was done. The failure is never the inspection - it is the request that arrived by text message in March and was never assigned to anybody. The panel counts what is past the date you promised, what is open and assigned to nobody, and how long the oldest one has been sitting there.
Your database
Fields
| Field | Type |
|---|---|
| Work order # | text |
| Property / unit | text |
| What needs doing | text |
| Reported by, and how | text |
| Reported on | date |
| Priority (your wording) | text |
| State | select |
| Assigned to | text |
| Promised / target date | date |
| Completed on | date |
| Cost | 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 my response times?
No. Response times come from your contract, your jurisdiction's repair standards or your own policy, they differ, and they change. You record the date you promised and this counts against that.