The project narrative and turning practice into a fundable project

What makes a project 'legible' to a funder?

Legibility means a tired reader can restate your project in one sentence after one read. NYFA program officer Kelly Olshan describes the failure mode precisely: "I've read many complex narratives where I get to the end and I still don't understand the basics of what the project is, or what the applicant is really asking for money to do." Her corrective is the "Who, What, When, Where, and Why" of a proposal, grounded before any conceptual elaboration. Fractured Atlas's "Grants for Artists" guide states the reviewer's need plainly: "The person reviewing your application needs to be able to quickly understand what kind of work you make and what you are proposing as a project."

Legibility is a kindness to the reader that the reader rewards with a higher score. A regional arts-council grants administrator, Anna Kojevnikov of the Acadiana Center for the Arts, recommends a blunt test: "Find someone that doesn't know anything about the project, have them read it and ask them to tell you what they understood the project to be." If they can't, the panel won't either.

This is where the practice-vs-project rule inverts, and misreading it sinks applications. Some funders deliberately fund the person or the practice, not a bounded project. The NYSCA/NYFA Artist Fellowship states it "is not a project grant, but is intended to fund an artist's vision or voice, at all levels of their artistic development," and explicitly asks applicants not to submit project proposals. Many residencies are similar: Hewnoaks tells applicants its residencies are "unstructured and process-oriented… You don't have to propose a specific project, but we want to know what you hope to gain from the experience." Yet other residencies and commissions demand a tightly defined deliverable.

Read the verb. Project grants fund making a defined work; fellowships fund being and becoming an artist; residencies fund time, space, and process. Submitting a bounded production plan to a vision-based fellowship reads as not understanding the award — and vice versa. A useful heuristic, per a University of Arizona Graduate Center guide: "fellowships go to people and grants go to projects." Even for practice/process awards, panels still want evidence of seriousness — a sense of why this time, this place, this juncture.

How does 'project' shift across funder types (councils, foundations, commissions)?

"Project" is not one thing. Public arts councils (e.g., NEA Grants for Arts Projects, 4Culture) typically require specific, definable activities with public benefit and often a community or audience dimension; 4Culture's criteria even let applicants choose an artistic-impact lens — Continuity, Growth, or Engagement — signaling that "continuing a long-term practice" can itself be a fundable project frame when named as such. Private foundations may fund either projects or unrestricted practice depending on mission. Commissioning bodies scope the most tightly of all: a commission is contractually a deliverable, with a scope of work that "specifies deliverables and dates," milestones, check-ins, and a finished object on a deadline — closer to a work-for-hire than an open inquiry.

The Canada Council illustrates how the same activity sorts differently: a residency to "build new professional skills… to deepen their practice" belongs in a sector-development stream, whereas "using those technologies to develop and stage creative work, such as a multimedia performance" belongs in a creation stream.

Before scoping, diagnose which definition of "project" the funder uses — production deliverable, public activity, career catalyst, or practice development — and scope to that.

Highest-leverage insightA funder is not asking for a smaller version of your practice but for a thing with edges, and the edges are what make the money spendable.

What's the difference between activities and outcomes, and why do panels care?

