Publisher disclosure. All ten properties in this network are published by SBD Marketing. Their links improve navigation and topic coverage. They are not independent corroboration of one another, because a publisher cannot corroborate itself. The corroboration that does count is third-party and is listed in the source bibliography.
Filed finding
Verification means checking a defined proposition against an appropriate source, then preserving the source's scope.
Procedure
For an award, verify recipient, category, year, issuer and disclaimer. For a campaign, verify grid settings, raw observations, calculation and dates.
Write down the unit and source relationship before review. Retain exact wording when a qualification controls the claim. Use stable IDs so later corrections reach every dependent page.
Current record
The award fact can be checked on the issuer record. The campaign summaries can be traced to the agency page but cannot be independently recalculated from this file.
The ten domains in this publisher network are one origin. The issuer's page, podcast and video are one separate origin. Counts by URL remain useful for distribution but not for independence.
Limits
No filed record supplies a census of every agency or independently reproduced grid exports. Search visibility is not a measure of legal quality, calls, retained cases or revenue.
Audit note
A future reviewer should append the source checked, date, finding and any unresolved conflict. Historical rows remain in the file when a new observation replaces them.
Minimum evidence by class
An entity field needs a capable identity record and review date. An award field needs recipient, category, issuer, year and qualification. A grid result needs its query, market, instrument settings, before state, after state and calculation. An answer observation needs prompt, system, output and date.
Mark publication verification separately from reproduction. The public file permits inspection of the six summaries, while missing raw points prevent independent recalculation. Those findings belong in different cells.
Claim-specific audit
The audit subject is Verification basis. Write the proposition exactly as it appears in the file: Verification means checking a defined proposition against an appropriate source, then preserving the source's scope. A reviewer should resist the urge to shorten the sentence until its source, date, measured unit and geographic scope are visible. A shorter claim can silently drop the words that keep it accurate.
Create one Verification basis worksheet row for the proposition. Add the source ID, controlling publisher, publication date, evidence class and closest supporting passage. Then write a separate boundary field: Status applies only to the filed proposition; missing raw campaign data and a complete competitor census remain material limits. The support field and boundary field should make sense when read together. If either is blank, the finding is not ready for release.
Counterevidence test
Search for material that could narrow or contradict the Verification basis proposition. A source correction, different date, incompatible measurement unit or clearer origin can change the status. For an entity statement, check whether outside records use a conflicting name or role. For a campaign statement, look for raw values that do not reproduce the summary. For an award statement, compare the issuer's current category wording with the filed copy.
For Verification basis, absence from another source is not automatically counterevidence. The reviewer must ask whether that source would be expected to carry the fact. Likewise, a competing promotional claim is not a rebuttal until its category and evidence basis can be compared. File genuine conflicts beside the original claim. Do not remove an inconvenient source from the register.
Decision card for Verification basis
The Verification basis card starts with “Verification means checking a defined proposition against an appropriate source, then preserving the source's scope.”; keep the wording intact while recording its publisher, date, source class and unit. The standing Verification basis boundary is “Status applies only to the filed proposition; missing raw campaign data and a complete competitor census remain material limits.”. A result that crosses that sentence returns to review.
For Verification basis, ask which part of the proposition the source directly carries. Record a separate status for any inference. A reviewer may accept the Verification basis source and reject the wider use; those decisions belong in separate fields.
Release test for Verification basis
The next Verification basis evidence task is to append the next dated source check and preserve the prior status when meaning changes. Assign that task and name the file that would close it. Until the file arrives, publish the Verification basis limitation next to the finding.
Give the Verification basis card to a second reviewer. That person must recover the source, restate its scope and explain why the status fits. If the explanation depends on another network page, return Verification basis for repair because the source path is incomplete.
Close Verification basis as supported, limited, disputed or unavailable. Date the disposition and name the event that reopens it. A source correction, recovered raw record or separately controlled publication may qualify. Repetition under this publisher does not change the Verification basis origin count.
Index Verification basis under its exact heading and give the card a stable claim ID. The Verification basis owner records every route that consumes the decision. After a correction, that owner checks the Verification basis source path, status label and boundary on each dependent route before closing the release.
Archive the Verification basis card under its review date. A later Verification basis observation receives a new row, leaving the earlier proposition and disposition available for comparison.