Written from 7 named sources · Sep 21 · first result Grounding a few field-standard practices so the blueprint stays accurate, then assembling the final operational document.# Guided Contact Report System & Fundraiser Onboarding Program Operational Blueprint — University Advancement Division How to use this document. This is a demonstration framework written from a university advancement perspective. It is CRM-agnostic and adaptable to other nonprofits. Picklists, SLAs, scoring bars, dollar figures, names, and sample dates are illustrative defaults created for demonstration. They were not supplied by the requesting institution and are not requirements that institution set. Calibrate them to the actual CRM, staffing model, gift-planning policy, and campaign structure. Design principle. The contact report is the division’s primary instrument of institutional memory. It is written for the next reader — a colleague, a successor, a data steward, a planned giving officer three years from now — not for the writer. University practice treats the report as the vehicle that captures the data needed to manage relationships and evaluate gift-officer work; a report is valuable when a future interaction would be enhanced by knowledge of this one.[[1]](https://butleru.my.site.com/askbutler/s/article/Contact-Report-Best-Practices) Executive Framework 1.1 Why this discipline exists Without a guided reporting system, intelligence lives in inboxes, notebooks, and turnover. With it, every visit, call, video, event conversation, and substantive email becomes structured, searchable, and routable intelligence that drives moves management, coordinated donor stewardship, and leadership decision-making. Two interlocking systems deliver that outcome: System Function A — Guided Contact Reporting Prompt-driven capture so every interaction produces actionable institutional intelligence, not a diary entry. B — Fundraiser Onboarding Enculturation into university culture, advancement lexicon, campaign priorities, and reporting as a professional competency. 1.2 Core tenets 1. Timeliness. File within 24–48 hours of contact; same-day for solicitations, grievances, estate-planning disclosures, or reputational risk. Field practice commonly requires logging meaningful interactions within 48 hours, with a clear next step assigned.[[2]](https://blog.blackbaud.com/moves-management-overview/) Some campuses set a three-business-day outer bound; the tighter window is the working standard here because memory decays and escalation windows close.[[1]](https://butleru.my.site.com/askbutler/s/article/Contact-Report-Best-Practices) 2. Signal-to-noise. Capture two layers and tag them differently: Intelligence changes strategy (capacity change, disinterest, bequest language, complaint, referral, ask readiness). Color builds relationship texture (grandchild’s name, love of the marching band, favorite spot on campus). Narrative is 3–6 sentences of substance, not a transcript. Color belongs in designated notes fields, not buried in strategy fields. 3. Moves management integration. Every report answers five questions: What stage were we in? What stage are we in now? What is the next move? Who owns it? By when? Moves management is the practice of assessing where a prospect sits in the donor journey and executing the next action that advances the relationship.[[3]](https://www.donorsearch.net/resources/moves-management/) A report without a next step is a diary entry, not a strategy document. Stages used here (illustrative): Identification → Qualification → Cultivation → Solicitation → Stewardship. 4. Data governance and ethics. Gift officers own narrative and prompt fields; data stewards own picklist integrity; prospect research owns capacity/inclination; Donor Relations and Planned Giving own resolution and expectancy records. Write as if the constituent could read the file. Do not record conjecture, gossip, or health detail that was not given directly by the constituent and relevant to the relationship.[[1]](https://butleru.my.site.com/askbutler/s/article/Contact-Report-Best-Practices) 5. Escalation discipline. Complaints, estate signals, and reputational-risk content trigger automatic routing, not passive filing. Speed of response is the value. 1.3 Anatomy of a complete contact report Every filed report contains all eight elements: Header metadata — contact date, type, attendees (constituents + staff), location, duration, solicitor(s) Purpose of contact — Discovery / Cultivation / Solicitation / Stewardship / Service Recovery / Qualification Narrative summary — 3–6 sentences Guided prompt responses — all seven core domains answered or marked N/A with justification Stage and move update — before/after, next move, owner, due date Action items — each with owner and due date, separate from the strategic next move Escalation flags and routing status Sensitivity classification — Standard / Restricted / Confidential 1.4 Quality rubric (manager review) Score 1–4 on each criterion. Illustrative certification bar: ≥14/16 across three supervised reports. Criterion Excellent (4) Adequate (3) Needs work (1–2) Specific Names, figures, dates, verbatim where meaningful Mix of specifics and generalities “Good visit, donor is positive” Forward-looking Next move + owner + date; owned action items Next move present; owner/date vague No next move Honest Disinterest and objections recorded as faithfully as enthusiasm Hints at concern Only positive spin Concise Readable in under 90 seconds Readable with skimming Transcript or wall of text A report is treated as substantive when it documents a real interaction and at least two of the following occurred: new philanthropic information (interests, capacity, timing); a gift discussion or solicitation; or clear next steps. After the meeting, officers should be able to answer: What did I learn that helps secure a gift? What motivates this prospect? What is the next sensible move?[[1]](https://butleru.my.site.com/askbutler/s/article/Contact-Report-Best-Practices) 1.5 Sensitivity, compliance, and ethics Tier Visibility Typical content Standard Advancement Cultivation narrative, reunion posture, public interests Restricted Assigned team + managers Health given by the constituent, family conflict, capacity estimates, moderate complaints Confidential Routed specialists only Severe complaint verbatim, explicit bequest detail, reputational risk Confidential-tier reports are excluded from broad search. Complaint and planned-giving fields are visible to routed teams only. Guided Contact Report System 2.1 Core record schema (CRM-agnostic) Map these objects to native CRM structures (actions, activities, tasks, affiliations, custom objects). Required fields are the minimum viable report. Field Type Values / notes Contact Date Date Required Contact Type Picklist Visit / Call / Video / Event / Email / Other Contact Purpose Picklist (multi) Discovery / Cultivation / Solicitation / Stewardship / Service Recovery / Qualification Attendees Lookup Constituents + staff; required Location Text Required Duration Number or picklist Minutes Solicitor(s) Lookup (staff) Required Narrative Summary Long text 3–6 sentence standard Sensitivity Tier Picklist Standard / Restricted / Confidential Moves Stage Before / After Picklist Identification → Qualification → Cultivation → Solicitation → Stewardship Next Move Description Text Required Next Move Owner Lookup (staff) Required Next Move Due Date Date Required Action Items Related list Each with owner + due date Escalation Flags Checkboxes + status Complaint / PG Signal / Reputational Risk + routed Y/N + date Report Filed Date Auto Timeliness audit (hours from Contact Date) 2.2 Guided diagnostic matrix Prompts appear conditionally (example: reunion-year alum sees the reunion prompt auto-surfaced from class year). A configurable management-driven layer injects time-bound institutional questions and is reviewed quarterly. Domain / module Guided diagnostic questions CRM input types Escalation / follow-up workflows Cross-departmental routing 1. Reunion & milestone engagement Is the constituent in a reunion cycle (illustrative: 5/10/25/50th)? Did reunion come up? Posture: attending, hosting, giving, ambivalent, declined? Milestone birthday or anniversary? Reunion Year (auto from class year); Reunion Posture picklist: Hosting / Attending / Giving / Ambivalent / Declined / N/A; Reunion Notes (text) If Hosting, Attending, or Giving: add to class-gift pipeline; invite to pre-event; volunteer task Alumni Relations & Class Gift officer; Annual Giving / Reunion team 2. Grievances & complaints Any dissatisfaction with stewardship, communications, institutional decisions, athletics, policy, or a past interaction? Record verbatim where possible. Complaint Flag (Y/N); Category (Stewardship / Comms / Policy / Athletics / Service / Other); Severity (Minor / Moderate / Severe); Verbatim (text); Resolution Status (Open / In Progress / Resolved / Closed-No Action) Any Flag = Y → Donor Relations ≤1 business day; Severe → VP Advancement same day; track to closure; service-recovery move Donor Relations (owner); VP Advancement if Severe; Dean / unit lead as needed; original officer remains relationship owner 3. Planned & estate giving signals Mention of will, trust, estate plan, beneficiary designation, IRA, life insurance, real property, or phrases such as “in my plans,” “after we’re gone,” “leaving something to the university”? PG Signal (Explicit / Implied / Contextual / None); Vehicle multi-picklist: Bequest / Trust / IRA / Insurance / Property / Other; PG Verbatim (long text); PG Indicator tag Any signal ≠ None → auto-notify Planned Giving; specialist outreach ≤5 business days; do not request documents, amounts, or legal advice in the discovery moment; treat as stewardship, not a countable gift Gift Planning / Planned Giving; Major Gifts partner 4. New discovered intelligence What did we learn that we did not already know? Career change, liquidity event, family, health (constituent-disclosed and relevant only), relocation, new interests, capacity indicators? New Intel Flag (Y/N); Categories multi: Career / Liquidity / Family / Health / Relocation / Interests / Capacity; Intel Detail (text) Feed Prospect Research queue; liquidity event → capacity re-rating task; research validates before rating change Prospect Research & Analytics; assigned gift officer 5. Referral & network leads Friends, classmates, business partners, or family with affinity or capacity? Offer to make an introduction? Referral Flag (Y/N); Referred Prospects (lookup / new records); Introduction Offered (Y/N); Relationship Map Notes Create new prospect (source = Referral); follow-up task to referring donor to facilitate intro (illustrative: ≤14 days) Prospect Management + Research; assigned officer owns follow-up; Annual Giving for broad leads 6. Broader philanthropy What other organizations or causes does the donor support? Where does the university sit in their philanthropic portfolio? What motivates giving generally? External Philanthropy (text); Portfolio Position (Primary / Significant / One-of-Many / Minimal); Motivations multi-picklist Feed inclination scoring; inform proposal framing and realistic ask range Major / Principal Gifts strategy; Research 7. Dreams & aspirations Vision for the relationship with the institution? What should giving accomplish? Legacy hope? Change they want to see? Capture verbatim. Aspirations Flag (Y/N); Aspirations Verbatim (long text); Themes multi: Scholarship / Faculty / Facilities / Athletics / Research / Access / Other Flag for major / principal gift strategy session; preserve verbatim as proposal spine Principal Gifts; Major Gifts; Dean / leadership for transformational themes 8. Management-driven supplemental Time-bound leadership question (example: “Did you discuss the campaign priority for the new engineering facility?”). Governed quarterly. Supplemental Prompt ID + Response (text / picklist, configurable); Campaign Topic Discussed (Y/N) Aggregate for campaign-readiness dashboard AVP / Campaign leadership; Dean’s office as relevant 2.3 Planned-giving codebook (required) A bequest intention is a donor’s indication of intent to leave a future gift. It is neither a legal nor binding commitment upon the estate; it is a courtesy notification that enables lifetime stewardship.[[4]](https://www.blackbaud.com/wp-content/uploads/2025/10/TipSheet-DI-23-Planned-Giving-Terms-You-Should-Know.pdf) Institutions commonly state that such notices are subject to change and are not pledges.[[5]](https://www.reed.edu/givingtoreed/bequest-intention/) Signal strength Definition Illustrative language Explicit Direct statement of completed or intended provision “We’ve put the university in our plans.” “We’ve named the university in our will.” “You are beneficiary of my IRA.” Implied Strong suggestion without confirmation “We’re taking care of the university in our estate plans — still working with our attorney.” Contextual Estate-planning context with no university link stated “We just met with our estate attorney to update everything.” None No estate or legacy language — Operating rule. Capture verbatim, express gratitude, promise specialist follow-up. Do not count the intention as a gift. Immediate workflow is Planned Giving stewardship and documentation options, not solicitation. 2.4 Complaint severity codebook (illustrative) Severity Definition Routing Minor Annoyance; no gift or reputational impact Donor Relations ≤1 business day Moderate Affects giving or engagement; no public/press risk Donor Relations ≤1 business day; officer remains relationship owner Severe Threatens the relationship, public criticism, or trustee / donor-leader involvement VP Advancement same day + Donor Relations; Dean / unit lead notified Rule. Never argue the complaint in the report. Record, route, respond. 2.5 Escalation and routing SLAs (illustrative defaults) Filing triggers routing. Flagged reports go to specialist owners first, then into quality review. Standard reports go to manager sampling. Trigger Route to SLA Record action Complaint = Y (any severity) Donor Relations ≤1 business day Resolution Status = Open; task assigned Severity = Severe VP Advancement + Donor Relations Same day Leadership response plan PG Signal = Explicit / Implied / Contextual Planned Giving Auto-notify on filing; outreach ≤5 business days PG Indicator tag; expectancy workflow only if policy allows Liquidity event Prospect Research ≤5 business days Capacity re-rating task Introduction Offered = Y Gift officer (referrer owner) ≤7 days to start facilitation Follow-up task Reputational risk VP Advancement Same day Confidential handling Fundraiser Onboarding & Culture Curriculum Frontline fundraiser tenure in higher education is commonly cited in the 18–24 month range, which makes onboarding a retention and pipeline-protection issue, not an HR formality.[[6]](https://www.evertrue.com/onboarding-new-gift-officers/) Formal onboarding that communicates unit philosophy, common expectations, institutional culture, and performance standards is a controllable factor in gift-officer success.[[7]](https://www.academicimpressions.com/major-gift-officer-training-onboarding/) Reporting excellence is taught as a core professional competency, not an administrative chore. Module 1 — Institutional culture and history (Days 1–10) Goal. Think like an institutional steward. Content. Founding story, mission, traditions, academic identity; advancement’s reputation with deans, faculty, and athletics; donor-centered ethics, confidentiality, and the “write for the next reader” mindset. Artifacts. Culture & Values Primer; shadow two veteran officers (one major-gift visit, one stewardship call); shadowing debrief with manager by Day 10. Success criterion. Can narrate the university story and advancement’s role in their own words. Module 2 — Advancement lexicon (Days 11–21) Goal. Speak the language fluently. Core vocabulary. Moves management, cultivation, solicitation, stewardship, qualification, capacity/inclination, LYBUNT/SYBUNT, soft credit, bequest expectancy, pipeline stages, portfolio, discovery, service recovery. Institution-specific language. Campaign names, fund nomenclature, school/unit abbreviations, donor society names, database shorthand. Artifacts. Glossary + acronym sheet; CRM navigation lab; terminology assessment Day 21 (illustrative bar: ≥90% to pass). Module 3 — Institutional priorities and campaign knowledge (Days 22–30) Goal. Connect donor aspirations to fundable priorities. Content. Top campaign priorities, funding gaps, case statements; unit-level priorities for the officer’s portfolio; the management-driven prompt layer — what leadership currently wants captured and why; proposal library tour. Artifacts. Priority Briefing Deck; mock contact report on a simulated donor visit (must include one PG signal and one aspiration quote). Success criterion. Can articulate the top three campaign priorities unaided by Day 30. Module 4 — Leadership-driven reporting discipline (Days 31–45) Goal. Master the guided report. Content. Timeliness standard, quality rubric, sensitivity tiers, escalation obligations (complaint + PG drills); setting next moves with owners and dates; live CRM filing labs. Artifacts. Certification — three supervised contact reports reviewed against the rubric; one must demonstrate correct complaint or PG routing. Success criterion. Three reports pass (illustrative: ≥14/16) by Day 45 before independent filing is authorized. Module 5 — CRM hygiene and metrics (Days 46–60, overlapping) Goal. Own a clean portfolio. Content. Visit counts, qualification targets, moves, submission rates; monthly timeliness dashboard; quarterly quality sampling; data-steward office hours. Artifacts. Portfolio assigned; timeliness tracking begins; 30-60-90 plan with manager. Success criterion. Full independence Day 60. Milestone Timing Success criterion Owner Culture immersion complete Day 10 Shadowing debrief Manager + buddy officer Vernacular assessment Day 21 ≥90% terminology check Training lead Priorities briefing Day 30 Top 3 campaign priorities unaided AVP / unit lead Contact report certification Day 45 3 supervised reports pass rubric Manager + data steward Full independence Day 60 Portfolio assigned; tracking begins Manager Completed models (all eight anatomy elements) Names, dates, and details are fictional illustrations. Dates are in September 2026. Template A — Standard: Reunion + new intelligence + aspiration 1. Header. Contact Date: 8 Sep 2026 Type: Visit Attendees: Jane Alvarez ’98 + Officer Lee + Alumni Officer Park Location: Donor’s office, Austin, TX Duration: 60 min Solicitor(s): Officer Lee 2. Purpose. Cultivation + Qualification 3. Narrative. Jane is excited for her 25th reunion next spring and open to hosting a regional pre-event. She shared she recently sold her startup and is considering how to direct new philanthropy. She gives primarily to STEM-access programs elsewhere and currently sees the university as “one of many — for now.” She said: “I want my giving to open doors I had to push open myself.” 4. Guided prompts. Reunion: Year auto-flagged (25th); Posture = Hosting; Notes: open to Austin pre-event, wants classmate co-host. Complaints: Flag = N. PG Signal: None. New Intel: Flag = Y; Categories = Liquidity, Career; Detail: startup sale — referred to Research for validation; career transition to advisor role. Referrals: Flag = N; Intro Offered = N. Broader philanthropy: External STEM-access nonprofits; Portfolio = One-of-Many; Motivations: Access, Equity. Aspirations: Flag = Y; Verbatim: “I want my giving to open doors I had to push open myself.”; Themes = Scholarship, Access. Supplemental: Campaign engineering facility discussed? Y — interested in lab tour, not yet in a proposal. 5. Stage & move. Cultivation → Cultivation; Next Move: Invite to engineering lab tour with Dean; Owner: Lee; Due: 25 Sep 2026. 6. Action items. (a) Park to send reunion host packet; Due: 12 Sep 2026. (b) Lee to request capacity re-rating; Due: 11 Sep 2026. 7. Escalation. No complaint or PG flags; Research queue task created for liquidity event. 8. Sensitivity. Standard. Template B — Complaint, escalated (Restricted) 1. Header. Contact Date: 9 Sep 2026 Type: Call Attendees: Robert Chen ’82 + Officer Diaz Location: Phone Duration: 25 min Solicitor(s): Officer Diaz 2. Purpose. Stewardship + Service Recovery 3. Narrative. Donor called frustrated after receiving duplicate solicitations despite requesting fewer emails in August. He feels his preference was ignored and is reconsidering his annual gift. Officer acknowledged the error, apologized, and committed to suppression plus a personal follow-up. Donor accepted the plan but expects confirmation this week. 4. Guided prompts. Reunion: N/A — not in cycle, not discussed. Complaints: Flag = Y; Category = Comms; Severity = Moderate (repeated solicitation after opt-down; gift at risk; no press risk); Verbatim: “I asked in August to cut back the emails and I’m still getting three a week — it feels like no one listens.”; Resolution Status = Open. PG Signal: None. New Intel: Flag = N. Referrals: Flag = N. Broader philanthropy: Portfolio = Significant (annual donor; university among top three). Aspirations: Flag = N. Supplemental: N/A. 5. Stage & move. Stewardship → Stewardship (recovery); Next Move: Personal apology + confirmation of email suppression; Owner: Diaz; Due: 11 Sep 2026. 6. Action items. (a) Donor Relations to apply suppression and confirm; Owner: Associate Kim; Due: 10 Sep 2026 (≤1 business day). (b) Diaz to call donor to confirm the fix; Due: 11 Sep 2026. 7. Escalation. Complaint Flag = Y, Moderate → routed to Donor Relations 9 Sep 2026 (within SLA); VP notification not required (Severe only). 8. Sensitivity. Restricted. Template C — Planned-giving signal, escalated (Confidential) 1. Header. Contact Date: 10 Sep 2026 Type: Visit Attendees: Margaret & Tom Ellis ’74 + Officer Chen Location: Donors’ home, Columbus, OH Duration: 90 min Solicitor(s): Officer Chen 2. Purpose. Cultivation 3. Narrative. In a home visit, the Ellises shared they recently met with their estate attorney and have provided for the university in their plans. They mentioned considering an IRA beneficiary designation but gave no amounts or percentages. They spoke warmly about scholarship support as a legacy and welcomed a follow-up with Planned Giving. No solicitation was made. 4. Guided prompts. Reunion: N/A. Complaints: Flag = N. PG Signal: Explicit — donors stated “we’ve put the university in our plans,” which meets the codebook definition of a direct statement of provision; Vehicle = Bequest + IRA; Verbatim: “We’ve put the university in our plans — after we met with our attorney last month, it just felt right.”; PG Indicator tag = Y. New Intel: Flag = Y; Categories = Family, Interests; Detail: grandchildren starting college search; interest in need-based scholarship. Referrals: Flag = N. Broader philanthropy: Local arts + health system; Portfolio = Primary; Motivations: Education, Legacy. Aspirations: Flag = Y; Verbatim: “We want to help kids who remind us of us — first in the family to go.”; Themes = Scholarship, Access. Supplemental: N/A. 5. Stage & move. Cultivation → Cultivation (PG stewardship track); Next Move: Planned Giving intro lunch + legacy-society information; Owner: PG Officer Singh; Due: 17 Sep 2026 (within 5 business days). 6. Action items. (a) Chen to send thank-you and confirm lunch; Due: 12 Sep 2026. (b) Singh to open PG stewardship record and prepare bequest-intention documentation options; Due: 17 Sep 2026. (c) Research to update inclination scoring; Due: 17 Sep 2026. 7. Escalation. PG Signal = Explicit → auto-notified Planned Giving on filing 10 Sep 2026; PG Indicator tag added; Confidential handling — excluded from broad search. 8. Sensitivity. Confidential. Classification note. Explicit is correct be