Activities are what you will do (hold workshops, paint canvases, record tracks). Outcomes are what will change or result (new audiences encounter a form, a community's story is preserved, your practice opens a new direction). The W.K. Kellogg Foundation's Logic Model Development Guide (2004) — the canonical primer — sequences five elements: inputs (resources), activities, outputs (the direct, countable products: "number of classes taught, meetings held, or materials produced"), outcomes (changes in knowledge, skill, behavior, status), and impact (the longer-term, systemic change). Kellogg's time horizons are specific: short-term outcomes are "attainable within 1 to 3 years," longer-term outcomes "within a 4 to 6 year timeframe," with impact "occurring within about 7 to 10 years."

Karsh & Fox, in The Only Grant-Writing Book You'll Ever Need, drive the discipline home: link "each program activity to a measurable objective" and steer clear of activities that "may be beneficial or enjoyable but do not match the program's specific goals."

Outcome thinking for artists need not be quantitative or instrumental. Creative Capital's application asks what kind of impact you hope for and why — and explicitly lists the options as "artistic, intellectual, communal, civic, social, political, environmental." That breadth is the permission structure: an artistic outcome ("the work extends what's formally possible in cameraless film") is a legitimate outcome, not a lesser one. The move is to name the change you intend in the register your work actually operates in, then say who it's for. Avoid two failure modes: vague aspiration ("inspire people") and borrowed social-service metrics that don't fit ("increase wellbeing by 20%").

Distinguish the artistic outcome (what the work does as art), the audience outcome (who encounters it and how they're changed), and the practice outcome (how it advances your trajectory). Creative Capital's prompt — "How might your proposed project act as a catalyst for your artistic and professional growth? In what ways is it a pivotal moment in your practice?" — explicitly invites that third register. Naming all three, briefly, signals you understand the difference between doing and achieving.

Where does logic-model / theory-of-change thinking help artists?

Experts genuinely disagree here.

For Arts-policy analyst Ian David Moss argues logic models are "a tool of tremendous power" that force clarity about how change actually happens; the discipline of stating assumptions ("if increased access, then new audiences") exposes magical thinking. The Kellogg guide stresses a theory of change "describes how and why you think change happens," which can sharpen even abstract artistic intentions.

Against Arts leader Laura Zabel (Springboard for the Arts) says she "hates" logic models for being "too reductive"; Diane Ragsdale, as Moss characterizes her more cynical view, worries they can be misused by funders to make themselves seem smarter than they really are or to blame grantees for failed strategies. A UK arts-evaluation guide (Figurative) concedes the core limitation: "the drivers behind social change are complex and non-linear, so any linear logic model will be inherently limited," and argues the process of thinking it through matters more than the diagram.

Use logic-model thinking as a private clarity tool — to pressure-test whether your activities plausibly produce your claimed outcomes — but don't let it flatten the proposal's voice into instrumental box-checking. The Kellogg guide itself notes models "should be adapted" and can take nonlinear forms (a cycle, not just a left-to-right chain), which better suits iterative artistic processes. Resist the deeper risk that critics like BAVO flag: instrumentalizing art so it is valued only for non-art outcomes. (François Matarasso engages this debate from the other side — he treats "instrumentalization" as something all art undergoes and reframes the real question as "for whose purpose," so he is not a flat critic of it.)

Highest-leverage insightWeak proposals stop at activities ("I will make 10 paintings"); fundable ones connect activities → outputs → outcomes ("10 paintings → a solo exhibition seen by X → a new public conversation about Y"). Panels fund change, not busyness.

What is the paragraph-level arc of a project narrative?

A workable default arc: Hook → What / Why-now → Method → Feasibility → Impact. Each part does a job: the hook earns the next paragraph and signals the stakes; what / why-now states the concrete project and its urgency; method shows how you'll make it (process, materials, approach) and proves it's grounded; feasibility (timeline, capacity, track record) shows you can deliver; impact names what changes and for whom. Cheryl Clarke's Storytelling for Grantseekers maps proposal sections onto story elements: the need/problem builds "tension and conflict," goals and objectives are "the resolution," and evaluation is "the epilogue and seeds for a sequel."

There is no single template; show options and pick by fit.

1. Freytag-style (exposition → rising action → climax → falling action → resolution): good when context matters and there's a pivotal insight or intervention to build toward.

2. Hero's-journey / transformation: centers the artist's trajectory; powerful for fellowships and career-catalyst framings, but Funding4Growth cautions it "can over-centre individualism" and may misfit collective or community work.

3. Inverted-pyramid / journalistic: the essential facts first, then supporting detail — best for tired readers and tight word counts.

4. Question-driven / inquiry arc: opens with the central question the work investigates, then offers method as the means of pursuit; suits research- and process-based practices.

Match the arc to the award type — inverted-pyramid for skimmable project grants, transformation arc for fellowships, inquiry arc for residencies and research.

The sources consistently warns against one rigid mold; the same project may need a different arc for a public council than for a private foundation. Whichever you choose, the narrative must read as a single coherent story — VCU's proposal guidance warns that disjointed, cut-and-paste sections confuse reviewers.

Think of every section as performing a job in the reviewer's decision, not just conveying information. The project description answers "what is this, concretely?" — Creative Capital's prompt insists you articulate "what form your project will take (i.e. a painting, dance, film, etc.)" and "be specific and concrete." The context/influences section answers "is this person serious and situated?" — it places the work "into a broader discourse." The method section answers "can this actually be made, and is the maker credible?" The impact section answers the reviewer's silent "so what?" The budget and timeline answer "is this real?" Grantsunlocked frames the reviewer's unspoken checklist: clarity, significance ("the 'So what?' question"), feasibility, and funder alignment.

The artist statement and the project narrative are different instruments. As Naturalist Gallery puts it, "an artist statement describes the ongoing practice… a project statement describes a specific body of work… Many artists fail structurally by using one where the other is needed." Panels detect that misalignment instantly.

Highest-leverage insightThe arc is a service to the reader, not a creative-writing flourish — each paragraph should answer the question the previous one raised. Unlike fiction, a grant narrative reveals its "ending" (the project and its value) immediately, then earns it. Front-load; don't withhold.

How should you write for someone reading hundreds of proposals?

Assume a skeptical, time-poor reader with a rubric and a stack. VCU's proposal guide is blunt: reviewers "have a lot of proposals to read and devote a small amount of time to each one" — so use "section headers, bullets, tables and figures, and white space… all formatting elements that make your proposal 'skimmable.'" A working grant reviewer, writing for Spark the Fire, confirms the conditions: pods of three or four reviewers, "just a few days to get through the entire stack," scoring against a rubric.

Legibility is a scored quality, not a courtesy. Most reviewers are instructed not to look at your website or social media (per Arts Midwest's guide), so the application is the only evidence. Write so the assigned reviewer who must summarize your project to the panel can do so accurately and enthusiastically — NIH's guidance frames this as writing so reviewers "can readily grasp and explain what you propose." If they misparaphrase you, you've lost before discussion begins.

The opening must deliver the core idea, not delay it. Robert Porter, in "Why Academics Have a Hard Time Writing Good Grant Proposals" (Journal of Research Administration, Fall 2007 — a paper named SRA International's Best Paper of the Year), observes that winning proposals "look different": "sentences are shorter," key phrases are bolded or underlined to stand out, and the writing front-loads its argument. The discipline: can you explain the project verbally in under ~75 words to a non-expert who then understands and is excited?

Creative Capital operationalizes this with a "One Line Project Description (50 words / 400 characters max)" — instructed to "be as concrete as possible" about "what form your project will take" — placed before the 500-word description, forcing the artist to lead with the essence.

Apply "first-sentence discipline" — the opening line should name what the project is and why it matters, so a reader who reads only that sentence still knows what they'd be funding. A composer interviewed in The Path to Funding described the proposal summary as "the hardest kind of writing… it has to be so super specific… there can't be any room for any misunderstanding," sometimes taking days for a single paragraph. Front-loading is not dumbing down; it's respect for the reader's time and a hedge against the reviewer who skims the middle.

What plain-language and signposting habits actually move the needle?

Concrete habits:

1. Replace jargon and "artspeak" with everyday language; NYFA's reviewers list "grandiose language for no particular reason" as a top pet peeve and prefer "direct, concise language."
2. Use structural signposting — headers, short paragraphs, white space — so the reader can navigate.
3. Use the present, active voice and avoid hedges; the GYST guide warns against "I hope to," "I attempt to," "I am aiming at," which "put the reader in doubt."
4. Use sensory, descriptive language so the reader can see/hear the work before reaching the work samples.
5. Cut every sentence that doesn't advance the argument. Highest-leverage insight: clarity is not the enemy of sophistication — Porter notes grant language "must sell a nonexistent project," which demands stronger, plainer prose than academic writing.

The test, per a working reviewer quoted by Spark the Fire: the best proposals read "less like a bureaucratic form and more like a story I want to see unfold," achieved through "clarity, specificity, and genuine passion," not fancy writing.

Highest-leverage insightLegibility is scored rather than merely appreciated: one reviewer has to summarise your project to the panel, and a misparaphrase loses the argument before discussion starts.

How do you make the ask unambiguous?

The ask answers three questions without ambiguity: what do you want (money / time / space and how much), what will it enable (the specific activity or work it makes possible), and what exists at the end (the deliverable). Olshan's example models it: before the conceptual detail, "the reader needs to know that you are requesting funding for a 50-minute outdoor concert series to take place at a venue in Queens." Karsh & Fox stress a logical chain from need → objectives → activities so the request feels intentional, not arbitrary.

Name the ask early and plainly, then let the rest of the narrative justify it. A reviewer who reaches your budget still unsure what the money does will not advocate for you. Even unrestricted awards (where funds aren't line-item-restricted) still expect a clear sense of what the support enables — Creative Capital's project grants are unrestricted, yet the application still demands a concrete project the funds will realize.

A deliverable is nameable, countable, and verifiable; an aspiration is a feeling or direction. Illustratively (not a live rule): "a publicly premiered 40-minute dance work," "an edition of 20 prints," "a manuscript delivered to a publisher" are deliverables; "deepen my exploration of memory," "grow as an artist" are aspirations. Aspirations belong in the why; deliverables belong in the what. Arts Midwest's guide warns that vague, estimated figures are "red flags for reviewers" and urges breaking work into concrete units (e.g., "$40/hr × 80 hours"). Grant-writing guidance echoes this: replace "I want to paint a series" with "five large-scale acrylic paintings juxtaposing urban geometry and organic textures."

Specificity is read as competence. Vague deliverables signal the artist hasn't actually planned the project, which reads as feasibility risk. Commissioning bodies formalize this — a commission's scope of work "specifies deliverables and dates," and check-ins are contractual — but the same precision strengthens any project grant.

The ask is only believable if the plan is. A timeline demonstrates you understand the project's scope and can manage it within the grant period; as the Path to Funding curriculum notes, "there has to be evidence that you know how to do what it is that you're saying you're going to do." Timelines should align with the methods section, flag milestones, and can take nonlinear/visual forms (Gantt charts, or even a cyclical diagram for iterative or cyclical work). The budget translates the story "from words to numbers" (Clarke) and must be internally consistent — Karsh & Fox note funders dislike budgets that "make no sense."

Work samples must evidence capacity for this project: Kojevnikov warns that "if you're submitting a proposal to build a giant metal sculpture, a work sample of wildlife photography is not going to cut it."

Feasibility is where ambition meets credibility. 4Culture scores it explicitly — "a practical timeline and thoughtful planning," "realistic and balanced budget." Slightly under-promising a completable project beats over-promising a visionary one you can't evidence you'll finish.

How do you connect the clear ask back to the funder without drifting into funder-matching?

The ask should visibly serve the funder's purpose, not just yours. Ehni frames it sharply: "A grant to your project is the vehicle through which a grantmaker expresses their own mission." Practically, mirror the funder's own criterion names and review structure in how you state the ask and impact — translated into plain, concrete description rather than parroted buzzwords — so a rubric-scoring reviewer can check the box without hunting. Grantsunlocked lists "poor funder alignment" among the silent reasons proposals fail.

These 18 entries are deliberately plural and tailorable. The throughline a program officer would underline: a fundable project is the smallest completable, nameable increment of your practice, stated so plainly that a tired reader can repeat it back, justified by a clear ask and a credible plan, and framed in outcomes that respect the art rather than instrumentalize it. The takeaways flagged above are the highest-leverage levers; if you internalize only those, you will already separate yourself from the large share of applicants who submit a practice where a project was asked for — or a project where a practice was wanted.

The deepest recurring disagreement in the field is worth holding consciously: logic/outcome frameworks are powerful clarity tools but become reductive when treated as the point rather than the scaffold. Tailor every example here to your medium and your funder; none of the illustrative deliverables, arcs, or phrasings is a live rule.

Alignment is about making the reviewer's job easy — show how funding this project advances their stated goals, in their words. Here the point is narrower: once you've chosen a funder, the ask and the impact paragraph should echo that funder's framing so the fit is self-evident — without contorting the project into something it isn't. As Arts Midwest's guide cautions, don't reverse-engineer a project to chase money you have "no intention" of using as proposed; reviewers detect the misfit.

Highest-leverage insightVagueness about the ask reads as an unfinished plan rather than as modesty, and a panel cannot fund a plan it is unable to price.

These are drafting habits rather than a template — the shape of a narrative follows the call it answers.

1. Write the one-sentence version first. Say what the project is in a sentence someone outside your field could repeat back. If they cannot, more detail will not rescue it.
2. Cut the project out of the practice and give it an end. Name what will exist when it is finished, and roughly when. A panel cannot fund something with no completion point.
3. Write the chain, not the list. Activities, then outputs, then outcomes: what you will do, what will exist because of it, and what changes as a result.
4. Put the ask before the budget. Say plainly what the money pays for and why that amount. Vagueness here reads as an unfinished plan rather than as modesty.
5. Read the draft as an assessor at application forty. Everything that matters should be findable in one pass, in the order a tired reader needs it.

Highest-leverage insightMost of this is rewriting rather than writing: the project usually exists already inside the practice, and the work is making it legible as a project.