Non-ProfitFree
Grants.gov Submission Rules and Pre-Check
Grants.gov permits characters in a filename that the funding agency's own rules do not, so a validated package can still be withdrawn.
Two authorities govern one upload and their rules disagree. Grants.gov permits an ampersand and a semicolon in an attachment filename. NIH's own instructions omit both, cap filenames at 50 characters including spaces, and require every filename in an application to be unique. In the worked example 23 attachments carry 11 filename defects. The portal's character rule stops two of them. The agency's rules stop eleven, so nine files clear submission and fail afterwards. Neither list is wrong, but only one of them decides whether you get funded.
Filenames are the visible half. Nine of the 23 are layered PDFs, six carrying fillable fields and three an inserted signature, which agency systems require flattened and no portal validation inspects. Three more were attached through the reader's own pane instead of the form's button, so they appear in the form and transmit nothing, and two of those sit on a mandatory form. That is 23 defects across 17 files, and the portal can see two.
Then the fixes get sorted by who has to make them. Twenty of the 23 cost minutes at the keyboard. Three need a signature re-executed and two of those signers are outside the organisation, which sets your real lead time. Pull the NOFO's requirements with a requirements matrix, and size the narrative against its published weights in the grant proposal pack. Anything the notice asks for that you cannot deliver belongs in an exceptions and risk note beforehand. If it comes back a decline, the declined proposal review reads it against the funder's criteria.
Both rule sets are published, and nobody reads them side by side
Grants.gov lists the characters permitted in an attachment name and includes the ampersand and the semicolon, warning that files outside the list may cause the entire application to be rejected. NIH publishes its own list for the same upload, omits both characters, and tells applicants to avoid the ampersand because it needs escaping. It then adds rules the portal has no view of: descriptive filenames of 50 characters or less including spaces, unique across the application, no double spaces, and nothing before the extension.
The stricter rules are the ones with teeth, and they are enforced after the timestamp is set. NIH states plainly that failure to follow its attachment requirements may lead to errors on submission or withdrawal of the application from funding consideration. A portal status of validated is a statement about the portal. It is not a statement about the agency that reads the package, and the gap between those two facts is where a year of work goes, quietly, several days after the deadline has closed.
The third class of defect is invisible to everybody until the agency asks where a document went. Grants.gov is explicit that attachments must be added through the form's own button, because using the reader's built-in attachment functions will cause errors in the submission and the attachments will not actually transmit. The file is visible in the form on your screen and absent from what the agency receives. Two of the three affected files here sit on a mandatory form, which is a completeness failure rather than a scoring one.
How it works
Send the notice
The funding opportunity notice and whichever appendix holds the attachment and formatting instructions.
Send the package
Every attachment with the filename it currently has, plus the forms in your workspace.
Get both verdicts
What the portal will stop, and what it will pass and the agency will later reject.
Fix in dependency order
Keyboard fixes now, signature fixes started immediately, since those are the ones with a queue.
What you get
- Every filename checked against the portal's character list and the agency's stricter one
- The files that clear submission and fail afterwards, named and counted separately
- Layered PDFs found before submission, split by whether flattening breaks a signature
- Each attachment matched to the form and slot the notice actually expects it on
- Fixes ordered by who has to make them, so the chasing starts on day one
- A rejection read back against the specific rule and authority that produced it
Common questions
The portal said my package was validated. Am I safe?
Validated means the portal accepted the transmission. It is not the funding agency's verdict on your filenames, your PDFs or whether every attachment arrived. In the worked example the portal clears 21 of 23 attachments while the agency's own published rules clear 12, and the gap is checked several days after the deadline closes.
How can a filename get an application withdrawn?
Because two authorities publish rules for the same upload and only one of them decides funding. Grants.gov permits an ampersand and a semicolon. NIH omits both, caps filenames at 50 characters including spaces, and requires uniqueness across the application. Nine of the 23 files here satisfy the portal and breach the agency.
What is a layered PDF and why does it matter?
Any PDF carrying fillable fields, a text box, an inserted image or an electronic signature. Agency systems require these flattened into a single layer, and no portal validation checks it. Nine of these 23 are layered, six from an unflattened letter-of-support template. Three carry signatures, which is the class that costs days.
My attachments are visible in the form. Can they still be missing?
Yes, and this is the failure that convinces people the agency lost them. Attachments have to be added through the form's own button. Files added with the reader's built-in attachment tools display on your screen and never transmit. Three here, two of them on a mandatory form, which is a completeness failure.
Which fixes should I start first?
The ones that are not yours to make. Twenty of these 23 defects are renames, flattens and re-attachments that cost minutes. Three need a signature re-executed because flattening can invalidate one, and two of those signers sit at a partner clinic and a county department. Those three set your actual lead time.
Does this work for a foundation portal rather than a federal one?
Yes. Fluxx, Foundant and Submittable each enforce their own document-type tags, appendix consolidation and file-type limits, and each publishes them somewhere in the notice. The mechanism is the same: read the portal's rules and the funder's own instructions against your folder before the timestamp matters.
How do I prove what the agency actually received?
Download the submitted package back out of the workspace and open it. That is the only artifact that reflects what transmitted, rather than what your screen showed while you were uploading. It takes about four minutes and it is the step that catches an attachment that never left.
Grants.gov Submission Rules and Pre-Check
Fill in the form and your workspace opens with the work already underway.