Major Donor Meeting Briefing

A gift officer rarely needs more raw CRM fields before a major-donor meeting. They need a coherent picture: who this person is in relation to the organization, what they have given and why it mattered, what recent conversations signaled, and which program outcomes speak to their interests. That synthesis is slow when it means opening the constituent record, gift history, contact notes, and impact reports in parallel, then rewriting the same story under time pressure.

This use case uses a large language model to draft a pre-meeting briefing from three required inputs: relationship history (notes, meetings, communications), giving record (amounts, designations, cadence, recognition preferences if recorded), and program impact notes tied to the donor’s interests or prior gifts. The model’s job is synthesis and structure. The officer’s job remains judgment: what to ask, when to ask, and how to hold the conversation.

Related workflows that often feed or follow this briefing include Major Gift Upgrade Readiness Scoring, Donor-Interest-Matched Impact Update, and Relationship Engagement Monitoring.

Treat the briefing as incomplete unless all three source types are present and usable.

Relationship history. Meeting notes, call summaries, email excerpts already stored in the CRM or stewardship system, event attendance, volunteer involvement, and any recorded preferences (communication channel, topics to avoid, family members involved in decisions). Prefer dated, attributed notes over free-form lore that cannot be traced.

Giving record. Soft and hard credits as your shop defines them, gift dates, designations or funds, pledge vs. cash status, recognition name preferences, and any documented matching-gift or donor-advised-fund context. Include gaps or lapses only if they appear in the record; do not invent explanations.

Program impact notes. Short, factual outcomes linked to programs the donor funded or has expressed interest in: what changed, for whom, over what period, and which metrics or stories your program staff already approved for donor use. If impact language is marketing copy with no program source, exclude it.

Optional enrichments help but do not replace the three required inputs: wealth or capacity screens already in the file, peer-network notes, prior proposal PDFs, and calendar context for the upcoming meeting (location, attendees, stated purpose).

Empty-output rule. If relationship history, giving record, or impact notes are missing, truncated beyond use, or clearly mismatched to the constituent, return no briefing body. Surface a short, explicit gap message naming which input failed. Do not fill holes with plausible narrative, sector averages, or “typical major donor” language.

A strong draft is short enough to read twice before the meeting and specific enough that another officer could brief from it. Aim for sections the officer can scan, not a biography.

Relationship snapshot. One paragraph on how the relationship started, who owns it, and the tone of recent contact. Call out unresolved threads from the last meeting (promised follow-ups, open questions, family or advisor involvement).

Giving pattern in plain language. Chronology of significant gifts and designations, not a dump of every transaction. Note consistency vs. episodic giving, shifts in fund preference, and any recognition or anonymity rules. Flag conflicts between systems (CRM vs. finance) for human resolution rather than choosing a side.

Interest and motivation signals. Themes that appear across notes and designations: scholarship, capital, unrestricted, a named program, geographic focus, faith or values language if the donor used it. Separate stated preferences from staff inference; label inference clearly.

Impact hooks tied to their gifts. Two to four concrete outcomes the officer can cite without overclaiming. Prefer program-approved numbers and stories. If the only available impact is organization-wide, say so and avoid implying the donor alone produced the result.

Meeting-facing agenda suggestions. Draft talking points and questions grounded in the file, including stewardship thanks, program update angles, and open items to close. Phrase asks as options the officer may adopt, revise, or discard. Never output a finalized ask amount, pledge language, or “recommended close” as if the model owns the strategy.

Risk and sensitivity flags. Health events, board politics, prior complaints, media exposure, or estate conversations that appear in notes. Present them as briefings for care, not as talking points to force into the meeting.

Run the briefing generation close enough to the meeting that notes are current, then treat the output as a first pass.

1. Confirm identity and household. Merge errors and soft-credit confusion are common; fix the record before trusting the narrative.
2. Verify every gift figure and designation against the system of record. Correct the draft if the model compressed or misordered gifts.
3. Check impact claims against program sources. Remove anything that cannot be defended in the room.
4. Rewrite the ask strategy yourself. Capacity scores, peer comparisons, and campaign priorities belong to the officer and leadership, not to the model’s prose.
5. Decide what stays off the table. Sensitivity flags may mean shorter meetings, a stewardship-only visit, or a delayed solicitation.

Human-in-the-loop is non-negotiable here. The model drafts the briefing so prep time goes into relationship judgment. The officer still prepares the ask, chooses language, and owns what is said to the donor.

When engagement signals look thin or contradictory, cross-check with Relationship Engagement Monitoring before treating silence or sporadic contact as disinterest.

Hallucinated intimacy. Models will smooth sparse notes into a warm, continuous relationship story. Prefer verbatim cues and dated facts. If notes are thin, the briefing should look thin.

Invented impact. Program outcomes without a source line are a credibility risk in a major-gift conversation. Require citation to the impact note or return empty for that section.

Ask overreach. Auto-generated “ask ranges,” upgrade percentages, or closing scripts create false confidence. Keep quantitative strategy in separate scoring tools such as Major Gift Upgrade Readiness Scoring, and keep this page’s output descriptive and preparatory.

Privacy and minimization. Include only what the officer needs for this meeting. Do not paste full email threads, medical detail beyond what notes already record for stewardship care, or third-party wealth data that your policies exclude from meeting packets.

Stale inputs. A briefing built on last year’s notes and last campaign’s impact sheet can steer the conversation wrong. Timestamp sources in the draft header and refuse to run when required inputs are older than your shop’s freshness threshold, if you set one.

Multi-donor households. When two decision-makers share a record, label whose words and gifts appear where. Ambiguous “they” language is a prep failure.

Start with one portfolio segment: active major-gift prospects with meetings scheduled in the next two weeks. Define the three input packages in your CRM export or stewardship workspace so every run uses the same shape.

Write a briefing template with fixed headings (snapshot, giving pattern, interests, impact hooks, agenda options, sensitivities). Constrain the model to those headings and to quoting or paraphrasing only from supplied text. Add a validation step that blocks output when any required section’s source payload is empty.

Pilot with two officers comparing model drafts to their own prep notes. Track time saved, corrections made, and whether any invented detail reached a donor conversation. Expand only after the empty-output path and human review habit are reliable.

Over time, connect briefing generation to interest-matched impact content (Donor-Interest-Matched Impact Update) so the impact section stays program-fresh, and to engagement monitoring so officers know when a meeting should be stewardship-heavy rather than solicitation-ready. The briefing remains a preparation artifact, not a substitute for presence in the room.