An AI search visibility audit template is the working file an agency fills during the audit: one structure covering scope and consent, the approved fact ledger, technical eligibility, the frozen prompt panel, the observation log, the source map, findings, and handoff, with an evidence field on every row. The template below is that file, downloadable as a CSV worksheet, reusable across clients because every field records what to capture and which artifact proves it. It is deliberately tool-agnostic: nothing in it requires a tracking subscription to complete.

What the template is, next to the checklist and the report

Three documents run a defensible audit, and conflating them is why most downloadable audit templates disappoint. The template is the workbook: the structure you fill while doing the work. The checklist grades that workbook after the fact; ours is the 47-point scoring model, and it assumes a workbook exists to grade. The report is the client-facing compression of the workbook; the report template covers that layer. Agencies searching for a GEO audit template usually want all three and download whichever one they find first, which is how audits end up with a beautiful report format wrapped around an evidence record that never existed.

Most templates currently circulating are also tool assets. The strongest vendor example, Ahrefs' audit report template, is built around its own Brand Radar data, which is labeled clearly enough but means the method travels only where the subscription does. A workbook should survive a tool change, because your evidence discipline is the part of the audit the client is actually paying for.

The eight sections and what each one forces

The worksheet has 34 fields across eight sections. Each row carries the field, what to record, the evidence artifact to save, and a status. The sections exist in dependency order: a later section filled before an earlier one is the template telling you the audit skipped something.

Two sections do most of the differentiating work. The approved facts section exists because representation review, the part clients care about most, is impossible without client-approved facts to grade against; an auditor without a ledger is grading AI answers against their own guesses. The handoff section exists because the second audit is where sloppy first audits die: a rerun with a drifted panel or changed account state produces a trend chart that measures the auditor, not the client.

Download: AI search visibility audit template (CSV worksheet, 34 fields). All eight sections with every field, what to record, the evidence artifact to save, and a status column. Duplicate the file per client and per audit wave; the structure is the reusable part.

Tool: Grade the filled workbook against all 47 checks. The interactive checker runs the scoring model this template is built to satisfy: confirm what your workbook already records and see every unconfirmed check ranked by weight, with the evidence that would close it.

Filling the technical section without inventing requirements

The technical eligibility fields deserve a note, because this is where audit templates most often import myths. The documented reality is narrower than most worksheets assume: Google states that appearing in AI Overviews and AI Mode requires being indexed and snippet-eligible under the normal Search technical requirements, with no special files or markup, and ChatGPT search eligibility runs through an ordinary crawler allowance documented in OpenAI's crawler docs. So the template's technical fields check access, indexability, rendered text, and controls, all things the platforms document, and none of it asks you to score a page against an invented AI readiness standard. The full crawler decision logic lives in OAI-SearchBot vs GPTBot, and the myth-versus-requirement sorting for Google's side is in the AI Overview technical requirements guide.

Every technical field requires a date on its evidence. "Robots is fine" is not a finding; a robots.txt capture with a body, a status code, and a timestamp is, because the next site deploy can silently change the answer.

Reusing the template across clients

The reusable parts are the structure, the field definitions, and the evidence discipline. The non-reusable parts are everything the fields contain: the business decision, the fact ledger, the prompt panel, and every observation. A template reused correctly produces audits that look identical in shape and completely different in content.

Three practices keep multi-client reuse honest. Duplicate the file per client and never edit a delivered copy, because a delivered workbook is evidence. Version the template itself separately from any engagement, so a field improvement does not retroactively change what an old audit claims to have checked. And keep the prompt panel out of the template file: panels are derived per client from their buyer decisions, and the derivation method in the prompt set guide is the part that transfers, never the prompts themselves.

Our position

A template is a floor, not a method. The value of a shared workbook is that the tenth audit is as complete as the third, that a colleague can pick up an engagement mid-stream, and that the checklist has something real to score. What it cannot do is substitute for the judgment fields: deriving prompts from the client's actual buyer decisions, deciding which findings matter, and refusing to report numbers the sample cannot support. An agency that ships the workbook as the deliverable has sold the scaffolding and kept the building.

The template deliberately promises nothing about outcomes: filling it proves what was checked and observed, not that citations or rankings will follow, and that boundary belongs in the scope section in writing. Price the work the workbook actually demonstrates with the audit pricing model, and when the audit closes, the handoff section's rerun specification is what turns a one-off project into a measurable baseline for the next wave.

Tracking AI citations means recording, per saved answer, which URLs an engine actually cited, keeping those records separate from brand mentions, and reporting rates only against a frozen prompt panel with a declared denominator. The downloadable schema below does exactly that across engines: an observation log, a citation record, a mention record, and a sampling plan, workable by hand in a spreadsheet or as the structure you impose on a tool's exports. What it deliberately does not do is rank anything, because a citation rate is a sample statistic, not a position.

Citations are not mentions, and neither is a rank

Three distinct events get blurred into "visibility" and must be logged apart. A mention is the brand named in answer prose. A citation is a URL surfaced as a source for the answer. A referral is a user actually clicking through, which lands in analytics. An answer can mention you without citing you, cite a third-party page about you, or cite you while describing you wrongly, and each of those is a different finding demanding different work.

The cross-engine problem is that each platform surfaces sources differently: inline links, footnotes, expandable source lists, and grounding panels are all "citations" in the loose sense while being differently visible to the user. Google's own documentation commits only to AI Overviews and AI Mode surfacing relevant links, and its Search Console reporting counts AI-feature traffic inside the ordinary Web search type per the AI features documentation, so no engine hands you a clean, comparable citation feed. The schema handles this with a citation_type field per record instead of pretending the surfaces are equivalent, and by never summing across engines: a ChatGPT citation rate and an AI Overview citation rate are two columns forever.

The four-table schema

The worksheet defines four small tables, and the discipline is in what they refuse to merge.

observation_log is the unit of everything: one row per saved answer, with platform, surface, account state, prompt id, stratum, run number, date, and a brand_present flag. Absence rows stay in the log because they are the denominator.

citation_records holds one row per cited URL per observation: the full URL, the domain, ownership (owned, influenceable, third party), the citation type, and whether the citation supports a brand mention or stands alone. The unit is the URL, not the domain, because a roadmap can only target pages someone can edit.

mention_records holds the sentence naming the brand and its accuracy grade against the client's approved fact ledger. Grading accuracy against memory instead of a ledger is how audits ship compliments instead of findings.

sampling_plan pins the wave: panel version, prompts per stratum, runs per prompt, spacing, and the denominator rule every reported rate must name. Answers vary between identical runs, so single runs are anecdotes; the measurement method behind these rules, including the rate formulas, is the measurement protocol.

Download: Cross-engine citation tracking schema (CSV schema and sampling worksheet). Every column of the four tables with its type, allowed values, and the reason it exists, plus the sampling plan fields with example values. Build it as spreadsheet tabs or impose it on a tool's exports; the schema is the part that keeps waves comparable.

What the tracking tools actually claim to cover

The tool market is loud, so here is what the major platforms state on their own pages, recorded as vendor claims rather than verified behavior.

Key facts, checked August 23, 2026

• Ahrefs Brand Radar describes tracking brand visibility across AI answers including AI Overviews and AI Mode, ChatGPT, Microsoft Copilot, Gemini, and Perplexity, with mentions, citations, and competitor benchmarking. Source: the Brand Radar product page.
• Otterly.ai lists monitoring for ChatGPT, Perplexity, AI Overviews, AI Mode, Gemini, and Copilot, and defines a share-of-AI-voice metric as the percentage of citations you own versus competitors. Source: the Otterly.ai site.
• Profound lists Perplexity, ChatGPT, Claude, Gemini, Grok, Microsoft Copilot, DeepSeek, and Google AI Overviews among tracked surfaces. Source: the Profound site.
• Semrush's knowledge base defines its AI Visibility Score as how often a brand is mentioned in AI answers relative to the median of top industry competitors. Source: the Semrush AI SEO Toolkit knowledge base.

Every tool above samples prompts it chooses, on a cadence it chooses, from accounts it controls, and each composes its metrics differently. That does not make the tools useless; it makes them incomparable with each other and with your panel. The schema is how you stay sane using any of them: tool numbers land in their own labeled columns, your frozen-panel observations land in theirs, and no rate is reported without its denominator. How to interrogate a vendor's sampling before trusting its trendline is covered in the AI visibility tools guide.

Tool: The classification checks carry weight three in the audit model. Mention and citation classified separately, absences logged, accuracy graded against an approved ledger: the interactive checker scores whether your tracking discipline would survive an audit review.

Running an AI citation audit with the schema

A citation audit is the point-in-time version of tracking: one wave, fully classified. Run the frozen panel, log every observation including absences, then classify each engine-answer pair into one of four states: cited (an owned URL appears as a source), mentioned without citation, cited via third party (a page about the brand, owned by someone else), or absent. The third state is the one that changes roadmaps, because it tells you which external pages currently carry your visibility and whether you can influence them.

Two rates per engine per stratum summarize the wave honestly: mention rate and owned citation rate, each over valid observations. Resist the composite score. A single blended number hides exactly the difference the audit exists to surface, and the report template shows how to present the two rates with their limits attached. Referral traffic joins the picture from analytics separately; ChatGPT referrals are attributable through the utm_source=chatgpt.com parameter documented in OpenAI's publisher FAQ, and Microsoft's side has its own first-party reporting covered in the Bing AI performance guide.

Our position

Track citations weekly by hand before buying anything. Twenty prompts, two engines, three runs, classified into the schema, takes an afternoon and teaches you what the numbers mean: how much answers vary between identical runs, how differently engines surface sources, and how often a mention carries no citation at all. An agency that learns those textures first can evaluate any tool's claims against its own observations. One that starts with a dashboard inherits a methodology it cannot see and reports numbers it cannot defend.

Citation tracking cannot promise citations, and nothing in this workflow makes an engine cite anyone; the schema only guarantees that whatever happens is recorded well enough to act on. The honest promise is smaller and more useful: comparable waves, defensible rates, and a clear view of which sources actually carry the brand's presence in AI answers.

Google documents exactly one technical requirement for appearing in AI Overviews and AI Mode: the page must be indexed and eligible to show in Google Search with a snippet, meeting the ordinary Search technical requirements. No special markup, no AI files, no new optimization layer. Everything else circulating as an "AI Overview requirement" is either a normal SEO practice wearing a new label or an invention. The matrix below sorts the circulating claims into documented, control, and invented, each against Google's own pages, so an audit can check what is real and skip what is not.

What Google actually documents

The authoritative page is short, which is itself the finding. Google's AI features and your website documentation states there are "no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary," and that eligibility means a page is indexed and eligible for a snippet under the standard technical requirements. It states directly that you do not need to create new machine-readable files, AI text files, or markup for these features. The positive advice it offers is the same foundational SEO Google recommends everywhere.

The documentation adds two structural facts worth knowing. AI features ride the normal Search index, which is why Googlebot's robots.txt rules are the access control; there is no separate AI Overviews crawler to allow or block. And AI Mode uses what Google calls query fan-out, issuing related searches to surface a wider set of links, which explains why pages can appear for prompts they do not literally match without any special preparation.

Key facts, checked August 23, 2026

• Google states there are no additional requirements and no special optimizations needed to appear in AI Overviews or AI Mode; eligibility is being indexed and snippet-eligible. Source: AI features and your website, page last updated December 10, 2025.
• The documented content controls for AI features are the standard ones: nosnippet, data-nosnippet, max-snippet, and noindex, plus robots.txt rules for Googlebot.
• Google-Extended is a robots.txt control token, not a crawler with its own user agent, and it governs use of content for training future Gemini models and for grounding. Google states it does not impact a site's inclusion in Google Search and is not a ranking signal. Source: Google's common crawlers documentation, page last updated July 14, 2026.
• Google states AI-feature traffic is included in overall Search traffic in Search Console, with no separate AI segment.

The requirement and myth matrix

Each row pairs a claim you will meet in audits, sales decks, and first-page SEO content against what Google's documentation actually supports. Three verdicts: documented (Google says it), control (real, but it limits AI appearance rather than earning it), and invented (no Google documentation supports it as an AI requirement).

The Google-Extended row deserves the careful phrasing, because it is the most consequential confusion in client work. Google publishes no sentence connecting Google-Extended to AI Overviews in either direction. What it publishes is the pair of facts above, and an auditor should present them side by side rather than asserting a link Google has not documented. A client who wants out of Gemini training but wants Search visibility is making two separate decisions with two separate controls, the same split OpenAI's crawlers require, as covered in OAI-SearchBot vs GPTBot.

Tool: The technical checks in the audit model stop at what platforms document. Public responses, robots rules, indexability, rendered text, and structured data agreement, each with dated evidence and none of the invented requirements. The checker scores your protocol against all 47 checks.

Why the myths persist

The invented requirements share one shape: they take a sensible content practice, relabel it as an eligibility gate, and sell urgency. Answer-first writing, clean structure, and accurate schema are all defensible craft, and none of them is a documented AI requirement. The distinction matters commercially because a requirement justifies emergency remediation budgets and a practice justifies ordinary editorial investment, and clients are currently buying a lot of the former priced as the latter.

The honest technical audit for Google's AI features is therefore almost identical to a competent indexing audit: public response codes, index and snippet eligibility, rendered text, snippet controls set intentionally rather than by accident, and structured data that agrees with visible copy. That work belongs inside the technical section of the audit worksheet, with a date on every piece of evidence, and it needs no AI-specific tooling to complete.

Our position

When a vendor claims a technical change is required for AI Overviews, ask for the Google URL. That single habit sorts the market: documented claims have one, and invented ones route to a blog post citing another blog post. Our position is that an agency should hold itself to the same test in reverse: never bill an AI eligibility fix you cannot anchor to a platform document, and label everything else as content strategy, which can be excellent work as long as it is sold as what it is.

None of this predicts appearance. Google states AI Overviews show only when its systems decide they add value, and being eligible makes appearance possible, not likely, a boundary this site applies to every engine. What eligibility work buys is the removal of self-inflicted absence, and that is worth exactly the modest, checkable effort it takes. The structural differences between Google's merged approach and the opt-in crawler architecture on other platforms are mapped in GEO vs SEO, and the reporting side, where AI traffic hides inside ordinary Search numbers, is covered for Microsoft's more transparent equivalent in the Bing Webmaster Tools AI performance guide.

Write the executive summary last, from proposal documents that already agree, and it becomes the easiest section in the application: six sentences covering request, need, response, outcome, credibility, and fit, each pulled from a section that already exists. The template below adds the step most summary advice skips: a reconciliation table you complete before drafting, so the summary physically cannot claim a number, a participant count, or an outcome that the rest of the proposal does not support.

Read first, written last

The executive summary carries an asymmetry that explains almost everything about how to write it. Candid's proposal guidance notes that a reviewer often reads the summary first to decide whether to continue reading at all. Yet the summary is the one section that cannot be drafted until everything else is finished, because its entire job is to compress documents that must already agree.

That is why "start with a strong hook" advice underserves this section. A reviewer who reads sixty proposals is not hooked by prose. They are checking, in half a page, whether the request coheres: does the dollar amount match the budget, does the participant count match the program, does the outcome promised match anything the evaluation plan can measure. A summary that survives that check earns the rest of the read. One that fails it ends the read early, exactly because it was read first.

The template treats the summary as a compression artifact, not an opening argument. If a sentence in it cannot be traced to a finished section of the proposal, the sentence is invented, and invented sentences are what reviewers catch.

Complete the reconciliation table before drafting

Fill this table from the finished proposal, taking each value from the named source document rather than from memory. Memory is where drift comes from: the narrative said 60 students in April, the budget was rebuilt for 48 in May, and the summary written in June splits the difference.

Then run the consistency checks: the request matches the budget total exactly, the participant count is identical everywhere it appears, the outcome commitment exists verbatim in the evaluation plan, and the staffing summary matches the personnel lines in role and effort. Every one of these is a check a reviewer can run in two minutes with the full proposal open, which is precisely why the summary must pass it first. This is the same cross-document discipline the full proposal template enforces section by section; the summary is where all of it becomes visible at once.

The six-sentence template

One sentence per slot, expanded to two only where the funder allows more than half a page.

1. Request: [Organization] requests $[amount] from [funder] for [project name], a [duration] program serving [number] [population] in [location].
2. Need: [Population] face [problem], evidenced by [strongest statistic with source and date].
3. Response: [Project name] will [core activity] at [frequency and duration], delivered by [staffing summary].
4. Outcome: By [date], the program commits to [measurable outcome], measured by [instrument or data source].
5. Credibility: [Organization] brings [years serving this population, prior results, or the relevant partnership].
6. Fit and sustainability: The request covers [what the money buys]; [other funding status], and [what continues after the grant].

Worked example: The six sentences for a fictional home-visiting program

Alder Grove Family Services is a fictional nonprofit used only to demonstrate the template; every figure is illustrative.

Alder Grove Family Services requests $62,400 from the Linden Trust to operate First Steps Home, a twelve-month home-visiting program serving 35 first-time parents in Harmon County. County health department data from 2025 (a fictional figure for this example) place Harmon County's rate of missed well-child visits at 28 percent, against 17 percent statewide. First Steps Home will deliver twice-monthly structured home visits over ten months per family, provided by two trained parent educators at 0.5 FTE each. By August 2028, the program commits to 85 percent of enrolled families completing at least 16 of 20 scheduled visits, measured through the program's visit log and verified against clinic attendance records. Alder Grove has provided family support services in Harmon County for nine years and operates the county's only bilingual parenting program. The request funds the two educator positions and program materials; a committed county contract covers supervision and facilities, and the county has budgeted to sustain one educator position after the grant year.

Every fact in those six sentences exists elsewhere in the fictional proposal: the $62,400 is the budget total, the 35 families appear in the program description and the per-family cost math, and the 85 percent completion commitment is the evaluation plan's first indicator. Nothing was written for the summary.

Download: Executive summary template (Markdown template). The reconciliation table with its consistency checks, the six-sentence template with every slot, and the format override checklist, as one copyable file you can drop into your proposal folder.

When the funder's format overrides the template

The funder's instructions replace this structure wherever they differ. Some foundations ask for a one-page summary with named headings; some want three sentences in a cover letter; many application portals replace the summary with fixed fields. Federal applications frequently require a separate project abstract with its own rules: the standard federal Project Abstract Summary form caps the abstract at 4,000 characters and warns that it will be published publicly if the project is funded, which changes what belongs in it. Check the live opportunity on Grants.gov rather than assuming the foundation pattern carries over; a public abstract written like an internal summary can expose partner names and figures you did not intend to publish.

The six sentences still earn their keep under every format, because they are the content inventory. A three-sentence version keeps the request, response, and outcome sentences. A one-page version expands each slot to a short paragraph. The reconciliation table does not change at all, because no format excuses a summary that disagrees with its own proposal.

Our position

Most executive summary advice weights the section by coverage: so many percent for need, so many for outcomes. That framing misses what the section is for. A summary is not a miniature proposal; it is proof of coherence. The reviewer's real question is whether the organization can state its own request without contradicting itself, and a six-sentence summary that reconciles perfectly outperforms a page of eloquent coverage that fumbles one number. Coherence is also the honest reason to write it last: not writing ritual, but the fact that agreement between documents is the only thing the summary can actually prove.

A strong summary cannot guarantee funding, and no template can promise a funder's decision; what it removes is the fastest reason to stop reading. Once the six sentences reconcile, the same fact base feeds every other compressed surface of the application: the complete annotated sample proposal shows a finished summary in context with the sections it compresses, and the core narrative template keeps the approved facts stable so next quarter's summary starts from the same source instead of from memory.

Below is a complete worked logic model for a fictional nonprofit job-readiness program: five columns, an assumptions row, and every number carried through so you can see how the columns earn each other. Reading a finished model is how the format actually clicks, but the example is only half the value. The other half is the alignment walkthrough: three misalignments this model shipped with in its first draft, how a reviewer catches each one, and a downloadable rubric for running the same review on your own model.

The worked nonprofit logic model

Worked example: Fairview Employment Alliance models its job-readiness program

Fairview Employment Alliance is a fictional nonprofit invented for this example; every figure is illustrative. Its program, WorkReady, serves 48 unemployed and underemployed adults a year in three 12-week cohorts of 16.

The arithmetic that makes the columns trust each other: 2 workshops x 12 weeks x 3 cohorts = 72 sessions. 16 participants x 4 coaching sessions x 3 cohorts = 192. 3 panels x 3 cohorts = 9. Each output is a consequence of the activity schedule, not a separate wish.

The five-column vocabulary comes from the W.K. Kellogg Foundation's Logic Model Development Guide, still the sector's reference document: resources and activities are "your planned work," while outputs, outcomes, and impact are "your intended results," with outputs defined as the direct products of program activities. Kellogg also puts rough clocks on the results side: short-term outcomes within 1 to 3 years, longer-term outcomes within 4 to 6, impact at the community or system level in 7 to 10. A 12-week program promising community-level change inside a grant year has answered a question nobody asked.

Logic model inputs examples: nouns with quantities

The inputs column fails by vagueness more than by omission. An input is something the program consumes, written so a stranger could price it.

Entries that pass: 0.5 FTE program coordinator at a stated salary share; 12 trained volunteer tutors averaging 2 hours a week; a $3,600 curriculum license; two donated classrooms with the donor named; a 24 percent documented fringe rate. Entries that fail: community support, strong partnerships, dedicated staff, technology. The failing entries are not false; they are unpriceable, and a reviewer who cannot price the inputs column cannot check whether the activities are affordable. Every passing entry also has a second home waiting for it: the same quantities become the personnel and cost lines of the grant budget, which is the fastest consistency check in the whole application.

Logic model activities examples: verbs with a dose

Activities are what the program does with the inputs, and each one needs a frequency and a duration because dose is what connects an activity to any believable outcome.

Entries that pass: run two 2-hour workshops weekly for 12 weeks; deliver 4 coaching sessions per participant; conduct monthly home visits for 10 months; train tutors in a 12-hour August institute. Entries that fail: provide support, offer mentorship, raise awareness, engage the community. An activity with no dose cannot be costed, cannot be scheduled, and cannot be tested against the outputs column, so it quietly exempts itself from every review the model exists to enable.

The alignment walkthrough

A logic model earns its keep when its numbers survive contact with the other proposal documents. Walk the Fairview model through four checks.

Inputs against the budget. Every input traces to a budget line or a named in-kind commitment: the $27,000 salary share, the $18,000 of coach hours, the $3,600 license. If the model lists a laptop lab and the budget has no equipment, replacement, or insurance line, one of the two documents is wrong.

Activities against the outputs. The multiplication above either works or it does not. First drafts routinely fail it, because the columns get filled on different days by different optimism levels.

Dose against the evidence. The 80 percent attendance output is not decoration: the curriculum publisher's evidence assumes participants actually receive the workshops, so attendance is a stated delivery requirement. Whatever supports your outcome claim, published evidence, prior program data, or a declared professional rationale, it assumes a dose, and the model must deliver that dose on paper.

Outcomes against the evaluation plan. Each outcome names its instrument: the portfolio checklist, the mock-interview rubric, the 6-month follow-up. The evaluation plan should measure exactly these, with the same wording. The CDC's program evaluation framework makes describing the program the second step of any credible evaluation precisely because an unaligned model leaves the evaluator measuring things the program never promised. One translation note from the CDC's own materials: its format treats outputs as an indicator that can live in the narrative rather than as a mandatory column, so when a funder supplies a form whose labels differ from Kellogg's, map your entries onto their structure instead of arguing with it.

Three misalignments and their fixes

The first draft of the Fairview model contained all three of the failures reviewers see most, planted here on purpose.

Output inflation. The draft said 90 workshops. The schedule supports 72. The fix is not averaging; it is recomputing the output from the activity schedule and letting the smaller, checkable number stand.

An outcome hiding in the outputs column. The draft listed "48 participants gain interview skills" as an output. The sorting rule: if the number can go up without any participant changing, it is an output; otherwise it is an outcome and needs an instrument and a timeframe. Skill gain moved to short-term outcomes and acquired the rubric.

An unresourced activity. Employer panels appeared in the activities column, but no coordinator hours or budget line paid for recruiting employers. The honest fixes are to resource the activity or cut it; the draft that leaves it unresourced is promising free work from a column that is supposed to be priced.

Download: Logic model review rubric (CSV rubric). Twelve review questions across resources, activities, outputs, outcomes, the long-term claim, assumptions, and cross-document alignment, each with the pass evidence to look for and the common failure it catches. Score 0, 1, or 2 per row before the model feeds the narrative or budget.

Our position

Study one worked model deeply rather than skimming ten. This is a logic model example nonprofit teams can actually check, and checkability is the point: galleries of models from other sectors read well and teach little, because the format is not the hard part; the arithmetic between the columns is, and you only see it when an example carries real numbers end to end. Build your own model with the people who will run the program, run the rubric on it, and treat every red cell as a finding about the program plan, not about the diagram.

A clean, aligned logic model cannot guarantee an award, and no diagram can. What it does is remove the contradictions that make reviewers stop trusting a proposal, and it hands every downstream document a single set of numbers to inherit. The column mechanics and the four arrow tests behind this walkthrough are covered in the logic model template; the budget side of the same discipline, explaining each cost's basis and purpose, is in the budget narrative template.

A budget narrative explains, line by line, what your budget spreadsheet cannot say for itself: the calculation behind each number, the program activity it pays for, and how shared costs were split. The template below gives every line item the same three-question pattern, basis, purpose, and allocation, with a worked personnel example and category blocks you can copy. Federal guidance asks reviewers to check consistency between the budget and the work plan, and foundation reviewers run the same check without announcing it, so the narrative's real job is proving the numbers and the program are one plan.

What a budget narrative is, and what it is not

