How to Get Grant DS1 Checklist: Your Step-by-Step Guide

A grant application is rarely just a form and a narrative — it is a package. Alongside your written answers, funders expect a set of supporting documents, and assembling them is where many applicants run out of time. This step-by-step guide is a document-gathering checklist for a grant application (the DS1 form and its companions), walking through exactly what to collect, in what order, and how to keep the whole package organized so nothing is missing when you submit.

Want expert help putting this into practice? GrantWinPro can guide you through it.

Start Early Because Documents Have Owners

The first principle of assembling an application package is that many required documents do not belong to you alone. Audited financials come from your accountant. A board resolution requires a board vote. Letters of support must be written and signed by partners on their own schedules. Because these depend on other people, they are the most likely to stall in the final days.

Begin gathering documents the moment you decide to apply, not the week before the deadline. Build a checklist immediately and assign each item an owner and a due date that falls comfortably before submission. A worked example: if you request a letter of support on the deadline day, you will not get it; requested three weeks out, it arrives with room to spare. Treating document collection as an early parallel track, rather than a last step, is the single most reliable way to submit a complete package.

Core Organizational Documents

Related: Grantwin - Complete Guide.

Most funders require a standard set of documents that describe your organization. Gather these once, keep them current, and reuse them across applications:

• Proof of nonprofit status — your IRS determination letter or local equivalent.
• Current operating budget — your whole-organization budget for the year.
• Recent financial statements — often audited, sometimes for the past two or three years.
• Board of directors list — with affiliations, kept up to date.
• Organizational chart — showing structure and key staff.

Maintain a folder of these standing documents so that each new application starts from a ready base. The only work then is confirming each is current and formatted to the funder's specification.

Project-Specific Documents

Beyond organizational paperwork, each application needs materials specific to the project you are proposing. These change with every opportunity and require fresh preparation. The centerpiece is your project budget — detailed, line-itemed, and matched to the narrative. Alongside it, funders often request a project timeline or work plan showing milestones and dates.

You may also need an evaluation plan describing how you will measure outcomes, a logic model diagramming your reasoning, and job descriptions for any funded positions. Prepare these in tandem with your narrative so they stay consistent with it. If your narrative promises 12 workshops, your timeline and budget must reflect exactly 12. Build these documents from the same underlying plan to keep the whole package internally coherent.

Give the project budget more time than any other project-specific document, because it is where inconsistencies do the most damage. Build it from real quotes and actual salary figures rather than estimates, and write a short budget narrative explaining how each line was calculated. Then reconcile it against the numbers scattered through the rest of your application — participants served, staff hired, sessions delivered — so a reviewer flipping between your narrative and your budget finds them telling the same story. A budget assembled last and in haste is the single most common source of the mismatches that undermine otherwise strong packages.

Letters and Partnership Documents

See also: Grantwin Tips and Strategies for Maximizing Success.

Letters of support and partnership agreements deserve special attention because they depend entirely on third parties and take the longest to secure. A strong letter of support does more than express general goodwill; it confirms a specific commitment — a partner agreeing to refer clients, share space, or contribute staff time.

To get useful letters, make it easy for your partners. Provide a brief outline of what the letter should address and the deadline you need it by, while letting the partner write in their own voice. Request letters at least three to four weeks ahead. Track each requested letter on your checklist and follow up politely as the deadline nears. If a funder specifies how many letters they want or from whom, honor that exactly rather than flooding the package with generic endorsements.

Format, Name, and Organize the Package

Once documents are gathered, prepare them to the funder's specifications before submission. Confirm each file is in the required format, within any size limit, and named according to the funder's conventions — many portals reject files that do not follow the naming rules. Convert documents to the requested file type rather than assuming the portal will do it for you.

Organize the package so it maps cleanly to the application's requirements list. A simple approach is to keep a single folder per application with subfolders for organizational documents, project documents, and letters, plus a master checklist showing the status of each item. This organization pays off during the final review, when you verify that every required attachment is present, correctly named, and ready to upload. A tidy package also reduces the risk of uploading the wrong or outdated version of a file.

Run a Final Completeness Audit

Before you submit, return to your checklist and confirm every item is collected, current, correctly formatted, and included. Cross-reference it against the funder's requirements list one more time, because funders bury document requirements in unexpected places. Confirm that signatures are in place and that any document with an expiration or date sensitivity is still valid.

Have a second person verify the package independently, since the person who assembled it is least likely to notice a gap. Only when the audit is clean should you submit — ideally a day early to absorb any technical trouble. Keeping your standing documents, project materials, and checklists organized in a system like GrantWinPro turns this assembly process into a repeatable routine, so each new application reuses a proven base instead of starting from scratch. A complete, well-organized package ensures your proposal is judged on its merits rather than set aside for a missing form.