PREPARING YOUR PACKAGE

Two documents.
Ten minutes of preparation, at most.

The panel needs less than you think, but what it gets shapes what it can tell you. This page covers the required uploads, the optional ones that measurably sharpen the review, the formats that parse cleanly, and when in your drafting cycle a run is worth spending.

REQUIRED

What a run cannot start without.

01Your proposal

The narrative you intend to submit. It need not be the final version: a mostly complete draft is enough. The panel reviews it as the proposal you would submit, so you hear what a real panel would raise while there is still time to fix it.

Put it all in one PDF. Only the project description is required; add the summary, references, letters, biosketches, current and pending support, budget documents, and facilities and equipment if you have them. Keep the cover page: the report's proposal facts (title, PI, amount, duration) are read from it. A required document you leave out is marked not verifiable, never a violation.
02The solicitation

The programme announcement, FOA, RFA, BAA, or call you are answering. This is what the panel judges you against — without it, the review has no rulebook and no criteria.

The agency PDF, unmodified, is what to upload. A link is not enough: the panel reads the document, not the web page.
OPTIONAL, BUT IT SHOWS

Four additions that change what the panel can say.

None are required. The budget, biosketches and letters go in the proposal PDF; prior reviews go in as a supporting PDF. Each closes a specific blind spot, named beside it.

Prior reviewer comments

The summary statement or panel summary from a previous submission of this work. The reviewers read it as background, so they know what an earlier panel raised and can see how this draft answers it.

Gives the panel the history of the work
Your budget and justification

The panel checks whether the money matches the science: effort that supports the aims, equipment the methods actually require, and years that line up with the timeline. A budget check also adds up the lines it can read and holds the budget to the call's ceiling, cost-sharing and indirect-cost rules, showing the figures behind each numerical flag.

Catches sums that don't add up and scope-to-budget mismatches
Biosketches for key personnel

Reviewers assess whether the team can do what the proposal promises. Without biosketches the panel can only judge the claim, not the evidence behind it.

Lets reviewers judge the team, not only the claim
Letters of support or collaboration

Where an aim depends on a partner site, a dataset, or a facility, a letter is the difference between an assertion and an arrangement.

Closes the most common structural weakness
FORMATS

What parses cleanly, and what does not.

FormatSupportNotes
PDF with selectable textBestPreserves structure, figures, and reference formatting. This is what agencies want anyway.
Scanned or image-only PDFDegradedThe reviewers see each page as an image, so a scan can be read, but quoting your sentences in the revisions needs a text layer. Export a text PDF instead.
DOCX, LaTeX source, ZIP archivesNot acceptedExport to PDF first. The panel judges the document a reviewer sees, not the source that produced it.
Password-protected filesNot supportedRemove protection before uploading. Files are encrypted at rest regardless, and deleted after the run.

The proposal and solicitation can be up to 15 MB each. As many as ten supporting documents can go alongside them, up to 5 MB each, and the whole run can be up to 20 MB and 200 pages, which is what the review models can read at once. If a document cannot be read, the run fails and is returned to your proposal automatically, so nothing is charged.

LEAVE IT OUT

Four things not to upload.

Human-subject data

Describe your clinical study in the narrative. Do not upload the patient records, identifiable datasets, or anything covered by a HIPAA obligation — we do not sign BAAs.

Export-controlled material

No ITAR, EAR-controlled, or CUI content. If your programme office has flagged the work, GrantPanel is not the right environment for it.

Another PI's proposal

Including one you are reviewing for an agency. Confidential peer-review material is not yours to process, and our acceptable-use policy prohibits it.

Full manuscripts and appendices

They dilute the reviewers' attention across text no panelist would read. Cite them instead — the reference audit handles the rest.

TIMING

Run it early enough to act on it.

Don't wait for the final version. One proposal includes three runs, so the first can be a mostly complete draft. Start about two months before your deadline: run 1 on the draft you have, run 2 after you fix the structural findings, and run 3 in the week before submission. Runs 2 and 3 read the revised proposal against what the earlier run found, so you see what moved.

A run four days out still catches compliance triggers, but a structural weakness found four days out is a weakness you submit with.

Before you start a run
Narrative is mostly complete; it need not be the final version
The solicitation is the current version for your deadline
Figures and their captions are in the document, not attached separately
References are included — the reference audit needs them
Every file is a PDF with selectable text, and none is password-protected
No human-subject data, CUI, or export-controlled content is in the package