How a check works
- Identify the validator. A file is not checked against a generic, hidden rule set.
- Apply applicable rules. The selected ruleset and profile determine available validations.
- Record evidence. Findings identify a state and source reference when the rule is source-backed.
- Present a limited decision. The outcome covers only the checks that ran, for that file and configuration.
Source categories
- Official submission instructions
Public instructions, form guidance, and documented requirements published by the relevant program or destination.
- Official technical specifications
Published file, schema, PDF, package, or submission-portal documentation used to support technical checks.
- Selected organization profile
A clearly identified profile configured for the check. A profile is shown as a profile, not represented as an external authority.
- Document integrity observations
Direct observations from the submitted file, such as whether a PDF can be read or an expected package entry is present.
What this cannot guarantee
No preflight can promise approval or acceptance. External systems can change, an instruction may be interpreted differently, and reviewers exercise discretion. Submission Preflight does not submit on your behalf, give legal, medical, grant, regulatory, or professional advice, or determine eligibility, merit, completeness beyond checked rules, or outcome.
Always read the destination’s current instructions and confirm that the validator and profile fit the actual submission. A pass means no blocking condition was found in the checks that ran, not that every possible issue has been ruled out.
Rule updates
Requirements can change. The service exposes current validator metadata and records the active ruleset where available. For high-stakes or time-sensitive work, review the original source and re-run after material changes.