Working With a Team on Grants

Grant writing is rarely a solo act, even when there’s only one grant writer. You need data from program staff, numbers from finance, sign-off from leadership, and letters from partners. The quality of your collaboration directly affects the quality of your proposals.

The Roles in a Grant Team

Even in small organizations, these functions exist — sometimes all in one person:

Grant writer

Program staff

Finance

Leadership (ED/CEO)

External partners

Communication That Works

The difference between a smooth grant process and a chaotic one usually comes down to one thing: how specific you are when asking people for things. “Can you help with the proposal?” gets you nothing. A specific request with context and a deadline gets you what you need.

Be specific in your requests. “Can you help with the proposal?” is too vague. “I need three paragraphs about the mentoring program’s outcomes — specifically the number of participants, completion rate, and any pre/post assessment data — by Thursday at noon” is actionable.

Provide context. When you ask for information, explain how it’ll be used. “This is for a foundation that cares deeply about evidence-based approaches, so specific outcome data with comparison points would be most useful” helps your colleague prioritize what to share.

Set internal deadlines before external ones. If the proposal is due Friday, your internal deadline for contributions should be Tuesday. This gives you time to integrate, review, and format.

Create a shared workspace. Whether it’s a shared folder, a document collaboration tool, or a grant management platform, everyone working on a proposal should be able to see the current state of the work. This prevents version conflicts and keeps everyone aligned.

Managing Feedback and Revisions

Pro tip

One person owns the final document. When multiple people edit the same document, you get inconsistent voice, formatting conflicts, and nobody sure which version is current. One person (usually the grant writer) integrates all feedback into a single master document.

Use comments, not edits. When reviewers want to suggest changes, comments preserve the original text and make the suggestion visible. Direct edits can introduce errors without anyone noticing.

Time-box the review. “Please review and send feedback by Wednesday” gives people a deadline. “Take a look when you get a chance” means you’ll be chasing them the night before submission.

Track who reviewed what. Keep a simple log: “ED reviewed narrative 4/10, Finance reviewed budget 4/11.” This ensures nothing ships without the right eyes on it.

When You’re the Only Grant Person

Many organizations have a single person handling all grants. If that’s you:

Build a roster of reviewers. Board members, peer professionals, even friends with good editing instincts can provide the fresh eyes you can’t give yourself.
Create templates and checklists. When you can’t delegate, systematize. A good checklist catches errors that a tired solo writer misses.
Use AI as your first reviewer. Before you ask a human to review, have AI check for consistency, completeness, and alignment with the funder’s criteria. This means your human reviewer is looking at a stronger draft.

The traditional collaboration approach — emailing drafts back and forth, tracking changes in Word, hoping everyone is editing the right version — creates friction that slows down every grant cycle. General-purpose tools like Google Docs help with real-time editing, but they don’t understand grant workflows. Purpose-built AI grant tools add collaboration features designed specifically for how grant teams actually work.

In Grantable

In Grantable: Grantable supports team collaboration with comments and @mentions on any document, file sharing with external partners, and shared workspace access. When multiple people work on the same grant, everyone sees the same current state — no version conflicts, no emailing drafts back and forth.

Check your understanding

Your program director sends you a two-page email full of information about a new initiative, but it's disorganized and mixes anecdotes with data. The proposal is due in a week. What's the most effective approach?

Key Takeaways

Be specific in requests, provide context, and set internal deadlines well before external ones
One person owns the final document — use comments rather than direct edits from reviewers
Create a shared workspace so everyone can see the current state of the proposal
If you're the only grant person, build a reviewer roster, lean on checklists, and use AI as your first review layer

Next Lesson

You’ve learned the skills. Now let’s put them into action — a practical plan for your first 30 days applying what this track has taught you.