Every Grant Shouldn’t Start From Scratch
Why Communications is the layer that gives a writer the ingredients to work from.
The OPTIC² model categorizes organizational clarity into six interdependent layers: Operations, Public Presence, Trust, Identity, Credibility, and Communications. This post is part of a series examining each layer in depth. For an introduction to the full model, start with The Writer Isn’t the Problem.
Somewhere in your organization, there is a folder full of old grant applications or proposals.
When a new proposal is due, someone opens one of them. Not because it is the right source, but because it is the most recent complete version of the story anyone can find. They update the numbers where they remember to, adjust the program description to reflect whatever changed last year, and swap in the new reviewer’s priorities where the old ones used to be.
This is how a lot of proposal writing actually works.
It is not laziness. It is the only rational response to a system where nothing is organized for reuse. When there is no approved source to write from, the last proposal becomes the source for the next one.
Over time, the organization’s story drifts because each revision was built on the previous revision rather than on a stable foundation.
That is a Communications problem.
What Communications actually is
In the OPTIC² model, Communications is the layer where Identity and Credibility become usable.
This layer contains no source truth of its own. That is by design. Everything here is built from the organizational canon — the approved mission, program descriptions, and language standards established in Identity — and from the documented evidence base in Credibility. When the canon changes, this layer updates. When the evidence improves, the copy blocks reflect it.
The Communications layer holds the writing kit: the pre-approved, version-controlled narrative assets that give anyone writing for the organization something solid to start from.
Boilerplate in short, medium, and long versions
Program descriptions ready for portal fields
A needs statement grounded in current local data
A capacity paragraph
An evaluation methods paragraph
Copy blocks for each program
A case for support
Not drafts. Not last year’s proposal. Assets built deliberately, approved, and maintained.
When this layer is in place, the writer is not starting from scratch; they are assembling from a stable source.
The real cost of starting over every time
The cost of rebuilding the story from scratch is not just time, though it is certainly that. It is also consistency.
Each proposal built from the previous one drifts a little further from the canonical truth. Program names shift. Impact claims grow or shrink depending on what the writer remembers or what seemed to resonate last time. The needs statement gets updated in one place but not another. The language the organization uses to describe its community evolves in the room but never makes it back into the documents.
By the time a funder is reading the third proposal from the same organization in three years, they may be reading three slightly different accounts of what the organization does.
That drift is not dramatic. It does not announce itself. It creates exactly the kind of incoherence that makes someone pause — not because any single version is wrong, but because the story does not quite hold together across time.
The Communications layer stops that drift. Not by policing the writer, but by giving them a better starting point than the last proposal.
Why this layer is not the same as having good writers
Organizations often respond to Communications gaps by asking the current writer to be more consistent, outsourcing writing, or sending around an email with the approved mission statement after the latest proposal goes out.
None of those fixes address the structural problem.
A good writer working from an unstable source will produce inconsistent output because consistency requires a stable foundation. The email with the approved mission statement will be used for this proposal and forgotten by the next one because it is not part of a system anyone can reliably find or use.
The fix is a better system for the writer to work from.
That is what the Communications layer builds: infrastructure.
What changes when the layer is in place
When Communications is built, something shifts for the person doing the writing.
The boilerplate is current, approved, and in one place. The program descriptions match what is on the website, what is in the annual report, and what the executive says in the room. The impact claims are drawn from the documented evidence base, which means they are specific, defensible, and consistent wherever they appear.
The writer still has to write. Proposals still require judgment, responsiveness to priorities in the application or RFP, and real craft. That work does not go away.
But it starts from a stable place instead of a salvage operation. The scramble changes character. It becomes about making the case rather than reconstructing the story. It’s about alignment rather than archaeology.
That is a very different kind of hard, and it is the kind the writer actually signed up for.
Where Communications connects to everything else
Communications sits downstream of Identity and Credibility in OPTIC² and that position matters.
If Identity is weak, the copy blocks built here will reflect that weakness. Program descriptions will vary because the approved names and descriptions were never documented. The mission statement in the boilerplate will drift because multiple versions exist. The Communications layer can only be as stable as the canon it is built on.
If Credibility is weak, the narrative assets will be thin in the same way. The impact claims will be vague because the evidence base is vague. The evaluation language will be soft because there is no measurement plan to draw from.
And when Communications itself is weak — when this layer is missing or underdeveloped — what outsiders see is an organization that tells its story a little differently every time. It is not dishonest, just inconsistent.
Which raises the same quiet question: Do they actually have this together?
The Communications layer is the answer that travels into every proposal, every portal, every report, and every conversation where someone needs to say clearly and consistently who the organization is and what it does.
It is not glamorous infrastructure, but it is the infrastructure the writer has needed all along.
