You paste a prompt into an AI tool and get back a tidy, confident draft. It could also describe any nonprofit in the country. The program has "holistic support", the community has "diverse needs" and your organization is "deeply committed to making a difference."
Generic output is mostly a sign of generic input. This article covers how to give a tool the right material, how to write down what your voice is, and how to edit a draft until it sounds like the people who do the work.
Why drafts come out generic
A writing tool that knows nothing about you writes from the middle of everything it has seen, which is how you end up with the same stock phrases every funder has read many times. It doesn't know that your clients call the program "the Tuesday group", that your founder started the pantry in a church basement, or that your service area has no bus line after 6 p.m.
The fix is not a cleverer prompt. It is more of your own material, plus an edit by someone who knows the place.
Pick the documents that sound like you
Your best voice samples are documents where someone who knows the work wrote for a real reader. Choose three to five from this list:
- A funded proposal whose narrative you'd be proud to reuse
- A recent annual report letter or impact story
- A donor appeal or newsletter that got a warm response
- A program description written by the program staff themselves
- Transcribed quotes or a few paragraphs from clients, partners or community members, used with their permission
Leave out anything stiff, anything written by committee and anything out of date. A tool will copy what it is given, including the filler.
If your files are scattered, this is also a good moment to build the boilerplate library: a single place for approved descriptions of your mission, programs, history and outcomes.
Write a one-page voice guide
Samples show a tool what you sound like. A short guide tells it, and any new colleague, what to do. Keep it to one page and cover:
- Names for things. "Participants" or "clients"? "Members" or "neighbors"? Use the words your community uses, and list terms to avoid.
- How you refer to yourselves. "We" or the organization's name?
- Tone. Plain and warm, or formal and technical? Pick one.
- Phrases you never use. Add the stock lines you keep cutting: "making a difference", "holistic", "underserved" if your community dislikes it.
- Facts you always state the same way. Founding year, service area, the correct name of each program.
A guide like this also helps your colleagues, which matters in a team with several writers.
Edit for specifics
Once you have a draft, edit with a single question at each paragraph: could any other organization have written this sentence? If yes, replace it with something only you could say.
Say a small literacy nonprofit gets this line in a first draft: "Our program provides holistic support to underserved families." A revision pass swaps in what only the staff knows:
Every Thursday evening, 18 families meet at the Eastside branch library. Parents work through reading practice alongside their children, and a volunteer from the neighborhood is there to help with homework and forms.
The second version tells a reviewer who is served, where, how often and by whom. It is also easier to check against your records, which helps accuracy. The need statement shows how to apply the same move to the problem you describe.
A short edit checklist
- Replace each adjective with a number, a name or an example.
- Cut stock phrases from your voice guide.
- Swap general terms for the words your community uses.
- Read the paragraph aloud. If you'd never say it to a colleague, rewrite it.
- Add one concrete detail a stranger could not guess.
Keep your voice and meet the reader's needs
Your voice isn't an excuse for long or ornamental writing. Federal guidance on plain language starts from the same idea: the Plain Writing Act of 2010 established the requirement that content for the public is written for its specific audience. You can borrow the instinct. Know who reads your proposal and write so they can find what they need. Clarity over cleverness in grant writing goes deeper on this.
Voice also includes the community's voice. A quotation, a story told with permission or a phrase used by participants can carry more than any polished sentence. Community voice in the proposal covers how to include it respectfully.
Match the voice to the funder without losing yourself
Your voice stays the same, but the register shifts with the reader. A community foundation's online form may invite a conversational answer. A federal narrative is read against a scoring table and rewards plain, labelled statements. A good voice guide says what changes by audience and what never does.
Say a small arts nonprofit keeps two lines in its guide: "Always call participants 'artists', never 'clients'" and "In federal narratives, lead each section with the answer to the scoring question, then tell the story." The first rule holds in every application. The second only applies when a reviewer is working through criteria. Writing both down means a new colleague, or a drafting tool, can follow them without guessing.
Check that edits didn't add new errors
Rewriting for voice is also where facts drift. A vivid detail added from memory, such as "18 families" or "since 2009", is still a claim. After the voice edit, check every number, date and name you added against your records before the draft goes further. Treat it as a short fact-check of its own.
Your next step
Choose three past documents that best represent your voice and keep them together in one folder. Add a note on each saying why you chose it, such as "clearest description of the program" or "best client story". Then draft your one-page voice guide from what you see in them.
If the hardest part is getting a first draft on the page, SoliContraX can build one from the materials you've collected, and you finish it in your own words. Those three documents are a good place to start. Get started with SoliContraX.