Assembling a Grant Application PDF Package Without Losing the Deadline
The portal closes at five, it is two thirty, and the application checklist has eleven required attachments. The narrative is written and the budget is approved, but the audited financials arrived as a scan from the accountant, the board roster is in a spreadsheet, the tax determination letter is a photograph someone took of a paper file, and the upload field accepts one document under ten megabytes. Grant deadlines are rarely lost on content quality. They are lost in the last ninety minutes of assembly.
Work from the funder's checklist as your literal table of contents, not from the order your files happen to sit in a folder. Convert what needs converting first: Excel to PDF for the board roster and budget tables so the grid survives, Word to PDF for the narrative so pagination is locked, and Image to PDF for that photographed determination letter, cropping it straight with crop first so it reads as a document rather than a snapshot. Then merge everything in checklist order and use organize to fix anything that landed out of sequence.
Reviewers skim under time pressure, so make the package navigable. Run page numbers across the merged file and put a simple contents page at the front listing each attachment with its starting page. If the funder wants a specific attachment uploaded separately as well as inside the package, use split to extract exactly those pages from the assembled master, which guarantees the standalone copy is identical to what is in the bundle rather than a slightly older draft from a different folder.
Size limits are the classic submission-day emergency. A package that includes scanned financials will balloon quickly, so run compress and check the result before uploading; text stays selectable so reviewers can still search terms like matching funds. If you are still over the limit after compression, the culprit is almost always a high-resolution scan, and rescanning that piece at 200 to 300 DPI usually solves what no compressor can. Name the final file so it stands alone in a reviewer's download folder, using the organization name, the program, and the year rather than final_v6.
A few limits worth planning around. There is no batch processing, so if you are submitting to five funders in one week, build one clean master package and then split or reorder per funder rather than rebuilding from scratch each time. Some funders request PDF/A archival format, which is not available here, so produce that from your word processor's export options if it is mandatory. There is also no metadata cleanup tool, so if authorship details matter to you, check them in your source application before exporting. Everything runs locally in the browser, which matters when a package contains donor lists or staff salary detail.