The ApplySpec approach
How we verify requirements
A useful check needs evidence and clear limits. A green measurement is not approval from an application portal.
Start with official sources
We use the authority's application portal, notices, brochures and upload instructions. Each recorded rule includes its official URL, document title, page or section reference and verification date. Third-party tools and search snippets are not authoritative requirements.
Keep cycles and versions separate
A requirement belongs to the named exam and application cycle. We do not carry it into another year without checking that year's sources. Verification dates describe a review, not continuous monitoring. Closed or stale records remain labelled with their cycle; check the official portal for current dates before applying.
Preserve conflicting instructions
When official sources disagree, we show the differing statements and their provenance. We do not silently choose a convenient value or turn an unresolved conflict into a pass. Updates require checking the relevant current notice or clarification and recording a new review date and version.
Mandatory limits and preferred guidance
An explicit mandatory format or pixel limit can be checked automatically. Recommended or preferred dimensions are guidance, not rejection thresholds. Personal preparation settings are separate from the authority's rules.
Manual and unknown checks
Face visibility, background, ink, authenticity, physical print size and document validity need human review. A checkbox acknowledges a task; it does not make it automatically pass. Unstated limits and ambiguous instructions remain unknown. Even passing all measurable checks does not guarantee acceptance.
KB and kB are not assumed byte counts
If an authority does not define whether KB or kB means 1,000 or 1,024 bytes, we retain its literal values and mark the byte convention unresolved. The tool can show exact bytes. Optional decimal-KB preparation targets are user choices, not an official size verdict.
Corrections and updates
Use the Contact page for current support availability and correction guidance. A useful correction identifies the ApplySpec page, rule and official source, without personal documents. After a source review, corrections should update the affected rule, provenance and tests together. We cannot promise an immediate response or detect every authority update.