How we verify and date specifications
A specification is useful only when a reader can see where it came from, when it was checked, and where uncertainty remains.
Source order
We first look for the responsible authority's live application instructions, published notice, help page, or official PDF. We record secondary guidance only when a primary page is unavailable or does not state the value. A secondary record is not relabelled as official simply because it appears plausible or is widely repeated.
What is compared
For document photos, reviewers compare the recorded dimensions, file size, file format, background instruction, and any published framing rule with the cited source. For exam uploads, the comparison can also include signature dimensions, KB bands, and name/date requirements. Values not supported by the source should be removed, narrowed, or marked for review.
Dates and visible status
Verified date · source means a person compared the stored record with the linked source on that date. Source needs review means the record lacks a dated primary-source confirmation. Neither label predicts what an application portal will do later.
A guide's “last reviewed” date refers to its editorial review. A specification's verification date refers to the cited requirements record. They may differ because a guide can be edited without changing the underlying numbers.
Changes and conflicting sources
When a portal changes, the registry is updated first so pages and tools that read that record receive the same value. Where two current official sources conflict, we disclose the conflict and direct users to the application flow they are actually using. We do not invent a compromise value.
Found a newer source? Report outdated information.