Create a practical proposal-development process for [PROPOSAL TYPE] responding to [OPPORTUNITY OR FUNDER]. The submission deadline is [SUBMISSION DEADLINE]. Our team and available capacity are [TEAM AND CAPACITY]. Key requirements, evaluation criteria, and submission rules are [REQUIREMENTS AND CRITERIA]. Build a process someone can run without prior context. First, identify the critical path backward from the submission deadline, including time for factual verification, executive review, formatting, portal upload, and a contingency buffer. Distinguish work that can happen in parallel from work that must happen in sequence. Produce: 1. A short assumptions and risks section, including missing information that could delay a compliant submission. 2. A step-by-step table with phase, task, owner role, inputs, deliverable, due date, dependency, and approval gate. Cover opportunity qualification, kickoff, requirements matrix, outline, evidence collection, drafting, budget or pricing alignment if applicable, reviews, revisions, compliance check, and submission. 3. A RACI-style decision list for final content, budget, legal/compliance, and submission authority. 4. A meeting cadence with purpose, attendees, and decisions required. 5. A one-page kickoff checklist and an escalation rule for missed dependencies. Use role names where I have not named people; do not invent team capacity, past performance, pricing, or qualifications. Treat every requirement as traceable: include a requirements matrix task that maps each criterion to an owner, evidence source, and final proposal section. Before answering, check that every task has one accountable owner and that the timeline includes a final compliance review before submission. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [PROPOSAL TYPE] | State the proposal type, such as a grant application, client RFP response, or internal business case. | Federal workforce-development grant application |
| [OPPORTUNITY OR FUNDER] | Name the client, funder, program, or opportunity and briefly describe the request. | State Department of Labor, apprenticeship expansion program for rural manufacturers |
| [SUBMISSION DEADLINE] | Enter the exact submission date, time zone, and any portal cutoff time. | November 14, 2026, 5:00 p.m. Eastern; portal closes at the deadline |
| [TEAM AND CAPACITY] | List the people or roles involved, their responsibilities, and known availability limits. | Maya owns narrative; Luis supplies employer data; Priya owns budget; COO approves; outside evaluator is available Tuesdays and Thursdays |
| [REQUIREMENTS AND CRITERIA] | Paste the proposal instructions, scoring criteria, page limits, required attachments, and submission rules. | 25-page narrative, 10-page budget appendix, three letters of commitment; scored on need, program design, outcomes, partnerships, and budget reasonableness |
How to use
- Paste the opportunity instructions in full, especially scoring criteria, attachments, and portal rules.
- Name the actual decision-makers and note any holidays, travel, or approval bottlenecks.
- Check that each scored criterion has an evidence source and a named accountable owner.
- Follow up with: “Turn this into a dated tracker for our kickoff on [DATE], using named people instead of roles.”
Variations
Grant kickoff agenda
Use this when you need to align a grant team before drafting starts.
Build a 60-minute kickoff agenda for a [GRANT PROGRAM] application due [DEADLINE]. Participants and roles are [TEAM]. Requirements and scoring criteria are [CRITERIA]. Produce a timed agenda, pre-read list, decisions to make in the meeting, a requirements-matrix template, and actions with owners due within five business days. Do not invent eligibility, evidence, or partner commitments. Before answering, check that every agenda item leads to a concrete decision or assigned action. Ask up to 3 questions only if a required input is missing.
RFP response tracker
Use this when the team has started an RFP and needs a disciplined production tracker.
Create an RFP response tracker for [CLIENT OR RFP], due [DEADLINE]. The response sections and requirements are [RFP REQUIREMENTS], and contributors are [TEAM]. Output a table with requirement ID, response section, source material needed, writer, reviewer, approver, draft due date, final due date, status, and risk flag. Include a separate compliance checklist for forms, attachments, pricing, signatures, and portal submission. Do not make up client needs or credentials. Check that every requirement appears once and every final item has an owner.
Proposal review plan
Use this when a draft exists and you need structured reviews before submission.
Design a review plan for a [PROPOSAL TYPE] draft due [DEADLINE]. Reviewers, roles, and availability are [REVIEW TEAM]. Evaluation criteria and nonnegotiable submission rules are [CRITERIA]. Produce review rounds for strategy, technical accuracy, budget consistency, executive approval, and final compliance. For each round, state what reviewers should assess, what feedback format to use, who resolves conflicts, and the handoff deadline. Do not rewrite the proposal or invent content. Check that review rounds leave time for revisions and final upload.
Tips
- Build the requirements matrix before drafting; it prevents elegant narrative that misses a scored criterion or required attachment.
- Assign one accountable owner per task even when several people contribute, or routine handoffs will become invisible delays.
- Reserve a separate compliance review for page counts, file names, signatures, portal fields, and attachments; content reviewers often miss these.
- Set an internal final deadline before the portal deadline so a browser, upload, or signatory problem does not decide the outcome.
FAQ
Can AI assign dates for a proposal process?
It can propose a backward plan, but dates depend on your team’s availability and approval speed. Provide the true deadline and capacity, then adjust the critical path with the accountable owners.
What is the most important proposal-process document?
A requirements matrix is usually the anchor. It shows where every requirement is addressed, what evidence supports it, and who owns the work.
Should the same person write and review each section?
Usually no. A separate reviewer can test whether the section actually answers the criterion and is supported by evidence.