In many organizations, one person or small team writes the application and a different group delivers the project. That split is practical, because writers write and program staff run programs. But it creates a risk: the proposal makes promises about timelines, numbers and staffing that the delivery team has never seen, and sometimes can't meet.
This article explains how the two teams differ, what goes wrong when they meet only after the award, and how to involve delivery staff early without turning the application into a committee project.
Understand that these are two different teams
The proposal team is whoever turns a funding notice into an application: the grant writer or development director, a budget lead, a reviewer and whoever approves the final version. Their goals are clarity, completeness and meeting the deadline.
The project team is whoever carries out the work after an award: the project director, program staff, the finance person who tracks spending and any partners. Their goals are results, a manageable workload and compliance with the award terms.
In a small organization, these may be the same three people wearing different hats. In a larger one, they may never have met. Either way, ask the question directly: who will be doing this work, and have they read the application?
See what goes wrong when they don't talk
A few failures show up again and again when the writer works alone.
- Timelines that ignore reality. The proposal says participants will be enrolled in month one. The delivery team knows recruitment, consent forms and site agreements take much longer.
- Numbers no one chose. A target for people served sounds good in a draft, but nobody checked it against staffing and capacity.
- Roles that don't exist. The narrative describes a position or a partner contribution the organization hasn't actually arranged.
- Activities without owners. A task appears in the work plan, but no one on the delivery side knows they're responsible for it.
These are not only awkward. Once an award is made, the project you described is the project you are accountable for. Under 2 CFR 200.308(f)(1), a recipient must request prior written approval from the federal agency or pass-through entity for a change in the scope or objective of the project, even when no budget revision is involved. Under 2 CFR 200.308(b), deviations from the approved project scope or objectives must be reported. In other words, a promise that was a draft sentence can turn into an approval request or a compliance problem. Foundations and state funders have their own terms, so read the award terms before you assume their flexibility.
Bring delivery staff in at three points
You don't need the delivery team in every drafting session. Three moments are enough, and each takes a short meeting.
1. The concept review
Before you draft sections, share a one-page summary of what you plan to propose: the problem, the approach, who is served, what will change and roughly what it will cost. Ask the delivery lead to read it and answer one question: could we do this?
If you're also deciding whether to apply at all, the go or no-go questions work well with the delivery lead in the room. The outline stage is the natural time for the concept review.
2. The work plan and timeline
Walk through the activities, milestones and deliverables with the people who will do them. Ask them to mark any date that's too early, any task that depends on something not yet in place and any step that's missing.
3. The budget review
Have the person who will manage the project, and the finance lead, check the staffing, effort and costs. The budget justification should describe what the delivery team plans to buy and do, not what the writer assumed.
Use specific questions
Delivery staff are busy, and "any feedback?" produces silence. Ask questions that take two minutes to answer:
| Topic | Question for the delivery lead |
|---|---|
| Timeline | Which date in this plan will we miss, and why? |
| Targets | Is this number of participants possible with the staff we've listed? |
| Staffing | Who actually does this task, and do they have time? |
| Dependencies | What needs to be in place before this starts? |
| Risks | What is most likely to go wrong in the first six months? |
A worked example
Say a rural health clinic is applying for a grant to offer diabetes classes. The draft says: "Within three months of award, 120 patients will complete the eight-week course." The delivery lead reads it and points out that the clinic has one educator, who can teach two classes at a time with ten patients each. Eight weeks per cohort means two cohorts fit in the first sixteen weeks, or about 40 patients, not 120.
The writer revises it to "Within six months of award, 60 patients will complete the course in three cohorts, and the clinic will add a second educator in the second year." That's a promise the clinic can keep, and the budget now includes the second position. Finding the problem in the draft cost one 20-minute conversation. Finding it after the award would have meant reporting a shortfall.
Keep the process light
Involving the project team shouldn't slow the application. A few habits help:
- Send a short read, not a full draft. A one-page concept and a one-page timeline get read. A forty-page document doesn't.
- Give a deadline for feedback. "By Thursday at noon" is easier to meet than "when you can".
- Decide who has the final say. Input is not a vote. The proposal lead decides what goes in, after hearing what's possible.
- Record what you changed. Tell the delivery lead how their feedback shaped the draft. They're more likely to help next time.
- Send them the final version. Everyone who will deliver the project should have the submitted application and the award terms, so no one has to guess what was promised.
The same approach works for team coordination in general, as described in managing a grant team.
Your next step
Invite the person who will lead delivery to your next concept review, and send them a one-page summary two days before the meeting. Ask them to bring one date or number they don't believe. Then change the draft before you write another section.
If your organization has fewer people than roles, SoliContraX can help the writing side move faster, so there is more time left for conversations like this one. Upload the notice, approve a concept with your delivery lead in the room and start from a draft built from your own materials. See how to get started.