Procedures and checklists

1. Build a draft from the process you know

Choose Build from notes, add a procedure title and paste one step per line. Each non-empty line becomes one step, in order. The builder keeps the original notes as a linked source and uses your wording for instructions. It does not invent missing instructions or call a language model.

You can also choose a local UTF-8 .txt or .md file in the notes dialog. Check its preview, then choose Use file notes to replace the notes field. Nothing is saved until you build the draft. The original file text and filename stay linked, including when you edit the imported notes. Files stay on your device; Markdown is read as plain text, without rendering links or fetching content.

1. Collect the handover files.
2. Check that the next owner can open the folder.

For this example, the builder creates two linked draft steps. You still need to add an owner or role, a purpose and a completion check for each step. For the second step, a possible check is: "The next owner confirms they can open the folder." Decide which steps are required and which need an evidence note. You can also create a blank procedure, edit and reorder steps, or add source notes manually.

2. Record a reviewed version

The draft readiness checklist counts required fields and lists what is missing. Choose Go to next missing field to focus the next incomplete field, including notes inside a collapsed source. Filled fields still need your accuracy review.

Use Review & save version after checking the title, owner, purpose, instructions and completion checks. Enter a reviewer name and a change note. The saved version freezes its source notes, step order and rules. Later draft edits leave earlier versions and their checklist runs unchanged. Comparisons identify changed fields, steps and order.

A reviewer name is self-entered, not an identity check or another person's approval. The app does not send a review request. Restoring a saved version to the draft asks for confirmation and replaces only the draft; saved versions and runs remain. Make a change before saving another version.

3. Run the saved checklist

Start a run from the version you want to follow and enter an operator name. Required steps must be marked done. An optional step may be skipped only with a reason; a step that requires evidence cannot be completed with an empty note. Editing a result's note returns that step to pending so you can check it again.

Once every step is resolved, Finish & lock run records completion. A completed run cannot be edited through the app; start another run to perform the procedure again. This lock is application behavior, not a verified signature or a tamper-proof audit trail.

4. Export the right record

Choose Download training guide on a saved version for a standalone HTML file. It contains that version, its review details and original source notes, excluding drafts and run records. Open it offline to read or print it in light or dark mode. It uses no scripts or external resources. Blank worksheet areas are for paper notes; the file does not save checklist results.

A saved version exports as Markdown with its source context. A run exports as CSV with its version, operator and step results. Print / PDF uses your browser's print controls for the selected guide or run. Markdown and CSV keep authored content literal and protect formula-like CSV cells, which can add an apostrophe to exported values.

These reports are not restorable workspace backups. Use Export backup to keep all procedures, drafts, source notes, saved versions and runs in one JSON file. Only a full workspace backup can be restored by this app.

What stays here

Procedures, versions and runs are stored in this browser profile with IndexedDB. Anyone using the same profile can read the workspace. Only the theme preference uses localStorage. There is no account login, cloud copy, automatic sync or app-provided encryption-at-rest guarantee.

The workflow makes no external data or model requests. Source references are plain text and are never fetched. Loading this site still requests its public files from the hosting service; following a MacL link opens another site. No procedure or report is sent to another person by the app.

Keep a backup before a change

Export before clearing browser data, changing devices, removing records or restoring a workspace. Browser storage can be unavailable, full or removed by the browser. Downloads contain readable source notes and run records; store and share them appropriately. Clearing this site's browser data does not delete files you previously downloaded or shared.

If saving fails or another tab saves first

Keep the affected tab open and export its current backup first. Unsaved edits may exist only in memory. A conflicting tab stops further edits until you use Reload saved; reloading discards that tab's unsaved state and returns to the last successful save. If storage is unavailable, the current session remains exportable, but it is not saved by closing or refreshing the tab.

Restore checks the backup's structure and limits, then asks before replacing the entire workspace. You can cancel while a file is being read. Editing the workspace or opening another dialog during reading cancels the pending restore; choose the file again when ready. A malformed or oversized backup is rejected without replacing current records. Backups can be edited outside this app: validation does not authenticate reviewer names, operators, timestamps or source accuracy.

Up to 10 procedures; each can hold 50 steps, 20 text sources and 10 reviewed versions. The workspace supports 100 total runs and an 8 MB UTF-8 backup. Source notes allow 10,000 characters, step instructions 4,000, completion checks 1,000 and run notes 2,000. The notes builder accepts up to 50 non-empty lines, each at most 4,000 characters, within 10,000 characters total.

Reviewer and operator names are self-entered; timestamps use the device clock. These are working records, not authenticated approval workflows, compliance certification or tamper-proof evidence. Review your procedure before using it and keep the context behind each instruction.

Text-file import accepts UTF-8 .txt or .md files up to 40 KB within the notes-builder limits above. A UTF-8 encoding marker is removed; original text and line endings are retained. Invalid encoding, unsupported files and oversized notes reject without changing the notes or workspace. PDF, Word, screenshots, OCR, transcription, cloud collaboration, automatic drafting, subscriptions and payments are not implemented. Broader browser, native-device, screen-reader and long-document acceptance remains open. The current free workflow requires no provider credentials.

Return to the procedure workspace