Record checkpoints as Pass, Review or Blocker with a short finding and evidence reference. The history stays in local browser storage and can be exported when a job needs an auditable handoff.
A Pass should correspond to a specific requirement: correct trim, accepted proof, measured color tolerance, complete manifest or confirmed finishing setup. It should not mean “looks fine” unless visual approval is genuinely the requirement.
Review means a human decision is still needed or the evidence is ambiguous. Blocker means the job should not continue under the recorded assumptions. Separating those states prevents every uncertainty from being treated as either harmless or catastrophic.
The log stores text, timestamps and references—not the proof files themselves. Export important histories as JSON or CSV and keep the actual proofs, measurements and provider approvals in the project archive. Clearing site data can remove browser-local checkpoints.