The budget narrative (many funders say budget justification; the two names describe the same document, and the funder's label wins) is prose that accompanies the line-item budget. The spreadsheet shows the numbers; the narrative shows the reasoning. Candid's proposal guidance describes the budget as the financial plan for the project, expenses and income for a stated period, and the narrative is where that plan proves it was derived from the program rather than invented beside it.

What the narrative is not: a restatement. A narrative that walks through the spreadsheet repeating totals ("Personnel: $19,344. Fringe: $4,254.") adds pages without adding evidence, and it creates a second copy of every number that can now drift from the first. The working rule that prevents both failures: numbers live in the spreadsheet, reasoning lives in the narrative, and each narrative block references its line rather than duplicating it.

Key facts, checked August 23, 2026

• Under 2 CFR 200.414, a recipient without a current negotiated indirect cost rate may elect a de minimis rate of up to 15 percent of modified total direct costs. The regulation states the election does not require documentation to justify its use and may be used indefinitely.
• The same cost principles require each cost to be charged consistently as either direct or indirect, never both.
• Federal budget-narrative guidance distributed with funding opportunities asks applicants to justify the need for and reasonableness of each cost, show the calculations, and demonstrate consistency between the budget and the project narrative or work plan. Start from the live opportunity's own instructions on Grants.gov, because the required format varies by agency.

Three questions every line must answer

The template applies one pattern to every line item in every category.

Basis: what is the arithmetic? Unit, quantity, rate, and the rate's source. "$4,800 for travel" is a number; "1,200 miles per quarter x 4 quarters x the current IRS standard mileage rate, for home visits across the county" is a basis. The rate source matters as much as the math: payroll for salaries, a vendor quote for equipment, a published price for licenses.

Purpose: which activity does it buy? Every line names the program activity it delivers, in the program plan's own words. This is the sentence that lets a reviewer read the budget and the narrative as one document, and its absence is what makes a budget feel padded even when it is not.

Allocation: how was a shared cost split? Any cost shared with other programs or funders states its split method: FTE share for people, square footage for space, usage counts for equipment. An unexplained partial cost invites the one question you never want in review: what is the rest of this, and who is paying for it?

Worked example: A personnel block that answers all three questions

The organization and figures are fictional, illustrating the pattern.

Program coordinator (0.5 FTE of a $54,000 annual salary = $27,000). Basis: effort estimated from the activity plan at 20 hours per week, covering delivery of six weekly workshop hours, coaching session scheduling, employer panel recruitment, and attendance tracking. Purpose: coordinates every WorkReady activity named in the program description. Allocation: the remaining 0.5 FTE is charged to the organization's state workforce contract; total effort across all funders is 100 percent, reconciled in the organization's effort ledger.

Fringe benefits at the organization's documented composite rate of 22 percent are charged on the salary amount charged to this grant: $27,000 x 0.22 = $5,940. The rate covers payroll taxes, health insurance, and retirement match.

Three sentences per role, and the reviewer can rebuild the number, find the activity, and see that no one is budgeted past 100 percent of a human being.

The category blocks

The downloadable template carries a block for each standard category, each running the same pattern with its category-specific trap named.

Personnel and fringe. The trap is double counting: fringe computed on full salaries instead of charged salaries, and people whose effort across all grants exceeds 100 percent. The staff-time math, with the effort-ledger check worked in numbers, is covered in the grant budget template.

Travel. Name the trips, the rate, and the program reason. Local mileage uses the current IRS standard rate; conference travel names the event and who attends, because unnamed travel reads as a slush line.

Equipment and supplies. Quantity times unit price with a quote source. Check the funder's equipment threshold; items above it usually need their own justification and a useful-life note.

Contractual. The deliverable, the rate, and how the rate was established: competitive quotes, a prior contract, or a published rate. A contractor line with no rate basis is the line reviewers question first.

Indirect costs. A rate, a base, and a source for both. On a federal award with no negotiated rate, elect the de minimis rate and compute the modified total direct cost base explicitly, naming what you excluded from it. For foundations, cite the funder's own overhead policy instead; quoting federal regulation at a funder it does not bind signals template reuse, not diligence.

Download: Grant budget narrative template (Markdown worksheet). The three-question pattern, a copyable block for every budget category with its trap named, and the six-check alignment pass, as one file you can fill beside your budget spreadsheet.

The alignment pass

Before submission, read the finished narrative against the other documents rather than against itself. Every activity in the program narrative has money behind it, and every budget line has an activity in front of it. Personnel names, titles, and effort levels match the program narrative exactly. Participant counts used in any per-unit math match the counts in the needs statement and outputs; if you built a logic model, its resources column and your budget lines should be the same list wearing different clothes. Multi-year requests explain each year separately and declare any inflation assumption. And the funder's own budget form, category names, and caps override this template wherever they differ.

This pass belongs on the calendar, not in the final hour: it is the same coherence gate the submission checklist runs, and it exists because last-week edits are where the narrative and the spreadsheet quietly stop agreeing.

Our position

Write the budget first and the narrative second, always in that order, and treat any sentence you cannot back with a line item as a finding about the budget. Teams that draft the narrative first end up justifying numbers that do not exist yet, which produces the most dangerous document in grant writing: fluent prose about an unpriced plan. The narrative is a proof, not a pitch, and a proof of nothing reads exactly like what it is.

A complete budget narrative cannot guarantee funding, and no document can promise a funder's decision. What it removes is the most checkable class of doubt: whether the organization can explain its own numbers. A narrative whose every line survives the basis, purpose, and allocation questions leaves a reviewer with only the judgment calls, and judgment calls are the argument you actually want to be having.

You become an instructional designer by proving you can run the workflow, not by collecting credentials: learn the analysis-to-evaluation sequence, build two or three case studies from realistic projects, and apply through the door your current background already opens. Most working designers entered from adjacent jobs, teaching, training, technical writing, or subject-matter expertise, and hiring reviewers screen demonstrated work far harder than they screen degrees. The table below maps each starting point to what it already proves, what it is missing, and the first project that closes the gap.

What do instructional designers do all day

Instructional designers turn a performance problem into learning that demonstrably works: they analyze what is broken and whether training can fix it, write measurable objectives, design and storyboard the learning experience, build or oversee the build, and evaluate whether anything changed. The day-to-day mix varies by employer: corporate roles skew toward eLearning production and stakeholder management, higher education roles toward supporting faculty and course standards, K-12 and government toward curriculum and compliance.

Federal statistics split the work across two occupations, which matters for every salary and outlook number you will read. The U.S. Bureau of Labor Statistics files corporate-style work under training and development specialists, with a bachelor's degree as the typical entry education and projected employment growth of 11 percent from 2024 to 2034, much faster than average. Education-system roles map to instructional coordinators, where the typical entry bar is a master's degree, often with licensure for public school positions, and projected growth is 1 percent. Both pages reflect May 2024 data, last updated August 2025. The title you will apply under straddles the two, and so do the expectations: the corporate door is credential-light and evidence-heavy, the education door is the reverse.

The five starting points, mapped to evidence

The useful question is not "am I qualified" but "what does my background already prove, and what is the first artifact that proves the rest." Every path below ends at the same destination: a small portfolio whose case studies show the full workflow, held to the standard in the portfolio evidence guide.

The pattern in column four is deliberate: reviewers doubt whatever your background did not force you to do, so the first project attacks the doubt directly rather than restating the strength.

The degree question, answered by door

The instructional designer requirements you will actually meet are door-dependent. For corporate and most remote roles, employers typically expect a bachelor's degree in something, and demonstrated work decides the rest; a master's in instructional design is one route to the theory but not a screening requirement most corporate reviewers apply. For public school and many higher education positions, the master's and licensure expectations are real gatekeeping, per the BLS instructional coordinator profile above. So the degree decision is a door decision: pursue graduate credentials if you want the education-system door, and spend the same money and months on demonstrated work if you want the corporate one. Whether a certificate shortcut helps, and what the real programs cost, is its own decision with its own page: the instructional design certificate guide.

No experience is an evidence problem, and evidence can be built

The search language here is blunt, how to become an instructional designer with no experience, or how to become an instructional designer without a degree, and both questions share one answer: the same path, with the practice projects doing more of the work. Choose a realistic workplace performance problem, run an honest training needs analysis on it, storyboard the resulting course with the storyboard template, build one polished module, and write the whole thing up as a case study that shows your decisions and their reasons. Label practice work as practice work: reviewers do not penalize honest scenarios, and they end conversations over fabricated clients. Two or three case studies at that standard outweigh any bullet point you could write about potential.

What to skip is equally specific: tool-tutorial collections with no design decisions, certificate stacking as a substitute for artifacts, and applying with a portfolio of decorative slides. Reviewers open a portfolio to answer one question, whether you can run the workflow, and everything that does not answer it is noise.

Is it a good career right now

The demand picture is mixed and honestly stated: strong projected growth on the corporate side (11 percent, much faster than average), flat on the education side (1 percent), per the BLS pages above. Remote work is genuinely common in corporate instructional design, and the field's pay spread is wide enough that the salary evidence deserves its own reading before you commit. On AI: production tooling is changing quickly, and the durable parts of the role are the ones tools do not own, deciding whether training is the fix, defining measurable outcomes, and evaluating whether they happened. A candidate whose portfolio demonstrates exactly those judgment layers is positioned for the version of the field that is arriving, not the one that is leaving.

Our position

Pick the door first, then spend accordingly. The most expensive mistake career changers make is buying credentials for the corporate door, which screens on evidence, or skipping credentials for the education door, which screens on them. The second most expensive mistake is postponing the portfolio until after a course, a certificate, or a degree finishes, when the portfolio is the artifact every door eventually asks for and the one thing no purchase produces on your behalf.

A path, a course, or a portfolio cannot guarantee employment, and this page will not pretend otherwise; hiring runs on openings, timing, and competition that no preparation controls. What preparation controls is narrower and decisive: whether, when a reviewer opens your work, they find evidence of the whole workflow or just claims about it.

An instructional design certificate is optional for the corporate door and insufficient for the education door, which makes it a purchase to reason about, not a requirement to meet. Functionally similar credentials currently run from $350 to $5,245, a fifteenfold spread for programs that all end in a non-degree certificate, so if you buy one, buy it for the structured, deadline-driven practice that produces portfolio artifacts, never for the paper alone. The price table and the four-question decision framework below are the whole decision.

Three different things share the name

Certificate language in this field is genuinely confusing, and the confusion is load-bearing for a lot of marketing.

A continuing education certificate is a non-credit program from a university extension school or training company: weeks to months, no academic credit, a completion document at the end. Most products called "instructional design certificate" are this. A graduate certificate is a for-credit academic credential, typically 12 to 18 credit hours that can sometimes ladder into a master's; it lives on a transcript and matters most at the education-system door, where degrees are screened. A certification in the strict sense, a credential you test into and renew against a standard, does not exist for instructional design; no license or board governs the title, so anything sold as making you "certified" is a completion certificate with confident wording.

Knowing which of the three a program is tells you most of what it can do for you before you read a single curriculum page.

What real programs cost right now

Searches for an instructional design certificate online, or for the best instructional design certificate programs online, surface dozens of roundups that rarely show verified prices, so here are four representative programs read from each provider's own page on August 23, 2026. All four are online instructional design certificate programs or offer a live-online format. Prices and cohort details change; verify on the provider's live page before paying anything.

Key facts, checked August 23, 2026

• ATD's Instructional Design Certificate lists at $2,245 for members and $2,545 for non-members, delivered face to face or live online, awarding 2.1 CEUs. Source: the ATD program page.
• The University of Washington's Certificate in E-Learning Instructional Design lists at $5,245 for four courses over eight months, about 7 to 9 hours per week, fully online. Source: the UW Professional and Continuing Education page.
• Oregon State University's E-Learning Instructional Design and Development Certificate lists at $2,395 plus a $70 registration fee, five six-week courses fully online and asynchronous, awarding 12.6 CEUs. Source: the OSU program page.
• The University of New England's Instructional Design Certificate lists at $350 for eight weeks, asynchronous online, 60 contact hours and 6 CEUs. Source: the UNE program page.

The spread is the finding. These four programs differ in depth, faculty attention, and project structure, but all four end in a non-credit completion certificate, and no employer screening pile distinguishes their papers the way the prices differ. What actually varies with price is structure: contact hours, feedback on your work, and how much finished artifact you leave with. That is the honest thing the money buys, and it is worth paying for exactly when you would not produce the work without it.

The four-question decision framework

Which door are you walking through? Corporate and remote employers screen portfolios and rarely require certificates; public school and many higher education roles screen degrees and licensure, where a continuing education certificate does not substitute. If your target is the education door, compare graduate certificates and master's programs instead, a different purchase entirely, as mapped in the career path guide.

What does your background already prove? A teacher buying a certificate to learn objectives and sequencing is buying what they own. The gap analysis in the career guide's starting-point table is the shopping list; buy against your actual gaps, which for most career changers are eLearning production and workplace analysis, not learning theory.

Do you need external structure to finish work? This is the strongest honest reason to buy. If three months of self-directed portfolio building would quietly become zero months, a cohort with deadlines and feedback is cheap at $350 and defensible at $2,400. If you reliably finish self-directed work, the same portfolio is buildable from free and low-cost materials plus the working templates on this site, starting with the needs analysis template and the storyboard template.

What else could the money buy? $5,245 is also: a laptop that runs an authoring tool, a year of software licenses, several books, and months of unhurried portfolio time. Price the certificate against that basket, not against zero. And the common search for an instructional design certificate, free and online, mostly maps to free learning without the credential document, which is fine if the skills were the point.

What a certificate cannot do

A certificate cannot substitute for work samples, because reviewers screen the portfolio and treat credentials as tiebreakers; a certificate line with no artifacts behind it reads as a course taken, not a capability held. It cannot make you "certified" in any regulated sense, because no such regulation exists. And it cannot guarantee employment or any hiring outcome, a promise some program marketing edges toward and no honest page will make; completion rates are not placement rates, and placement claims without method behind them are marketing.

What it can do, bought for the right reason, is real: force finished work out of you on a schedule, put experienced feedback on that work, and leave you with two or three artifacts that belong in the portfolio the certificate was never a substitute for.

Our position

Buy structure, not signaling. The certificate-as-signal theory fails on contact with how screening works: reviewers spend their first minute on work samples, and no completion certificate survives a weak portfolio sitting next to it. The corollary cuts both ways: if a program's pitch leans on its paper, walk; if its pitch leans on the projects you will finish and the feedback you will get, it is at least selling the thing that matters, and the remaining question is only whether the price beats building the same artifacts on your own discipline.

The salary pages you will read while deciding deserve the same skepticism as the program pages; the salary evidence guide separates federal survey data from self-reported estimates so the return side of this purchase is at least computed on honest numbers.

Federal wage data puts the median at $69,280 for training and development specialists and $77,440 for instructional coordinators, the two occupations instructional design straddles, per the May 2025 BLS survey. Self-reported job-board figures run higher: Glassdoor's median total pay estimate is around $92,000 and Payscale's average base is about $72,800 as of their August 2026 pages. The sources disagree because they measure different things with different methods, not because one is lying, and the table below shows the full percentile spread with every method labeled.

No federal category says "instructional designer"

The first honest fact about instructional design pay is that the federal wage survey has no occupation code for it. The Bureau of Labor Statistics' Occupational Employment and Wage Statistics program files the work under two codes, and which one describes your target job changes the numbers materially.

Training and development specialists (SOC 13-1151) covers the corporate side: designing and delivering workplace learning. It employed 458,300 people in the May 2025 survey. Instructional coordinators (SOC 25-9031) covers the education-system side: curriculum and instruction standards work, employing 227,760, concentrated in elementary and secondary schools, universities, and educational support services. A corporate eLearning designer maps mostly to the first; a school district or university instructional designer mostly to the second. Job postings titled "instructional designer" draw salary ranges from both pools, which is one reason posted ranges vary so widely. Degree-linked searches, instructional design and technology salary among them, land in the same two occupations; the degree name does not create a third pay pool.

The percentile table, from the federal survey

Figures are annual wages for the United States from the BLS Occupational Employment and Wage Statistics profiles, May 2025 reference period, read August 23, 2026. OEWS is an employer survey, so these are wages employers report paying, base pay without bonuses or equity.

Read as a career arc rather than a snapshot: the 10th-to-25th band approximates entry-level pay, the median is the mid-career center of gravity, and the 75th-to-90th band is where senior, lead, and specialized roles live. Both occupations crack $120,000 at the 90th percentile, which is the honest version of the "six-figure instructional designer" claim: real, and roughly a top-decile outcome, not a typical one.

Why Glassdoor and Payscale say something different

Job-board numbers are self-reported by people who chose to file a salary, which skews the sample toward corporate, current, and confident respondents, and some sites report total pay rather than base.

As of pages read on August 23, 2026: Glassdoor's instructional designer page estimates median total pay near $92,000 with a typical range of roughly $74,000 to $117,000, total pay including bonus estimates on top of base. Payscale reports an average base of $72,801 from 2,283 self-reported profiles, with a $55,000 to $96,000 range between its 10th and 90th percentiles.

The reconciliation is method, stated plainly: a federal employer survey averaging across every sector including lower-paying school systems sits below a self-selected sample of corporate professionals reporting total compensation. Neither number is wrong; they answer different questions. Use OEWS to understand the occupation, and use the self-reported sites as directional evidence about the specific corporate title, weighted by their disclosed sample sizes and dates.

What actually moves the number

Sector. The single biggest lever. The instructional coordinator pool is dominated by education employers, and school-system pay bands sit below the corporate market for similar skills. The same person crossing from a university ID role to a corporate L&D role often crosses several deciles of the table above.

Seniority and scope. The search language tracks the bands: entry level instructional designer salary questions map to the 10th to 25th percentiles, and senior instructional designer salary questions to the 75th and above. Senior pay arrives with scope: owning programs, stakeholders, and evaluation rather than producing assigned modules.

Industry within corporate. Glassdoor's self-reported industry cuts show regulated and technical industries, pharmaceuticals and aerospace among them, estimating noticeably above the overall median; treat these as self-reported signals rather than survey facts, but the direction matches the seniority logic: complexity and compliance budgets pay for design judgment.

Geography and remoteness. State and metro OEWS figures vary widely, and remote corporate roles increasingly price against national bands rather than local ones, which has generally helped candidates outside major metros.

Evidence at the table. Salary bands are ranges, and where you land in one is a negotiation that runs on demonstrated scope: the portfolio that shows you operating at the level you are pricing. This is also the honest frame for hourly and freelance questions: freelance rates are priced per project on demonstrated capability, and no published average substitutes for evidence of your own work.

Our position

Cite the federal table in decisions and the job boards in conversations. When you are choosing whether to enter the field, comparing sectors, or planning the jump from education to corporate, the OEWS percentiles are the defensible base rates. When you are negotiating a specific corporate offer, the self-reported corporate numbers are closer to that market's own self-image and useful precisely because employers read them too. Confusing the two produces either timid asks built on sector-blended medians or entitled ones built on total-pay estimates, and both lose winnable negotiations.

None of these figures can guarantee any individual outcome, and salary statistics cannot price you: they describe pools you may or may not resemble. What they can do is anchor the decision this cluster exists for, whether and how to enter the field, and put honest return numbers behind any certificate or program purchase you are weighing on the way in.

A hiring-ready entry-level instructional design portfolio is three or four case studies, each proving a different segment of the workflow with visible artifacts: a needs analysis, a design document, a storyboard, and at least one finished interactive build. Reviewers skim before they read, so every case leads with the performance problem and captions every artifact with what it proves. The 30-check screening list below is the pass a reviewer runs in the first few minutes, downloadable as a CSV so you can score your own portfolio before anyone else does.

What a reviewer does with your portfolio

The person who opens your portfolio is rarely settling in to admire it. They are screening, usually between other tasks, and they are trying to answer one question fast: can this person run the workflow our job description implies, or can they only produce artifacts that look like the ones made by people who can?

That distinction decides everything about how the portfolio should be built. A gallery of polished screenshots answers the wrong question. Screenshots show that you can operate an authoring tool, which is worth something: employer job-posting data aggregated by O*NET's in-demand technology skills for instructional designers shows tools like learning management systems, PowerPoint, Camtasia, and Storyline appearing across real postings. But tools are the cheapest thing on that list to demonstrate and the easiest to fake. What screening actually filters on is judgment: whether you can diagnose a performance problem, design against it, defend a decision, and say honestly what the result was.

So the unit of the portfolio is not the artifact. It is the case study: a short, skimmable account of one project that carries its artifacts as evidence. An artifact without a case around it is decoration. A case without artifacts inside it is an unsupported claim.

This is also the right lens for the instructional design portfolio examples and samples that circulate in link roundups: study them for how their case studies argue, not for layouts to copy. An example shows you a finished surface, never the analysis behind it, and the analysis is what a reviewer is hunting for. The same standard applies whether a job posting calls the file an eLearning portfolio or a learning and development portfolio; the label varies, the checks below do not.

Three cases cover the whole workflow

You do not need ten projects. You need the smallest set of cases that, together, prove the full workflow. For workplace learning and development roles, three cover it:

Each case should be scoped to one performance problem. A useful test: if you removed the project's deliverable entirely, would the case still describe a problem worth solving? If not, the case is organized around the artifact instead of the problem, and it will read as a tool demo.

The three cases can come from one scenario. A single workplace problem, followed from training needs analysis through a storyboarded build to a facilitated rollout, produces all three cases with more coherence than three unrelated projects, because the reviewer watches the same evidence move through every stage. It also means that creating an instructional design portfolio starts with choosing a scenario worth diagnosing, not with opening a website builder.

The anatomy of one case study

A case study that survives skimming has six parts, in this order, under headings a reader can navigate by:

1. The problem. Who could not do what, to what standard, and what it cost. One paragraph. No tools mentioned yet.
2. Your role and the constraints. What you specifically did, and the real limits: timeline, budget, tooling, stakeholder availability. Constraints are not excuses; they are the conditions under which your decisions make sense.
3. The analysis. What evidence you collected and what it showed, including the causes training could not fix.
4. The decisions. At least one design decision explained with the alternative you rejected and why. This is the paragraph reviewers quote back in interviews.
5. The artifacts. Each one captioned with what it proves, not just what it is. "Storyboard, screens 1 to 3, showing the branching feedback for the first decision point" beats "Storyboard sample."
6. Results and limits. What was observed, stated separately from what was hoped. If the project was a practice build with no deployment, say exactly that and report what your quality review and pilot testing found instead.

Worked example: A problem statement that carries a case, from a fictional practice scenario

Northstar Systems is a fictional mid-size software company used here as a practice case. A problem statement built from it reads: "Tier-1 support agents resolved 61 percent of refund tickets correctly on first response against a 90 percent standard, producing 31 escalations a quarter. The analysis found three causes: newer agents could not locate the two-step policy check, the correct lookup took five clicks from the ticket screen, and handle-time scoring penalized the agents who did it right. The training response below addresses the first cause; the tooling and scorecard recommendations that address the other two are included in the analysis document." Two sentences of evidence, one sentence of honest scope. A reviewer who reads nothing else now knows this candidate diagnoses before building.

No client work is not the obstacle it looks like

Career changers stall on a false premise: that a portfolio requires employer-sanctioned projects, and that everything else is pretend. Reviewers do not actually hold that standard, and the alternative to practice work is usually worse: real client work you cannot legally show. Which practice project to build first depends on where you are coming from; the career path guide maps each starting profession to the evidence reviewers will doubt and the project that answers it.

Our position

A clearly labeled practice project beats an unverifiable claim about confidential work, and it is not close. A reviewer can evaluate every decision in a practice case because the whole case is visible; a redacted case asks them to trust what they cannot see. The rules that make practice work legitimate are strict, though. Label it as practice, prominently, in the case itself; a fictional scenario presented as a real client is a lie that ends the interview when it surfaces. Build it against a realistic scenario with real constraints rather than an idealized one. And carry it through the full workflow, because the practice cases that fail are the ones that skip the analysis and start at the storyboard, which quietly proves the candidate starts at the storyboard.

Real workplace experience still belongs in the portfolio when you can use it. Teachers, trainers, HR practitioners, and subject-matter specialists usually have more raw material than they think: a process you documented, an onboarding you redesigned, a session you ran repeatedly and improved. The rule is permission and de-identification. Get written permission for anything produced for an employer, strip names and figures that are not yours to publish, and when permission is not available, rebuild the case as an explicitly labeled reconstruction with the sensitive material replaced.

The 30-check screening list

These are the checks a screening reviewer applies, mostly without naming them, grouped by the order in which failures actually eliminate candidates. Five checks on identity and access, eight on case-study structure, seven on artifacts, five on writing, and five on accessibility and polish. The full list with pass conditions ships in the CSV below; the categories and the checks most portfolios fail:

The accessibility rows are not garnish. A portfolio is a work sample, and accessible practice is part of the work being sampled; a candidate whose own portfolio fails basic contrast and alt-text checks is making a claim about their build standards whether they intend to or not. The same discipline shows up inside artifacts: an eLearning storyboard whose columns include alt text and accessibility notes signals the habit better than a paragraph asserting it.

Download: Portfolio screening checklist (CSV, 30 checks). All 30 checks with the reviewer's question and a concrete pass condition for each, grouped by category. Score your portfolio against it before sending it anywhere; every check is written so a friend outside the field can run it for you.

Scoring yourself honestly

Run the checklist as a gate, not a tally. The identity and access checks are pass or fail: a single broken link can end a screening, so fix every one before weighing anything else. In the remaining categories, treat any failed check as a task with a named fix, and re-run the whole list after changes, because portfolio edits have a habit of breaking links and reshuffling order.

Then have one person outside the field run the same list. If they cannot find your strongest case, tell what you did on a team project, or read your objectives as concrete actions, a hiring reviewer will not either, and the reviewer will not email you about it. They will just move on.

A portfolio cannot produce an interview, an offer, or any hiring decision, and this page will not pretend otherwise; hiring runs on more variables than any document controls. What a portfolio built this way can do is narrower and worth the work: it stops being the reason you are screened out, and it gives every later conversation concrete evidence to stand on.

You cannot rank in ChatGPT, because there is no results page, no stable position, and no fixed answer: the same question can produce different brands, different sources, and different descriptions across runs, accounts, and days. What you can do is influence four things that are real: whether OpenAI's crawlers can fetch your pages, whether your content is usable as a source when the assistant searches, how your brand is represented when it does appear, and whether you can measure any of it honestly. This page maps each layer to concrete work, and names the myths that waste budget.

Why "rank" is the wrong verb, mechanically

A classic search engine computes an ordered list for a query and shows everyone roughly that list; rank is a real property of that system. ChatGPT composes an answer. When it answers from model weights alone, your brand's presence depends on how it appeared in training data nobody can inspect or petition. When it decides the question needs fresh information, it runs a search, fetches a handful of sources, and writes a synthesis, sometimes with citations. Two runs of the same prompt can search differently, select differently, and phrase differently.

That variability is not a measurement problem to engineer away; it is the system's actual behavior, and any vendor or consultant promising a "number one spot in ChatGPT" is selling a property the system does not have. The honest reframe: stop asking "where do we rank" and start asking "in a fixed, recorded sample of buyer questions, how often do we appear, as what, and sourced from where." That question has an answer you can defend, and the difference between the two questions is the difference between GEO and SEO as disciplines.

The four layers you can actually work on

The honest version of how to rank in ChatGPT maps onto four layers, and the order matters because each depends on the one before it. This is the same structure as the four-layer model of AI search visibility; here it is applied to ChatGPT specifically.

Layer 1 is where cheap, real wins live. OpenAI operates distinct crawlers with distinct jobs, and sites regularly block the wrong one for the wrong reason. OAI-SearchBot fetches pages for search-backed answers with links; GPTBot collects content for model training; ChatGPT-User acts on live requests a user triggers. Each is documented, with IP ranges, in OpenAI's bot documentation. Blocking GPTBot is a policy decision about training; blocking OAI-SearchBot is a commercial decision about being findable, and inheriting one from the other is the single most common self-inflicted wound in this space. The full separation, and how to audit it, is in OAI-SearchBot vs GPTBot.

Layer 2 is mostly work you already understand. When ChatGPT searches, it needs what any search-backed system needs: pages that load without executing a fragile JavaScript path, say one specific thing checkably, and carry the facts near the claim. OpenAI's own publishers and developers FAQ frames appearing in search-backed answers in terms of being crawlable and useful as a source, not in terms of any special markup. There is no secret ChatGPT meta tag, and anyone selling one is charging for Layer 2 SEO hygiene with a new label.

Layer 3 is the layer buyers feel. A brand can appear in answers and be described wrongly: an old price, a retired product, a competitor's feature attributed to you. Assistants assemble descriptions from whatever sources they trust, so contradictions between your site, your directories, and third-party profiles become contradictions in answers about you. The fix is unglamorous: one set of entity facts, kept identical everywhere the systems demonstrably read.

Layer 4 is what makes the other three billable. Because answers vary, single observations prove nothing in either direction. A defensible measurement is a frozen panel of buyer-decision prompts, run on schedule, with answers recorded before anyone changes anything; the method is specified in how to build an AI visibility prompt set, and the reporting discipline in how to measure AI search visibility.

Tool: If it cannot be scored, it is a slogan. Before spending anything on ChatGPT visibility, score the protocol you would actually run against 47 published checks covering scope, access, prompts, evidence, and handoff. Two minutes, no account, and it grades the method rather than the brand.

The myth table

What an honest ChatGPT engagement promises

Written scope for this work, whether internal or sold, should promise exactly four deliverables: a crawl-access audit with the specific rules found and fixed, a source-eligibility review of the pages that answer buyer questions, a representation baseline recording how the brand is currently described against approved facts, and a measurement panel with its freeze rules and schedule. It should decline, in writing, to promise rankings, citations, traffic, or revenue, because no one controls the model's selection.

That refusal is not modesty; it is the commercial position that survives. The buyer who wanted a ranking guarantee will eventually get one from someone, watch it fail to materialize in any verifiable way, and remember who declined to sell it. Meanwhile the four deliverables above produce observable before-and-after evidence: rules unblocked on a date, contradictions reconciled on a date, appearance rates in a frozen panel moving between observation windows.

This page cannot guarantee that any of it makes ChatGPT mention you, and neither can anyone else; the model's selection is the model's. The work above changes what the system can fetch, verify, and quote about you, and it produces the records that show whether the needle moved. In a market full of ranking promises, being the one with records is the durable advantage.

Below is a complete sample grant proposal for a small nonprofit: a fictional $48,500 request for an after-school reading program, with every section annotated to show the decision it makes and the evidence it stands on. Read the annotations, not just the prose, because the sample's value is the reasoning, and its wording belongs to a fictional organization whose facts are not yours. The full proposal is downloadable at the end, and every name and number in it is invented and labeled as such.

What this sample is and is not

Cedar Bend Youth Alliance is a fictional nonprofit: a $420,000 youth organization requesting $48,500 from an equally fictional community foundation for a two-site after-school reading program. That makes this a complete sample grant proposal for a nonprofit organization at the scale where most first applications actually happen. The sample is written to the standard a real foundation proposal has to meet, and its sections follow the structure most U.S. foundation applications request, the same structure Candid Learning's guide to grant proposals describes: summary, organization background, need, program, objectives, evaluation, budget, sustainability.

What it cannot be is a form to fill in. A funder's own guidelines control the sections, lengths, and order, and where they differ from this sample, the guidelines win. And a sample's sentences fit its own fictional facts; how to pull the structure out of an example without inheriting its wording is its own skill, covered in our section-by-section review of weak and strong proposal passages. The blank structure this sample fills in, with length shares and a failure check per section, is the grant proposal template.

The executive summary, annotated

Cedar Bend Youth Alliance requests $48,500 from the Maple Grove Community Foundation to operate Read Together, an after-school reading program serving 60 students in grades 2 to 4 at two Cedar Bend elementary schools during the 2027 school year. On the district's 2025 state reading assessment (fictional figure), 41 percent of third graders scored below proficiency, against 33 percent statewide, and the two partner schools sit above even that district rate.

What this section is doing. The first sentence carries the five facts a program officer triages on: who is asking, for how much, to do what, for whom, and when. The second states the problem in one number rather than one adjective. The full summary, in the download, closes with the measurable target and one line of credibility. Nothing in it appears for the first time; a summary that mentions something the proposal never develops is a promise the reviewer will go looking for. The drafting method behind a summary like this, including the reconciliation table that keeps its numbers honest, is in the executive summary template.

The statement of need, annotated

At the two schools this proposal serves, Hollis Elementary and Park Lane Elementary, the below-proficiency rates were 48 and 46 percent. ... Both schools operate reading intervention during the school day, but intervention slots cover fewer than half of the students below benchmark, and no structured reading support exists in the after-school hours at either site.

What this section is doing. Three moves, in order. It localizes the problem to the exact sites served, because a statewide number cannot justify a two-school program. It defines the gap as a service gap, which is the only kind of gap a program can close. And it names the community's assets, high attendance, an active volunteer base, a data-sharing agreement, so the program reads as building on strength rather than importing rescue. In a real proposal, every figure would carry a source and date: district assessment reports, and public data platforms like data.census.gov for population and income context. The sample flags its invented figures as fictional precisely where a real proposal would cite.

A full treatment of this section, with a downloadable drafting template, is in our needs statement template; finished passages across six program types are in the companion needs statement examples.

The program description, annotated

Sessions follow a consistent structure: 10 minutes of fluency practice, 20 minutes of guided reading at the student's assessed level, and 15 minutes of paired reading with a volunteer. ... Students are referred by school reading staff from the below-benchmark group not served by in-school intervention, with family consent required for enrollment and data sharing.

What this section is doing. It answers the operational questions a skeptical reader asks in order: what exactly happens, how often, delivered by whom, to which students, selected how, with what consent. Dosage is specific (two 45-minute sessions weekly for 28 weeks) because "ongoing tutoring" cannot be costed or evaluated. The referral sentence quietly proves coordination with the schools instead of claiming it. Note what the section refuses to do: it does not re-argue the need, and it does not describe activities the budget does not fund.

Goals, objectives, and evaluation, annotated

Objective 1: By May 2028, at least 70 percent of students attending 80 percent or more of sessions gain one or more benchmark levels on curriculum-based measurement from the fall baseline.

What this section is doing. One goal, three objectives, each with a number, a date, and an instrument. The 80 percent attendance condition matters: it scopes the outcome promise to students who actually received the program, which is the honest version of the claim. The evaluation section then commits to measuring with the same instrument the district uses, so results are comparable, and states that shortfalls will be reported, not buried. The logic connecting activities to outcomes follows the same program-logic discipline taught in the W.K. Kellogg Foundation's logic model development guide; the logic model template on this site builds that chain column by column.

The budget, annotated

Program coordinator (0.5 FTE of program manager), $24,000. Reading specialists (2 part-time, 28 weeks), $12,600. Books and session materials, $4,200. Volunteer training and coaching, $1,800. Evaluation, $2,400. Administrative allocation, $3,500. Total request: $48,500.

What this section is doing. Six lines that reconcile exactly with the request in the first sentence of the proposal, because the fastest way to lose a reviewer is arithmetic that disagrees with the ask. Every line maps to something the program description said would happen: the specialists deliver the sessions, the materials line buys the 420 titles the program section counted, the evaluation line funds the measurement the objectives promised. In-kind contributions from the district (space, books, data access) are named rather than left implicit, which both strengthens the partnership story and keeps the true program cost visible. The grant budget template carries this reconciliation discipline as working formulas.

Sustainability, annotated

What this section is doing. The weakest sustainability sections promise that the program will "seek diverse funding." This one names three specific sources with a condition attached to each: renewal funding, a measurable donor-base appeal, and a district absorption request contingent on hitting the year-one objectives. Making year-two plans conditional on year-one evidence is not a weakness; it tells the funder their grant buys a real test with a decision at the end of it.

Download: Complete sample grant proposal (Markdown, 8 sections). The full Cedar Bend proposal as one readable file: executive summary, background, need, program, objectives, evaluation, budget summary, and sustainability, roughly 1,100 words, with the fictional labels kept in place. Use it as a structural benchmark beside your own draft, then replace every fact with your organization's verified evidence.

Using the sample without inheriting its facts

Work section by section, and for each one, write down the decision the sample made before you write any prose of your own: what the summary chose to lead with, how the need section localized its numbers, what condition the objectives attached to their promise. Then close the sample and draft from your own evidence file. If a sentence of yours only works because the sample's version worked, it is borrowed confidence, and a program officer who asks one follow-up question will find the gap.

Two boundaries, stated plainly. This sample is fictional teaching material: no Cedar Bend Youth Alliance exists, no figure in it describes a real district, and presenting adapted sample language as your organization's evidence is the exact failure that review processes exist to catch. And a proposal built on this structure cannot guarantee funding or promise an award, only a fair hearing, because the decision belongs to the funder and to facts outside any document. What the structure buys is narrower: a proposal in which every claim is checkable, every number reconciles, and nothing depends on the reader's goodwill to fill a gap.

A grant proposal example is only useful if you can see why a passage works. Below are seven paired passages, one weak and one strong for each major proposal section, from executive summary to sustainability, with the structural difference named in each pair. Every passage is fictional and written for this article; the point is the pattern, not the wording. Read the pairs, then use the three-question extraction protocol at the end to pull structure out of any example without inheriting its facts.

Why examples mislead as often as they help

Proposal examples fail readers in a specific way: the reader absorbs the confidence of the prose instead of the evidence behind it. A funded proposal's sentences worked because they matched that organization's facts, that funder's priorities, and that year's competition. Copy the sentence without the facts and you get fluent text that collapses at the first program-officer question.

So each pair below isolates what actually transfers: the structural move. The weak passages are not parodies; they are the median of what small nonprofits actually submit, fluent and empty. Every organization and number in both columns is fictional.

Executive summary

Weak: "Hopewell Community Services respectfully requests your consideration for funding our vital programs. For over 15 years, we have been dedicated to making a difference in the lives of those we serve, and with your generous support, we can continue this important work."

Strong: "Hopewell Community Services requests $32,000 to expand its weekday meal delivery from 85 to 140 homebound seniors in Lawton County over 12 months, adding one driver and a second prep shift. Last year the program delivered 21,300 meals with a 96 percent on-time rate; the county waitlist stands at 61 seniors."

The difference. The weak version spends its only guaranteed read on adjectives. The strong version answers who, how much, what, for whom, and how well the organization already does it, in two sentences. Notice that "vital" and "important" disappear and nothing is lost, because the waitlist number carries the urgency the adjectives were faking.

Needs statement

Weak: "Food insecurity is a devastating national crisis affecting millions of Americans. Now more than ever, vulnerable seniors desperately need our help to survive these challenging times."

Strong: "In Lawton County, 2,140 adults over 65 live alone on incomes below 150 percent of the poverty line (fictional figure; a real proposal cites the source and year). The county's two congregate meal sites both closed in 2024, and the nearest grocery delivery service does not cover the four rural zip codes where 40 percent of these seniors live."

The difference. Scale and location. A national crisis cannot be fixed by a county program, so the national framing actually argues against the applicant. The strong version scopes the problem to the population the program can reach and shows a specific access gap, the kind a program can close. Guidance like Candid Learning's overview of what proposals must establish consistently points the need section at evidence, not urgency language.

Program description

Weak: "Bridgeway will provide comprehensive, holistic job-readiness services using evidence-based best practices, empowering participants through a client-centered approach tailored to individual needs."

Strong: "Bridgeway enrolls 20 participants per 10-week cohort, three cohorts a year. Each participant completes twice-weekly workshops, a mock-interview cycle with volunteer employers, and one paid 40-hour work placement. A case manager meets each participant weekly; completion means attending 16 of 20 workshops and finishing the placement."

The difference. The weak version is entirely made of category words: comprehensive, holistic, evidence-based, client-centered. None can be costed, staffed, scheduled, or verified. The strong version is made of countable nouns, and a reviewer can price it, imagine its calendar, and check it later.

Objectives

Weak: "Participants will gain increased confidence and improved job-readiness skills, and awareness of career pathways will be raised throughout the community."

Strong: "By June 2028, at least 70 percent of participants who complete a cohort will hold employment of 20 or more hours per week at the 90-day follow-up, measured by case-manager verification calls, from a 2026 baseline of 54 percent."

The difference. Verbs. "Gain," "improve," and "raise awareness" describe internal states nobody can observe; the strong objective names a behavior, a threshold, a date, an instrument, and a baseline. One honest test: if the objective came true, could a stranger tell? The strong version survives that test, and it also scopes the promise to completers, which is the claim the program can actually stand behind.

Evaluation

Weak: "The program will be continuously evaluated through surveys and feedback to ensure quality and continuous improvement."

Strong: "The case manager records enrollment, attendance, completion, and 90-day employment status in the participant database weekly. The program director reviews cohort dashboards monthly, reports to the board quarterly, and the annual report to the funder includes results against each objective, including any missed targets and what changed in response."

The difference. The weak version names an activity with no owner, schedule, or consequence. The strong version assigns every measure a person and a cadence and, critically, commits in advance to reporting misses. That single clause changes how a funder reads every other number in the proposal, because it prices in honesty. The measurement logic that connects activities to outcomes is the same chain a logic model makes explicit, in the tradition of the W.K. Kellogg Foundation logic model guide.

Budget narrative

Weak: "Personnel: $45,000. This covers staff costs for the program. Supplies: $8,000 for necessary program supplies and materials."

Strong: "Program coordinator, $38,400: 0.6 FTE at $64,000 annual salary, responsible for cohort scheduling, employer partnerships, and reporting. Workshop materials, $2,760: 60 participants at $46 per participant, based on 2026 actual per-participant cost. All salary figures use current payroll; no positions are projected."

The difference. A calculation basis. The weak version restates the line item's name as its justification. The strong version shows the arithmetic (rate times quantity), ties the cost to a responsibility the program description already named, and says where the numbers come from. When a budget narrative reconciles line by line with the program section, reviewers stop auditing and start reading.

Sustainability

Weak: "We will pursue diverse funding sources to ensure the program's long-term sustainability beyond the grant period."

Strong: "Year-two funding combines three sources: a renewal request to this fund contingent on meeting the employment objective, expansion of the employer-partner contribution program that covered 12 percent of costs in 2026, and a fee-for-service contract under negotiation with the county workforce board, with a decision expected by March. If the county contract is not signed, the program continues at two cohorts rather than three."

The difference. A plan has names, percentages, dates, and a stated fallback. The weak version is a wish with a professional vocabulary. The fallback sentence does the most work: it tells the funder the organization has already decided what happens if the optimistic case fails, which is exactly the thinking funders are trying to detect.

The extraction protocol: three questions per section

When you review any example, funded or fictional, ask these three questions of each section and write the answers down before drafting your own:

1. What decision did this section make? Not what it says, but what it chose to lead with, scope to, or leave out.
2. What evidence does it stand on? List each fact the passage depends on. If your organization does not hold an equivalent fact, the structure transfers but the confidence does not; the missing fact becomes a research task, not a phrasing problem.
3. What would a skeptic ask next? The strong passages above all pre-answer an obvious follow-up. Find the follow-up your draft invites and answer it in the text.

The three questions work on any specimen: a funded grant proposal example from a database, the grant application example a funder publishes with its own guidelines, or the constructed pairs above. Real funded proposals are worth studying alongside pairs like these, and funder research shows you what a specific foundation actually funds: a foundation's Form 990-PF lists its actual grants, and Candid's guide to finding 990s covers how to pull them. For a complete proposal to study end to end with every section annotated, the sample grant proposal for a nonprofit organization on this site carries a full fictional application, and the nonprofit grant proposal template turns the structure into a drafting document. The reusable version of your own strongest passages belongs in a core grant narrative that you adapt per funder rather than rewriting.

One boundary, stated without hedging: even the strongest passage cannot guarantee funding, because the decision depends on the funder's priorities, the year's competition, and facts outside any document. What the strong column buys is the absence of self-inflicted rejections: no unverifiable claims, no arithmetic that fails, no promise the program cannot keep. That is the whole, sufficient case for writing this way.

Six complete needs statement examples are below, one each for eviction prevention, rural medical transit, home visiting, adult ESL, diabetes prevention, and senior digital access. Every example is fictional and annotated against the same six-part evidence chain: population and place, observed condition, comparison, community knowledge, data limitation, and program relevance. Use them to calibrate how a finished passage reads; build your own from the drafting structure in our needs statement template, with your verified local data in place of every invented figure here.

How to read these examples

A needs statement, which many funders label a statement of need, establishes that a defined population in a defined place experiences a documented gap, and that the applicant understands the gap well enough to act on it. Each example below runs that chain in about 130 words, which is the density most foundation applications force. The annotations name which sentence does which job.

All organizations, places, and figures are fictional. In a real statement, every number carries a source and year: population and income context from data.census.gov, county-level health measures from County Health Rankings, and child and family indicators from the KIDS COUNT Data Center. The needs statement template holds the drafting structure and a data-sourcing walkthrough; these examples show what it produces.

Example 1: Eviction prevention

In Garton County, landlords filed 1,840 eviction cases in 2026, a 34 percent increase over 2024, and 62 percent of filings involved arrears under $1,200 (fictional court data). No emergency rental assistance has operated in the county since federal program funds closed out. Families who called our housing helpline last year most often reported a single missed paycheck, a medical bill, or a car repair as the triggering event, and callers had typically already borrowed from family before calling. Court records cannot show how many households leave before a case is filed, so filings understate displacement. Small, fast arrears grants at the helpline stage address the specific gap the data shows: crises measured in hundreds of dollars that become removals costing families and the county far more.

Annotation. Sentence one carries place, condition, trend, and the detail that makes the program plausible (small arrears). Sentence two shows the service gap. Sentence three is community knowledge from the organization's own contact with the population, labeled as what it is. Sentence four states the data's limit instead of hiding it. The last sentence connects need to response without yet describing the program.

Example 2: Rural medical transit

Adults over 60 make up 31 percent of Harlan Valley's population, against 22 percent statewide (fictional figures), and the valley's last fixed-route bus service ended in 2023. The nearest dialysis, oncology, and cardiology providers sit 41 miles away in Dorset City. In our 2026 survey of 118 valley seniors, 44 reported missing at least one medical appointment in the prior six months for lack of transportation; missed-appointment data from the providers themselves was not available to us, so we report only what patients told us. Volunteer drivers already carry neighbors informally. A scheduled, insured volunteer transit program formalizes what the community has improvised, aimed at the appointment types where a missed trip has clinical consequences.

Annotation. The comparison sentence (31 versus 22 percent) earns the geographic focus. The survey sentence shows first-party evidence with its sample size, then explicitly separates what was measured from what was not, which is the credibility move most statements skip. The final two sentences frame the community as the solution's origin, not the problem's container.

Example 3: Early childhood home visiting

In the Fairfield Flats neighborhoods, 210 children under three live in households below the poverty line, and the neighborhood's share of children entering kindergarten meeting readiness benchmarks was 41 percent in 2026, against 63 percent citywide (fictional school district data). The city's two home visiting programs maintain waitlists totaling 96 families and neither serves the Flats' largest language community, Somali, in-language. Somali-speaking mothers in our parent circles consistently describe wanting developmental guidance from someone who shares their language and has raised children here. Kindergarten readiness is measured at one point and misses earlier development, a limit of the available data. An in-language home visiting track staffed by trained neighborhood mothers meets the documented gap where existing programs cannot reach it.

Annotation. This example shows need scoped by language access, not only by income, and the community-knowledge sentence carries the program's design logic. Note the phrase "described wanting": reported preference is presented as reported preference, not converted into a statistic.

Example 4: Adult ESL and literacy

An estimated 5,600 adults in Brenner County speak English less than very well (fictional figure modeled on American Community Survey categories), while the county's single adult ESL provider enrolled 240 learners last year and turns away applicants each term. Employers in the county's two largest sectors, food processing and eldercare, list English communication as the top barrier to promoting current employees, per our 2026 interviews with nine HR managers. Waitlist length understates demand, since adults stop applying when terms fill. Evening and shift-compatible ESL classes co-located at the two largest worksites address the specific mismatch the evidence shows: demand concentrated among working adults whom daytime, off-site classes structurally exclude.

Annotation. The supply-versus-demand arithmetic (5,600 potential learners, 240 seats) is the whole argument in one comparison. Employer interviews add a second, independent evidence stream, attributed and dated. The limitation sentence turns a weak-looking waitlist number into an honest floor.

Example 5: Diabetes prevention

Adult diabetes prevalence in Corvin County is 13.8 percent against 10.1 percent statewide, and the county ranks in the bottom quartile of its state on food environment measures (fictional figures of the kind County Health Rankings reports). The county hospital's community health assessment names diabetes as a top-three priority, but its prevention classes ran at 40 percent capacity last year: residents in our focus groups described the hospital campus as unfamiliar and the class times as built for retirees. Prevalence data cannot say which residents are pre-diabetic and unaware, so the true prevention population is larger than any current count. Peer-led prevention groups in churches and the community center take a clinically validated curriculum to the places attendance evidence says people actually go.

Annotation. This example demonstrates the most useful move in the set: it explains why an existing service underperforms (location and scheduling) using the community's own account, which converts "another program exists" from a threat into the justification.

Example 6: Senior digital access

Of Marsh Point's 3,100 residents over 65, an estimated 38 percent have no home broadband subscription (fictional figure; the American Community Survey publishes this measure by age and geography). The public library's device-lending program requires online reservation, an access barrier its own staff flagged to us. Since the regional health system moved appointment scheduling and test results online in 2025, its patient portal adoption among patients over 65 stands at 29 percent, per its published community report (fictional). Our senior center members most often ask for help with exactly two tasks: the patient portal and benefits renewals. Twice-weekly drop-in tech help staffed by trained volunteers, with loaner tablets that require no online reservation, addresses the two documented tasks where being offline now carries direct consequences.

Annotation. The need is framed by consequence, not by deficit: the problem is not that seniors lack a skill, it is that essential systems moved and left a specific access gap. The two-task detail, drawn from the organization's own contact records, keeps the program honest and small.

The ethics review: urgency without exaggeration

Every example above holds three ethical lines, and a needs statement that breaks them fails even when it persuades. First, evidence over adjectives: no population is described as desperate, broken, or forgotten, because the numbers carry the urgency and the adjectives cost the community its dignity. Second, strengths stay visible: five of the six examples name an existing community asset, which reflects the principles articulated by Community-Centric Fundraising that communities are not raw material for fundraising narratives. Third, stories are consent-bound: none of the examples quotes an identifiable person, and the Ethical Storytelling pledge is the standard to apply before any client story enters a proposal.

A needs statement also cannot prove that your program is the answer; it proves the gap is real, documented, and reachable, and the program sections that follow it must carry the rest, the way the annotated sample grant proposal shows a need section handing off to program and evaluation. Even a fully evidenced statement cannot guarantee a funder's decision. What the six-part chain guarantees is smaller and decisive: nothing in your opening section will be the reason a reviewer stops trusting the rest.

Use a script-format storyboard with 14 columns: screen ID, screen title, objective served, on-screen text, narration, media description, interaction type, interaction behavior and feedback, branching, alt text, accessibility notes, assessment link, review status, and open questions. The last five are the ones most free templates omit, and they are where builds actually go wrong. The template below ships as a CSV with three fully written example screens, so you can see the level of detail each column owes its reader before you delete the examples and start.

A storyboard is a contract, not a sketch

An eLearning storyboard has one job: to let a developer, a reviewer, and a subject-matter expert object to the course before anyone builds it. Every decision the storyboard defers lands in the build, where changing it costs the most. That is the test for what belongs in the document, and it is the whole discipline of storyboarding for eLearning. Not "would this help someone imagine the course" but "could someone block a mistake here."

Most free storyboard templates fail that test quietly. They are empty grids with columns for text, narration, and a thumbnail, which captures what the course says and leaves out everything reviewers need to catch: which objective a screen serves, what exactly happens when a learner answers wrong, where the branch goes, what the alt text will be, and whether anyone has actually signed off. A storyboard missing those columns does not prevent the rework; it schedules it.

The format question matters less than people think. A script-format storyboard lives in a document or spreadsheet and describes visuals in words; a visual-format storyboard mocks up each screen in slides, which is why most Word storyboard templates you will find are script-format tables and most PowerPoint storyboard templates are visual mockup grids. An instructional design storyboard can be either; the columns below matter in both. Visual formats earn their cost on media-heavy projects with a separate graphic designer who needs layout intent. For most workplace projects, and for anyone building portfolio evidence, script format is the right default: faster to revise, reviewable in comments, and diffable when the SME changes the policy for the third time.

The 14 columns and the failure each one prevents

The alt text and accessibility columns deserve their own defense, because they are the first ones deleted to make a template "cleaner." Accessibility requirements like text alternatives, captions, and keyboard operability are testable success criteria under WCAG 2.2, and for anyone building toward U.S. workplace or government contexts they are procurement requirements under Section 508. The storyboard is the last cheap place to meet them. An alt-text decision costs one cell at design time and a remediation ticket after launch.

What a filled storyboard example looks like

The download doubles as an instructional design storyboard example set: three complete screens from a fictional practice scenario, Northstar Systems, a made-up software company whose tier-1 support agents misquote refund policy. Here is the shape of one, compressed:

Worked example: Screen NS-01-030, a decision screen, from the fictional Northstar case

Objective served: O1. On-screen text: "A customer on the Starter tier bought 41 days ago and asks for a refund. What is the correct first response?" Interaction: multiple choice, three options. Behavior and feedback: the correct answer confirms the two-step order and quotes the policy line; each wrong answer receives feedback naming the specific step it skipped, then offers a retry. Branching: correct routes forward; two wrong attempts route back to the teaching screen. Alt text: "Support ticket from a Starter tier customer 41 days after purchase." Accessibility notes: options are buttons in a list, feedback renders as adjacent text rather than a vanishing toast, retry does not trap keyboard focus. Assessment link: assesses Q1. Review status: in review. Open question: second wrong-answer feedback wording still pending SME.

Notice what the level of detail buys. The developer can build this screen without a meeting. The SME can veto the policy line before it is recorded. The reviewer can see that a wrong answer produces teaching, not just "Incorrect." And the open-questions cell admits what is unfinished instead of hiding it in someone's inbox.

Download: eLearning storyboard template (CSV, 14 columns). All 14 columns with three fully written example screens from the clearly labeled fictional Northstar case, plus blank rows. Open it in Google Sheets or Excel, keep the examples beside your first real rows as a detail benchmark, then delete them.

Running the review the columns make possible

A storyboard only earns its columns if the review actually uses them. The working sequence, for a small team or a solo builder recruiting help:

1. Objective pass. Read only the objective-served and assessment-link columns. Every objective gets taught and assessed somewhere; every screen serves something. Orphans on either side get cut or fixed before anyone reads prose.
2. SME pass. The SME reads on-screen text, narration, and feedback verbatim and initials the review-status column per screen. Factual review of a paraphrase is not review.
3. Build pass. Whoever will develop it reads media, interaction, and branching columns hunting for anything they cannot build from the words alone. Each find becomes an open-questions entry, not a conversation that evaporates.
4. Access pass. Alt text and accessibility notes checked for every screen, including the boring ones. This pass takes minutes at storyboard stage and days after launch.

Then freeze it. A storyboard that keeps changing after sign-off is not a living document; it is an unsigned one. Changes after freeze go through the open-questions column with a new review-status entry, so the record of what was agreed survives the project.

A template cannot make content accurate, and this one does not try: the SME pass exists because no column layout can verify a policy quote or a compliance claim. What the columns can do is make every deferred decision visible while it is still cheap, which is the whole difference between a storyboard and a wish. The same discipline should already be present one step earlier, in the needs analysis that decided this course was worth building; a storyboard, however clean, cannot rescue a course that training should never have been asked to deliver.

A training needs analysis starts from a performance gap stated in observable numbers, collects evidence from records, performers, and managers, sorts the causes into skill, environment, and incentive, and only then decides whether training is the fix, because training closes exactly one of those three cause types. The template below carries that whole sequence in 18 fields plus a 24-question evidence bank, as a CSV, with a fully worked fictional example in every field so nothing has to be guessed.

Start from the gap, not the request

Training needs analysis and training needs assessment name the same instrument; this guide uses analysis throughout. How to conduct a training needs analysis is mostly a question of sequence: gap first, evidence second, causes third, decision last, and the sequence exists because most training requests arrive with the solution already decided: "we need a course on X." An analysis that accepts that framing is an order form. The version worth doing walks the request backwards to the performance gap behind it, because the gap is the only thing that can validate the solution.

A usable gap statement has four parts, and refusing to proceed without them is most of the method: who is not doing what, to which standard, and what it costs. "Agents need refund training" is a request. "Tier-1 agents resolve 61 percent of refund tickets correctly on first response against a 90 percent standard, driving 31 escalations a quarter" is a gap: it names the population, the observable behavior, the standard, and the cost. Everything downstream, including whether the eventual course was worth building, gets measured against those numbers.

If no standard exists, that is the first finding, not a blocker to route around. A gap cannot be measured against a standard nobody wrote down, and performers cannot be fairly trained toward one either. The U.S. Office of Personnel Management's guidance on training planning and evaluation makes the same structural point for federal agencies: needs identification precedes design, and evaluation is planned against those needs, not appended afterward.

The gate: training closes one kind of cause

Evidence in hand, sort every cause you found into three bins:

The gate is the honest sentence most analyses never write: training only closes the first bin. A course aimed at an environment cause produces trained people performing wrongly for the same reason as before, plus a line item proving something was done. This is the oldest finding in performance analysis, argued for decades by practitioners in the Mager and Pipe tradition, and it survives because organizations keep paying to relearn it.

The template forces the gate by structure: the cause fields are separated by bin, and the is-training-the-fix field requires a response for every cause, not just the trainable one. An analysis that finds all three bins occupied, which is the common case, recommends a smaller course than requested plus the tooling and incentive fixes that training cannot deliver, each with an owner.

Our position

An analyst who cannot say "training is not the fix here" is not analyzing; they are quoting. The credibility of every future recommendation rests on being structurally able to reach that conclusion, which is why the decision gate belongs printed in the template rather than held as a private intention. This is also, bluntly, what makes a needs analysis persuasive as portfolio evidence: a case study whose analysis finds a tooling cause and a scorecard cause alongside the skill gap reads as diagnosis. One that finds only "needs training" reads as sales.

The 18 template fields

The template is a single sheet in five sections. Every field ships with a worked entry from the fictional Northstar Systems case, a made-up software company used throughout, so the filled column reads as a complete training needs analysis example rather than a set of blank prompts.

The evidence section deserves its reputation for being skipped. Asking people what training they want is a survey, not an analysis; people report the causes they can see, and environment causes are precisely the ones performers stop seeing. The bank below exists so the evidence pass is a checklist rather than an improvisation.

The 24-question evidence bank

Eight questions for performers, eight for managers, eight for the records and environment. Used verbatim, the first two groups are a ready training needs analysis questionnaire for interviews; the records questions are asked of systems, and the discipline in every case is writing down the answer with its source.

Performers: Walk me through the last one you handled; what did you do first? Show me where you look this up; how long does it take? What do you do when you are not sure? What would you change about how this task works? When you get one wrong, how do you find out? What part of this did nobody ever teach you? What shortcuts or personal notes do you use, and may I see them? If a new hire shadowed you tomorrow, what would you warn them about?

Managers: What does good performance look like in numbers? Who meets that standard now, and what do they do differently? When performance dips, what usually turns out to be the cause? What has already been tried, and what happened? What do your metrics reward that might work against this standard? If training worked, what number would move first? What would make you call this effort a failure in a year? Who else feels this problem and should be in the room?

Records and environment: What does the last full quarter of data show against the standard? Is the standard written anywhere performers can reach in the flow of work? When was the process last changed, and were performers told? How many clicks does the correct path take from where work happens? What do quality audits say the most common error actually is? Do error rates differ by shift, tenure, or team in a way that points at a cause? What do top performers use that the official process does not include? What happened to the error rate the last time anything changed?

Three of these questions pay for the whole exercise more often than any others: the shortcut question, because private cheat sheets are a map of where the official process fails; the metrics question, because incentive causes hide inside scorecards nobody thinks to blame; and the already-tried question, because it stops you from proposing last year's failure with new branding.

Download: Training needs analysis template (CSV, 18 fields + 24 questions). The full template: 18 fields across framing, evidence, causes, decision, and measures, every field carrying a worked entry from the clearly labeled fictional Northstar case, plus the complete 24-question evidence bank. Open in Google Sheets or Excel and overwrite the examples with your own case.

Writing it up so a sponsor can push back

The write-up is one page in the template's field order: the gap with its numbers, the evidence with its sources, the causes in their bins, the response per cause with owners, and the measures with a review date. Resist the appendix urge. A sponsor who can read the whole analysis in three minutes can challenge it, and an analysis that survives challenge is the only kind worth acting on.

The success measures close the loop that the gap statement opened, and they should be chosen before anything is built, in the terms the four-level evaluation tradition associated with the Kirkpatrick model calls behavior and results: not whether learners liked the course or passed its quiz, but whether first-response accuracy moved from 61 toward 85 and escalations fell. If the measures only exist at the reaction level, that is a finding about the analysis, not a limitation of measurement.

Be plain about what the instrument cannot do. A needs analysis cannot make a broken process trainable, cannot substitute for the sponsor's authority to fix scorecards or tooling, and cannot promise that closing the skill gap will move the business number by itself when other causes remain open. What it can do is make each of those statements checkable, which is what separates an analysis from an opinion with a template. When the decision is that training is part of the fix, the analysis hands its objectives directly to the design stage, and its standard travels with them into the storyboard that will hold the build accountable and into the portfolio case that will eventually prove you did all of this.

An AI visibility audit is defensible when another practitioner can see what you checked, what you observed, and where judgment entered the conclusion. The 47-point model in this article grades exactly that: scope and consent, approved facts, technical eligibility, the prompt sample, answer observations, the source map, findings, and the client handoff. Before findings enter a client report, score 85 or higher and confirm every weight-three critical check. The checklist grades your protocol, not the brand's popularity, and it never predicts citations.

Use the checklist at three moments: before fieldwork to catch missing scope, during the audit to keep the evidence record complete, and before handoff to reject findings that nothing supports. An audit that skips the third pass ships opinions with screenshots attached.

Key facts, checked August 7, 2026

• Google states a page must be indexed and eligible for a snippet to appear as a supporting link in AI Overviews or AI Mode, with no additional technical requirements and no special schema for AI features. Source: Google Search Central, AI features and your website.
• OpenAI documents OAI-SearchBot as the crawler that surfaces sites in ChatGPT search results, separate from GPTBot, which governs model-training preferences. The two controls are independent. Source: OpenAI crawler documentation.

How the 47-point scoring model works

Every check carries a weight of two or three. Weight-three checks, 29 of the 47, mark conditions that can invalidate a conclusion on their own: missing consent, an unfrozen prompt set, a finding with no saved evidence. Weight-two checks mark gaps that weaken the audit without collapsing it. The score is earned weighted points divided by 123 possible points, times 100.

The client-ready verdict has two gates, not one. The weighted score must reach 85, and all 29 weight-three checks must be confirmed. A missing critical check caps the verdict at Usable with material gaps, even when the arithmetic score is 85 or higher. Weight-two gaps may remain only when the score still reaches 85 and a human reviewer judges them acceptable for the declared scope.

A high score does not mean the brand is visible. It means the audit can explain its own evidence. Those are different achievements, and only the second one is under your control.

Tool: Score your own protocol against all 47 checks. The interactive version of this model. Confirm what you already record, see which sections are weak, and get every unconfirmed check ranked by weight with the evidence to keep and the failure that costs the point.

Download: The 47-point audit checklist as a working file (CSV template). All 47 checks with section, weight, the evidence artifact to save for each check, and the failure that most often costs the point. Use it as the quality tab of the audit workbook this model grades.

Scope, consent, and the approved fact ledger

The first eleven checks exist because most bad audits fail before anyone opens an answer engine. Scope failures are quiet: nobody wrote down the one business decision being tested, so the prompt panel drifts toward whatever wording produces interesting screenshots. Consent failures are louder. Auditing a prospect's brand without recorded permission produces evidence you cannot present, and in the worst case a sales deck built on observations the prospect never authorized.

The fact ledger is the check practitioners skip most. Representation review, the part of the audit clients care about most, is impossible without it. If the client has not approved, in writing, the canonical business name, the offers and their fit conditions, the locations, and the sources behind every credential claim, then the auditor grades AI answers against their own guesses. When an engine repeats an old service area, an audit without a dated ledger cannot even say whether that is an error.

Weight-three checks here are consent, approved offers, sourced claims, and written exclusions. The exclusions check surprises people: it requires that what the audit does not promise (rankings, citations, traffic, revenue) exists in writing before fieldwork. That single artifact prevents the most expensive handoff argument, and it is why the audit proposal carries a dedicated exclusions section.

Technical eligibility before any prompt runs

The seven technical checks come third for a reason of arithmetic, not ideology. Google's public position is that AI Overviews and AI Mode have no special technical requirements beyond normal indexing and snippet eligibility (Google Search Central), and ChatGPT search inclusion runs through an ordinary crawler allowance, as covered in OAI-SearchBot vs GPTBot. So if a priority page returns the wrong public response, blocks the relevant crawler, carries a stray noindex, or hides its material facts in client-side rendering, every downstream observation about that page is noise. You would be measuring the visibility of a page the systems cannot fully use.

What fails in practice, in rough order of frequency: a blanket bot block added years ago during a scraping scare that now also blocks search crawlers; material facts that exist only in JavaScript-rendered widgets or images; structured data that disagrees with visible copy on price, address, or offer names; and technical checks performed while logged in to a CDN-whitelisted network, so the auditor never sees the challenge page the public gets. The seventh check, dated evidence for every technical claim, exists because "robots is fine" without a date is unfalsifiable one site release later.

The prompt sample and the observation log

Thirteen checks cover sampling and observation because this is where audits most often stop being audits. The prompt checks enforce one discipline above all: the panel is derived from buyer decisions, then frozen before the first saved run. Tuning wording after seeing which phrasing favors the client converts the audit into a demonstration. The full derivation method, including the four strata and the branded-versus-unbranded separation, is in the prompt set guide.

The observation checks are storage discipline. Exact prompt text, full answer evidence, run date, platform, surface, and account state, for every run, including runs where the brand was absent. Absence is data. The two classification checks are weighted three because their failure produces the most misleading client numbers: counting a prose mention and a cited link as the same event overstates source use, and skipping the representation check against the fact ledger means the audit reports presence without ever asking whether what was said is true. Repeated runs matter because generative answers vary; a single run reported as "the state of ChatGPT" is the sampling equivalent of polling one person.

Sources, findings, and the client handoff

The last sixteen checks turn a pile of observations into something a client can act on without being misled. The source map checks force two separations: owned versus third-party cited sources (so the roadmap targets pages someone can actually edit), and competitor numbers computed on the identical frozen panel. A competitor comparison built on different prompts, dates, or run counts is fiction with a table format.

The findings checks encode the difference between observation and explanation. "The brand was absent from 14 of 20 unbranded discovery prompts" is an observation. "The engine penalizes the site" is an invented mechanism nobody observed, and check source-5 requires it to stay labeled unknown. The handoff checks then protect the client from your own report: method limits visible in the main document rather than an appendix, the four evidence layers of the four-layer visibility model kept separate rather than blended into one proprietary percentage, and a roadmap whose items would still be worth doing if no sampled answer ever changed. That last check is weighted three because it is the honesty test for the entire engagement.

A passing executive finding reads like this: across the declared 30-prompt panel and three repeated runs, the firm appeared in category answers, but its US service area was omitted in four of seven mentions, and the approved ledger disagrees with two public profiles on geography. Correct the profiles, publish one canonical fact source, and repeat the identical panel after the changes are discoverable. Sample, observation, factual basis, action, review method. No mechanism claims, no promises.

What to refuse to score

Our position

Some things stay off this checklist deliberately, and refusing to score them is part of the method. We do not score "share of voice" across all AI conversations, because a 30-prompt panel is a declared sample, not a census, and multiplying it into a market claim is fabrication with extra steps. We do not score proprietary visibility indexes that publish no formula and no denominator; a number you cannot recompute is marketing, not measurement. And we do not score predicted citations, because nobody outside the platforms controls or observes the selection mechanism. An auditor who scores these things is not being thorough. They are converting unknowns into billable certainty, and the audit fails the moment a client repeats one of those numbers to their board.

If a client asks for these numbers anyway, the honest substitutes exist: mention and citation rates over a declared panel with the denominator shown, tracked over identical reruns, as described in the measurement protocol.

Rerunning the audit without breaking the baseline

The checklist is also the re-audit instrument. A quarterly or half-yearly wave only produces a trend if the panel, platforms, run counts, account state, and classification rules match the baseline exactly, which is what check handoff-6 locks in at delivery time. When the business genuinely changes (new offer, new geography), version the panel, keep a stable core of unchanged prompts for continuity, and label the break in every chart. Small movements between two waves of a 30-prompt panel are usually variance, not trend; treat single-digit swings as noise unless they persist across waves.

Score the protocol before the first client sees a finding, price the scope you actually declared using the pricing model, and hand the completed evidence record to the client report template. In that order. The report is the last step because everything defensible about it is created earlier.

An AI visibility prompt set is a controlled panel of buyer decisions, not a keyword list rewritten as questions. Write one sentence describing the commercial decision in scope, derive prompts across four strata (problem discovery, category discovery, comparison and fit, validation and risk), freeze the panel before the first saved observation, and reuse the identical version for every future wave. Freezing before observation is the discipline that separates an audit from a demonstration.

The panel exists to answer one question honestly: when a real buyer works through this decision with an AI assistant, does the path lead toward the brand, and is the brand described accurately when it appears? Everything in the method serves that question, and everything that biases it, especially editing prompts after seeing results, destroys it.

Key facts, checked August 7, 2026

• Google's AI-features guidance says its systems understand synonyms and general meaning, so publishers do not need to capture every phrasing variation, and warns that creating pages for every variation primarily to manipulate rankings violates its scaled-content policy. Source: Google, AI features and your website.
• OpenAI documents OAI-SearchBot as the crawler that surfaces sites in ChatGPT search, independent of GPTBot training controls, which matters when you declare platforms for a panel. Source: OpenAI crawler documentation.

That Google guidance is about content, but it strengthens the audit method too: use related wording to understand one decision, not to manufacture thirty supposedly different intents.

Derive prompts from one buyer decision

Start with a single sentence that names the person, their context, the alternatives, and the decision:

An operations manager at a US HVAC contractor with 20 field technicians is deciding whether to buy dedicated field service management software, extend the accounting suite the company already pays for, or keep dispatching from spreadsheets.

This sentence does the real work. It fixes geography and audience, names the competing options (including the do-nothing option, which is usually the strongest competitor), and gives every prompt a purpose. A prompt either samples a question this buyer would plausibly work through, or it does not belong in the panel.

Do not begin with "what should we ask ChatGPT?" Platform choice comes after the buyer model. The same decision panel is then observed on whichever surfaces you declare, and the 47-point audit checklist requires those declarations before the first run.

The four strata and what each one tests

Problem discovery prompts describe the costly situation without naming a category or brand. They test whether the buyer's problem, phrased the way an operator phrases it, leads toward the relevant solution space at all.

Category discovery prompts ask what kind of product, provider, or method helps. These are unbranded and commercially decisive: if the category answer omits the brand's segment or misdefines the category, nothing downstream recovers it.

Comparison and fit prompts test alternatives, tradeoffs, and non-fit conditions. They are worth more than endless "best X" variants because real buyers compare against the specific alternative they already have.

Validation and risk prompts ask whether a named option is credible, supported, and appropriate. Branded prompts live here, and their results must never be blended with discovery results, because a brand that dominates its own name while vanishing from discovery has a serious problem that a blended number would hide.

The default 30-prompt panel splits roughly 9, 9, 8, and 4 across the strata; the planner's per-stratum rounding can shift a prompt between adjacent strata. The exact split is not a law; the balance is the point. A panel that is all comparisons measures shortlist behavior and nothing upstream of it.

A complete worked 30-prompt panel

Worked example: A 30-prompt panel for one declared buyer decision

The scenario is the buyer decision sentence above: field service management software evaluated by a US HVAC contractor. The product category is real; the scenario is an illustration, so branded prompts use [brand] and [competitor] placeholders rather than invented company names. Substitute the audited brand and its named competitors.

Problem discovery (9):

Category discovery (9):

Comparison and fit (8):

Validation and risk (4):

Notice what the panel does not contain: ten punctuation variants of the same question, prompts engineered to make [brand] the only sensible answer, and prompts no operator would ever type. P25 exists specifically to test whether non-fit conditions are represented honestly, because a panel with no unflattering prompts is a sales asset, not a sample.

Download: Prompt-set worksheet with the worked panel (CSV worksheet). All 30 illustration prompts with stratum and the decision each one tests, plus empty capture columns for your own prompts, platform, account state, run number, mention classification, cited URLs, and representation results.

Freeze the panel, then control every run

Freeze the panel, with a version number and a date, before the first saved observation. This is the baseline discipline: the first complete set of runs against the frozen panel is the only baseline you will ever get, and every future wave is comparable only if the panel, platforms, account state, location context, and run counts match it.

For each observation, save the prompt ID and exact text, platform and surface, signed-in or signed-out state, date and time, location and language context, run number, the full answer evidence, every cited URL, the mention classification, and the representation result against the approved fact ledger. Run the frozen panel more than once per platform, because generative answers vary between identical runs. Three runs is a practical directional convention, not a statistical law; state the count and its limits rather than calling any of it representative, as covered in the measurement protocol.

When the business genuinely changes, version the panel. If v2 replaces five prompts after the client launches a new offer, keep the unchanged 25 as a continuity core and never draw one trend line across the break.

Keep denominators and classifications honest

Two bookkeeping rules protect the client from the numbers.

First, mentions and citations are different events. A brand named in prose was recalled or synthesized; a brand cited as a linked source was retrieved and used. Count them in separate columns, always.

Second, report strata separately before any total. If the brand appears in 6 of 30 prompts, that is a 20 percent mention rate on that declared panel, nothing more. The useful decomposition is usually: unbranded discovery rate (say 1 of 20, 5 percent), branded validation rate (5 of 10, 50 percent). The blended 20 percent hides exactly the finding that matters, which is that buyers who have not heard of the brand never encounter it. Reporting layers separately is the same principle that structures the four-layer visibility model.

Our position

Most prompt sets we see in agency reports are keyword exports with question marks added, and we consider that method malpractice, not a shortcut. Keywords describe how people type into a search box; buyer decisions describe how people reason with an assistant. A panel derived from keywords measures the habits of the old channel in the new one, and it produces exactly the inflated branded numbers that make audits look successful while discovery quietly fails. Build the panel from the decision, accept the smaller and less flattering numbers, and you get findings a client can act on.

Tool: Six of the 47 checks grade the panel on its own. Confirm the derivation, the strata, the freeze, the run counts and the separated denominators, and see whether the sample section holds before the rest of the protocol is graded against it.

Write the buyer-decision sentence, build the four strata, freeze the panel, and only then open an answer engine. Score the whole protocol against the 47-point audit checklist before any finding reaches a client.

An AI visibility report has ten sections in a fixed order: decision and scope, executive finding, method and limits, technical eligibility, mentions and citations, representation accuracy, sources and competitors, findings, roadmap, and appendix. The front half is short and client-facing; the back half is traceable evidence. Every number carries its denominator, and every recommendation traces to an observation. The full Markdown template is downloadable below.

Download: AI visibility client report template (Markdown template). The complete ten-section structure with placeholder fields, per-section guidance notes, the finding block with separated observation, interpretation, and recommendation fields, and the metrics tables with denominator columns built in.

What the report has to survive

A client reading their first AI visibility report brings three reasonable questions: what is actually happening, how do you know, and what should we do about it. The report also has to survive a fourth reader you will never meet: the skeptical colleague, procurement reviewer, or replacement agency who inherits it later and checks whether the numbers trace to anything.

Rank-tracking reports survived on familiarity. AI visibility reports cannot, because the evidence is unfamiliar: sampled answers instead of positions, classification instead of counting, limits that are structural rather than apologetic. So the template's job is to make unfamiliar evidence legible without pretending it behaves like rank tracking. That drives every structural choice below: short and decisive at the front, fully traceable at the back, method visible in the middle because the method is part of what the client is paying for.

Everything in the report is built on the numbers produced by the measurement protocol. If the observation log does not exist, there is nothing to report, and no template fixes that.

Sections 1 to 3: the front the client reads

Section 1, decision and scope, names the business decision the report supports, then the frozen parameters: audience, geography, platforms, the prompt panel size and strata, run counts, priority pages, and explicit exclusions. The reasoning: a report without a named decision gets read as a score, and scores get argued with. A report scoped to a decision gets used.

Section 2, executive finding, is one page answering the three client questions in order: what we observed (one to three findings, each with numerator and denominator), how we know (two sentences pointing at the method), and the recommended next action with an owner and an acceptance check. Write it last, compress it hardest.

Section 3, method and limits, states that the report is a controlled sample of observed answers, not a census of AI answers or users; how prompts were selected; what account state and personalization applied; and that nothing in the report establishes a ranking or predicts future mentions, citations, traffic, or revenue. Do not shrink this into a footnote. When a competitor's report waves a black-box score around, your visible method is the differentiation.

Sections 4 to 7: the evidence core

Section 4, technical eligibility, reports first-party checks on priority pages: response codes, robots and index controls, canonicals, and whether material facts appear in rendered text, each with a checked date. It stays separate from answer observations because the two evidence types fail independently: a page can pass every check and never be cited, and a cited page can carry a representation error. This section is the first layer of the four-layer model, and the report keeps all four layers in separate sections for the same reason the model does.

Section 5, mentions and citations, is the baseline table: valid observations, brand mentions, owned citations, and their rates, split by platform and by prompt stratum. Branded and unbranded strata never share a denominator; a pooled rate flatters recognition and hides the discovery problem.

Section 6, representation accuracy, compares each material statement in sampled answers against the approved fact ledger and labels it accurate, incomplete, outdated, conflicting, or unsupported. This is usually where the commercially urgent findings live, because a confident wrong answer in front of a buyer outranks any visibility statistic.

Section 7, sources and competitors, maps which owned and third-party sources appeared, which sources answered the buyer's questions without the brand, and which competitors were named per stratum. This is the section that converts observation into a work plan, because it shows where the evidence gaps physically are.

First-party platform data joins the report here as its own labeled subsection, never merged into panel rates: Bing's AI Performance preview reports aggregated citation activity with its own coverage and caveats (the reconciliation workflow covers the details), and ChatGPT referral clicks are attributable through the utm_source=chatgpt.com parameter documented in OpenAI's publisher FAQ.

Sections 8 to 10: findings, roadmap, appendix

Section 8, findings and priorities, is one block per finding, each preserving the same chain: observation, interpretation, buyer consequence, recommendation, owner, confidence, acceptance check. The chain is the integrity mechanism; the worked example below shows why the first three fields must never blur.

Section 9, roadmap, sequences actions by dependency, not effort: eligibility blockers before content work, factual conflicts before anything that would amplify them. Each row names the finding it derives from. A roadmap item with no parent finding is an upsell, and clients can tell.

Section 10, appendix, carries prompt IDs, the observation log reference, the fact ledger version, definitions, and a change log. Raw answer dumps stay in the evidence workbook; the appendix points to them.

Writing one finding: the three-field discipline

Worked example: One finding, written as observation, interpretation, and recommendation

This illustration uses abstract placeholders throughout. It describes no real or invented client, and its numbers exist only to show the structure.

Observation. In the [period] panel, [Brand]'s service pages were cited in 0 of 36 valid unbranded observations on [platform]. The eligibility check found the service directory returns its content only after client-side rendering, and the rendered-text check failed for 4 of 6 priority pages (evidence rows [IDs], checked [date]).

Interpretation. We assess, labeled as inference, that the rendering gap is the earliest plausible blocker: the platform does not expose why any page was or was not cited, but pages whose material facts are absent from rendered text cannot be expected to appear as sources. Competing explanations, thin third-party evidence among them, remain open until the blocker is cleared.

Recommendation. Ship server-rendered content for the 4 failing pages (owner: [role]), verify with the same rendered-text check, then rerun the identical panel after the pages are re-crawlable. Acceptance check: rendered-text pass on 6 of 6 priority pages; the citation rate itself is not a promise and is not the acceptance criterion.

The discipline: the observation contains only what was recorded. The interpretation is labeled as inference and admits alternatives. The recommendation is the smallest action with an acceptance check the agency actually controls.

Cadence, versioning, and what to cut

Report on a cadence the noise floor can support. A monthly full panel is the workable default for most engagements; weekly reporting of a 30-prompt panel mostly reports variance, and a quarterly gap leaves representation errors live too long. Between full waves, report only first-party data and shipped work. Whatever the cadence, version the method: any change to prompts, platforms, run counts, or classification rules gets a new method version in the report header and starts a new comparable series. A trend across method versions is a fabrication with extra steps.

Cut without mercy: decorative screenshots that add no evidence, proprietary scores with no formula, raw prompt dumps in the client layer, generic GEO education, and any recommendation without a parent finding. Before the report ships, run the whole package through the 47-point audit checklist; findings that fail its evidence checks go back to the workbook, not to the client.

Tool: Six handoff checks decide whether this report is deliverable. Method limits in the main document, the four layers kept separate, a roadmap that survives without a citation, and a rerun spec. Confirm what you already do and the checker ranks the rest by weight.

Our position

The strongest thing an agency can put in this report is a sentence most agencies refuse to write: "we did not detect a change." Reporting inside the noise floor as progress spends the client's trust to buy one good meeting, and it converts the whole engagement into score theater that a competitor with a cleaner method will eventually expose. The template's separation of observation from interpretation exists precisely so that "no detectable change, here is what we are doing about it" reads as competence. In our experience of building these systems, it is also the sentence that makes clients extend engagements, because it proves every other sentence was earned.

You can measure AI search visibility this week with nothing but a spreadsheet: freeze a panel of 30 buyer prompts, run each one three times on the platforms your buyer actually uses, log every answer in an observation log, and report mention, citation, and representation-accuracy rates with the denominators visible. What no budget can buy is a census of every AI answer, so treat any single number that claims to be one as marketing, not measurement.

What is observable, and what vendors imply

Three kinds of evidence about AI search visibility actually exist.

First, sampled answers. You can run a declared set of prompts on a declared platform on a declared date and record what came back: whether the brand was mentioned, whether an owned page was cited, whether the statements about the brand were accurate. That is a sample, and it only supports claims about itself.

Second, first-party platform reporting. Google states that AI Overviews and AI Mode traffic is counted inside the Performance report's Web search type, with no separate AI segment, in its AI features documentation. Bing's AI Performance preview reports aggregated citation activity for supported Microsoft experiences.

Third, referral traffic. OpenAI's publisher FAQ says ChatGPT appends utm_source=chatgpt.com to outbound links, which makes clicked visits attributable in analytics.

Everything else is inference. Nobody outside the platforms observes the full population of prompts, the personalized answers other users see, or the influence of an answer that never produced a click. Vendor dashboards that print one visibility score are sampling too; they are just not showing you the sample. The four-layer model is the map for keeping these evidence types apart: eligibility and outcomes come from first-party checks and analytics, evidence and representation come from sampled answers.

The protocol: five working days, one spreadsheet

Day 1: freeze the scope and the facts. Write down the business decision, geography, language, platforms, observation dates, priority pages, and exclusions. Then build the approved fact ledger: the brand's name, offers, locations, credentials, and pricing language as the client wants them stated, each with a source and an owner. Decide now what counts as a material representation error. Scope written after the data arrives is not scope, it is rationalization.

Day 2: freeze the prompt panel. Build 30 prompts from real buyer decisions, split across the four strata of the prompt-set method: roughly 9 problem discovery, 9 category discovery, 8 comparison and fit, and 4 branded validation and risk. That page covers derivation; the rule that matters here is that the panel is frozen before the first run and never edited after you see which wording flatters the client.

Days 3 and 4: run and log. Run every prompt three times per platform, logged out unless the scope says otherwise. One spreadsheet row per prompt per run per platform. Save the full answer text and every cited URL. For a 30-prompt panel on two platforms, that is 180 rows. It is tedious. It is also the entire difference between "I saw" and "we observed."

Day 5: classify, then calculate. Classification comes first because a rate computed over unclassified rows cannot be audited. The next section defines the fields.

Download: AI visibility observation log (CSV template). The exact log used in this protocol: one row per observation with prompt stratum, run number, account state, mention and citation fields, the six-value representation label, evidence link, and validity flag, plus a field guide explaining each column.

Classify before you calculate

Each row gets independent fields, because the events are independent:

• brand mentioned: yes or no
• owned source cited: yes or no
• third-party source cited: yes or no
• representation: accurate, incomplete, outdated, conflicting, unsupported, or not applicable
• competitors named: exact names
• valid observation: yes or no

A mention is not a citation. A citation is not an endorsement. An accurate mention without a citation and a cited page under an inaccurate summary are different findings that demand different work, and a merged field would erase the difference. The citation side of the log has its own expanded schema, with per-URL records and ownership classification, in the AI citation tracking guide.

The validity flag is the quiet workhorse. A row missing its saved answer, exact prompt, date, or platform is marked invalid and never enters a denominator. If the method allows, rerun it; if not, the denominator shrinks and the report says so.

Rates that publish their denominators

For a 30-prompt panel run three times, the denominator is 90 observations per platform. Compute per platform and per stratum, never pooled:

mention rate = observations with a brand mention ÷ valid observations

owned citation rate = observations citing an owned URL ÷ valid observations

representation error rate = material mentions with an error ÷ material mentions reviewed

competitor appearance rate = observations naming the competitor ÷ valid observations

Branded and unbranded strata must never share a denominator. On a 30-prompt panel run three times, the 4 branded validation prompts yield 12 observations and the 18 unbranded discovery prompts yield 54. A brand that appears in 10 of the 12 branded observations and 2 of the 54 unbranded ones has not "appeared in 12 of 66." It has a recognition result and a discovery problem, and the pooled number hides both.

Establish a noise floor before claiming change

Answers vary run to run even when nothing about the site changed. Before attributing movement to your work, measure how much the method moves on its own: run the frozen panel in two waves a few days apart, before any changes ship, and use the spread between waves as your practical noise floor.

Worked example: Reading a follow-up wave against a two-wave baseline

All numbers here are declared assumptions to show the arithmetic, not observations from any real brand.

Assume a 30-prompt panel, three runs, one platform: 90 valid observations per wave, of which the 18 unbranded discovery prompts contribute 54. The example tracks the unbranded discovery rate, because that is the number client work usually needs to move.

The two baselines differ by 4 points with zero intervention, so 4 points is the observed noise floor of this method. The follow-up sits 4 points above baseline B: inside the floor, so the honest reading is "no detectable change yet." A follow-up at 23 of 54 would clear the floor by a wide margin and justify investigation, but it would still be a sampled observation, not proof the fixes caused it.

This is a working heuristic, not a confidence interval. Its job is to stop a 3-point swing from becoming a victory slide.

Kit: GEO Retainer Kit. A noise floor is only worth measuring if the panel behind it stops moving. This kit is the operating shape that keeps it still across months: a cycle calendar whose change log records what each edit does to comparability, the runbooks for one cycle, and the two-page document the client reads at the end of it. The observation method itself is the course, not this.

First-party data belongs beside the log, not in it

Key facts, checked August 7, 2026

• Google reports AI Overviews and AI Mode activity inside the Search Console Performance report under the Web search type, and states that indexing and serving are never guaranteed, per Google Search Central.
• OpenAI's crawler documentation states that sites which disallow OAI-SearchBot will not be shown in ChatGPT search answers, and that GPTBot governs model training, not search inclusion.
• Bing's AI Performance public preview, announced February 10, 2026, reports total citations, average cited pages, sampled grounding queries, and page-level citation activity, and warns these metrics do not indicate ranking, authority, or page importance, per the Bing Webmaster Blog.

Use these sources as separate columns of evidence with their own denominators. Bing counts citations across all traffic to supported Microsoft experiences; your panel counts observations of 30 frozen prompts. Both are real, and adding them together produces a number that means nothing. The practical reconciliation workflow is in the Bing AI Performance guide.

Our position

We refuse single-number AI visibility scores, including our own. A composite score needs weights, and every weight is an editorial opinion wearing a lab coat: it silently decides that a citation is worth some multiple of a mention, that platforms are interchangeable, and that branded and unbranded prompts can share a denominator. When the score moves, nobody can say which opinion moved it. We report per-layer, per-platform rates with visible denominators instead. When a stakeholder insists on one number, we give the unbranded mention rate with its denominator attached, because that is the number their pipeline actually feels.

Where the numbers go next

Tool: Seven of the 47 checks cover the observation log alone. Character-exact prompt text, account state, full answer evidence, absence classified alongside every mention, and citations counted apart from prose. Tick what your spreadsheet already holds and the rest comes back ranked by weight.

Run the panel through the 47-point audit quality gate before any number reaches a client, then write the findings into the client report template, which keeps observation, interpretation, and recommendation in separate fields. If you are deciding whether a tracking tool should replace the spreadsheet, apply the criteria in the method-first tools comparison: a tool that will not show its prompts, runs, and denominators is asking you to report numbers you cannot defend.

AI search visibility is not one question, it is four, and they must be answered in order: technical eligibility (can answer engines reach and use your pages), evidence (do sampled answers draw on your sources), representation (when the brand appears, is it accurate), and outcomes (does observable traffic or action follow). Each layer gates the next, so any diagnosis starts at the earliest layer that fails, and any score that averages the layers together destroys the information you paid to collect.

The model in one view

Ask ten marketers whether a brand is "visible in AI search" and you get ten confident, incomparable answers: one pasted a prompt into ChatGPT, one read a screenshot thread, one is quoting a tool that prints a proprietary score with no method behind it. None of that survives a paying client's three reasonable questions: what is happening, how do you know, and what should we do.

The four-layer model exists to make those questions answerable. Reading the diagram top to bottom: technical eligibility feeds evidence, evidence feeds representation, representation feeds outcomes, and each connection is a gate that the layer above must pass before the layer below means anything.

Figure: The four-layer model of AI search visibility. Each layer gates the one below it, so diagnosis always starts at the earliest failing layer.

Layer one: technical eligibility

Before any answer engine can use your content, its systems have to reach and read the pages that matter: robots directives, response codes, rendering, index controls, canonical signals, facts present in rendered text. Boringly technical, completely decisive.

The failure mode is silence. A disallowed crawler produces no error a marketer ever sees, just absence, and absence gets misdiagnosed as "the algorithm does not like us" when the real cause is a header nobody has inspected since the last migration. This is also the only layer where the platforms publish hard rules: OpenAI's crawler documentation states that sites disallowing OAI-SearchBot will not be shown in ChatGPT search answers, and Google's AI features documentation says a page must be indexed and snippet-eligible, with no additional AI-specific requirements. Which crawler governs what is covered in the OAI-SearchBot versus GPTBot guide.

Eligibility questions have observable, checkable answers. That is exactly why they come first.

Layer two: evidence

Reachable is not the same as used. The second layer asks whether answers to relevant buyer questions actually draw on your sources: linked, cited, or paraphrased. Your pages are candidates here, but so is everything else the engine can retrieve about you: directories, reviews, old press, a competitor's comparison table.

This is where public GEO conversation collapses, because people sample one prompt, once, on one surface, and generalize. Answer engines are probabilistic and personalized; a single observation is an anecdote. The professional version is a controlled sample: a frozen prompt panel derived from buyer decisions, repeated runs, every observation preserved, exactly as specified in the measurement protocol. Small, boring, repeatable. That is what turns "I saw" into "we observed."

A layer-two failure means the retrieval pool around your buyer's questions is owned by other people's documents. The fix is evidence work, not markup tricks.

Layer three: representation

When the brand does appear, is it described accurately? Wrong pricing, dead product names, a competitor's feature attributed to you, a three-year-old positioning statement recited as current fact. Representation errors are more commercially dangerous than invisibility, because a buyer who reads a confident wrong answer does not know it is wrong, and neither do you until you check.

Representation is classifiable, which is what makes it reportable: every material statement in a sampled answer is compared against an approved fact ledger and labeled accurate, incomplete, outdated, conflicting, or unsupported. Classification against approved facts is what makes the finding client-safe rather than an opinion about tone.

Layer four: outcomes

Finally the commercial layer: does any of this move enquiries, demos, trials, sales? It is the layer everyone wants to discuss first and the layer with the least direct evidence. Referral clicks are partially observable: OpenAI's publisher FAQ documents the utm_source=chatgpt.com parameter on ChatGPT links, and Google keeps AI Overviews and AI Mode activity inside Search Console's Web search type. Assisted influence, the answer that shaped a decision without a click, is mostly not observable today.

The honest position: report outcomes as directional, tie them to the evidence in layers one through three, and refuse to invent a number where none exists. Clients do not leave because you told them measurement has limits. They leave because you promised what you could not show.

The gating is the point

The layers form a dependency chain, and the chain is what makes this an audit instead of a debate. There is no evidence without eligibility. Representation problems are only findable once real answers exist to inspect. Outcome claims without the first three layers are astrology with a dashboard.

Two practical consequences follow. First, diagnosis always starts at the earliest unresolved layer, because work on a later layer is unfalsifiable while an earlier one fails: content investment cannot be evaluated while a crawler block is live, and no amount of representation polish matters on pages no engine reads. Second, the layers must never be averaged. A composite score that blends an eligibility pass with a representation failure manufactures a middling number out of two findings that demand opposite actions.

Key facts, checked August 7, 2026

• Google states AI Overviews and AI Mode have no additional technical requirements beyond normal indexing and snippet eligibility, and that serving is never guaranteed, per Google Search Central.
• OpenAI states OAI-SearchBot governs ChatGPT search inclusion while GPTBot governs model training, per OpenAI's crawler documentation.
• Bing's AI Performance preview reports citation activity for supported Microsoft experiences and explicitly warns the counts do not indicate ranking, authority, or page importance, per the Bing Webmaster Blog.

Running a layer-by-layer diagnosis

Work the table top to bottom and stop at the first failing row. The finding is the layer, the evidence, and the smallest action that would clear the gate.

The sentence this produces, "your problem is at layer two, here is the evidence, here is the fix," is worth more to a client than any visibility score on the market. The 47-point audit checklist turns this diagnosis into a scored protocol, and the report template gives each layer its own section so the findings stay separated all the way to the client.

Tool: Grade your own protocol layer by layer. The checker scores the same gates as separate sections, so a complete technical review cannot cover for a panel you never froze. It grades your method, not the brand, and it never estimates visibility.

Our position

This model is deliberately conservative, and that is our editorial position: a layer is not "done" because work happened in it, only because its gate check passes with evidence another practitioner could inspect. We reject maturity-model framings where a brand earns points in all four layers simultaneously, because they let vendors sell layer-four dashboards to brands with layer-one blockers. Sequence is the product. Anyone selling you outcomes before eligibility is selling astrology.

This framework is the thinking layer of the AI Search Visibility Audit System, which turns it into a full working service: the scoped prompt protocol, the observation method, the representation baseline, and the client report, proposal, and 90-day roadmap that package it.

OAI-SearchBot, GPTBot, and ChatGPT-User are three different OpenAI agents with three different consequences. Allow OAI-SearchBot if you want pages eligible to appear in ChatGPT search answers. Disallow GPTBot if you want content excluded from future model training. ChatGPT-User performs fetches a human triggered inside ChatGPT, and OpenAI notes robots.txt rules may not apply to it. The two policy decisions are independent, and the most common commercial configuration is: allow search, decide training separately.

Key facts, checked August 7, 2026

• OpenAI's crawler documentation (platform.openai.com/docs/bots, currently served at developers.openai.com/api/docs/bots) lists OAI-SearchBot, GPTBot, ChatGPT-User, and OAI-AdsBot as distinct user agents.
• OpenAI states: "Sites that are opted out of OAI-SearchBot will not be shown in ChatGPT search answers."
• OpenAI states: "Disallowing GPTBot indicates a site's content should not be used in training."
• OpenAI publishes IP ranges for verification at openai.com/searchbot.json, openai.com/gptbot.json, and openai.com/chatgpt-user.json.
• OpenAI's publisher FAQ says it can take about 24 hours after a robots.txt update for its search systems to adjust.

Three agents, three jobs

The names look interchangeable and the consequences are not. Here is each agent in plain language, per OpenAI's crawler documentation.

OAI-SearchBot is the search crawler. It discovers and fetches pages so they can be surfaced, linked, and summarized in ChatGPT's search features. Blocking it removes the site from ChatGPT search answers. Allowing it makes the site eligible; it does not make inclusion or citation likely, only possible.

GPTBot is the training crawler. It collects content that may be used to train OpenAI's foundation models. Blocking it signals that your content should not be used for training. It has no documented role in whether you appear in ChatGPT search.

ChatGPT-User is not a crawler in the scheduled sense. It fetches a page when a user's action inside ChatGPT or a Custom GPT requires it, for example asking about a specific URL. Because the fetch is user-initiated, OpenAI notes robots.txt rules may not apply. Treat it like a browser you cannot opt out of through robots.txt alone; access controls and authentication remain your levers.

OAI-AdsBot exists too: it validates pages submitted as ChatGPT advertisements. Most publishers can ignore it until they buy ads.

What a robots.txt line actually buys you

A robots.txt rule is a forward-looking instruction to a specific user agent. Three consequences follow that trip people up.

First, the change is not instant. OpenAI's publisher FAQ says its search systems can take about 24 hours to reflect a robots.txt update. Audit screenshots taken an hour after the deploy prove nothing either way.

Second, blocking is not erasure. The documentation describes what future crawling will respect. It does not describe retroactive removal of content already collected, so do not promise a client that a GPTBot disallow deletes anything from an existing model.

Third, a blocked page can still surface as a bare link. Per the same FAQ, if OpenAI learns a disallowed URL from a third-party search provider or from crawling other pages, it may show just the link and title. The documented way to prevent that is a noindex meta tag, which requires the crawler to be able to read the page. A page that blocks the crawler and relies on a meta tag it cannot fetch has an unenforceable policy.

The decision table

Pick the row that matches the client's actual intent, then implement exactly that.

Copy-paste robots.txt for each policy

Merge these into the existing file rather than replacing it, and test the final result. A conflicting or more specific group elsewhere in the file can change the effective outcome.

Policy 1: allow both declared uses.

User-agent: OAI-SearchBot
Allow: /

User-agent: GPTBot
Allow: /

Policy 2: search yes, training no. This is the configuration most marketing sites ask for.

User-agent: OAI-SearchBot
Allow: /

User-agent: GPTBot
Disallow: /

Policy 3: exclude both.

User-agent: OAI-SearchBot
Disallow: /

User-agent: GPTBot
Disallow: /

Policy 4: open marketing site, closed sensitive paths.

User-agent: OAI-SearchBot
Disallow: /portal/
Disallow: /drafts/

User-agent: GPTBot
Disallow: /portal/
Disallow: /drafts/

Remember what none of these blocks: ChatGPT-User fetches triggered by a person, and any crawler that ignores robots.txt. Robots.txt is a published policy, not an access control. Anything genuinely confidential belongs behind authentication.

Verify the policy like an auditor

Configuration is a claim; verification is evidence. After any change:

1. Fetch the public robots.txt without authentication and archive the body, status, and timestamp.
2. Evaluate each agent's group against every priority URL, not just the homepage.
3. Confirm the CDN, WAF, or bot-management layer is not blocking an agent you allowed. Security products frequently block AI crawlers by default, which silently defeats a search-visibility objective.
4. If you have log access, verify claimed crawler hits against OpenAI's published IP ranges (searchbot.json, gptbot.json, chatgpt-user.json) before treating them as real. User-agent strings are trivially spoofed.
5. Recheck about 24 hours later, and again after any CDN or security-rule deployment.

Keep the evidence labeled honestly: a robots.txt capture proves the served policy, a verified log hit proves a fetch, and neither proves inclusion, citation, or training use. That separation between access and outcomes is the first layer of the four-layer visibility model, and the full access review sits inside the 47-point audit checklist.

Our position

Our position: search discovery and training consent are different decisions with different owners, and a consultant should never merge them. "Improve our ChatGPT visibility" authorizes an OAI-SearchBot review. It does not authorize silently changing the client's training policy, which is a governance call for the business owner, sometimes with legal input. Record the approved choice for each agent, the change date, the exact rules deployed, and the rollback text. The engagement should leave a paper trail, not just a robots.txt diff.

Tool: Seven of the 47 checks cover technical eligibility. Public responses, robots rules, indexability, canonicals, rendered text, structured facts, and a date on every one of them. Confirm what you verified and the checker ranks the rest of the protocol against it.

This page covers OpenAI's agents specifically. Google takes the opposite architecture, with AI Overviews and AI Mode riding the normal search index and the standard snippet controls, sorted requirement by requirement in the AI Overview technical requirements guide and covered structurally in GEO vs SEO. For the reporting side of Microsoft's ecosystem, see Bing Webmaster Tools AI performance.

The AI Performance preview in Bing Webmaster Tools is the first mainstream first-party report of AI citation activity: it shows how often your pages were displayed as sources in supported Microsoft AI experiences, which pages, and a sample of the retrieval phrases involved. Use it as a labeled first-party column beside your prompt-panel data. Do not use it as an AI rank tracker: Bing itself says the counts do not indicate ranking, authority, or page importance.

Key facts, checked August 7, 2026

• Bing announced the AI Performance public preview in Bing Webmaster Tools on February 10, 2026, per the Bing Webmaster Blog.
• The report covers Microsoft Copilot, AI-generated summaries in Bing, and select partner integrations, described generically as supported AI surfaces.
• Its measurement categories are Total Citations, Average Cited Pages, Grounding Queries, and Page-level Citation Activity, plus a visibility trend timeline; Bing states grounding queries are a sample, not a complete list.
• Bing explicitly warns the metrics do not indicate placement or presentation, ranking, authority, or page importance, and confirms robots.txt and other content controls are honored.
• The feature is a preview: metric names, definitions, and coverage can change, so recheck the interface before every client report.

What the preview actually reports

No screenshots here, deliberately: the interface is a preview and will drift. Described honestly, the report is a dashboard inside Bing Webmaster Tools for a verified property, with a selectable date range, four measurement blocks, and a trend graph.

Total Citations counts how many times your pages were displayed as sources in AI-generated answers during the selected period. It is an aggregate event count across all users of the supported surfaces, which is exactly what your sampled panel can never see, and why the two must stay separate.

Average Cited Pages reports the average number of unique pages from your site displayed as sources per day. Together with total citations it tells you whether citation activity is concentrated on one page or spread across many.

Grounding Queries lists key phrases the AI used when retrieving content that ended up cited. Two cautions: Bing says this is a sample, and these are retrieval phrases, not the text users typed. Treat them as themes, never as a prompt-demand dataset.

Page-level Citation Activity shows citation counts for specific URLs, revealing which pages participate in AI answers at all. The trend timeline puts the citation counts on a time axis, which is where over-interpretation usually starts.

How the data flows, and why it is not a rank

The diagram below traces both pipelines. In text: Bing's pipeline runs from your site pages (subject to robots.txt), through Microsoft's retrieval, into AI answers that display sources, and finally into the aggregated AI Performance report. Your pipeline runs from a frozen prompt panel into an observation log. Both feed the client report as separately labeled sources with different denominators, and they are never summed.

Figure: Two pipelines into one client report: Bing's aggregated first-party citation reporting and your controlled prompt panel. They answer different questions and keep separate denominators.

The missing arrow is the point: nothing in either pipeline reports where a citation appeared inside an answer, how it was presented, or whether anyone acted on it. Bing states this directly, which is more honesty than most third-party AI visibility dashboards manage. A rising citation trend is evidence of participation, not position.

Client-safe wording for each metric

Folding it into the measurement protocol

The preview slots into the measurement protocol as a first-party evidence column with three rules.

Log every export. Preview interfaces change, and a trend across changed definitions is broken. Record the date range, filters, the interface's current metric definitions, and known site changes during the period, every time.

Download: Bing AI Performance export log (CSV template). One row per export: property, date range, comparison period, the four metric values, top cited URLs, grounding-query themes, current interface definitions, site changes in the period, and the panel wave it is reported beside.

Keep denominators apart. Bing counts citation events across all users of its surfaces; your panel counts your own frozen observations. A workable report sentence: "Bing Webmaster Tools reported 84 citations to 11 pages during July. In our separate 30-prompt, three-run Copilot panel, an owned page was cited in 14 of 90 valid observations. These datasets have different coverage and are reported separately." Fold both into their own labeled subsection of the client report, and never one chart.

Use each source for what it is good at. The panel answers "what happens on the buyer questions we chose"; the Bing report answers "how much citation activity exists beyond our sample." Disagreement between them is information: heavy reported citation activity alongside a silent panel usually means your panel is missing question territory where the site already participates.

From cited pages to next actions

Citation data earns its place when it changes work priorities. Check the earliest layer of the four-layer model before celebrating or panicking, then use the table.

After a material content fix, Bing positions IndexNow as the way to notify participating engines of changed URLs, per its documentation; the honest framing is "we notified, then monitored," never "we resubmitted, so citations will follow." Nothing on this page or in the Bing report guarantees a future citation.

Tool: Keeping this denominator separate is a scored check. Platform counts and panel observations are different populations, and the protocol grades whether your record keeps them apart, alongside 46 other checks on scope, eligibility, sampling and handoff.

Our position

Take the preview seriously and its framing literally. First-party citation data from a platform is strictly better evidence than any scraped estimate of the same thing, and agencies should adopt it now. But the moment a report converts these counts into an "AI rank" or folds them into a composite score, it manufactures exactly the black box that Bing's own caveats warn against. The preview's caveats are not fine print to route around. They are the most honest sentences in the entire AI visibility tooling market right now, and your client report should quote their substance, not bury it.

Price an AI visibility audit from scope, not from a competitor's number: price = (delivery hours x loaded hourly cost + direct tool cost) / (1 - target gross margin). Under the declared assumptions worked below, that produces roughly $3,000 for a small diagnostic, $9,200 for a standard agency audit, and $25,700 for a complex multi-market engagement. Those are derived planning figures from stated inputs, not observed market benchmarks, and the fastest-growing input is always the observation count: prompts times platforms times repeated runs.

There is no reliable public price sheet for this service, and copying a competitor's retainer is copying a number whose prompt sample, platforms, evidence standard, deliverables, and implementation boundary you cannot see. Cost gives you a floor. The client's decision value and willingness to pay set the ceiling. Everything here is about computing the floor honestly.

The three cost drivers that actually move the fee

Observation volume. The audit's variable cost is mostly evidence capture, and it multiplies: a 30-prompt panel on three platforms with three repeated runs is 270 observations. At two to three minutes each to run, save, and classify, that is nine to fourteen hours before anyone reviews a citation or checks a fact. This is why "just add Perplexity" is never a small favor: one added platform on that panel is 90 new observations.

Evidence standard. An audit that saves exact prompts, full answers, classifications, and fact-ledger comparisons (everything the 47-point audit checklist requires) costs two to three times the hours of a screenshot deck. This is the difference between a defensible audit and a demo, and it is the difference clients are actually paying for.

Scope surface. Pages, competitors, languages, locations, and stakeholder count each add fixed chunks of work: more technical checks, more fact approvals, more findings to write, more meetings.

Estimate hours per workstream, from the work itself:

These are derived planning ranges assuming an experienced practitioner, one language, cooperative client inputs, and a documented workflow. They are not industry benchmarks; replace them with your own time data after two engagements, which is the single highest-leverage pricing improvement available to you.

Loaded hourly cost means the real internal cost of the person: salary or contract cost plus employment burden plus the non-billable time their billable hours must carry. It is not the rate on your invoices. The U.S. Small Business Administration's break-even guidance treats price, variable cost, and margin as one connected decision; this model applies that discipline to a scoped service.

The calculator excludes taxes, payment fees, sales cost, and local legal requirements; add those in your own commercial model. Round the output to a sensible number after the math, never instead of it.

Three worked calculations at three scopes

Worked example: Small diagnostic baseline, priced at $3,000

Declared assumptions: 16 prompts, 2 platforms, 2 runs per prompt per platform (64 observations), 5 priority pages, essential technical checks, a decision memo instead of a full report. Solo practitioner with a loaded cost of $65 per hour; $60 of tool cost; 50 percent target gross margin.

Hours: discovery 2, technical 4, prompt design 3, observation and classification 5, source map 2, findings and memo 4, handoff 2. Total 22 hours.

Delivery cost = 22 x $65 + $60 = $1,490 Price floor = $1,490 / (1 - 0.50) = $2,980, rounded to $3,000

The diagnostic exists to answer one question: does a full audit look justified? Price it low enough to be an easy yes, high enough that you are not subsidizing discovery.

Worked example: Standard client audit, priced at $9,200

Declared assumptions: 30 prompts, 3 platforms, 3 runs (270 observations), 10 priority pages, full fact ledger, competitor comparison on the same panel, client report and 90-day roadmap. Loaded cost $75 per hour for a senior practitioner; $250 in tools; 55 percent target margin.

Hours: discovery 4, technical 7, prompt design 6, observation and classification 14, source and competitor map 6, findings and roadmap 8, report and handoff 7. Total 52 hours.

Delivery cost = 52 x $75 + $250 = $4,150 Price floor = $4,150 / (1 - 0.55) = $9,222, rounded to $9,200

Note what the margin is for: it funds the sales cycle for deals that do not close, methodology maintenance, and the re-run when a platform changes an interface mid-engagement. It is not padding.

Worked example: Complex multi-market audit, priced at $25,700

Declared assumptions: two languages and regions, so two 30-prompt panels on 3 platforms with 3 runs (540 observations), 20 priority pages across two locales, regulated-industry fact review, compliance sign-off, and two stakeholder workshops. Blended loaded cost $85 per hour across a senior lead and an analyst; $600 in tools; 60 percent target margin, reflecting higher delivery risk.

Hours: discovery and stakeholders 10, technical 16, prompt design 12, observation and classification 28, source and competitor map 14, findings and roadmap 16, compliance review 6, report, workshops, and handoff 12. Total 114 hours.

Delivery cost = 114 x $85 + $600 = $10,290 Price floor = $10,290 / (1 - 0.60) = $25,725, rounded to $25,700

At this scope, price discovery separately and first. Every unresolved variable (which regions, which platforms, how many stakeholders) swings the fee by thousands, and guessing on the client's behalf is how complex audits become unprofitable.

If a computed floor is too high for a buyer, the honest moves are to cut named scope (fewer platforms, a diagnostic instead of a full audit), improve delivery efficiency, or choose a different buyer. The dishonest move is keeping the price and quietly cutting the evidence standard, which produces the screenshot-deck audits this market is already drowning in.

Keep audit, implementation, and monitoring priced apart

The audit diagnoses and prioritizes. Implementation changes facts, content, technical controls, and profiles. Monitoring re-runs a declared panel on a schedule and reviews first-party signals. These have different owners, different acceptance criteria, and different margins, and bundling them into one undefined "GEO retainer" makes both the margin and the client's expectations unmanageable. Sell the audit fixed-fee against the scope in the proposal template, and let monitoring or implementation be its own decision after the roadmap exists. The transition conversation is easier, not harder, when the audit was priced and delivered as a bounded product, and it is the natural expansion path described in how to sell AI visibility audits.

Mid-engagement, the fee changes only through scope: added platforms, languages, pages, competitors, prompts, runs, or deliverables, priced from the same model before the work starts. Lower the fee only by removing something named. A discount with unchanged scope is a silent decision to cut evidence quality later.

Kit: GEO Retainer Kit. Pricing monitoring apart is the easy half. Deciding what it is each month is the half that decays. This kit is the retainer agreement, an eight-tab cycle calendar, the monthly and quarterly runbooks, the two-page document the client reads at the end of a cycle, and four routes for a request that arrives outside scope. It carries no audit method and no second copy of the KPI framework.

Underpricing is how audits stop being audits

Our position

Our position is that underpricing does more damage to this service than overpricing ever could, because the price quietly sets the evidence standard. An agency that sells a "full AI visibility audit" for $1,500 has two options: lose money or skip the work that makes the audit defensible, and they always skip the work. No frozen panel, single runs, no fact ledger, mentions and citations blended, findings asserted rather than traced. The client pays for measurement and receives theater, then reasonably concludes the whole category is snake oil, and the next honest agency inherits that skepticism. Price from the observation math, show the math to the buyer, and let the cheap competitor explain what their number includes. A practitioner who cannot defend their price from their scope should not yet be selling audits.

Tool: A fee is only defensible if the protocol behind it is. The calculator prices the scope. This one grades the method inside it across 47 weighted checks, so you find out which sections are thin before a buyer asks what their money bought.

Estimate your observation count from the prompt-set method, run your own numbers through the calculator above, and track actual hours by workstream from the first engagement, so your second price is built on your evidence instead of this model's assumptions.

A defensible AI visibility audit proposal sells a controlled decision, not a mystical score: a reproducible baseline, traceable findings, and a prioritized plan, with every outcome you cannot control named as an explicit exclusion. This page is the complete template, section by section, with the exact language to use and the promises to refuse. The Markdown file below is ready to adapt; have local counsel review contractual language before signature.

Download: AI visibility audit proposal template (Markdown template). All ten sections with bracketed fields: objective, scope, method, client inputs, deliverables, exclusions, acceptance criteria, timeline and change control, fee, and the responsible-use statement, plus signature blocks.

Key facts, checked August 7, 2026

• The FTC requires advertisers to have a reasonable basis, meaning objective evidence, for claims before an ad runs, and at minimum the level of evidence the claim states. A proposal promising AI rankings an agency cannot substantiate creates exactly this exposure. Source: FTC advertising FAQ for small business.
• Google states there are no additional technical requirements and no special schema to appear in AI Overviews or AI Mode, which is why a proposal promising secret AI optimization is promising something the platform says does not exist. Source: Google Search Central.

What the buyer is actually purchasing

Before any section, get the frame right, because every language pitfall in audit proposals comes from misstating what is for sale. The client is buying three things: a baseline another practitioner could reproduce, findings that trace to saved evidence, and a roadmap with owners. They are not buying a visibility outcome, because nobody outside the platforms controls one. A proposal that implies otherwise wins the deal and loses the relationship at the first quarterly review, and the honest version is genuinely easier to sell to a skeptical buyer, as covered in how to sell AI visibility audits.

One gate before you write anything: if you cannot fill in the scope fields below from real information, do not guess and do not pad the fee for uncertainty. Sell a short paid discovery phase first. A proposal written before discovery is a fee attached to assumptions.

Objective and scope: where disputes are prevented

The objective section needs exactly one sentence pattern:

[Agency] will assess how [audience] can encounter and understand [client brand]
while deciding [business decision], across [declared platforms], in [geography]
and [language], producing a reproducible baseline, material gap findings, and a
prioritized action plan for the next [period].

Say "assess how the brand can encounter and understand," never "improve how the brand ranks." The first is observable work; the second is a promise about platform behavior. Pitfall language to strike from drafts: "dominate AI search," "become the recommended answer," "optimize for every model." Each one is an objective claim about outcomes you cannot substantiate, which is the FTC's reasonable-basis problem wearing a sales hat.

Scope needs six declared fields, and each one exists because its absence has a specific failure mode:

• Brand and offers. One legal or trading name and named offers. Without it, findings sprawl into service lines nobody asked about.
• Platforms and surfaces, including account state and location context. "AI search" is not a platform; "ChatGPT search, signed out, US context" is.
• Prompt panel: count, strata, run count, and date window, frozen before observation. This imports the whole method of the buyer-decision prompt set into the contract.
• Priority pages, listed or defined by a selection rule.
• Competitors, named or selected by a rule written before observation, always measured on the same panel and denominator.
• Technical review, itemized: public response, robots and crawler access, indexability and snippet controls, canonicals, rendered text, structured-versus-visible facts.

Method, inputs, and deliverables

The method section is short and load-bearing. Commit in writing to freezing the panel before observation, preserving exact prompts and full answer evidence, classifying mentions and citations separately, grading statements against a client-approved fact ledger, and labeling findings observed, verified, inferred, or unknown. Then add the sentence that protects every future engagement: like-for-like comparisons use the same declared method version, and a material method change starts a new baseline. This matches the open measurement protocol, and referencing a published method in the proposal is itself a trust signal.

Client inputs deserve their own numbered list with a deadline: one authorized owner, written approval of everything in scope, the approved fact ledger with a source per claim, agreed tool access, and response times for factual questions. The pitfall is politeness. If the input section has no consequence attached, the fact ledger arrives six weeks late and the delivery date is still yours. Tie delays to a day-for-day extension and to change control.

Deliverables should be countable artifacts: the scope and method record, the dated fact ledger, the technical eligibility record for a stated number of pages, the frozen panel and observation log, the mention, citation, representation, and source baseline with competitor comparison, findings traced to evidence, the client report, the handoff session, and a 90-day roadmap with owners and acceptance checks. Each maps to a section of the 47-point audit checklist, which functions as your internal quality gate; keep the internal scoring out of the proposal unless the buyer benefits from seeing it.

Exclusions: the section that sells

List, as items not included unless added in writing: guarantees of any ranking, mention, citation, recommendation, sentiment, traffic, lead, or revenue outcome; a census of all prompts, users, models, or answers; access to or claims about platform-internal systems; implementation work; continuous monitoring past the observation window; additional languages, regions, brands, or platforms; and legal or regulatory advice.

Our position

The refusal to guarantee outcomes belongs in the proposal as a selling point, stated proudly, not buried as legal hedging. Our position is that in this market the guarantee is the red flag: any vendor promising AI citations is promising behavior of systems they neither control nor observe, and a buyer who gets burned by one becomes every honest agency's hardest prospect. The agency that writes "nobody can guarantee how these platforms behave, so we do not, and here is the controlled evidence we deliver instead" is making a claim a competitor cannot copy without abandoning their pitch. Sophisticated buyers, the ones worth keeping, read the exclusions section first. Give them a reason to trust the rest of the document.

This section also pre-answers the most common sales objection, "how do we know it worked?", with something better than a promise: acceptance criteria.

Tool: Six of the 47 checks live in the proposal, not the audit. One named business decision, recorded owner consent, fixed geography and language, declared platforms, bounded offers, and written exclusions. All six are settled in this document, and the checker grades them alongside the other 41.

Acceptance, timeline, and fee

Acceptance criteria convert "done" from a feeling into a checklist: every scope field filled, the frozen panel preserved, every material finding traced to evidence, the four evidence layers reported separately, every roadmap item owning an owner and an observable completion check, limits and unknowns visible, deliverables opening in the agreed formats. A client who co-signs these criteria cannot later demand acceptance conditioned on a visibility outcome, because the document already defines acceptance.

Timeline language has one pitfall: quoting a start date before inputs exist. Anchor the window to a start condition ("five business days after section 4 inputs are complete") rather than a calendar date you do not control. Put change control next to it: added prompts, runs, platforms, pages, competitors, languages, or deliverables change the fee and window, presented in writing before the added work begins. Every scope addition multiplies observations, not just effort; one added platform on a 30-prompt, three-run panel is 90 new observations to capture and classify.

Price the declared scope with the scope-first pricing model rather than working backward from a competitor's number whose scope you cannot see. A fixed fee is safe exactly when the scope section above is complete; that is the commercial reason the scope rigor pays for itself.

The responsible-use statement

End with the paragraph that makes the whole document coherent:

Generative answers vary by platform, model, location, account state, wording,
and time. This audit reports a controlled, declared sample and available
first-party evidence; it cannot guarantee how any platform will behave.
Recommendations are designed to improve public clarity, technical eligibility,
evidence quality, and buyer usefulness even where sampled answers do not change.

The last sentence is the quiet test of the engagement's worth. If your roadmap would be worthless when sampled answers stay unchanged, the audit was theater, and this statement will feel dangerous to include. If the roadmap fixes real representation conflicts, real eligibility failures, and real evidence gaps, the statement costs nothing and reads as confidence. Write the proposal so that sentence is true, deliver against it, and hand the results over in the client report template.

GEO does not replace SEO, and it is not just SEO renamed. Four things genuinely change: the crawler policies you manage, the surfaces where visibility evidence appears, the way you measure it, and the deliverables a client pays for. The foundations, crawlability, indexation, rendered text, and pages worth citing, carry over unchanged. Sell the difference as a bounded audit with a declared method, not as a new discipline with new promises.

Demand is real, definitions are not

The argument about the acronym is mostly noise. The demand behind it is measurable. DataForSEO-derived estimates published by Tracemetry in May 2026 put "AI search engine optimization" at 8,100 U.S. monthly searches, "generative engine optimization" at 4,400, and "GEO vs SEO" at 2,900, with 510 percent year-over-year growth on the comparison query itself. These are third-party index estimates: useful for sequencing which pages and services to build, useless as traffic forecasts.

Whether the label is GEO, AEO, LLM SEO, or answer engine optimization, the buyers behind these queries are mostly agencies and in-house marketers deciding whether to build a service or buy one. That framing matters, because the honest answer to "GEO vs SEO" is a work breakdown, not a winner. Here are the four places the work actually diverges.

Change 1: crawler policy splits into separate decisions

Classic SEO manages one crawl relationship per engine: let Googlebot in, let Bingbot in, done. AI search adds agents whose robots.txt rules carry different consequences and therefore need separate decisions.

OpenAI alone documents three relevant agents. OAI-SearchBot controls whether a site can appear in ChatGPT search answers. GPTBot controls whether content may be used to train future models. ChatGPT-User fetches pages when a user asks about them, and OpenAI notes robots.txt rules may not apply to those user-initiated fetches. A publisher can allow search discovery while refusing training with two robots.txt groups, which is a governance decision no classic SEO engagement ever had to record. The directive-by-directive comparison, with copy-paste policy blocks, is in OAI-SearchBot vs GPTBot.

Google went the opposite direction and merged the decision into normal Search. Its AI features documentation states there are "no additional requirements to appear in AI Overviews or AI Mode," no special structured data, and no new machine-readable files. Eligibility rides on the standard index and the standard snippet controls; the claim-by-claim sorting of what Google documents against what circulates is in the AI Overview technical requirements guide.

So the crawler work changes shape, not difficulty: fewer tricks, more policy. Someone at the client has to own the training-consent decision, and it should never be a consultant quietly editing robots.txt.

Key facts, checked August 7, 2026

• OpenAI documents OAI-SearchBot (ChatGPT search inclusion), GPTBot (model training), and ChatGPT-User (user-initiated fetches) as separate user agents with separate controls.
• OpenAI states that sites opted out of OAI-SearchBot "will not be shown in ChatGPT search answers."
• Google states no additional requirements, schema, or AI-specific files are needed to appear in AI Overviews or AI Mode.
• Search demand figures above are third-party DataForSEO-derived estimates for the United States, published May 2026.

Change 2: evidence moves from positions to answers

A rank tracker observes an ordered results page that most searchers roughly share. An assistant produces a paragraph. The units of evidence become: was the brand mentioned, was it cited as a source, was it described accurately, and which competing sources supplied the answer. None of those has a stable position number, and two users can get materially different answers to the same prompt.

That changes competitive analysis too. In classic SEO you study the URLs above you. In answer surfaces you study the source environment: the review sites, directories, publications, and community threads an assistant repeatedly draws from when your buyers ask their questions. Winning often means being represented correctly inside those sources, not only on your own domain.

Change 3: measurement becomes sampling, not tracking

Because answers vary across runs, accounts, and days, a screenshot of one good answer is an anecdote, not a baseline. Honest measurement borrows from research method instead of rank tracking: freeze a prompt panel built from real buyer decisions, run it repeatedly under declared conditions, classify mentions and citations against an approved fact ledger, and report rates with visible uncertainty. The full method lives in how to measure AI search visibility, and the panel construction in how to build a prompt set.

First-party reporting is also thinner than search operators are used to. Google folds AI-feature impressions into overall Search Console performance data rather than breaking them out, per its AI features guidance, while referral traffic from assistants shows up in analytics only when a user clicks through. You will spend more time qualifying what a number can and cannot support. That discipline is billable; hiding it is not.

Change 4: deliverables shift from rank reports to evidence

A monthly position report makes no sense for a surface without positions. What a client can actually buy:

1. A scoped observation baseline: prompt panel, platforms, repeated runs, dated captures.
2. A technical eligibility review: crawl access per agent, rendering, indexation, canonical state on priority pages.
3. An approved fact ledger and a representation review: what assistants say about the brand, checked against facts the client signed off.
4. A source and competitor map for the panel.
5. A prioritized roadmap with owners, including work that belongs in the existing SEO program rather than a new invoice.

That package is auditable, repeatable, and useful even if no generated answer changes by the next review. How to price it is covered in the audit pricing model, and how to sell it without hype in selling AI visibility audits.

The rebranding triage table

Most of what is marketed under GEO is one of three things: real new work, old work with a new label, or fiction. Triage the claims you will hear:

The dishonest row deserves its own page, because "rank us in ChatGPT" is the single most common buyer request in this market: how to "rank" in ChatGPT walks the four layers that are actually workable and the myths that are not.

Our position

Our position: GEO is a real extension and a bad religion. Most of the work is existing search craft, and any pitch that declares SEO obsolete is selling a name, not a method. But the genuinely new part, crawler governance with separate consequences, evidence sampling across answer surfaces, and representation review against approved facts, produces findings a rank tracker cannot, and it is worth paying for on its own line. Buy or sell the method. Never buy or sell the acronym.

What stays exactly the same

Crawl access, indexability, canonical clarity, server-rendered or reliably rendered text, honest structured data, internal links, and pages that actually resolve a buyer's question. Google's guidance for AI features points publishers back to the same foundations, and every answer engine that cites the web depends on them. An agency that cannot diagnose an indexation problem is not ready to sell a premium AI visibility audit, because the audit's first layer is that diagnosis.

The editorial bar also survives intact: original information, evidence, and a clear page purpose. Scaled near-duplicate content was a bad strategy for search engines and is an equally bad strategy for systems that compress sources into one answer.

Tool: Where the first engagement is usually thin. Before scoping anything, grade the method you would actually deliver against 47 weighted checks. It takes two minutes, needs no account, and it names the sections that are weak rather than rating the brand.

The sentence that closes the meeting

When a client asks which one they need, use this:

SEO keeps the brand's pages eligible and competitive in classic search. AI visibility work adds a controlled view of how answer engines use sources and describe the brand, then turns that evidence into fixes that help both surfaces.

It is accurate, it prices the work as an extension rather than a replacement, and it survives contact with a skeptical CFO. To scope the first engagement, start with the 47-point audit checklist and choose tooling with the method-first tool comparison. If you want the complete delivery system, the AI Search Visibility Audit System packages the method, workbook, report structure, and proposal.

A workshop buys momentum: one or two proposal components drafted under live guidance in a day or two. A course builds capability: the complete proposal system, produced piece by piece over weeks. Choose by the work you need to finish, not by the format's marketing. And if your deadline is under a month away, buy neither; draft from free guidance now and train after you submit.

What each format can actually produce

A grant writing workshop is a compressed live session, usually a half day to two days, in person or on a video call. Run well, it leaves you with three things: a working map of proposal anatomy, one or two components drafted and reviewed in the room (most often a needs statement or a full outline), and an honest list of what your organization still lacks. The classic workshop failure is an agenda packed with information and zero production time. Before you register, ask the organizer one question: what document will attendees leave holding? If the answer is "notes and a slide deck," you are buying a lecture.

A course is a sequenced curriculum consumed over weeks, self-paced or cohort-based. A good one produces the full artifact set: a funder shortlist with eligibility evidence, a needs statement, a logic model, an evaluation plan, a budget with narrative, a letter of inquiry, and a submission workflow. The classic course failure is the mirror image: recorded lectures that never require you to assemble a complete proposal, so you finish "knowing about" grants while owning nothing. The test for both formats is identical. Name the artifacts that exist after the training that did not exist before it.

Free introductory teaching sets the floor for judging either purchase. Candid's Introduction to Proposal Writing is on demand, free, and about one hour long, and Candid's grant proposals knowledge base covers standard proposal structure at no cost. A paid workshop or course has to beat that floor with guided production, feedback, and reusable tools. Information alone is already free.

Start from your deadline, not the format

Deadline pressure decides more than preference does.

Deadline within four weeks. Neither format rescues this proposal. A workshop eats a working day you cannot spare, and a course's payoff arrives after your submission date. Draft directly from free guidance and a published structure such as our nonprofit grant proposal template walkthrough, submit, and schedule training for the week after.

Deadline in one to three months. This is the strongest case for a self-paced course, run against the live proposal so every module's output becomes a section of the real document. You get the deadline met and the system built once, instead of paying twice in time.

No live deadline. Either format works, so decide on learning mode and budget. This is also the only situation where a workshop-first path makes sense as a cheap commitment test before a larger course purchase.

The learning-mode question nobody asks

Self-paced study demands protected work time, and buyers routinely underestimate it. A course that lists "5 hours of lessons" will also need 5 to 8 hours of applied work, and those hours must be defended on a calendar against the same duties that made training feel urgent. If your weeks never contain two quiet hours, a scheduled workshop's external accountability is worth real money, even at a higher cost per artifact.

Workshops carry their own preparation tax. Arriving without a candidate funder, your program facts, and a folder of source documents converts a production day into a note-taking day. If you book one, spend an hour beforehand assembling that packet.

There is also a team version of this decision. Training one person builds one person's skill; it does not create an organizational workflow, and grant proposals are organizational documents where program, finance, and leadership each own facts. If the goal is a shared process, a facilitated internal working session built around your own live proposal, with course materials as the backbone, beats sending a single staffer to either format alone.

Worked example: Pricing both formats for one fictional nonprofit

Rivergate Pantry Network is a fictional food-security nonprofit invented for this calculation. Every number below is a declared assumption, not a quote from a real provider.

Assumptions: a regional one-day workshop at $325 per seat, producing 2 reviewed components in 8 staff hours including travel. A self-paced course at $249 (the price of our own Professional tier, declared here because we sell it), producing 12 working deliverables across 12 staff hours. Staff time valued at $30 per loaded hour.

Read the gap honestly. The workshop's two components include live human review, which the self-paced number does not. And the course figure assumes the learner finishes; completion is the real risk of self-paced study. If you judge your finish probability at 50 percent, double the course's expected cost per component to about $102. It still wins on volume, but the margin is narrower than the raw table implies, and a learner who never finishes pays $609 for nothing.

The decision table

If your real question is whether the training should end in a credential, that is a separate purchase with separate math; we untangle it in certification versus certificate.

What no format can do

Training changes what you can produce. It cannot guarantee what a funder decides, because awards turn on program fit, the funder's budget cycle, and the competing pool, none of which any instructor controls. Treat every provider claim about win rates as a red flag, and treat your own first submission as a system test rather than a referendum, a framing we expand in your first grant proposal.

Our position

Buy a workshop for momentum and a course for capability, and never buy either as a substitute for starting. For the small nonprofits we write for, the free Candid hour plus one disciplined week with good templates outperforms an unexamined $500 seat. The format is the second decision. The artifact you need to finish, on the date you need to finish it, is the first, and once you can name that artifact, this choice mostly makes itself.

A grant writing certification is an independent credential: you meet experience requirements, pass an exam from a certifying body such as GPCI (the GPC) or CFRE International, and renew on a cycle. A certificate is documentation that you completed a course; any provider can issue one. For most small-nonprofit staff, neither is the real purchase. Buy training for the proposal system it makes you produce, and pursue certification only when your career sells grant expertise itself.

Two words, two different products

The words look interchangeable and the marketing wants them to. They are not.

A certificate is proof of course completion. You paid, you finished the modules, you received a document. Nobody independent verified your competence, there was no experience requirement to enroll, and the certificate never expires because there is nothing to maintain. Its value equals the value of the work the course made you produce, no more.

A certification is a credential owned by a body that did not teach you. It typically requires documented professional experience before you may even sit for the exam, tests competencies defined by practitioners, and lapses unless you renew with continuing education. The credential is an attestation about you, not about a course.

The distinction matters most on a resume. Completing an online class does not make you a "certified grant writer," and presenting course completion as professional experience is the kind of inflation that an experienced hiring manager or client spots immediately. Write "Certificate, [course name]" for a certificate and reserve "certified" for an actual credential.

What the credential bodies require

The two credentials that matter in the US grant and fundraising field are the GPC and the CFRE.

The Grant Professional Certified (GPC) credential is administered by the Grant Professionals Certification Institute, and the program is accredited by the NCCA, an independent standards body for certification programs. Eligibility runs on a point system across four areas: education, experience, professional development, and community involvement. Candidates then pass a competency exam and enter an ongoing certification maintenance program.

The CFRE (Certified Fund Raising Executive) is broader than grants; it covers professional fundraising. CFRE International's eligibility requirements count your months of employment as a professional fundraiser and your actual professional performance alongside education, followed by an exam across six knowledge domains and recertification every three years.

Key facts, checked August 7, 2026

• GPC: administered by GPCI, NCCA-accredited, point-based eligibility including documented experience, competency exam, ongoing maintenance requirements.
• CFRE: eligibility built on employment history and professional performance, six-domain exam, recertification required every three years.
• Neither body certifies beginners: both count professional experience before you can sit for the exam.
• Current fees for both credentials are published only on the credential owners' own sites; training providers' summaries go stale.

That third fact resolves a common search: there is no legitimate shortcut to "certification without experience." A beginner's real path is a course, then practice on live proposals, then a credential years later if the career calls for it. Any program selling certification-like language to people with zero proposals behind them is selling a certificate wearing a costume.

What employers actually check

The Bureau of Labor Statistics occupational profile for fundraisers, the closest federal profile to grant work, lists a bachelor's degree as the typical entry-level education and treats certification as a voluntary credential, not a requirement to practice. There is no license to write grants.

What carries weight in hiring and client selection, in our reading of the field, is evidence of finished work: proposals you researched, wrote, and submitted, ideally with outcomes you can discuss honestly, plus a writing sample and demonstrated funder research skill. A credential can strengthen a strong portfolio, and some government and large-institution job postings do name GPC or CFRE. But a credential cannot substitute for the portfolio, while a portfolio routinely substitutes for the credential, especially at the small organizations doing most of the hiring.

Price the full cycle, not the exam fee

Certification costs arrive in more lines than the brochure shows, and several of them recur.

Two habits protect you. First, price the whole first cycle, exam through first renewal, before deciding; comparing exam fees alone systematically flatters the more expensive credential. Second, start a continuing-education log the day you are certified. People who reconstruct years of professional-development records at the renewal deadline lose real time, and occasionally lose the credential. And take every number from the credential owner's current fee schedule, not from a prep provider's summary page; providers sell preparation, and their pricing pages drift out of date.

A decision tree you can run in five minutes

1. Do you sell grant expertise itself? You are a consultant, a career grant professional, or aiming at jobs that name a credential. If no, stop here: take the skills path, meaning a course applied to a live proposal, starting at zero cost with Candid's free Introduction to Proposal Writing. Our course evaluation framework is the follow-on decision. If yes, continue.
2. Do you meet the experience thresholds today? If no, a certificate cannot bridge the gap and neither can enthusiasm. Build proposals for two to three years, then return. If yes, continue.
3. Will a specific employer, client type, or RFP verifiably reward it? Check actual postings and RFPs in your niche for GPC or CFRE language. If yes, certify; the credential now has a payer. If you cannot find one, the money is usually better spent on advanced training or on the tools of delivery, and if you are on the hiring side of this question, our guide to choosing grant writing services covers how to weigh a consultant's credentials against their work.

Our position

Our position: most small-nonprofit staff need skills, not credentials. The staffer who became "the grant person" last quarter gains nothing this year from an exam built for people with years of documented practice, and gains everything from producing one complete, submitted proposal. A credential cannot guarantee a funder's decision or a hiring outcome, and neither can any course, including ours; funders score the proposal in front of them, not the letters after its author's name. Buy the thing that improves the proposal first. The credential can wait until the market you serve asks for it by name.

If the underlying choice is really about training format rather than credentials, start instead with course versus workshop, and if you are pre-first-proposal, with building readiness before persuasion.

A grant proposal template has nine working sections: executive summary, organizational background, statement of need, program description, objectives and outcomes, evaluation plan, budget with narrative, sustainability, and attachments. The complete template is on this page, copyable, and in a free Markdown download with no email gate. Each section comes with what it must prove, how much space it deserves, and the failure reviewers actually see. Assemble every application against the funder's own instructions, which always override any template.

Key facts, checked August 24, 2026

• A nonprofit grant proposal has nine stable sections; the order and lengths below fit most U.S. foundation applications, and the funder's live instructions always override them.
• Candid Learning's grant proposal guide describes the same core components; its free introduction to proposal writing is the standard sector walkthrough.
• Federal applications follow the format their notice of funding opportunity mandates; start those from the notice itself via Grants.gov's applicant resources, not from any generic template.
• The template on this page and the downloadable skeleton are free, complete, and identical in structure; no email address is required for either.
• A template improves review readiness; it cannot guarantee an award, an invitation, or any funder decision.

Most grant proposal templates fail in one of two ways: they are a bare list of headings that tells you nothing about what a reviewer needs from each section, or they are a finished sample whose polished sentences fit someone else's facts. This nonprofit grant proposal template takes the third path. It gives you the structure, the burden of proof each section carries, and the space each deserves, and then it makes you write your own program into it. A template earns its keep by stopping you from forgetting a section a reviewer expects and by telling you when a section is actually done. It does not write the proposal.

One boundary stated plainly: a clean structure improves review readiness, but it cannot guarantee an award, an invitation, or any funder decision. What it can do is remove the self-inflicted rejections, and those are more common than most teams admit.

The template, complete and copyable

Copy the skeleton below straight into your working document, or download the same structure as a Markdown file. This is a free grant proposal template in the plainest sense: the whole thing is on the page, the download adds per-section writing prompts and failure checks, and neither asks for an email address. Length shares assume a ten-page narrative; scale them proportionally for shorter limits, and use the funder's lengths whenever they specify their own.

# [Organization name]: proposal to [funder] for [program name]

## 1. Executive summary (half a page, written last)
Who you are, the documented need, the program that answers it,
the amount requested, and the intended, measurable result.

## 2. Organizational background (one page)
Capacity relevant to THIS program: current work, staffing,
one or two verifiable results with dates. Legal status,
service area, and annual budget stated once.

## 3. Statement of need (1.5 to 2 pages)
Population, condition, consequence, and your relevance, in
that order. A source and data year on every figure.

## 4. Program description (three pages)
Who does what, for whom, when, where, at what capacity.
The participant's path from intake to exit. Staff roles,
partner commitments, and a timeline with owners.

## 5. Objectives and outcomes (half a page)
Each objective checkable later: who changes, in what way,
by how much, by when. Outputs separated from outcomes.

## 6. Evaluation plan (1 to 1.5 pages)
The questions you will answer, the indicators, the data
sources, who collects what and when, and how results
will be reported and used.

## 7. Budget and budget narrative (per funder format)
Every line with unit, quantity, rate, and source, traced
to an activity. Narrative explains basis and purpose.

## 8. Sustainability (half a page to one page)
What continues after the grant, what ends, and what future
decisions depend on. No vague pledge to find other funders.

## 9. Attachments (per funder list)
Only what the funder requests, current, signed, and in the
requested file format.

Download: Grant proposal skeleton (Markdown template). All nine sections with per-section writing prompts, length shares for a ten-page narrative, a named failure check for each section, and a compact letter-proposal variant for small foundations. Reorder freely to match any funder's format.

What each section must prove

Think of every section as answering a skeptical question, not filling a slot. The table gives the question, the space it deserves in a ten-page narrative, and the failure mode that shows up in weak submissions. Together, the table and the skeleton form a complete proposal template map: the skeleton tells you what to write, the table tells you when each section can be called done.

Three of these deserve expansion because they carry most of the weight.

The statement of need must establish population, condition, consequence, and your relevance, in that order, with a source and data year on every figure. It is the section most often written backward, starting from the program and reverse-engineering a need. The full method, with a worksheet, is in the needs statement template.

The program description is the largest section because it is the one a reviewer cannot reconstruct from anywhere else. Your background can be verified, your need can be checked against public data, but only you can explain the operating model. If a stranger cannot sketch a participant's week from this section, it is not finished.

The budget must reconcile with the narrative line by line: every budget line traces to an activity, every staffed activity to a budget line. The grant budget template covers the formulas and reconciliation checks; the evaluation plan template and logic model template do the same for the measurement sections.

Weak versus strong, on the page

The fastest way to calibrate is to see the same content written both ways. Everything below uses Cedar Bend Youth Alliance, a fictional nonprofit invented for worked examples on this site, with illustrative figures. Two companion pages extend this section: a complete annotated sample proposal assembled end to end from the same fictional case, and seven more weak-and-strong passage pairs covering every major section.

Worked example: Statement of need: two openings from a fictional applicant

The fictional Cedar Bend Youth Alliance is requesting funds for an after-school reading program. All figures are illustrative placeholders.

Weak: "Literacy is a growing crisis in our community. Studies show that reading is critical to student success. Cedar Bend Youth Alliance urgently needs funding to continue its vital work helping struggling readers."

Every sentence fails a different way. The first claims a trend with no data. The second cites "studies" without a source. The third commits the classic circular need: the applicant's funding gap presented as the community's problem.

Strong: "In the Cedar Bend school district, 41 percent of third graders scored below proficient on the 2025 state reading assessment, against 33 percent statewide (state education department, 2025). The district's two elementary schools ended their own after-school tutoring in 2024 when a federal grant lapsed. Students who are not reading proficiently by the end of third grade face documented long-term academic risk, and no other structured literacy program currently operates in the district."

Population, local figure with comparison and source, a specific gap in services, and a consequence. The organization has not appeared yet, which is correct: the need belongs to the community, not the applicant.

Worked example: Executive summary: the same fictional request, twice

Weak: "Cedar Bend Youth Alliance is a dynamic, community-driven organization dedicated to empowering youth. We respectfully request support for our innovative programming, which transforms lives every day."

No amount, no program, no population, no result. A reviewer reading only this paragraph could not describe the request.

Strong: "Cedar Bend Youth Alliance requests $48,000 to operate a structured after-school reading program for 60 third and fourth graders at two elementary schools in the Cedar Bend district during the 2027 school year. The program provides four hours weekly of small-group instruction from two certified teachers, targeting the 41 percent of district third graders below reading proficiency. We will measure progress with fall and spring benchmark assessments and report results to the funder within 60 days of the school year's end."

Amount, program, population, place, dose, staffing, the need in one clause, and a measurable commitment. Six sentences of the full proposal, compressed honestly. This is why the summary is written last. The full drafting method for this section, with a reconciliation table that catches number drift before it reaches the reviewer, is in the executive summary template.

Grant proposal format: how to present the document

The format questions that stall teams have short answers, because the governing rule is always the same: the funder's current instructions control the format, and the template adapts to them, never the reverse.

Section order. Use the order in the skeleton when the funder does not specify one. When they do, their order wins, even when it splits sections this template joins. The vocabulary rule matches: if the funder says "problem statement" where you say "statement of need," their term goes on the heading.

Page and word limits. Treat limits as hard. Count them the way the funder counts them, because a portal's character count usually includes spaces while a word processor's may not, and apply the length shares from the table inside whatever total the funder allows.

Cover page. Add one only when the funder requests or permits it, and then include exactly the fields they ask for. An unrequested cover page spends a page of a reviewer's attention on information the application form already carries.

Files and delivery. Deliver in the requested file type, follow the funder's naming rules exactly, and keep one source file for every number so the narrative, budget, and attachments cannot drift apart during final edits. The submission checklist runs these format checks as a gate before the portal's final screen.

Federal applications. These are not a formatting variant of the foundation structure; the notice of funding opportunity mandates its own forms, sections, and limits. Build federal applications from the notice itself, using Grants.gov's applicant resources as the entry point.

The letter proposal: a foundation template variant

Many smaller foundations, family foundations especially, ask for a short letter rather than a full narrative. When they do, the letter is not a cover note for a proposal; it is the funding proposal, complete in three pages or fewer. The same nine burdens of proof apply, compressed into a foundation proposal template you can hold in one sitting:

1. The request, first paragraph. Organization, amount, program, population, and period. The strong executive summary above, at half its length.
2. The need, one to two paragraphs. The strongest local figure with its source and year, the service gap, and the consequence.
3. The program, two to three paragraphs. What happens, who delivers it, at what capacity, and the one or two objectives you will measure.
4. Capacity and budget, one paragraph each. The result that proves you can run this program, then the total budget, the amount requested, and the other confirmed sources.
5. The close. Contact, offer of a full proposal or site visit, and the signature of the person accountable.

A letter proposal is a different document from a letter of inquiry, which asks whether a full application is welcome rather than making the complete request; the letter of inquiry template covers that one-page screening build, and the skeleton download includes this letter variant alongside the full structure.

Allocate length before you draft

Length allocation is a decision, not an accident. Teams that draft without shares end up with the sections that were easiest to write, usually background and mission language, crowding out the sections reviewers weight most, usually program design and evaluation.

The practical method: take the funder's page or word limit, apply the shares from the table above, and write the target at the top of each section of your working file before drafting a sentence. When a section runs over, the overage must be argued for, not defaulted into. Half a page of trimmed organizational history buys you half a page of staffing detail in the program description, and that is almost always the better trade.

Two allocation rules hold across formats. First, the need and program sections together should consume at least half of any narrative; if they do not, the proposal is describing the applicant more than the work. Second, no section should be padded to hit its share. A tight three-quarter page evaluation plan beats a stretched page and a half.

Assemble per funder, in this order

The template is the stable half of the system. The other half is a per-funder assembly sequence, and the order matters because each step can end the work before you spend the next step's hours.

1. Eligibility before anything. Confirm geography, program fit, applicant type, and grant size range against the funder's current guidelines. A fail-closed eligibility matrix makes this a gate instead of a vibe.
2. Map the funder's requirements. List every question, limit, format rule, and attachment from the live instructions. This map is the working grant application template for that funder: it, not the generic structure, controls the final document's order and vocabulary.
3. Pull from your core narrative. Reuse approved facts, not recycled prose. The core grant narrative template separates the facts that stay stable from the decisions you must remake per funder.
4. Draft to the map, using the section standards above. Write need and program first, budget alongside program, evaluation against objectives, background against what this funder cares about, summary last.
5. Reconcile and package. Check every number across narrative, budget, and attachments, then run the submission checklist before the portal opens its final screen.

Our position

Our position: maintain one internal template and rebuild every application from the funder's requirements map, even when a previous proposal to a similar funder exists. Recycled proposals fail in a characteristic way: they answer last year's questions in last year's vocabulary, and reviewers who read hundreds of applications recognize the mismatch immediately. The template's job is to make each section's burden of proof explicit so that reuse happens at the level of verified facts, where it is safe, and never at the level of finished prose, where it silently rots. Teams that adopt this split spend slightly more time per application and dramatically less time repairing contradictions at deadline.

For a first-time applicant, structure is necessary but not sufficient; readiness comes before persuasion, and it is worth confirming you can operate and report on a grant before polishing prose about one.

A logic model is a five-column table that states how your program is supposed to work: inputs, activities, outputs, short-term outcomes, and longer-term outcomes. The blank template is the easy part, and it is downloadable below. The real work is testing the four arrows between the columns, because a reviewer reads the model left to right and stops trusting the proposal at the first arrow that asks for faith instead of evidence. Build the model with the program team before the narrative is drafted, then let the narrative, budget, and evaluation plan inherit its numbers.

What each column actually claims

Each column of a logic model makes a different kind of claim, and mixing them is the most common defect reviewers see. The W.K. Kellogg Foundation Logic Model Development Guide, still the most widely used primer in the sector, frames the model as a picture of how the program is supposed to produce change, not as a form to complete.

Inputs are what the program consumes: staff time stated as an FTE share, volunteers, partners, facilities, materials, and money. Write them as nouns with quantities. "Community support" is not an input; two donated classrooms and twelve trained volunteer tutors are.

Activities are what the program does. Write them as verbs with frequency and duration: run 60-minute tutoring sessions twice a week for 28 weeks. An activity without a schedule cannot be costed or tested.

Outputs are the countable products of activities: students enrolled, sessions delivered, attendance achieved. Outputs prove delivery, nothing more.

Short-term outcomes are the first changes in participants: knowledge, skill, behavior, or condition, each with a named measure and a time by which it should be observable.

Longer-term outcomes are the later changes the program contributes to. The honest verb here is contributes. A 28-week tutoring program contributes to grade-level reading proficiency; it does not cause it alone.

Most published templates add a row for assumptions and external context beneath the columns. Keep it. It is where the model admits what has to stay true in the world for the chain to hold.

The four arrow tests that make or break the model

A logic model fails in the arrows, not the boxes. Teams fill five columns independently, each column looks reasonable, and the chain still does not hold. Test each arrow with one question before anything else in the proposal inherits the model.

Figure: The five columns and the four arrow tests between them. Test 1 checks capacity, test 2 checks delivery arithmetic, test 3 checks the evidence for change, and test 4 checks the timeline and attribution of the longer-term claim.

Test 1, capacity: are the inputs enough to run the activities at this scale? This is arithmetic, not optimism. If the activities need 1,120 tutor-hours and you have twelve volunteers averaging two hours a week for 28 weeks, you have 672 hours. The model fails here quietly and often, because ambitious activities read well in a narrative.

Test 2, delivery: if the activities run as planned, do the output counts follow? Two sessions a week for 28 weeks is 56 session dates. If the outputs column says 80, the columns were filled independently. This is the easiest arrow to verify and the one reviewers check first.

Test 3, evidence: why should this dose of outputs produce the short-term outcome? This is the real causal leap. The answer can be published evidence behind the curriculum, prior results from your own records, or a stated professional rationale, but it must exist somewhere the proposal can point to. If nothing supports the arrow, shrink the outcome claim until something does.

Test 4, timeline: does the short-term change lead to the longer-term change within a window you can claim? Grant periods are short and community change is slow. State what the program contributes and over what horizon, and leave system-level change to the assumptions row if your program is one actor among many.

The CDC Program Evaluation Framework treats a clear program description as a precondition for any credible evaluation, which is exactly what a tested logic model provides: columns four and five become the outcomes your evaluation plan measures, and column one becomes the personnel and cost basis of your grant budget.

A worked model for a fictional reading program

Worked example: Cedar Bend Youth Alliance, a fictional nonprofit, models its after-school reading program

Cedar Bend Youth Alliance is a fictional organization used only to demonstrate the method. Its program: after-school reading tutoring for 40 elementary students across one school year.

Now the arrows. Test 1: sessions run in two rooms with up to 20 students each, so a session needs 6 tutors at a 1:3 or 1:4 ratio; with 12 tutors alternating, each volunteers one evening a week, which the recruitment commitment supports. Test 2: 28 weeks x 2 sessions = 56 dates, matching the outputs column. Test 3: the curriculum publisher reports fluency gains at two sessions weekly, and Cedar Bend's pilot-year records show similar direction; the 75 percent attendance output exists precisely because the evidence assumes that dose. Test 4: grade-level proficiency is claimed as a contribution measured on the district's own assessment, not as a result the program causes alone.

Every number in this table now has a second job: the budget prices the coordinator at 0.4 FTE, the evaluation plan measures the fluency benchmark, and the narrative describes 56 sessions. One source, many documents.

A second complete model, built for a fictional job-readiness program with an alignment walkthrough, deliberately planted misalignments, and a scoring rubric, is in the nonprofit logic model example.

Outputs are not outcomes, and reviewers know it

The fastest credibility test a reviewer runs on a logic model is whether column three leaked into column four. Attendance, materials distributed, and sessions held are delivery facts. Calling them outcomes signals that the program has not thought about change.

The sorting rule: if your team can make the number go up without any participant changing, it is an output. You can raise enrollment with better recruiting. You cannot raise a fluency benchmark that way. When a funder's form uses different labels, and many merge outcomes and impact or say results, keep the internal distinction anyway and translate at the end.

The same discipline protects you from the opposite failure, promising outcomes with no output floor beneath them. Change needs a dose. If the evidence behind your curriculum assumes 75 percent attendance, that attendance level belongs in the outputs column as a stated requirement, and your reporting should say what happens when it is missed.

Fit the model to capacity, then to the funder

Two checks remain before the model is done.

Capacity fit. A model can pass all four arrow tests on paper and still exceed what your staff, partners, and budget can hold. Read the inputs column against reality: total effort across all programs, volunteer turnover, the partner agreement that exists only as goodwill. This is also where a logic model differs from a theory of change: the theory explains why change happens in your community at any scale, while the logic model commits one funded program, at one scale, to one delivery plan. If a funder asks for both, the logic model must be the smaller, harder-edged document, and the two must tell the same causal story.

Funder translation. Keep one internal model per program and translate it to each application. Map your labels to the funder's labels, cut columns they do not ask for, and adopt their form when they supply one; the funder's live instructions always win. What you should not do is redesign the program per application. The model holds the program still while the packaging changes, which is the same principle behind keeping one core narrative that individual proposals adapt.

Download: Logic model worksheet (CSV worksheet). The five columns plus the assumptions row and all four arrow tests, as a fillable worksheet with an evidence column and a confirmed / estimated / open status field for every entry.

Our position

Build the logic model before the narrative, with the people who will run the program, and treat it as the source file every other document inherits from. A logic model drawn after the narrative is decoration, and reviewers can tell: its numbers drift from the budget, its outcomes drift from the evaluation plan, and its arrows are vibes. Fifteen minutes of arrow testing before drafting saves the coherence rework that pre-submission review would otherwise catch at the worst possible time.

A tested logic model cannot guarantee an award, and no template can. What it removes is one of the most common reasons reviewers stop trusting a proposal: a causal chain that contradicts its own budget and narrative. Verify any funder-specific format requirements on the live opportunity before you translate the model into an application.

A needs statement is an evidence chain with four links: a defined population in a defined place, a documented condition affecting them, the consequence if it continues, and your organization's relevance to responding. Build each link from a sourced figure or documented community knowledge, then write the prose in that order. The worksheet below structures the chain; the worked example shows it assembled from the kinds of figures you can pull from public data sources today.

Most weak needs statements fail before the writing starts, because the writer begins with the program and reverse-engineers a problem to justify it. The chain method forces the opposite order. You establish that a specific population experiences a specific documented condition with real consequences, and only then say why your organization is positioned to respond. If the chain will not close, that is a research finding, not a writing problem: either narrow the claim or reconsider the request before drafting the rest of the proposal.

Download: Needs statement worksheet (Markdown worksheet). The four-link evidence chain as fillable fields: population and place, condition with comparison, consequence, program relevance, plus a data-limitations section and a framing review checklist to complete before submission.

The four links, and what breaks each one

Population and place. Who experiences the problem, where, and how many. The commonest defect is a geography mismatch: county-level data used for a two-zip-code program, or statewide figures standing in for a neighborhood. The fix is not always better data; sometimes it is an honest sentence stating that county figures are the smallest reliable geography available and explaining why they still describe your service area.

Condition. What is observably happening, anchored by a local figure and a comparison that gives it meaning: the state average, the national rate, or the same figure three years ago. A number without a comparison is decoration. A comparison without a source and data year is an invitation for the one reviewer who checks.

Consequence. What follows for the people, not for your organization, if the condition continues. This is where the circular need dies or survives. "Without funding, our program will close" is your problem. "Students below proficiency at the end of third grade face documented long-term academic risk" is the community's problem, and it is the one funders exist to address.

Program relevance. Why this organization, here. One or two sentences of positioning: presence in the community, track record with the population, the specific gap in existing services you fill. Resist expanding this into the program description; that section comes next and the logic model will carry the causal detail.

Build the links from public data

Three public sources cover most U.S. community needs statements, and all three let you cite a specific table with a data year.

data.census.gov is the Census Bureau's query interface for American Community Survey tables: population counts, poverty, income, language, housing, and education attainment down to tract level. Note the survey vintage and whether you are using 1-year or 5-year estimates; for small geographies the 5-year tables are usually the only reliable option, and their margins of error are published alongside the estimates.

countyhealthrankings.org publishes county-level health outcomes and the factors behind them, from food environment to childcare cost, with each measure's source and year documented on the page.

The KIDS COUNT Data Center from the Annie E. Casey Foundation aggregates child and family wellbeing indicators by state, county, and city, and is often the fastest route to a defensible comparison figure for youth-serving programs.

Layer documented community knowledge on top of the public figures: intake data, waitlist counts, listening-session notes, frontline staff observations. Name the method ("in structured interviews with 14 parents conducted in spring 2026") so the reviewer can weigh it, and use stories only with documented consent.

Worked example: A four-sentence chain for a fictional after-school reading program

Cedar Bend Youth Alliance is a fictional nonprofit used for worked examples on this site. Every figure below is an illustrative placeholder marked with its intended source type; when you build your own chain, pull the current values for your geography from the sources named.

Four sentences, four sources, and the chain closes: a defined population, a measured condition with a comparison, a concrete service gap as the consequence, and an organization already present with demonstrated demand. Note what is absent: no adjectives doing evidentiary work, no statistics unconnected to the argument, and no mention of the applicant's budget.

To calibrate against finished passages rather than a single chain, the needs statement examples page carries six complete fictional statements across different program types, each annotated against this same structure.

Describe need without deficit framing

An evidence chain can be accurate and still describe a community as nothing but its problems. The Community-Centric Fundraising principles are the clearest published articulation of the alternative: fundraising grounded in the community's own priorities and strengths rather than in donor-facing portrayals of deficiency. The Ethical Storytelling pledge covers the narrower question of consent and dignity when individual stories appear in fundraising materials.

In practice, three habits keep the chain honest without hollowing it out. Describe people by circumstance, not by label: "students scoring below proficiency on the 2025 assessment," not "failing students." Put assets in the frame: existing organizations, engaged parents, the school district's own efforts, because a funder is investing in a community's capacity to change, and a statement that shows no capacity argues against its own program. And keep the condition separate from the people: the problem is the absence of after-school literacy support, not the children.

Small and rural communities add a data problem: samples are small, margins of error are wide, and some indicators are suppressed entirely. Say so directly in a data-limitations sentence rather than borrowing a bigger geography's numbers silently, and lean harder on documented local knowledge, which you can gather at any scale. Distance and travel time to the nearest existing service are legitimate, measurable evidence of need that urban-centric templates forget to ask for.

Our position

Our position: the needs statement is the section where honesty and persuasiveness are the same property. Reviewers read hundreds of statements padded with alarming national statistics that never touch the applicant's actual service area, and a short chain of local, sourced, recent figures outperforms a long recitation precisely because it is checkable. We advise teams to cap the section at two pages and at roughly five figures, each with a job in the chain, and to treat any figure that cannot name its source and year as unusable rather than negotiable. We cannot guarantee how any reviewer scores a given statement, but we have yet to see a proposal harmed by a needs section a stranger could verify in an afternoon.

Keep the chain consistent downstream

The needs statement is load-bearing for the rest of the application. The population defined in link one must be the population your program description serves and your evaluation plan measures; the condition in link two supplies the baseline your evaluation plan improves on; the consequence in link three is what your outcomes claim to prevent. When a funder's letter of inquiry stage compresses everything to a paragraph, the LOI version is links one through three in three sentences, not a new argument.

Store the approved chain, with sources and data years, in your core narrative so the next application starts from verified figures instead of from last year's prose. When the source publishes a new data year, the module goes stale and the figures get repulled; the sentence structure survives, the numbers never assume they do.

A grant budget is the program plan restated in numbers: every line needs a unit, a quantity, a rate with a source, and a visible trace to an activity. Download the CSV template below and fill the calculation column before the total column, because a total you cannot rebuild from units is a total you cannot defend. The two places small nonprofits lose the most credibility are staff time math and indirect costs, and both are worked through with real numbers in this guide.

Four questions every budget line must answer

Reviewers do not read budgets as accounting documents. They read them as a test of whether the program plan is real. A line passes that test when it answers four questions on its face.

What is the unit and quantity? Miles, hours, FTE share, participants, sessions. A round number with no unit ("Supplies: $5,000") announces that nobody did the math. The same amount as "40 student kits x $95 + 2 printer refills x $620" is a plan.

Where does the rate come from? A salary from your payroll, a mileage rate from the current IRS standard, a vendor quote, a published license price. The rate source is what turns an estimate into evidence, and it is the first thing a finance reviewer asks for.

Which activity does it serve? Every line should trace to something the narrative says the program will do. If you built a logic model, its inputs column is the skeleton of this budget, and a cost with no activity behind it is a flag in both directions: either the budget is padded or the narrative is incomplete. The narrative side of that trace, section by section, is laid out in the grant proposal template.

What does the funder's rule say? Salary caps, indirect cost limits, disallowed categories, match requirements. The live opportunity governs, and Candid's proposal budgeting guidance is a sound general reference for how foundation reviewers expect budgets and narratives to fit together.

The template carries all four as columns, so a blank cell is a visible unfinished task rather than a silent gap.

Download: Grant budget template (CSV template). Line-item budget with columns for unit, quantity, rate, calculation to run, activity trace, funder rule check, and narrative section, plus worked example rows for personnel and fringe. Formulas are written out so they survive any spreadsheet tool.

Staff time math without double counting

Personnel is usually the largest category and the one most often built backwards, starting from a dollar amount that feels fundable instead of from time the program actually needs.

Worked example: Pricing a program coordinator at 0.4 FTE, with the double counting check

Assumptions, all declared: a fictional organization pays its program coordinator a $52,000 annual salary; its written fringe benefit rate is 24 percent of salary; the grant period is 12 months; a full-time year is 2,080 hours.

Step 1: estimate the time from the activity plan, not from the budget target. Two tutoring sessions a week with preparation, volunteer coordination, family nights, and data entry come to roughly 16 hours a week. 16 / 40 = 0.4 FTE.

Step 2: salary charged to the grant = $52,000 x 0.40 = $20,800.

Step 3: fringe = $20,800 x 0.24 = $4,992. Fringe is calculated on the salary charged to this grant, never on the full salary.

Step 4: the double counting check. The coordinator is already charged at 70 percent effort to another funded project. 70 + 40 = 110 percent of one human. That budget is unbuildable, and cross-checking effort across all active and pending grants is the single most valuable personnel review a small nonprofit can run. The fix is honest: reduce this grant's share to 0.30 FTE ($52,000 x 0.30 = $15,600, fringe $3,744) and either shrink the activity plan to match or add a second funded role.

Sanity check in hours: 0.4 FTE = 832 hours across the year, which the 16-hour weekly estimate supports. Total personnel for the role at the corrected 0.3 FTE: $15,600 + $3,744 = $19,344.

The pattern generalizes: salary x FTE share, fringe rate x charged salary, and one organization-wide effort ledger that keeps every person's total at or under 100 percent. When a person is split across funders, the split must also match how their time will actually be tracked, because the grant report will have to reconcile with timesheets.

Indirect costs and the de minimis rate

Indirect costs pay for the administration that makes programs possible: bookkeeping, audit, rent for the office that is not program space, the director's time on compliance. Two failures are common: claiming nothing, which quietly starves the organization, and applying federal rules to funders they do not bind.

Key facts, checked August 7, 2026

• Under 2 CFR 200.414, a federal award recipient that has never negotiated an indirect cost rate may charge a de minimis rate of up to 15 percent of modified total direct costs (MTDC).
• MTDC is a reduced base: it excludes items such as equipment, capital expenditures, participant support costs, and the portion of each subaward beyond the regulation's threshold, so the de minimis rate is not 15 percent of the whole budget.
• 2 CFR 200 governs federal awards. Private foundations set their own overhead policies in their opportunity terms, and many cap indirect below the federal de minimis or fold it into a project budget line.

The working rule for a small nonprofit: on a federal application with no negotiated rate, elect the de minimis rate, compute the MTDC base explicitly in the budget file, and show the multiplication. On a foundation application, read the funder's policy first and never write "15 percent per 2 CFR 200.414" to a funder the regulation does not bind; cite their own policy or ask. In every case the indirect line follows the same discipline as any other line: a rate, a base, a source for both.

Reconciliation: one story across four documents

A budget that is internally correct can still sink a proposal by disagreeing with the documents around it. Before submission, reconcile four ways:

• Budget vs. narrative: every activity in the narrative has money behind it, and every budget line has an activity in front of it. Twelve tutors in the story and ten stipends in the spreadsheet is the kind of contradiction reviewers remember.
• Budget vs. staffing: names and effort levels in the narrative match the personnel lines exactly.
• Budget vs. timeline: costs land in the periods where their activities happen. In a multi-year budget, resist dividing the total evenly across years; year one carries startup and training, later years carry full delivery, and a flat split tells the reviewer the schedule was never costed. Declare any inflation assumption on multi-year salaries instead of hiding it in the rates.
• Budget vs. budget narrative: the narrative explains basis and purpose ("0.3 FTE of the coordinator's $52,000 salary, to run 56 tutoring sessions"), it does not restate totals. If the number and its explanation live in different documents, keep one source file and generate both from it. The complete category-by-category worksheet for that document is the budget narrative template.

The same reconciliation sweep belongs in the coherence gate of the grant submission checklist, where it catches the drift that accumulates during last-week edits. In-kind contributions, where the funder permits them, follow the identical rule: a documented value basis and a named commitment, never an inflated market guess.

Our position on padded budgets

Our position

Do not pad. The folk advice to add 10 or 15 percent "because funders always cut" produces budgets that cannot survive a line-item question, and one collapsed number costs more trust than the padding was worth. The legitimate versions of the same instinct are all visible: real fringe rates instead of forgotten ones, allowable indirect costs claimed rather than waived, a declared inflation assumption on multi-year salaries, and honest quantities with sources. If the defensible total is more than the funder will fund, cut scope and say what was cut. A budget you can rebuild from units in front of a skeptical reviewer is the strongest sales document in the entire application.

A clean budget cannot guarantee funding, and no template can promise a funder's decision. What it does is remove the most checkable reasons for doubt, and it leaves you with a file you can actually manage the grant against after an award. The evaluation section deserves the same treatment as every other cost: hours and rates in a small work breakdown, as covered in the evaluation plan template, not a decorative percentage.

An evaluation plan for a small nonprofit needs three things: two or three questions you actually want answered, one indicator per question that passes four tests (defined, feasible, relevant, interpretable), and a data collection plan your current staff can run. Download the template below and fill it in that order. Size the plan to the program: a $48,000 program with a part-time coordinator should not promise an external evaluation design, and funders read an oversized plan as a plan that will not happen.

Proportionate is the standard, not the fallback

Small organizations often write evaluation sections apologetically, as if the real standard were a control group and their plan were a compromise. The opposite is true in the published guidance. The CDC Program Evaluation Framework makes utility and feasibility explicit standards: an evaluation is judged by whether its results get used and whether it can actually be carried out, not by methodological ceremony. The W.K. Kellogg Foundation Evaluation Handbook goes further and frames evaluation primarily as a learning tool for the organization running the program.

That reframing changes what you write. A proportionate plan that names who collects what, when, and what decision the data informs is a complete answer to the evaluation question on a foundation application. A borrowed university-style design with no one to run it is not a stronger answer; it is a visible risk.

The plan also has to respect a boundary: more measurement is not automatically better, because every instrument costs staff time and asks something of participants. Collect only what you will use, and only what you can protect.

Write questions before you pick metrics

The template starts with evaluation questions, not indicators, because a metric without a question is unfalsifiable filler. A good evaluation question is one a board member would actually ask, or one whose answer would change how you run the program next year. Two or three are enough for a small program.

Questions come straight out of the program's causal chain. If you built a logic model, columns three through five already contain them: did we deliver the dose we planned, did the short-term change appear, and is there early evidence of the longer-term contribution? A plan grounded this way cannot drift into measuring things the program never promised.

Then, and only then, pick one indicator per question. The discipline of one indicator each is deliberate: it forces the team to choose the measure it trusts most, and it keeps the collection burden inside what a part-time coordinator can sustain.

Four tests every indicator must pass

Run every candidate indicator through this table before it enters the plan. An indicator that fails any test either gets repaired or gets cut.

The interpretable test deserves one caution: do not invent precision to pass it. If the program has never measured this indicator, the honest plan sets year one as the baseline year and states that a target will be set from it. A target conjured without a starting condition is the kind of number that turns into an accountability problem in the grant report.

The data collection reality check

Before the plan is final, walk each indicator through one concrete week of program operation and answer four questions in writing.

Who collects it, by name or role? "The team" collects nothing. If the answer is the same coordinator who runs sessions, the tool must fit inside session routines, like a sign-in sheet that feeds a spreadsheet.

What tool captures it? Name the actual artifact: the benchmark score report, the five-question paper survey, the attendance spreadsheet. If the tool does not exist yet, creating it is a task in the program timeline.

When, and how often? Match timing to when change can plausibly be observed. Fluency gains do not appear in October; attendance problems do. Frequent operational indicators, rare outcome indicators.

What protects participants? State where data lives, who can see it, and what consent covers. Never collect identifiable data you have no plan to protect, and never promise anonymity a spreadsheet full of names cannot deliver.

Two method cautions belong in this check. First, qualitative material: interviews and open responses are legitimate evidence for a defined learning question, but a handful of memorable comments is not representative impact, and the plan should label quotes as illustrative. Second, the evaluation's cost is real work: hours for collection, entry, and analysis belong in the grant budget as a small work breakdown, not as a generic percentage pasted onto the total.

A worked plan for a fictional tutoring program

Worked example: Cedar Bend Youth Alliance, a fictional nonprofit, plans evaluation for its reading program

Cedar Bend Youth Alliance is a fictional organization used only to demonstrate proportionate scale. The program: after-school reading tutoring for 40 elementary students, twice weekly across 28 weeks, run by a 0.4 FTE coordinator and volunteer tutors.

Three features make this plan credible rather than impressive. Every indicator passes all four tests, including feasibility: the only external data source has an agreement already in place. The collection burden is roughly two hours a month plus two benchmark pulls, which a 0.4 FTE coordinator can absorb. And each row ends in a use, so no data is collected into a void. The stated limitation, written directly into the plan: no comparison group, so fluency gains are reported as change among participants, not as proof the program caused the change.

Download: Evaluation plan template (Markdown template). Seven sections: program summary, evaluation questions, the four-test indicator table, the data collection plan with owners and privacy handling, analysis, use of results, and limitations.

Say how you will use the results

The weakest sentence in most evaluation sections is a promise of continuous improvement with no mechanism behind it. Replace it with named decisions: which meeting reviews the data, what threshold triggers what action, and what goes to the funder when. The Kellogg handbook's core argument is that evaluation exists to inform exactly these decisions, and a funder reading a named decision process can tell the plan is real.

Include the uncomfortable branch too: what happens if results are weaker than expected. The honest answer, that the team will examine dose and delivery first and adjust the model, reads far better than silence, because every experienced reviewer knows weak first-year results are common.

Our position

Our position: for organizations under roughly $1 million in budget, an internal, proportionate evaluation plan with two or three question-backed indicators beats a subcontracted evaluation design on almost every application, because the funder is buying credibility of execution, not methodology. The exception is a funder that explicitly requires independent evaluation, in which case that requirement, and its real cost, belongs in the budget from day one.

A proportionate plan cannot guarantee an award or a particular result; it guarantees that whatever happens, you will know, and can say so with evidence. Check the funder's live instructions for required measures or reporting formats before finalizing, and give the pre-submission review one specific job: confirm the evaluation plan measures exactly the outcomes the narrative promises.

A letter of inquiry (LOI) is a screening document: the funder is deciding whether to invite a full proposal, not whether to fund you. Build it as five paragraphs on one page: request and fit, need, program, organization and numbers, close with next step. Lead with the amount and purpose in the first sentence. The Markdown template below has the full paragraph-by-paragraph build; the funder's own instructions override it wherever they differ.

The LOI exists because program officers cannot read full proposals from everyone. Candid Learning's letters of inquiry guide is blunt about the stakes: for many foundations the LOI alone is enough to make the screening decision. That reframes the writing job. You are not teasing a proposal or building suspense; you are giving a reader with a stack of letters everything needed to sort yours into "invite" in under three minutes.

Key facts, checked August 7, 2026

• Candid Learning's LOI guidance sets a maximum of three pages and lists six components: introduction, organization description, statement of need, methodology, other funding sources, and final summary.
• Funder terminology varies: some say "letter of intent" or "concept note" for the same screening step, and some LOIs are portal forms with character limits rather than letters. The funder's current instructions define the format, always.

Download: Letter of inquiry template (Markdown template). The five-paragraph structure with sentence-level prompts, per-paragraph length targets, a numbers-consistency rule, and a pre-send checklist. Formatted for a one-page letter; adaptable to portal fields.

What the reader is screening for

Before the anatomy, know the test you are being given. A program officer screening LOIs is answering four questions in order: is this within our guidelines, is the need real and in our focus area, is the program plausible at this organization's scale, and is the number sensible. A letter that makes any of those answers hard to find gets sorted down regardless of writing quality.

That is why the first check happens before drafting: confirm fit against the funder's current guidelines with a real gate, not optimism. The eligibility matrix method makes this a fail-closed step. An eloquent LOI to a funder whose guidelines exclude you costs you the hours and teaches the funder your organization does not read instructions.

The five-paragraph build

Candid's six components map cleanly onto five paragraphs once the introduction and summary stop being ceremonial. Each paragraph below has one job.

Paragraph 1, request and fit, two to three sentences. Name your organization, the amount, the program in one clause, the population, and the place, all in the first sentence. Add one sentence connecting the request to the funder's stated priorities using their published language accurately. Warm-up openings ("For over twenty years, our organization has...") spend the most valuable real estate in the letter on the least useful content.

Paragraph 2, need, three to four sentences. Population, condition with your single strongest sourced figure, consequence. This is the needs statement evidence chain compressed to its skeleton. One figure, maybe two; a statistics dump at this length reads as a form letter.

Paragraph 3, program, three to five sentences. What you will do, for whom, at what scale, over what period, delivered by whom, toward what checkable change. Describe this program, not your organization's whole portfolio. Mission language is the classic failure here: "empowering youth to reach their full potential" survives editing because it sounds fine, and it tells the screener nothing.

Paragraph 4, organization and numbers, two to three sentences. One capacity fact chosen for relevance to this program, then the money: total project cost, amount requested from this funder, and other funding committed or pending. Use only numbers you can reconcile with the full budget later; an LOI total that disagrees with the invited proposal's budget is a credibility wound at the worst possible moment.

Paragraph 5, close, one to two sentences. Offer the full proposal, name a contact with direct phone and email, thank them once. No new claims.

Worked example: A complete fictional LOI, annotated by paragraph

Cedar Bend Youth Alliance and the Meridian Community Fund are both fictional, invented for worked examples on this site. All figures are illustrative.

"Dear Ms. Alvarez,

Cedar Bend Youth Alliance requests $48,000 from the Meridian Community Fund to operate a school-year after-school reading program for 60 third and fourth graders in the Cedar Bend school district, in direct support of the Fund's published priority of early-grade literacy. [Request, amount, population, place, and fit, one sentence each way.]

On the 2025 state assessment, 41 percent of the district's third graders scored below reading proficiency, against 33 percent statewide. The district ended its only after-school tutoring program in 2024 when federal funding lapsed, and students already behind now have no structured literacy support outside school hours. [Condition with sourced comparison, then consequence. Two sentences carry the whole need.]

The program will provide four hours per week of small-group instruction, in groups of no more than five students, delivered by two certified teachers at both district elementary schools from September 2027 through May 2028. Students are referred by classroom teachers using fall benchmark scores. We will measure progress with fall and spring benchmark assessments and expect at least two-thirds of participants to improve one proficiency band. [Dose, scale, staffing, referral path, and a checkable outcome.]

Cedar Bend Youth Alliance has operated youth programs at both schools since 2019 and currently maintains a waitlist of 38 families requesting academic support. The total program cost is $61,000; the district is contributing facilities valued at $8,000, and a $5,000 request is pending with a local family foundation. [One relevant capacity fact; a money picture that will reconcile with the full budget.]

A full proposal and current financial statements are available at your request. Thank you for the Fund's consideration; I can be reached directly at the phone and email below. [Close, contact, done.]"

The letter runs about 280 words: one page with letterhead and generous margins. Nothing in it would need to be walked back in the full proposal.

Why one page wins

Candid's ceiling is three pages, and some funders explicitly request two. Our advice when the funder is silent on length: draft to one page, every time.

Our position

Our position: length discipline is the LOI's real test, and one page is the honest default. The screening reader gives your letter minutes; a second and third page do not receive proportional attention, they dilute it, and they usually exist because the writer declined to make prioritization decisions. The one-page constraint forces exactly the choices the full proposal will need anyway: the single strongest need figure, the one capacity fact that matters, the checkable outcome. When a funder asks for more, add depth to the program paragraph and the money picture, in that order; never respond to a page limit by shrinking type or margins, which reads as exactly what it is. We cannot guarantee any funder's screening decision, but a letter that makes the four screening answers findable in one page never loses on format.

After it goes out

An LOI is a pipeline event, not a completed task. Log it in your grant tracking spreadsheet with the date sent, the funder's stated response window, and the follow-up date when silence becomes a polite status inquiry. If the invitation comes, the full proposal assembles from the same fact base the letter drew on; if the full-proposal side is newer territory for your team, Candid Learning's free introduction to proposal writing is the standard sector course for it. Either way, an invited proposal cannot contradict the letter that earned the invitation, which is the strongest argument for writing LOIs from a maintained core narrative rather than from scratch: the letter and the eventual proposal share sources, so they cannot disagree.

If the answer is no, record it and move on; a declined LOI cost you one page, which is the entire point of the instrument.

Screen every funder in two stages. Stage one is a set of six binary gates: legal status, geography of benefit, program area, whether applications are accepted, request size, and timing. Any failed gate ends the screen, no matter how good the rest looks. Stage two scores fit factors from 0 to 2 with weights, and only funders that passed every gate get scored. The downloadable matrix below holds both stages in one file, and the funder's most recent Form 990-PF supplies most of the evidence.

Why a single fit score misleads

Most eligibility screens fail the same way: they average. A funder scores 9 out of 10 on mission alignment, geography, and grant size, so the team starts drafting, and three weeks later someone notices the guidelines say "invited proposals only." The strong average hid a hard disqualifier.

The fix is structural, not motivational. Split the screen into two stages with different math.

Disqualifiers are binary and fail closed. A gate is a condition the funder controls and you cannot negotiate: tax status requirements, funding geography, whether unsolicited applications are accepted at all. Gates take exactly two values, pass or fail, and an unanswered gate counts as a fail until you find evidence. That is what fail closed means: missing information stops the screen instead of sliding through as a hopeful "probably fine."

Fit factors are scored and weighted. Once every gate passes, the question changes from "may we apply" to "is this worth our hours compared to the other funders on the list." That is a ranking problem, so scores and weights are the right tool there, and only there.

Two failure patterns make the separation worth enforcing. First, sunk research time converts weak prospects into pursuits: after six hours of reading a foundation's filings, "no" feels like waste, so the screen bends. Second, teams stretch terminology, renaming an existing tutoring program "workforce readiness" because the funder uses those words. A gate row that asks "does a program you already run fit without renaming it" catches the stretch before it reaches a proposal draft.

Stage one: six gates that fail closed

Two of these deserve a note. Geography of benefit is about where outcomes happen, not where your office sits: a nonprofit headquartered in one county serving families in a neighboring one should screen against the second county. And the timing gate is a real gate, not a pep talk. If the deadline is in twelve days and the person who owns proposals has four free hours, the honest answer is fail for this cycle, and the funder goes back into research for the next one.

When a gate fails, record which one and why in your grant tracking spreadsheet before moving on. A dated "failed gate 4, preselected grantees only, per 2024 filing" saves the next person from repeating the same six hours of research next year.

Stage two: fit factors worth scoring

Score each factor 0, 1, or 2, multiply by its weight, and sum. The matrix uses eight factors with weights of 1 to 3; the maximum is 32.

Our working thresholds: pursue at 22 or above, hold and revisit between 16 and 21, drop below 16. Set your own if you like, but set them before scoring a specific funder, because thresholds chosen after the fact always confirm the decision someone already wanted.

A zero on relationship is normal and is not a problem to fix by inventing one. The factor exists because a genuine warm path changes how you open a conversation, not because cold applications are doomed.

Download: Grant eligibility matrix (CSV template). All six fail-closed gates and all eight weighted fit factors, each with its evidence question, source, and recording rule. Open it in any spreadsheet tool and complete one copy per funder.

How to read a 990-PF for real signals

Private foundations file Form 990-PF annually, and it is the closest thing to ground truth about what a foundation actually funds, as opposed to what its website says. The IRS describes the form's purpose and contents on its About Form 990-PF page, and Candid's guide to finding 990s and 990-PFs lists the places to retrieve filings free, including Candid's own search tools and the IRS Tax Exempt Organization Search.

Four places in the filing feed the matrix directly:

• Part XV, the application information section. Foundations state here whether they accept applications and, if so, in what form and by when. The phrase "contributes only to preselected charitable organizations" is a hard fail on gate 4. This section alone settles more screens than any other source.
• The grants paid schedule. The full list of recipients and amounts. From it, pull the median grant (gate 5 and the size-match factor), look for organizations that resemble yours (grantee similarity), and check whether the same names repeat year over year (renewal behavior).
• Total grants paid, across two or three filings. A foundation whose grantmaking dropped by half may be winding down or reorienting; a rising line supports a better payout score.
• Officers and trustees. The names your board reads to find a genuine connection, which is how the relationship factor gets its evidence.

One caution absorbed from hard experience: a 990-PF is a snapshot that is usually one to two years old by the time you read it. Filings tell you patterns; only the funder's current guidelines tell you rules. When the two disagree, the guidelines win, and a phone call or email to the funder beats both.

Worked example: One fictional nonprofit screened against two fictional funders

Cedar Bend Youth Alliance is a fictional nonprofit with a $420,000 budget and an after-school reading program serving 120 children in one county. It plans a $15,000 ask. Both funders below are fictional; the point is the mechanics.

Funder A, the fictional Harwood Family Foundation. Gates 1 through 3 pass: no unusual status requirements, same county, and children's literacy is a named priority. The grants list even shows a median grant near $18,000. But Part XV of the most recent filing states the foundation contributes only to preselected organizations. Gate 4 fails, the screen ends, and no fit score is calculated. On a single-score screen, Harwood's excellent alignment would have produced a high number and a wasted proposal.

Funder B, the fictional Bright Plains Fund. All six gates pass, so stage two runs:

Total: 24 of 32, above the pursue threshold of 22. Cedar Bend logs the score, the two weakest factors, and the evidence links, then moves Bright Plains to qualified status in its tracker. The zero on relationship stays a zero; nobody manufactures a connection.

What each result means in practice

A completed matrix produces one of three outcomes, and each has a next action rather than a feeling.

Pursue means the funder enters your pipeline with a deadline and an owner. For a foundation that asks for a letter first, the next artifact is usually a letter of inquiry, not a full proposal.

Hold means the fit is real but not competitive against your other options this cycle. Record the score and the recheck date. Holds are where next year's best prospects come from, because the research is already done.

Drop means a failed gate or a low score, written down with its reason. A documented no is an asset; an undocumented no is a question someone will re-research in eighteen months.

If this is your organization's first time screening funders at all, run the matrix on three candidates before writing anything, and read our guide to your first grant proposal for how the screen fits into a 30-day path. And keep the boundary honest: a matrix disciplines where your hours go, but it measures fit, not outcomes, and it cannot guarantee that any funder, however well matched, will invite, fund, or renew you. What it can do is stop you from spending forty hours on applications that were ineligible before the first sentence was written.

A core grant narrative is a maintained internal file of approved fact modules, each with an owner, a source, and a last-reviewed date, that feeds every application you write. It is not a folder of old proposals and not a master proposal you lightly rebrand. The method rests on one distinction: which facts stay stable across every application, and which decisions must be remade for each funder. The outline template below implements the split with seven modules and explicit staleness triggers.

Every grant team eventually notices it is writing the same organizational description for the fifth time and reaches for reuse. The reach is correct; the usual implementation is not. Copying prose from the last proposal drags along that funder's vocabulary, that program year's numbers, and framing decisions that were right once, for one reader. The core narrative method moves reuse down one level, from finished sentences to verified facts, so every application starts from current truth and makes its own framing decisions. Candid Learning's grant proposal guide lists the components nearly every funder asks about; the core narrative is the internal system that keeps your answers to those recurring components accurate between applications.

Download: Core grant narrative outline (Markdown template). Seven fact modules with an ownership header for each, a stable-versus-re-decide note per module, seven staleness triggers mapped to the modules they affect, and the usage rule that keeps application drafts from corrupting the source file.

What stays stable, what gets re-decided

The whole method is this table. A fact belongs in the core narrative when it is true regardless of who is asking. A decision belongs to the individual application when the right answer depends on the funder.

The failure mode on each side is different. Treating a stable fact as flexible produces the proposal that "improves" the annual budget or rounds up last year's outcomes, which is how organizations drift into claims they cannot report against. Treating a per-funder decision as stable produces the copy-paste proposal, which fails for reasons covered below.

Seven modules with clean boundaries

The downloadable outline defines seven modules: identity and legal facts, organizational capacity, need evidence base, program models (one sub-module per program), results and evidence, financial profile, and community voice standards. The boundary rule that makes them work: a module contains facts with the same owner and the same staleness behavior. Financial facts change on the fiscal-year cycle and belong to the finance lead; need figures change when public sources publish a new year and belong to whoever owns research; program models change when delivery changes and belong to program managers.

Each module carries a four-line header: owner, approver, last-reviewed date, and sources. A module without an owner is a rumor with formatting. The needs statement chain, once its figures are approved, lives in module three; the reconciliation-ready numbers behind your budget live in module six.

The flow from core to application runs one direction, with corrections returning through module owners rather than being made inline.

Figure: The core-to-application flow. Facts enter the modules from verified sources, applications assemble from the modules through the funder's requirements map, and corrections discovered while drafting return to the modules through their owners instead of being edited inline.

In words: verified sources feed the approved modules, applications are assembled from the modules through each funder's requirements map, and anything a draft reveals as wrong or better goes back to the module through its owner. The dashed arrow at the bottom is the review loop: staleness triggers reopen a module regardless of whether an application is in flight.

Staleness triggers, not annual cleanups

A core narrative that is only refreshed when a deadline exposes a stale fact is a liability with a nice filename. The alternative is event-driven review: name the events that invalidate facts, and map each event to the modules it touches.

The outline ships seven triggers: fiscal-year close or completed audit (identity, capacity, financial modules), any leadership or key staff change (identity, capacity, programs), a completed program data cycle (programs, results), a new public data year (need evidence), any change to program design or partners (programs), a funder rejection citing a factual issue (whichever module sourced it), and a hard backstop of twelve months since last review for the whole file. When a trigger fires, the module's owner repulls from sources and the approver re-dates the header. The grant tracking spreadsheet is the natural place to log trigger dates, since it already tracks the deadlines that make stale facts expensive.

If your team uses AI drafting assistance, the core narrative is also the control that makes it safe to the extent it can be: the model transforms approved module text and is never the source of a fact, a number, or a funder preference. NTEN's AI resources for nonprofits cover the governance side; the module file is the practical enforcement, because a fact that is not in a module does not go in a draft, whoever or whatever wrote the sentence.

Why copy-paste proposals fail screening

Our position

Our position: recycled proposals fail screening at a rate their authors never see, because the rejection letter does not say "this was written for someone else." It says nothing, or it says "not a fit." But the tells are structural and readers who screen hundreds of applications register them fast: the vocabulary matches a different funder's program areas, the emphasis answers questions this funder did not ask, a stray sentence addresses the wrong geography or the wrong grant size, and the numbers carry a faint vintage mismatch. Renaming the funder and updating the ask is not customization; customization means remaking the right-hand column of the stable-versus-re-decided table for this reader. The core narrative exists precisely so that teams under deadline can afford to do that: when the facts are pre-verified, the hours go to funder-specific decisions instead of fact archaeology. This method cannot guarantee an invitation or an award; no writing system can. What it changes is whose mistakes you are eliminating, and the self-inflicted kind, stale numbers, wrong-funder vocabulary, internal contradictions, are the only kind fully in your control.

The core narrative pays off most visibly at the two speed-sensitive moments in the pipeline: the letter of inquiry, which becomes an hour's assembly instead of a day's writing because every paragraph draws on a current module, and the invited full proposal, which starts from the same fact base as the letter and therefore cannot contradict it. Teams that hire outside help get a third benefit: a maintained module file is the single best onboarding document you can hand a contract writer, and scoping that handoff is half the battle in buying grant writing services well.

Run four gates in order before you submit: compliance, coherence, evidence, copy. Compliance comes first because eligibility, registration, and format failures get applications rejected without a reviewer ever weighing the idea, so the checks that catch the most rejections run before the checks that improve the writing. The interactive checklist below holds all 32 checks, and the download is the same list in Markdown for your project folder. Open the compliance gate the day you decide to apply, not the week of the deadline.

Why the gates run in this order

Most submission checklists are ordered by document, which buries the fatal checks among the cosmetic ones. This checklist is ordered by failure severity: each gate catches a class of failure that makes the later gates irrelevant.

Compliance failures end the application. An ineligible applicant, a lapsed registration, a missing required form, or a blown deadline is not a weak proposal; it is a non-proposal. Federal opportunities are explicit about this mechanical layer: the Grants.gov Grants Learning Center walks through the registration and application lifecycle precisely because these steps fail applicants before review begins, and SAM.gov entity registration, which is free, is the prerequisite that takes the longest to fix when it lapses. Foundations are gentler but not different in kind: their portals, formats, and eligibility terms are still pass or fail.

Coherence failures survive to review and lose it. Numbers that disagree across documents make a reviewer distrust everything else.

Evidence failures weaken the case. Unsourced statistics and stale letters do not reject an application, but they cap its score.

Copy failures embarrass. The wrong funder's name in a reused paragraph rarely kills a strong proposal, but it is the error everyone remembers.

Working the gates in order also assigns time correctly: gate 1 starts at go-decision, gates 2 and 3 run when documents are complete, and gate 4 is the final 48 hours. Funder instructions always supersede any generic list, this one included; the first act of gate 1 is reading the live opportunity end to end. Candid's proposal guidance makes the same point from the funder side: the application that gets reviewed is the one that answers what was actually asked.

Download: Grant submission checklist (Markdown checklist). All 32 checks in the four gates as checkbox lists, plus the post-submission record steps, ready to copy into each grant's project folder.

Gate 1: compliance, the checks that reject outright

Ten checks, and the theme is verify, never assume. Eligibility is confirmed on the live opportunity page, not remembered from last year's cycle; a funder that accepted you in 2024 may have narrowed its geography since. If eligibility is genuinely uncertain, resolve it before any drafting with a fail-closed screen like the grant eligibility matrix, because everything after an eligibility mistake is wasted work.

The registration checks deserve their 48-hour buffer. Portal accounts lock, credentials expire, and the person with submission authority goes on vacation. The check "every required registration was tested with a real login this week" exists because discovering a dead login at 4 p.m. on deadline day is a self-inflicted rejection. The same logic covers the deadline itself: record it with its time zone, and set the internal deadline at least 48 hours earlier so a portal outage is an inconvenience instead of a catastrophe.

Format checks close the gate: current form versions, every attachment in the requested file type, limits counted the funder's way (a portal character count includes spaces; your word processor's may not), and naming rules followed exactly.

