Grant Proposal Template Checklist

Capture the funder name, opportunity number (NOFO, FOA, RFP ID), award ceiling, period of performance, and submission deadline. Source from Grants.gov, SAM.gov, foundation portals, or the buyer's procurement site. Verify the eligibility section before any capture work — wrong NAICS or set-aside category disqualifies the bid.

Capture manager and proposal lead score the opportunity against your win-theme criteria: customer intimacy, past performance, solution fit, pricing competitiveness, and discriminators. A no-bid here saves 80+ hours of proposal labor and protects your win rate. Document the decision rationale even when bidding.

Record why this opportunity didn't clear the gate — eligibility, pricing fit, capacity, OCI, or strategic fit. Notify the capture team and sales leadership so the opportunity doesn't reappear in pipeline forecasting. File the rationale for future market intelligence.

For federal opportunities, SAM.gov registration must be active through award. Verify the UEI, CAGE code, and entity admin contact. Expired SAM registration is a common reason proposals are rejected at submission — renewal takes 7-10 business days and can't be rushed.

Build the compliance matrix from Sections L (instructions) and M (evaluation criteria) for federal RFPs, or the equivalent submission/evaluation sections for foundation grants. Every shall, must, and required becomes a row. Page limits, font size, attachment formats, and naming conventions all matter — non-compliance is the fastest way to get bounced.

Schedule the kickoff within 5 business days of the bid decision. Agenda covers compliance matrix walkthrough, win themes, discriminators, ghost positioning against named competitors, role assignments, and the proposal calendar with Pink/Red/Gold review dates.

Assign a named author for each compliance-matrix section — technical, management, past performance, pricing, resumes. Authors get the page allocation, win themes for their section, and the draft due date. Capture manager owns the cross-section narrative.

For federal work, confirm small-business set-aside compliance (8(a), HUBZone, SDVOSB, WOSB) and teaming agreements before any partner contributes content. Run OFAC sanctions screening on partners. Execute NDAs and teaming agreements before sharing the solicitation or draft sections.

Three to five win themes mapped to the funder's evaluation criteria. Each theme answers: why us, why not the competitor, what's the proof point. Discriminators must be features the competition cannot match, not table-stakes capabilities. Ghosting the incumbent's known weaknesses is fair game when substantiated.

Lead with the funder's stated mission and the problem they're trying to solve, not your company history. Map win themes to evaluation criteria. Keep to the page limit — for most federal grants this is 1-2 pages. Reviewers read this first and use it to frame the rest of the proposal.

Address every Section L requirement in the order presented, with subheadings matching the solicitation language. Include the methodology, work breakdown structure, schedule, and risk mitigation. Pull proof points from Loopio or Responsive content library where reusable; rewrite anything that smells like boilerplate.

Select three to five references matching the solicitation's relevance criteria — similar scope, dollar value, period of performance. Confirm with each customer POC that they will respond to a CPARS or reference questionnaire. Past performance that the customer won't validate is worse than no reference.

Build labor categories, direct costs, indirect rates (DCAA-approved or provisional), fringe, overhead, G&A, and fee. Tie every line in the budget narrative to a task in the technical approach. For foundation grants, follow the funder's budget template exactly — custom formats get rejected.

Resumes follow the solicitation's required format and page limit. Letters of commitment from key personnel and named subcontractors are signed and dated within the proposal window. Letters older than 30 days from key partners raise flags during evaluation.

Pink Team reviews the storyboard or 30-50% draft for strategy, win themes, and compliance with the solicitation outline. Reviewers should be unbiased — pull SMEs not involved in drafting. Output is a feedback memo with prioritized rewrites before Red Team.

Red Team scores the 90% draft as evaluators would, using the Section M criteria. Each reviewer assigns scores and writes evaluator-style strengths and weaknesses comments. Drafts that score below the win threshold need a recovery plan before Gold Team.

Capture manager assigns rewrite owners for each flagged section with a hard 72-hour deadline. Pull in a fresh SME if the original author is too close to the material. Re-score against Section M before declaring the section ready.

Gold Team is executive sign-off on the final draft: pricing strategy, risk acceptance, and go/no-go on submission. Attendees include CRO or VP Sales, capture manager, contracts lead, and legal. Discount or pricing exceptions get approved here, not at submission.

Walk every row of the compliance matrix against the final document — page counts, font, margins, file naming, attachment formats, required certifications. Federal submissions through Grants.gov or SAM.gov reject files that violate format rules; there is no resubmission window once the deadline passes.

SF-424 or equivalent transmittal forms require the authorized organizational representative's signature, not the proposal manager's. Route through DocuSign or wet-sign per funder requirements. Verify representations and certifications (reps and certs) are current in SAM.

Submit at least 24 hours before the deadline — Grants.gov, eRA Commons, and foundation portals all experience surge load at deadline and have rejected late submissions traceable to portal slowness. Save the submission confirmation number and timestamp.

Grants.gov sends a Tracking Number, then a Validation receipt, then an Agency Receipt. All three must arrive; a Tracking Number alone does not mean the proposal was accepted. For foundations, request written confirmation from the program officer.

Update the Salesforce or HubSpot opportunity stage to Proposal Submitted with expected decision date, weighted probability based on historical win rate for this funder, and forecast-call notes for the next pipeline review.

Funders often issue Evaluation Notices (ENs) or clarification questions with 48-72 hour response windows. Pre-stage the team — capture manager, technical lead, pricing lead — and the proposal master file so responses go out fast. For competitive-range RFPs, rehearse the oral presentation against the evaluation criteria.

Record the funder's decision in the CRM and trigger the appropriate next workflow. Awarded proposals go to contracts and the CSM handoff motion; unsuccessful proposals go to the win-loss review queue. Closed-lost without a debrief is a wasted learning opportunity.

For federal losses, request a written or oral debrief within the FAR 15.506 window (typically 3 days from notification). Capture the winning competitor, the score gap, and the evaluator strengths and weaknesses. Feed findings into the next bid/no-bid scorecard so the same gap doesn't repeat.

Hand off the win package to contracts for award negotiation and to the CSM for kickoff planning. Transfer CRM ownership per rules of engagement, post the win summary in the account channel, and schedule the customer kickoff within 10 business days of contract execution.