Recheck by trigger, not by promise

The sheet will not tell you when it has gone stale. Instead of trusting the snapshot, recheck on a concrete trigger — a moment when you are about to rely on the row.

Trigger 1 — Before saving a candidate

Reopen the page and confirm the fields just before you commit a row as a candidate. What you save should match what the page shows now, not what it showed when the row was first written.

Trigger 2 — Before an off-site action

Recheck just before you prepare to leave the site and act on the listing. The last thing you see should be the current page, not a remembered label.

Trigger 3 — After waiting

Reopen the page again after time has passed. Recheck what changed, and keep what is still open as a question.

Frame noteThese triggers are moments of action, not schedules. The point is to recheck when you are about to rely on the row.
ΔOpen item: has a row been relied on without rechecking, because the sheet was assumed to still be accurate?

A worked trigger

  1. Before saving: the page is reopened and the six fields are re-read.
  2. Before acting: the page is rechecked one more time before the off-site step.
  3. After waiting: the page is reopened later and changes are recorded.

Illustrated version check — not live monitoring or a verified listing.

Continue your review

Next, understand the time gap with the snapshot vs current guide, and record changes with the listing change guide.

Browse Products