01 / Define the target

One row should represent one public surface

Store the exact URL, the neutral category of information involved, the responsible publisher, and the requested outcome. Separate a live source page from its search preview because the two may close on different dates.

Avoid pasting the exposed value into the tracker. The URL and a category such as contact detail, duplicate profile, or incorrect association are usually sufficient to manage the request.

02 / Record the handoff

Submission evidence should be compact and verifiable

Save the request date, case number, delivery receipt, and provider response window. If a verification email is required, record whether it was completed without preserving codes or identity documents.

A confirmation page proves receipt, not removal. Keep the status as submitted or processing until the public surface itself changes.

Working principle

Receipt, processing, source removal, and search refresh are four different states.

03 / Follow the clock

Use provider deadlines instead of random checks

Set the next review date from the stated service window. Follow up once the window has passed, quoting the case number and exact URL without retelling the entire history.

Escalate when the provider gives a route for escalation or when the response addresses a different page. Precision makes the unresolved question easy to identify.

04 / Verify closure

Check the source, preview, image, and copied surfaces separately

Open the URL while signed out, inspect the major search preview, and check whether images or derivative directories still expose the same category of information. These surfaces can update on different schedules.

Close the row only when the requested outcome is visible. If one derivative remains, create a new row for that surface rather than reopening a completed source request without evidence.

In practice

Read a request as a sequence of evidence

Consider a fictional directory correction. The publisher acknowledges the request, later reports completion, and its current page no longer contains the field. An older search preview still displays the former wording. These observations support different states.

A status is only as strong as its evidence
Evidence observedSupported stateStill unproven
Submission receiptRequest submittedReview or correction
AcknowledgmentRequest receivedPublic source changed
Completion messageProvider reports completionIndependent public verification
Current page reflects the changeSource change verifiedSearch previews and separate copies updated
Specific preview no longer shows old wordingThat search display checkedEvery query or other source is clear

Close the source task once its defined outcome is visible. Keep the remaining preview task attached to the same issue, with its own observation date and next action. Do not restart a successful source request merely because another layer has not changed.

The reverse distinction matters too: a missing search result does not demonstrate that the source is gone. Record what you actually checked, preserve the provider’s stated response window, and leave unresolved surfaces explicitly pending.

For the next layer, read how to diagnose a stale search preview.