The Request Ledger

Use result, action, status, ranking, and next step. The result identifies the public surface. The action records what was actually done. Status distinguishes a receipt from an outcome. Ranking captures visibility as an observed range. Next step prevents a pending item from becoming an open-ended worry.

A stable format makes different sources comparable without forcing unrelated details into one narrative.

Prefer visible states such as submitted, acknowledged, source changed, stale display, denied with reason, or verified absent. Avoid labels like handled or fixed when the public result has not been checked.

• Submitted means the request left your control.
• Acknowledged means a system or person received it.
• Complete means the intended public outcome was independently verified.

A case number and exact URL usually carry more operational value than a folder of full-page screenshots. Keep a narrow capture only when the visible wording is likely to change or the appeal requires proof. Do not repeat sensitive details in filenames, notes, and status fields merely because they appeared once on the source.

Write the next review date, the response window, or the exact condition that unlocks another action. A useful next step might be to confirm the source after a stated interval or request a stale-result refresh once removal is visible. It should not be a vague instruction to keep checking.