Gate 2: coherence, one story across every document

Eight checks that all reduce to a single test: could a reviewer put any two documents side by side and find a contradiction? The total request, activity list, staffing effort, timeline, beneficiary counts, logic model numbers, and evaluation targets must match everywhere they appear, and nothing may contradict your public filings or website, which reviewers do check.

A concrete illustration, using a fictional organization: Cedar Bend Youth Alliance's narrative promised twelve trained tutors, while its budget funded training stipends for ten. Neither document was wrong on its own; they were written two weeks apart. That is how coherence failures actually happen, drift during editing rather than error at drafting, which is why this gate runs after documents are final and again after any late change. The prevention is structural: keep one source file for numbers, the budget built to trace to the program plan, and generate every other mention from it. Documents drift less in the first place when they are drafted inside one grant proposal template, where every section's numbers share a source.

Gate 3: evidence, every claim can be traced

Seven checks on the load-bearing claims. Every statistic carries a source, a date, and a working citation; need data describes your actual service area rather than a national figure standing in for it; and outcome claims from past programs trace to your own records, because "we improved outcomes for 300 families" will eventually be asked about in a report or a site visit.

Two checks here are ethical as much as editorial: quotes and participant stories need documented consent, and no claim may promise an outcome the program design cannot support. The second one is the quiet discipline of the whole application: a proposal that promises what its own logic model does not claim has converted enthusiasm into a future reporting problem.

