Client & Job Register
The pack writes the estimate, the statement of work, the invoice and the late-payment demand. This is the thread connecting them: which job is at which stage, what was quoted, what was invoiced and what has actually been paid. The real problem for an independent worker was never writing the invoice - it is noticing in March that January's never landed, or that a finished job was never invoiced at all. The panel counts both, and says how many days past its date the oldest unpaid invoice is.
Your database
Fields
| Field | Type |
|---|---|
| Client | text |
| Job / project | text |
| Stage | select |
| Quoted on | date |
| Quoted amount | text |
| Delivered on | date |
| Invoice # | text |
| Invoiced on | date |
| Invoiced amount | text |
| Payment due (per your agreement) | date |
| Paid on | date |
| 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 total my income or assume payment terms?
Neither. Amounts are free text so any currency and any wording works, and a total computed here could disagree with the invoice you actually sent. Terms are whatever your agreement says. It counts documents and dates, which is where money actually goes missing.