Private transaction checklist and status planner
Use this checklist to keep task ownership, manually entered dates, status and confirmation notes together on one browser. It validates the fields before saving or importing and can export the same information as JSON or CSV. It does not calculate legal deadlines, interpret a contract or decide whether a transaction is ready to close.
Plan the next task
Start with a short, non-identifying transaction label. Add a task title, an owner label and a calendar date only when you have a confirmed date to record. Use the source note for the role or document reference that explains the task. Keep contracts, personal information, account numbers and wiring details in the approved systems your team uses for them.
The date field stores calendar text in year-month-day order. It rejects an impossible day instead of silently moving it into another month. It has no state default, holiday calendar or deadline formula. A licensed professional decides which dates and obligations apply; the planner only preserves what you enter.
Use status as a communication field
The available statuses are not started, requested, received, reviewed and completed. Agree with your team what evidence is needed for each transition. Receiving a file does not establish that it is correct, and selecting reviewed does not perform a review. The workflow guide explains how to keep those handoffs distinct.
Editing replaces a saved value; this is not an activity archive. Keep a dated export if you need an earlier copy. A status change preserves an unsaved transaction-label edit without treating that text as saved.
Keep a copy you can inspect
Export JSON for the original structured text. CSV is available once you have a task; it prefixes text cells so a spreadsheet does not treat formula-like entries as formulas. This planner recognizes that encoding when importing its own CSV. Do not assume that another application will reconstruct the same fields or protection.
Paste an exported JSON or CSV file’s text into the import area. Validation happens first, and replacing a non-empty checklist requires confirmation. Invalid dates, unsupported fields and malformed files leave saved data unchanged. The date portability reference explains why preserving calendar text is different from converting it into a timestamp.
Understand what stays on the browser
Saved tasks use browser storage, with no account or device synchronization. Tabs on the same browser load each other’s changes and clearing. Before writing, the planner rereads storage; a changed copy stops that action and loads the newer state. Someone using the browser may read saved tasks; this is not a secure vault.
Unreadable saved text makes the planner read-only. Download the raw text to keep a copy, or explicitly clear it before editing. Preparing that download enables editing but leaves the original stored text intact until a later save or clear.
Use the explicit confirmation and clear control to remove this planner’s saved checklist. It does not delete downloaded files. Browser cleanup can erase saved tasks. The print control uses the browser’s print workflow; native print preview and paper output were not checked. With scripts blocked, editing is disabled and no saved tasks are read.
Not covered on this page
- Legal deadlines, state rules, contract interpretation or closing approval.
- Document storage, signatures, permissions enforcement or audit history.
- Team synchronization, secure-vault claims or native print-output verification.
Sources
This original tool’s behavior is supported by its published measurement records and fictional examples. It makes no claim about a third-party transaction service.
How we test: methodology. Found a mistake? Corrections.