Letters of support and boilerplate round out the gate. A letter dated two cycles ago that never mentions this program is evidence against the partnership, not for it, and boilerplate financials that lag a year behind your published filings create exactly the contradiction gate 2 exists to catch.

Gate 4: copy, the last-mile check

Seven checks, all cheap, all best done by someone who did not write the proposal. The wrong funder name in reused text is the classic, and it survives self-review because the writer reads what they meant. Placeholder text and tracked changes hide in attachments. Sections in the funder's requested order, the funder's own vocabulary for their headings, acronyms spelled out at first use, and final file names complete the pass.

The fresh-reader check is the one to protect when time is short. One end-to-end read by a colleague catches more gate 4 failures than three more passes by the author, and it doubles as a final coherence sniff test.

After you submit: preserve the record

Submission is not done at the click. Save the confirmation number, timestamp, and receipt email into the grant's record; archive the exact files submitted in a dated folder, because you will revise these documents for the next application and "which version did they get" becomes unanswerable otherwise; and note who submitted under which account. If the funder's portal shows a submitted status, capture it.

This record is what turns a scramble into a system. It feeds your grant tracking spreadsheet, gives a rejected application an honest starting point for revision, and gives an awarded one a clean baseline for reporting.

Kit: Post-award Grant Management Kit. The record you just archived is the first thing the next stage needs. This kit is that stage: an eight-sheet workbook, seven letters to your funder and two worksheets covering what a signed agreement obliges, when each report is due, and what evidence sits behind every number in it. Its reporting calendar works six internal dates backwards from each funder deadline. It says nothing about the application you just submitted.

