Submission wayfinding
Start with where the file is going.
Choose a destination lane, declare the information the check actually needs, then review source-linked findings before you submit. A preflight checks the stated technical scope, not whether a destination will accept your file.
NIH grants
Common Forms and NIH attachments with the relevant submission context made explicit.
ROUTE 02CTGOVClinicalTrials.gov
Protocol and results checks for PDF, XML, and JSON submission records.
ROUTE 03CM/ECFFederal court filing
Technical PDF readiness with your court name and current local file-size limit.
ROUTE 04JOURNALJournal manuscript
One-credit checks for data availability, interests, funding, contributions, ethics or consent, and AI-use disclosure.
ROUTE 04BREPORTINGReporting signals
Three-credit manuscript signal checks for PRISMA 2020, CONSORT 2025, STROBE, and ARRIVE 2.0.
Evidence, not a black box.
Every returned finding names the condition, why it matters, what to do next, and the source supplied by the validator.
Destination, validator, profile, and court policy where applicable.
PASSFile structure, text extraction, and destination-specific checks are evaluated.
REVIEWOnly the destination or receiving authority can make this decision.
OUTSIDE SCOPEChoose precisely
Destination-first routing keeps a manuscript from being treated like a court filing or registry record.
Use the right access
An email-verified preview is limited. A paid key returns a readable HTML report, JSON report, and remaining credits where available.