A good verification note is short enough to use and detailed enough to reproduce. It should tell a reader what was checked, when it was checked and where the evidence stops.
Begin with the issuer and document title. “PAGCOR list” is too vague if the agency publishes separate records for Gaming System Administrators and licensed casinos. Identify which file you used. Next, copy the document’s own “as of” date, then add the retrieval date separately. The relevant PAGCOR lists were accessed on 11 November 2026 but marked as of 29 October 2026. Keeping both dates prevents a reader from mistaking file access for a live update.
Record the exact row. Include the legal entity, brand, any listed product category and the domain string as printed. Do not normalize away a www prefix or replace one suffix with another. If the website redirects, record the initial and final hostnames separately. If an entry appears in a different list or under another entity, do not borrow it.
Consider a hypothetical correction note: an earlier article said a domain appeared in the GSA list, but the linked page actually concerned licensed casinos. Preserve the earlier wording, identify the corrected list category, and explain whether the underlying entity match changed. This shows the consequence of the correction rather than hiding it behind a refreshed date.
Add the source location: page number or row number when available, exact URL, and the time when the source was accessed. For a quotation, preserve enough surrounding context to avoid changing the statement’s meaning. If the source is a reproduction of an Act, say so. If a webpage was temporarily unavailable, report that access limitation rather than treating the error page as substantive evidence.
Then list checks not performed. Examples include current status after the snapshot, certificate expiry, security-seal serial verification, redirect-chain review, later advisories, or the classification of an independent publisher. These are not signs of failure; they tell the reader which questions remain open. Avoid generic certainty labels that hide those boundaries.
Finally, separate fact from interpretation. “The hostname is printed in the dated list” is a documented fact. “This proves every associated product is authorized” is a broader interpretation and is not established by that fact alone. Similarly, “I did not locate this spelling in the files reviewed” is an honest search result; “the entity does not exist” is a much larger claim.
A reusable note might read: “Issuer/document: PAGCOR GSA list; snapshot date: 29 October 2026; retrieved: 11 November 2026; row: PODEC / NuSTAR; exact hostname: nustargame.ph; result: exact printed match; not checked: live certificate, later changes, third-party publisher permissions.” That format gives readers enough context to repeat the check without implying more than it found.
A transparent evidence note is not legal advice or a guarantee. It is a map from a claim to its source, date and limits. When a later review is needed, the same fields make it easy to identify what must be refreshed.