A practical walkthrough

Make the record useful.

1. Replace the fictional sample site and date with your own inspection.
2. Edit the area and wording of each checkpoint.
3. Choose Not inspected, Meets expectations, Needs attention or Not applicable.
4. For Needs attention, describe the observation. Add a responsible-person label and target date if useful.
5. When resolved, keep Needs attention selected, check Finding resolved and add the resolution note. This preserves the original observation.
6. Preview the report, inspect its contents and download text or print to PDF.
7. Save locally and download a full backup for a durable copy.

Coverage is not a pass

The report counts reviewed applicable checkpoints separately from findings. All Not applicable means no applicable checkpoints; it does not certify that an inspection passed. A resolved finding remains a recorded finding.

Repeat without rewriting history

Enter the next inspection date and choose Repeat checklist. It copies the current wording into a new record and resets observations, states, names, notes and resolutions. Earlier records remain editable snapshots, not immutable audit logs.

Local records and limits

Keep up to 12 inspections with 30 checkpoints each. Save explicitly before leaving. Clearing browser data can remove saved records. Restore replaces the whole in-memory collection after confirmation; save again to retain it. Full ZIP backups may be up to 32 MB; older text-only JSON collections can also be restored.

Sharing

Reports exclude internal notes. Inspector and responsible-person names are optional and initially off. Public observations, target dates and resolution notes appear in reports, so review them before sharing. A responsible-person label sends no notification and grants no access.