Our position

Our position: a submission checklist should be binary, and 32 of 32 is the only passing score. Weighted scores make sense for grading a method, but a submission is a gate, not a grade; an application that is 94 percent compliant is 100 percent rejectable. Passing every check still cannot guarantee an award, and any checklist that implies otherwise is selling something. What the gate guarantees is narrower and worth exactly its cost: your proposal will be judged on its merits, by a reviewer, instead of discarded on mechanics by a portal or a screener.

Use one spreadsheet as the single source of truth for every grant opportunity: one row per opportunity per cycle, one named owner per row, and eight stages that each have written entry criteria. An opportunity changes stage only when its criteria are met, never because a deadline is close. The downloadable tracker below ships with the exact columns explained in this article. Below roughly 30 applications a year, this beats a CRM, and we explain why.

One row per opportunity, one named owner

A grant tracker fails for predictable reasons: three partial copies exist, "status" means something different to each person who edits it, and rejected applications get deleted, taking their lessons with them. The countermeasures are rules, not features.

One file. Not one per program, not a personal copy per fundraiser. Every question of the form "where are we with that funder" is answered by this file or the file is broken.

One row per opportunity per cycle. A renewal is a new row, not an edit to last year's, because last year's row is now a record. The tracker must preserve both wins and losses so the organization learns without rewriting history: a funder that declined you twice with feedback is a different prospect from one you never approached, and only intact rows show that.

