Filing & Service Register
The pack drafts the documents. This holds the procedural spine that decides whether they count: what was filed and when, how it was served and on whom, and whether the proof of service ever went back to the court. A self-represented litigant loses on that chain far more often than on the wording - a case can be thrown out because the papers were posted by the wrong person. It asserts no service rule, because who may serve and how is set by your court; it shows you which rows are blank.
Your database
Fields
| Field | Type |
|---|---|
| Document | text |
| Case / docket number | text |
| Stage | select |
| Filed on | date |
| How filed (in person, mail, e-filing) | text |
| Fee paid / waiver | text |
| Served on whom | text |
| How it was served, and by whom | text |
| Served on (date) | date |
| Proof of service filed on | date |
| Next court date / deadline | 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 know how I am allowed to serve papers?
No. Who may serve, by what method, in what time, and what proof the clerk requires are set by your court and jurisdiction, differ per document and change. Ask the clerk - they answer this question all day - and record here what you did.