Create organizational prompt templates for consistency across team and proposal types
In your initial experiments with AI for grant work, you've likely used AI in an ad-hoc manner: When you need something written, you open Claude and craft a prompt on the fly. This approach works for occasional use, but it creates problems when AI becomes central to your grant workflow:
The solution is a prompt template system: standardized, documented prompts for your team's most common grant tasks. Templates aren't rigid or creative-limiting—they provide a starting framework that team members customize for specific contexts.
When multiple team members use the same prompt template, they get similar quality output, which they then customize. This is much more efficient than everyone developing their own approach. It's also more likely to preserve organizational voice and priorities.
Faced with a blank screen in Claude, many people struggle with where to start: What should I ask for? How much detail? What tone? A template removes this initial friction. You just fill in the specific details for your situation.
Effective prompts embody your organization's approach to grant work. When a skilled grants manager develops a prompt that gets consistently good results, that prompt captures their expertise. Templates help transfer that expertise across the team and preserve it if the person leaves.
Start with your most repetitive, time-consuming tasks that multiple people do:
Create 3-5 templates for your highest-value tasks first. Once you see success and workflow benefits, expand to additional templates.
A good template includes:
Task Description: What is this prompt for? When should you use it? Example: "Use this template when you have raw funder guidelines and need to quickly summarize their priorities and requirements in a standard format."
Context Section: What information does the user need to provide? "Paste the funder's complete guidelines or RFP here."
Core Instructions: What should AI do? "Analyze the funder guidelines and extract: (1) funding priorities and focus areas, (2) eligible organizations and programs, (3) required application materials, (4) evaluation criteria they emphasize, (5) funding timeline, (6) application deadline and contact information."
Output Format: How should output be structured? "Format as a 1-2 page summary document with clear sections."
Customization Notes: What can users change? "Modify the categories if this particular funder has unique requirements (e.g., if they emphasize equity or sustainability)."
PROMPT TEMPLATE: Needs Statement Development
WHEN TO USE: You have background research, data, and program context but need to synthesize this into a compelling needs statement for a grant proposal.
CONTEXT INFORMATION [USER PROVIDES]:
- Program focus area (e.g., youth employment, literacy)
- Geographic area served
- Target population details
- Current gaps in services or outcomes
- Data supporting the need (statistics, research, community input)
- Current efforts/resources available
CORE INSTRUCTIONS:
Write a compelling 400-500 word needs statement for a grant proposal that:
1. Grabs attention with a compelling opening that illustrates the problem
2. Provides specific data about the scope of the need (how many people, what outcomes)
3. Explains root causes of the problem
4. Acknowledges existing efforts but identifies gaps
5. Makes the case that the gap represents an important funding opportunity
6. Uses active voice and specific examples
7. Is written for funders who may not be experts in this area (accessible but sophisticated)
Use the following background information: [USER INSERTS]
OUTPUT FORMAT:
- Compelling opening paragraph
- 2-3 body paragraphs showing scope, causes, and gaps
- Closing that frames this as an opportunity
- Include at least 3 specific statistics or data points
Store your prompt templates somewhere accessible to your entire team. Good options:
Organize templates by category (Proposal Development, Grant Management, Reporting) so team members can quickly find what they need.
Your template library should include:
Version Control: As you use templates, you'll discover improvements. Version your templates and communicate updates to your team so everyone is using current versions.
While one core template works for most situations, you may develop variations for different funder types. For example, a needs statement for a family foundation might emphasize personal impact and stories, while a needs statement for a government funder might emphasize data and alignment with national priorities.
Rather than completely separate templates, create one master template with customization notes for different funder types:
"For family foundations: Include a compelling individual story in the opening. Emphasize emotional impact alongside statistics. Use warm, accessible language. For government funders: Lead with research citations. Emphasize alignment with agency priorities. Use more formal language."
Similarly, you might adjust prompts based on program type. A youth development needs statement might emphasize different data points than an environmental or health program. Note these variations in your templates.
When someone new joins your grants team, orientation should include: Here are our AI prompt templates. Here's how to use them. Here are examples of output from each template. Here's how to customize templates for your specific situation.
Help team members understand that templates are frameworks, not scripts. They should:
How do you know if your prompt templates are working?
Every 6 months, review your most-used templates and ask: Are these templates still working? What modifications have we made to the core template? What do users struggle with? Update templates based on what you learn.
To ensure all outputs from your templates reflect your organizational voice, create a house style guide that influences all your prompts. This might include:
Reference this style guide in all your templates. Example: "Write in our house style: accessible but sophisticated, emphasizing partner strengths and community assets, avoiding deficit language."
As your team grows, templates become increasingly valuable for ensuring consistency and accelerating work. A 3-person team might have 5 core templates; a 10-person team might benefit from 15-20 templates covering proposal development, grant management, reporting, and communication.
Assign one team member as "template librarian"—responsible for maintaining and updating templates, training new users, and evolving the template system as your work evolves.
Action Item: Select the single grant task your organization does most frequently. Document the ideal approach to this task: What information is needed as input? What steps should happen? What quality standards should be met? What's the ideal output? Draft a prompt template for this task. Test it with a real example and refine based on the output. Share the template with team members and gather their feedback.