One named owner per row. A person, not a team. The owner is whoever answers for the next action, which is different from doing all the work.

Two things stay out. The tracker is not a second accounting system: award spending lives in your bookkeeping, and the tracker holds only the award amount, period, and report dates. It also never holds participant data. Names of people your programs serve do not belong in an operations file that half the staff can open.

Eight stages with entry criteria

Stages are the core of the tracker, and a stage without entry criteria is just a mood. This table is the decision gate for every move:

The single most common corruption is stage drift under deadline pressure: a prospect jumps from research to drafting because the deadline is Friday, and the eligibility screen happens retroactively, if ever. The entry criteria exist precisely to make that visible. If the criteria for qualified are not met, the row does not say qualified, whatever the calendar says.

Two boundary notes. Declined-by-silence needs the 60-day rule because some funders never write back, and a row stuck in submitted forever poisons your pipeline numbers. And the active stage is where most small organizations lose track of obligations: grantmakers' own practice surveys, like PEAK Grantmaking's review of grant reporting practice, show how varied reporting requirements are across funders, which is exactly why each award's specific report dates belong in the row instead of in someone's memory.

The columns that matter and why

Every column earns its place by feeding a decision. The tracker has 18:

What is deliberately absent: probability percentages (small samples make them theater), a "priority" column (the fit score already ranks), and any budget detail beyond the ask and award (that lives in the grant budget workbook).

