Why a Master LOI Template Stops Working (and What to Reuse Instead)

You wrote the program description once, carefully, and it was good. Then the next funder asked for it in 1,000 characters. Then one asked for it split across four boxes. Then one wanted the same facts arranged around a question you had not thought to answer.

At some point most people try to solve this with a master document — one strong version of everything, kept current, pasted in as needed. It works for a while. Then it quietly stops working, and it is worth understanding why, because the failure is structural rather than a sign you built it wrong.

Two different things get called "reuse"

There is the content: who your organization is, what the project does, what you are asking for, what will change if it works, what evidence you have. That material is genuinely stable. It should be written once, carefully, kept current, and reused for years.

There is the artifact: the two-page letter, the formatted document, the finished thing you submit. That is not stable, and no amount of maintenance makes it stable, because it is shaped by requirements that belong to the funder rather than to you.

Conflating those is what makes the master document feel like a betrayal. The content in it was reusable. The document around it never was.

Three mechanisms, any one of which defeats a single document

Length ceilings do not negotiate. One funder allows two pages; another allows one. A form field stops accepting input at a fixed character count. A two-page document is not "slightly too long" for a one-page limit — it is inadmissible, and the cut is not a trim. Removing half the words means deciding which half of the argument survives, which is writing, not editing.

Structural decomposition breaks the document into pieces. When the first step is a web form rather than an attachment, your narrative has to be dismantled into their fields — organization background here, need statement there, outcomes in a box of their own. A document is a sequence with transitions; a form is a set of independent answers. The connective tissue that made your letter read well is exactly what a form has nowhere to put.

The same truth gets asked for differently. Two funders both want to know who you serve. One asks for demographics. One asks how you determine eligibility. One asks what the community said it needed. Those are not formatting variants of one answer — they are different questions about the same underlying facts, and answering the second with prose written for the first produces something that technically responds and visibly misses.

Notice that none of these is about writing quality. A better master document fails all three the same way.

What a content bank looks like instead

Not one file. A small set of things you can assemble from, each kept current on its own.

• Organizational identity — legal name, founding, mission in one or two sentences, scale.
• Program description — what happens, for whom, how often, where. Written plainly rather than persuasively, because persuasion is funder-specific and the facts are not.
• Need and evidence — the numbers you cite most, each with a note saying where it came from and what period it covers.
• Outcomes — what changes, and how you know.
• The ask — the amount, what it covers, and how it fits your budget.

Keep each at the longest length you ever need, and cut down per application. Cutting a good long version is fast; expanding a short one under deadline is not.

The trap on the other side

The opposite failure is reusing an old application wholesale, and it is the more dangerous one, because it produces something that looks finished.

Last year's LOI carries last year's numbers, last year's staff, and a description of a program that may have changed since. Those facts do not announce themselves as stale — they read as confident and specific, which is exactly why they slip through. A figure that contradicts your own most recent filing is worse than no figure, and nobody notices until a funder does.

If you take one thing from an old application, take the structure. Re-derive every number from its source.

A quick way to tell which one you are doing

Before you paste, ask what you are pasting: a fact or a finished passage.

A fact you re-verify and re-frame for this funder's question. A finished passage you are hoping will survive intact — and if it is longer than the space you have, or written against a different question, it will not.

The part that is actually the job

If this sounds like the reshaping is the real work rather than an annoyance around the real work — yes. That is the argument.

The writing most people picture, the blank page and the good sentences, is a small share of the hours. The rest is taking a set of facts your organization already knows and putting them into the shape this particular funder asked for. Getting good at that is mostly a matter of keeping the facts somewhere they can be reshaped from, instead of somewhere they have to be excavated. If you are building that set for the first time, start with the records worth gathering first.