Download: Grant tracking spreadsheet (CSV template). All 18 columns from the table above, plus one clearly labeled fictional example row showing a completed submitted-stage entry. Import into Google Sheets or Excel and delete the example row once yours exist.

When a CRM actually earns its cost

Our position

Below roughly 30 applications a year, a spreadsheet beats a CRM, and it is not close. The reasoning: at that volume your bottleneck is decision discipline, not data volume. Stage definitions, entry criteria, and a weekly review live in how the team works; software cannot supply them, and a CRM that encodes someone else's pipeline stages actively fights the ones you defined. Meanwhile the CRM's costs are real and recurring: per-seat fees, admin time nobody budgeted, and a data model built for individual donor cultivation, not for a 14-column opportunity record. We have watched more grant pipelines die of half-configured CRMs than of overfull spreadsheets. Switch when the volume makes rows unmanageable, when multiple people need simultaneous structured edit access with permissions, or when grants tracking must integrate with a donor database the organization already runs well. Until then, the spreadsheet is not the compromise. It is the better tool.

The weekly review that keeps it honest

A tracker decays without a rhythm. Twenty minutes a week, same day, owner present, three passes:

1. Sort by next action due. Anything overdue gets done, rescheduled, or explicitly dropped. An overdue action with no decision is the first crack in the single source of truth.
2. Scan stage entered dates. Rows stale for more than 30 days get a question: what criterion is unmet, and is anyone actually working on it? Some honest answers move rows backward, which is allowed and healthy.
3. Check upcoming deadlines and report dates. Every deadline inside the next 45 days needs its internal deadline and its submission checklist started. Report dates get the same treatment as application deadlines, because to the funder they are the same kind of promise.

Kit: Post-award Grant Management Kit. Take the free tracker above first. It follows applications to a decision and gives the whole period after that one cell, called Report due dates. This kit is what goes behind that cell: a reporting calendar that gives a single report twenty-six columns and six dates worked backwards from the funder deadline, plus an obligation register that quotes the agreement rather than paraphrasing it, an evidence ledger and a spend checkpoint. If the one cell is enough for your volume, keep your money.

Handle declines in the same session, while the row is open. Close the record, write the outcome notes, and where the funder permits it, ask for feedback; Candid's guidance on what to do after a rejection offers usable questions that respect the funder's constraints. Then make a fresh fit decision for next cycle instead of assuming resubmission. A tracker full of honest declined rows is the cheapest funder research you will ever own.

One boundary, stated plainly: a tracker disciplines your process and protects your obligations, but it cannot guarantee awards, renewals, or any funder's decision. What it guarantees is narrower and worth having anyway: that nothing is lost, nothing is ambiguous, and every hour you spend on grants is spent on a row that deserved it.

Decide what gap you are buying help for before you talk to any provider: funder research, full proposal development, review and editing, or systems and training are four different services with different fee logic. Compare providers only after normalizing scope with the checklist below, pay hourly or flat fees rather than a percentage of awards, and walk away from anyone who guarantees funding. If your real need is under four applications a year, training a staff member usually beats hiring out.

Four service models, matched to four gaps

"Grant writer" is a label that covers at least four distinct services, and most bad engagements start by purchasing the wrong one. Name your gap first, then buy the service that fills it.

The most expensive mismatch is buying full proposal development when the organization is not ready for it. A writer cannot invent your program design, your outcomes, or your budget; if those do not exist, a drafting engagement stalls into billed discovery meetings. Candid's overview of what a grant proposal contains is a fast readiness test: if you cannot supply the raw facts behind each component, buy program design help or systems help first, not writing.

Anchoring the cost conversation helps too. The Bureau of Labor Statistics profiles fundraisers as an occupation, including wage data; a consultant's rate should make sense next to the fully loaded cost of an employee doing the same work, given that consultants carry their own overhead, taxes, and unbilled time.

Fee structures and the commission problem

Three fee structures are legitimate, each fitted to a different level of uncertainty. Hourly fits open-ended or poorly defined work such as editing and discovery; ask for a cap. Flat project fees fit well-defined deliverables such as one application to one named funder; they only work when the scope is written down, which is what the checklist below is for. Retainers fit ongoing multi-application relationships; insist on a monthly deliverables list so the retainer buys output, not availability.

The fourth structure is the one to refuse.

Our position

Do not pay for grant writing as a percentage of awarded funds, and treat any provider who proposes it as disqualified. This is our position, and it aligns with a norm that the established fundraising profession has held for decades: the major professional associations' codes of ethics reject percentage-based and contingent compensation for fundraising work. The reasoning is practical, not ceremonial. First, grant awards are typically restricted to the funded program's costs, so a commission either invoices money the award cannot legally pay or quietly inflates the budget to cover it, and funders read budgets carefully. Second, contingency pay rewards volume of asks over honesty of fit: a commissioned writer profits from submitting everywhere, including to funders you should have screened out. Third, it prices the work dishonestly in both directions, paying the writer nothing for a strong proposal a board member later torpedoes, and overpaying for an award your relationship, not the prose, actually won. Pay for the work. The work is real whether or not the funder says yes.

Red flags that end the conversation

Some signals are worth a follow-up question. These are not those. Each row here is a reason to stop evaluating and move on.

The pattern underneath the table: confidence and urgency are not evidence of method. A strong provider shows you a process, names its limits without being asked, and is comfortable telling you no application is worth submitting this quarter.

The 28-item scope-of-work checklist

Fee comparisons between providers are meaningless until scope is normalized. A $3,000 quote covering research, two review rounds, and submission is not more expensive than a $2,000 quote covering a single draft with no revisions; it is a different product. Before signing, and before comparing anyone's price to anyone else's, walk both quotes through the same checklist.

Download: Grant writing scope-of-work checklist (CSV checklist). 28 items across seven sections: deliverables, client inputs, timeline and reviews, fees and payment, exclusions and boundaries, confidentiality and access, and acceptance and handoff. Every item is a yes-or-no check against the provider's written scope.

Three items on the list deserve emphasis because they are the ones providers most often leave vague. Named deliverables by document: "grant writing support" is not a deliverable; "one letter of inquiry and one full proposal to two named funders" is. Client inputs with due dates: most blown timelines are blown by the client, and a fair scope says what you owe and when. Handoff: you should end any engagement owning editable files and a reusable core narrative, because a provider whose work product evaporates when they leave has sold you dependency, not capacity.

Hire, train in-house, or do it yourself

The honest version of this decision starts with volume and staff time, not with how intimidating the first application feels.

• Fewer than two applications a year, small asks: do it yourself. A first small proposal to a local funder is genuinely learnable; our first grant proposal path walks the 30-day version, and the total effort is smaller than managing a consultant would be.
• Two to six applications a year, and a staff member has four or more hours a week: train in-house. This is the most common situation and the most commonly misdiagnosed one. Buying proposal development here means renting a capacity you will need forever; a structured course plus templates builds it once. See our breakdown of what a beginner grant writing course must include before choosing one.
• Two to six applications a year, and genuinely no staff time: hire proposal development, but scope it per application and keep funder selection in-house with your own eligibility screen. Outsourcing the go or no-go decision to the person paid per proposal is a conflict you do not need.
• More than six applications a year, or federal opportunities in play: hire systems and training first, then decide whether ongoing development help is still needed. High volume without internal infrastructure fails no matter how good the hired writer is.
• The proposal exists but has never been outside the building: buy review and editing only. It is the cheapest engagement on the menu and often the highest leverage per dollar.

Whichever branch you take, keep the outcome boundary in view: a competent provider improves the clarity, completeness, and fit of what you submit, and that is worth paying for, but no service can guarantee an award, and we cannot guarantee one either. Buy scope, verify method, own your files, and let the funder's decision be the one thing nobody sold you.

Your first grant proposal should be a small ask, to a local funder, for a program you already run. Spend the first week proving eligibility and fit, not writing. Then assemble five documents (a fact sheet, a needs statement, a core narrative, a program budget, and an outcomes list), give yourself 30 days, and submit three business days early. The readiness checklist below tells you whether you are actually ready, which matters more than how the prose sounds.

Pick a first opportunity you can win

Most first proposals fail before the first paragraph, at the selection step. The instinct is to chase the biggest opportunity you can find, because the need is real and the numbers are exciting. Resist it. The right first opportunity looks deliberately modest:

• Local or regional, not national. Community foundations, local family foundations, and giving programs at businesses in your area fund small organizations they can see. National funders mostly do not.
• A small ask, roughly $2,500 to $15,000. Sized to the funder's typical grant, which you can check in their materials and filings using an eligibility screen before writing a word.
• A short application. Many local funders start with a two-page letter of inquiry or a simple form. That is a feature, not a consolation prize.
• A program that already exists. Fund what you already do. A proposal for real, running work gets to say "we serve 60 families a month," which no amount of writing skill can fake for a program that starts "if funded."

And one clear negative: federal grants are the wrong first grant. The government's own Grants.gov learning pages are worth reading to understand the landscape, but federal applications assume registrations, audit readiness, and compliance systems most young organizations do not have; even the prerequisite SAM.gov entity registration is a process of its own. File federal under "later," without guilt.

One more thing worth saying plainly, because new organizations hear the opposite: having tax-exempt status does not make you grant-ready, and not being grant-ready yet is normal. Readiness is a set of documents and countable facts, which is exactly what the rest of this article builds.

The minimum viable proposal system

You do not need a grants department. You need five documents, most of which you will reuse for years:

1. A one-page organization fact sheet. Legal name, EIN, mission in one paragraph, founding year, budget size, board count, people served last year. Every application asks for these; answering from one approved page keeps the answers consistent.
2. A needs statement with local evidence. Two or three paragraphs on the problem, anchored by at least one local data point. Our needs statement template covers the structure; the sector context in the National Council of Nonprofits' overview of the nonprofit sector is a useful reminder that funders know most applicants are small, community-based organizations like yours.
3. A core narrative. The reusable who, what, where, when, and how many of your program, written once and adapted per funder rather than rewritten from scratch. Start from the core grant narrative template.
4. A program budget with units and rates. Not round numbers. "Reading tutor, 6 hours weekly, 30 weeks, $25 per hour" survives questions; "$4,500 for staffing" invites them. The grant budget template does the arithmetic scaffolding.
5. An outcomes list you can actually count. Two or three observable results, with how you will count them. Attendance records and skill assessments beat aspirations.

If you want structured instruction alongside these documents, Candid's free introduction to proposal writing is a legitimate starting point, and we compare deeper options in our guide to grant writing courses for beginners. When a funder asks for a full narrative rather than a short form, the nine-section grant proposal template supplies the structure these four documents plug into.

A 30-day timeline, worked in full

Worked example: A fictional food pantry's first proposal, day by day

Maple Hollow Community Pantry is a fictional nonprofit with a $180,000 budget, one full-time director, and a weekend meal program that served 140 households last year. It is applying to the fictional Riverton Area Community Foundation for $7,500 toward the meal program. The application is a four-page form with a budget attachment. Assumptions: the director can give the proposal about five hours a week, and a board member has agreed to be second reader.

Notice what the fictional timeline spends its days on: 12 of 30 on eligibility and facts, 8 on drafting, 10 on review and logistics. First-time applicants usually invert this, spending 25 days writing and a panicked evening on everything else.

Where beginners over-invest and what to skip

The pattern in the timeline generalizes. Effort clusters in the wrong places on a first proposal, and knowing the pattern in advance is the cheapest correction available.

Two of these deserve a sentence each. The second reader is non-negotiable: after two weeks inside a draft you can no longer see missing answers, and reviewers can. And instructions-compliance is scored before prose quality everywhere that matters; a beautiful proposal that ignores a word limit or omits a required attachment announces that the organization does not follow directions, which is the opposite of what a funder is trying to learn about you.

Download: First proposal readiness checklist (CSV checklist). 25 checks across six areas: organization basics, program facts, numbers, funder fit, draft materials, and submission logistics. Mark each ready, in progress, or missing. Submit when nothing is missing, and not before.

After you hit submit

Log the submission in your grant tracking spreadsheet with the decision date the funder stated, then expect silence. Weeks or months of it is normal and is not feedback.

If the answer is yes: send the acknowledgment, read the award letter's reporting requirements the day it arrives, and put every report date in the tracker before celebrating.

If the answer is no, and it often will be: that is a data point, not a verdict on your organization. Funders decline strong applications for reasons that have nothing to do with the applicant, including simple arithmetic between requests received and dollars available. Where the funder allows questions, ask for feedback politely, record what you learn, and make a fresh decision about next cycle rather than resubmitting on autopilot.

We will be straight with you about the boundary: a disciplined process cannot guarantee an award, for a first proposal or a fiftieth, and anyone who says otherwise is selling something. What the process does is make you the applicant whose facts check out, whose budget adds up, whose application is complete and early, and who answered exactly what was asked. Those applicants win more than their share, and after one honest 30-day cycle, you will be one of them, with a fact sheet, narrative, budget, and tracker already built for proposal number two.

Sell AI visibility work to clients who already trust you, as a bounded observation engagement: a fixed-scope audit with declared prompts, platforms, evidence, and deliverables, priced on hours rather than promised outcomes. Qualify hard and refuse clients whose sites fail the prerequisites, because a failed engagement in a new category costs more than the fee. The consultants who last in this market sell observation. The ones who churn sell rankings.

Sell observation, not outcomes

The product is not "get us into ChatGPT." No one controls what a probabilistic answer engine generates, and any pitch that implies otherwise converts well and collapses at the first quarterly review. What you can sell honestly, and repeatedly, is uncertainty reduction: a controlled view of how answer engines currently use the client's sources and describe the brand, plus the eligibility, factual, and source fixes that evidence justifies. What actually changes between classic search work and this engagement is laid out in GEO vs SEO; the sales conversation goes better when you can name those four changes without hype.

Our position

Our position: selling observation over outcomes is not a compliance posture, it is the stronger commercial strategy. An outcome promise makes you liable for platform behavior you cannot control, prices the engagement against a fantasy, and dies at renewal when the fantasy does not arrive. An observation engagement is deliverable on schedule every time, survives skeptical procurement review, and renews on its own evidence, because the second audit is only comparable if the client keeps buying your method. Guarantee the method, the evidence, and the deliverables. Never guarantee mentions, citations, traffic, or revenue.

The rest of this page is the practical machinery: honest answers to the real objections, a qualification tree for whom to refuse, and a worked pricing anchor.

The objection table

These are the objections that actually come up, with answers that stay true after the contract is signed.

The third and seventh answers do the most work in real conversations, because they concede ground a hype seller cannot afford to concede. Conceding it is exactly what makes the rest credible. The crawler-policy detail behind the seventh sits in OAI-SearchBot vs GPTBot, and the tooling stance behind the eighth in the method-first tool comparison.

Refuse these clients: a qualification tree

A new service category cannot absorb bad-fit engagements. Walk each prospect through five gates, in order, and stop at the first failure.

1. Is the site crawlable and indexed on its priority pages? If no: refuse the AI visibility audit and propose SEO remediation first. Answer engines select from accessible, indexable sources; auditing visibility a site is not eligible for wastes everyone's money.
2. Do AI assistants plausibly mediate a buyer decision for this business? If no, for example a purely local walk-in trade with no consideration phase: refuse, or narrow to a small readiness diagnostic. Do not manufacture a threat.
3. Is there an owner who can approve brand facts and act on findings? If no: pause until a sponsor exists. An audit whose findings have no owner becomes a PDF, and unowned PDFs do not renew.
4. Does the client accept an observation deliverable rather than an outcome guarantee? If no, after you have explained it once, clearly: walk away. This gate protects you from the exact client who will demand the ranking you never promised.
5. Does the budget cover the minimum viable scope? If no: offer the smaller readiness diagnostic instead of quietly shrinking the method until the evidence is meaningless.

Prospects who clear all five gates convert well and renew, because the engagement was designed to succeed before it was sold.

The pricing anchor, worked

Anchor the conversation in an hour model, not a competitor's retainer. The full model, with per-workstream hour ranges by scope tier, is in how to price an AI visibility audit. The standard worked case from that model:

Worked example: Standard audit price floor

Declared assumptions: standard scope of 30 prompts across 3 platforms with 3 runs (270 observations), 52 delivery hours, loaded cost $75 per hour for a senior practitioner, $250 direct tool and transcription cost, 55 percent target gross margin.

Delivery cost: 52 x $75 + $250 = $4,150.

Price floor: $4,150 / (1 - 0.55) = $9,222, rounded to $9,200.

Quote the scope at or above the floor, then round to a commercially sensible number. In the sales conversation, the useful line is the observation count: 30 prompts x 3 platforms x 3 runs is 270 classified observations before any technical, factual, or source work. Clients who see that arithmetic stop comparing the audit to "reading some AI answers."

Present one number for a defined scope with named exclusions: implementation, ongoing monitoring, and new markets are separate proposals. Scope creep in a new category reads as improvisation, and improvisation kills trust exactly where you need it most.

Sell it inside accounts you already have

Cold-pitching AI visibility invites the hype comparison. Existing clients skip it, because the trust and the site knowledge already exist. The motion that works:

1. Raise it inside a scheduled review, not a special meeting. One slide: what answer engines are, what you can and cannot observe, what a baseline costs.
2. Bring a three-prompt sample for their own brand, run twice, screenshots attached, clearly labeled as an anecdote rather than a baseline. Its job is to make the category concrete, not to alarm. If the sample looks fine, say so; that honesty is the pitch.
3. Scope from their real buyer decisions, using the panel construction method in the prompt set guide.
4. Send a fixed proposal with method, deliverables, exclusions, and acceptance criteria, structured like the audit proposal template.
5. Deliver the audit, then let the roadmap sell the next stage. Monitoring and implementation renew from evidence, not from urgency.

Tool: Sell observation only if you can evidence it. Written exclusions, consent on record, a frozen panel and findings that trace to saved evidence are all scored checks. Know your own weak sections before a prospect finds them.

Fear-based selling is the shortcut to avoid at every step: no "your brand is invisible in AI" cold emails, no invented revenue-loss figures, no urgency theater. Beyond being commercially fragile, unsubstantiated performance claims are the kind of advertising the FTC's guidance for small businesses exists to police: claims need substantiation, and an observation engagement is the rare service whose claims are fully substantiatable. If you want the complete delivery system behind the sale, method, workbook, report, and proposal, that is what the AI Search Visibility Audit System packages.

No tool measures "AI visibility." Each observes one slice of it: sampled prompts, a mined prompt corpus, referral clicks, or crawler logs. Choose by observation method and evidence access, not by a proprietary score, and match the plan's prompt capacity to the panel you already run. For small scopes, one client, under about 50 prompts, one or two engines, a disciplined spreadsheet often beats a subscription. At agency scale, prompt trackers earn their fee by removing capture labor.

What each tool class actually observes

Every vendor in this market sells a window, not the weather. There are four windows, and they answer different questions.

Prompt trackers (Otterly.AI, Profound, Semrush's AI Visibility Toolkit) run a list of prompts against AI engines on a schedule and record the answers. They observe exactly what your panel asks, under the vendor's collection conditions, and nothing else. This is the closest match to an audit workflow built on a frozen prompt set, like the one described in how to build an AI visibility prompt set.

Corpus monitors (Ahrefs Brand Radar) mine a large index of search-derived prompts, 405 million or more by Ahrefs' own description, and report where a brand appears across it. They observe breadth you could never sample manually, but the prompts are the vendor's, not your buyers', so treat the output as market context rather than a client baseline.

Referral analytics (GA4 source filters, Bing Webmaster Tools) observe outcomes: humans who clicked from an AI surface to the site. They see nothing about answers where no click happened, which is most of them.

Log analysis (server or CDN logs checked against published crawler IP ranges) observes access: which AI agents actually fetched which pages. It is the only class that can verify the eligibility layer covered in OAI-SearchBot vs GPTBot.

No class observes why a model chose a source, what any individual user saw, or the effect of personalization and memory. A vendor score that implies otherwise is compressing a sample into a certainty.

Decide the criteria before opening a vendor tab

Comparing feature grids first is how agencies end up owning three overlapping subscriptions. Write down the scope you must serve, then test candidates against these criteria in order:

1. Method disclosure. How are prompts sourced, where are answers collected (consumer product, API, headless browser), how often, from what location and account state? If the vendor will not say, you cannot defend the numbers to a client.
2. Raw evidence access. Can you read and export the full answer text, cited URLs, and timestamps per run? Scores summarize; evidence survives client scrutiny.
3. Capacity fit. Does the prompt allowance cover your actual panel across your actual engines, or does the real scope live in add-ons?
4. True scope cost. Price one representative client end to end, including engines, markets, seats, and workspaces.
5. Workflow fit. Client isolation, report editing, and export into your reporting template.
6. Exit path. Historical data portability, and a method you could continue without the tool.

Four vendors compared, checked August 7, 2026

All figures below are vendor-stated, read from public pricing and documentation pages on the check date. They change often; verify on the purchase date.

Key facts, checked August 7, 2026

• Otterly.AI: Lite $29/mo for 15 prompts, Standard $189/mo for 100, Premium $489/mo for 400; four core engines with Claude, Google AI Mode, and Gemini as add-ons.
• Semrush AI Visibility Toolkit: $99/mo per domain billed annually, 25 custom prompts with daily runs, mentions from ChatGPT, Google AI, Gemini, and Perplexity.
• Profound: Starter $99/mo (ChatGPT only, 50 prompts), Growth $399/mo (3 engines, 100 prompts), Enterprise custom with up to 9 engines.
• Ahrefs Brand Radar: standalone $199/mo single platform or $699/mo all platforms; prompt index of 405M+ search-backed prompts; Grok data collection paused at the check date.

Read the table against your scope, not in the abstract. A solo consultant with one client panel of 20 prompts on two engines has no use for a 405-million-prompt corpus. A five-client agency running 100 prompts daily across four engines will burn analyst hours a $189 plan would erase.

When a spreadsheet beats a subscription

The manual method is not the budget option; it is the method-control option. You choose the prompts, conditions, and classification rules, and you keep every answer as evidence. The tradeoff is capture labor.

Worked example: Manual capture cost vs a prompt tracker

Declared assumptions: a 25-prompt client panel, 3 repeated runs per prompt, 2 engines, monthly cadence, 2 minutes to run and log each observation, analyst loaded cost $70/hour.

Observations per month: 25 x 3 x 2 = 150.

Capture time: 150 x 2 minutes = 5 hours. Add 1 hour for setup drift and rechecks: 6 hours.

Manual capture cost: 6 x $70 = $420 per month, before classification and reporting, which both routes still require.

Tool route: Otterly Standard at $189/mo covers the panel with capacity to spare; Semrush at $99/mo covers exactly 25 prompts on one domain. Either is cheaper than manual capture for this scope, but only if its collection conditions and exports satisfy the audit method. If the tool cannot export raw answers with timestamps, the $420 buys evidence the subscription cannot.

The spreadsheet wins when any of these hold: the engagement is a one-time baseline rather than continuous monitoring; the client demands full answer evidence; you are still validating that clients will pay before committing to annual, per-domain billing; or your panel is under roughly 50 observations per run. The subscription wins on daily cadence, multi-client portfolios, and engine breadth. The full manual protocol is in how to measure AI search visibility.

Score candidates with the worksheet

Run every shortlisted tool through the same 24 criteria before paying. The scorecard below implements the criteria from this article with weights, a 0 to 2 scoring scale, and space for evidence notes, so two people evaluating the same tool produce comparable results.

Download: AI visibility tool evaluation scorecard (CSV worksheet). 24 weighted criteria across observation method, evidence access, coverage and cost, workflow fit, and exit path, with a question to ask, passing evidence, and scoring columns for each.

Our position

Our position: buy evidence access first and scores last. A proprietary visibility index is a compression of sampled observations under undisclosed conditions, and an agency that reports it as a KPI inherits a number it cannot defend when a client asks why it moved. The tools worth paying for expose their method, retain raw answers with citations and timestamps, and export everything. By that standard, the best first purchase for most agencies is one month of disciplined manual measurement, because it teaches you exactly which capabilities you are buying and which you are outsourcing blind.

Tool: Score the method before you score the vendors. The scorecard above rates what a tool exposes. This one rates what you do with it, across all 47 checks, so you can tell a capability you are missing from a subscription that would not have fixed it.

Once the tool decision is made, fold its outputs into the audit workflow: the 47-point audit checklist covers what to inspect, and GEO vs SEO frames where tool-based observation sits inside the wider engagement. The AI Search Visibility Audit System includes the full workbook the scorecard feeds into.

A beginner does not need tips; a beginner needs a sequence. Grant writing is six skills learned in a fixed order: organizational readiness, funder fit, program design, budget, narrative, and assembly. A beginner course is worth buying only if its modules follow that order and end with a complete practice proposal. Before spending anything, do Candid's free one-hour introduction and run the readiness self-check below.

The skill sequence a beginner must build

Grant writing fails backwards. Weak proposals are rarely badly written; they are written before the facts existed. So the curriculum question for any beginner is not "how do I write persuasively" but "what must exist before each section can be written." That dependency chain is fixed:

1. Readiness facts. Tax status, mission, programs, people, and a real budget number, confirmed and approved, because every later claim rests on them.
2. Funder fit. A researched shortlist of funders whose stated eligibility, geography, and interests you actually match. Most wasted beginner effort is spent applying to funders a ten-minute check would have excluded.
3. Program design. The problem, the program, and a simple logic model connecting resources to activities to outcomes.
4. Budget. The program priced honestly, with a narrative explaining each line, agreeing with the logic model to the dollar.
5. Narrative and letter of inquiry. Only now the writing: a reusable core narrative and a letter of inquiry cut to the funder's stated length. Candid's free letter of inquiry guidance shows the standard form.
6. Assembly and submission. Compliance against the funder's instructions, attachments, and an on-time submission with a record of what was sent.

Figure: The beginner skill sequence: six stages in dependency order, with submission records feeding the next application's funder research.

The loop at the bottom is the part beginners are never told: your submission record and funder research carry into the next application, which is why the goal of a first course is a reusable system, not a single document. That framing, readiness before persuasion, is the whole argument of your first grant proposal.

A readiness self-check before any purchase

A course multiplies what you bring to it. Answer these honestly:

• Can you name the one organization you would build the proposal for? A real nonprofit, a planned one with a fiscal sponsor, or a clearly labeled fictional practice organization all work; "not sure yet" does not.
• Can you get its facts? Mission, program details, staff, board, and the actual budget total, plus someone authorized to approve claims about it.
• Do you have roughly 10 or more hours over the next month, on the calendar, not in theory?
• Do you know which funding channel you are aiming at? Foundations are the beginner channel; federal grants run on separate registration and compliance systems, outlined at the Grants.gov learning center, and are not a first project.
• Can you accept that finishing a strong proposal is the outcome you are buying? Training improves what you submit; it cannot guarantee what any funder decides.

Three or more "no" answers means the free tier below is your entire curriculum for now, at the correct price of zero.

Do the free hour before you spend anything

The information layer of grant writing is free and good. Candid's Introduction to Proposal Writing is on demand, about one hour, and includes worksheets and a sample proposal; the surrounding proposal writing knowledge base covers each component in the standard structure. Do the hour, then attempt one unassisted paragraph: describe your program's problem with a number and a source, no adjectives.

That paragraph is diagnostic. If it came easily, keep going with free materials and our template walkthroughs like the needs statement template and grant budget template; you may not need a course yet. If you stalled on what belongs in it, or on where facts come from, that is precisely the gap a sequenced course closes, and you now know it from evidence rather than marketing.

Download: Beginner learning path checklist (Markdown checklist). The six-phase sequence as a working checklist, from the free orientation hour through submission, with the free-resource links and a stated test for when buying a course is justified.

How to judge a beginner course specifically

General course quality criteria apply (our 10-point evaluation framework is the full version), but beginners should weight four things the general buyer can compromise on:

• The module order matches the skill sequence. Research and program design before persuasive writing. A curriculum that opens with storytelling teaches you to decorate facts you do not have yet.
• It assumes zero experience and defines terms. LOI, indirect costs, restricted funds, logic model: each defined at first use. Sample lessons reveal this in minutes.
• Every module ends in applied output. A beginner cannot self-generate practice; the course must force production, and a fictional practice organization should be explicitly supported for learners without a nonprofit yet.
• Time and feedback claims are honest. Stated guided plus applied hours, and an exact statement of what human review is included, even if that statement is "none."

Set time expectations from the sequence, not from a sales page. A credible beginner curriculum needs roughly 5 to 6 hours of instruction plus 5 to 8 hours of applied work to reach one assembled practice proposal, so plan on 10 to 13 hours across three to six weeks. A program claiming a complete grant education in an afternoon is compressing stages 2 through 6 into a lecture, and a program demanding 60 hours before your first finished artifact is teaching a career, not a first proposal.

The choice between course and workshop formats also lands differently for beginners: a one-day workshop compresses the sequence into hours, which serves refreshers far better than first exposure, while self-paced study asks for a discipline that first-timers should verify they have (the free hour above is that test) before paying for it. The full trade-off, including a worked cost comparison, is in course versus workshop.

What to skip until later

Skip certifications: the credible ones (GPC, CFRE) require documented professional experience you do not have yet, and anything "certifying" beginners is a certificate in costume, a distinction unpacked in certification versus certificate. Skip federal-grant training until a specific federal opportunity exists; the registration, compliance, and reporting load is a different discipline, and learning it speculatively burns the hours your first foundation proposal needs. Skip proposal software and AI drafting tools until the sequence above is habit; tools accelerate systems, and a beginner does not have a system yet.

Our position

The best beginner curriculum is boring on purpose: facts, fit, program, budget, then words. We built our own course in that order, and we still tell beginners to take Candid's free hour first, because a paid course is only worth buying once you have evidence you need one. Spend money on sequence and forced production. Everything else a beginner is sold is either free elsewhere or premature.

A grant writing course is nonprofit-specific when its final project is a complete proposal for an actual organization and its curriculum covers the mechanics generic writing courses skip: funder research, restricted funds, logic models, budgets with narratives, and compliance. Score any candidate course against the 10 points below before paying. Free training from Candid sets the quality floor; a paid course must beat it with guided production, not more information.

The one question that sorts every course

Ask what learners hold at the end. If the answer is a completed proposal, built section by section for a real organization (or a clearly labeled practice one), the course is teaching grant writing. If the answer is a quiz score, a discussion post, or a certificate graphic, the course is teaching about grant writing, and a quiz has never been evidence that someone can assemble a proposal.

This one question eliminates most generic options quickly, because a proposal is not an essay. It is a coordinated pack of documents where the needs statement, program design, budget, and evaluation plan must agree with each other and with the funder's instructions. A course that never forces that agreement has not taught the hard part. Everything else in the checklist below refines this first cut.

The 10-point course evaluation checklist

Score each point 0 (absent), 1 (partial or vague), or 2 (verified from the syllabus, a sample lesson, or the sales page). Points 1 and 2 are gates: a course scoring 0 on either fails regardless of its total. For the rest, treat 14 of 20 as a defensible bar.

1. Final project is a real proposal. The course ends with a complete, assembled proposal, not fragments or quizzes.
2. Full artifact coverage. Needs statement, program description with a logic model, evaluation plan, budget with narrative, letter of inquiry, and an assembly step all appear in the curriculum.
3. Nonprofit-specific mechanics. Restricted funds, governance claims, funder research through public filings, and post-award reporting are addressed, not just "persuasive writing."
4. Research before writing. Funder fit and eligibility come before drafting in the module order. Courses that open with storytelling teach the sequence backwards.
5. Feedback honesty. The sales page states exactly what human feedback is included at the tier you would buy, including "none." Self-paced with no review is a legitimate product; an ambiguous promise of "support" is not.
6. Materials currency. Lessons and tools carry a visible updated date, and any cited portals or funder practices are current.
7. Editable working tools. Templates ship as editable documents and spreadsheets you will reuse, not locked PDFs.
8. Time honesty. Guided hours and applied working hours are stated separately, and the total fits your calendar.
9. Declared channel fit. The course says plainly whether it teaches foundation grants, federal grants, or both. Federal work runs on different rules and portals; see the Grants.gov learning center for what that channel involves.
10. Clean outcome claims. No promised awards, win rates, or income figures, and access, refund, and license terms are written down.

Download: Grant course evaluation scorecard (CSV template). The 10 checklist points as a scoring worksheet: criterion, what to verify, where to look, a 0 to 2 score column, and an evidence column so a colleague can audit your evaluation.

Red flags that end the evaluation early

Some findings should stop the scoring entirely.

• Guaranteed or implied win rates. "Our students win 87 percent of grants" is unverifiable and misunderstands how awards work. Funder decisions turn on fit, budget cycles, and the competing pool; no course can guarantee them, and a provider claiming otherwise is telling you how they market everything.
• No syllabus and no sample lesson. If you cannot see the module list before paying, you cannot run any checklist, and that is the point of hiding it.
• Certification language for a certificate. "Become a certified grant writer" attached to a course-completion document borrows the authority of independent credentials like the GPC and CFRE without their requirements. The difference is a purchase-defining distinction we cover in certification versus certificate.
• Permanent urgency. Evergreen countdown timers and "3 seats left" on a self-paced digital product tell you the seller's respect for evidence.
• One-size funding claims. A course promising to cover foundation, federal, corporate, and international grants equally in a few hours covers none of them usably.

The price landscape, checked August 7, 2026

Prices in this market map to structure more than to quality, so evaluate what the money buys at each tier rather than assuming expensive means rigorous.

Key facts, checked August 7, 2026

• Free tier: Candid's Introduction to Proposal Writing is on demand and about one hour, with worksheets and a sample proposal; Candid's proposal knowledge base is also free.
• Self-paced systems typically sell for a low three-figure price; our own Nonprofit Grant Proposal System is $119 (Essentials) or $249 (Professional with editable templates and worked demonstrations).
• Live formats price by scheduled human time: workshops per seat per day, cohort courses and university certificate programs above self-paced products because instructor hours are the cost driver.
• Independent certifications (GPC, CFRE) are a different purchase entirely: exams with experience requirements and renewal cycles, priced on the credential owners' sites.

The honest generalization: paying more buys scheduled human attention, not better information. The information layer is largely commoditized by the free tier. So decide first whether you need accountability and feedback (live formats) or a production system on your own schedule (self-paced), a trade-off we work through in course versus workshop.

Where our course fits, and where it does not

We sell a course in this category, so here is its scorecard treatment rather than a pitch. The Nonprofit Grant Proposal System is self-paced, built for small US nonprofits pursuing foundation grants, and structured so the final deliverable is a complete funder-ready proposal pack: shortlist, needs statement, logic model, evaluation plan, budget with narrative, core narrative, and letter of inquiry, about 5.5 guided hours plus 4.5 to 8 applied hours. Its worked examples run on Cedar Bend Youth Alliance, a fictional practice nonprofit, and are labeled as such throughout.

Where it does not fit: it is not a federal grants course; Uniform Guidance, SAM registration, and NOFO responses are a different system, and buyers heading there should score federally focused training instead. It includes no live human feedback at any tier; a buyer who knows they need a reviewer should weight point 5 accordingly or budget separately for review. And like every course on this page, it cannot guarantee a funded proposal.

Our position

Run the scorecard even on us, and even on free options. A course that survives points 1 and 2, states its feedback and channel honestly, and fits your actual hours will serve you at any price tier, and a course that fails them will waste your time at any price. If you are choosing your very first training purchase with no proposals behind you, start with the beginner curriculum guide, and put the free Candid hour before any invoice.