Prompt Tier Quick Reference
| Tier | When to Use | Key Feature | Review Required |
|---|---|---|---|
| Fast Draft | Internal docs, brainstorming, low-stakes drafts | Speed; output is a first draft | Staff reviews before use |
| High-Accuracy | Applicant-facing, donor-facing communications | Includes verify/flag instructions | Staff verifies all facts and tone |
| Governed Workflow | Policy docs, award decisions, equity-sensitive content | Human review step + audit trail note + consent check | Supervisor or committee sign-off |
Platform-agnostic: All prompts work in ChatGPT, Claude, Gemini, Copilot, BoodleBox, and similar tools. | No PII rule: Never paste applicant names, SSNs, or identifiable data into any prompt.
CAT 01
Applicant Outreach & Recruitment
Prompts 1–1001
▾
Use case: First-generation students who may have limited familiarity with formal scholarship applications.
PROMPT — FAST DRAFT
You are a scholarship program communications specialist writing for first-generation college students who may have limited experience with formal applications. Write a 150-word program announcement for [program name] that: states eligibility in the first sentence, names the award amount and deadline, lists exactly 3 steps to apply, and ends with one sentence of encouragement. Use plain language (8th-grade reading level). No jargon.
02
▾
Use case: Build a FAQ that answers what first-generation, rural, or underrepresented applicants actually need to know before applying.
PROMPT — GOVERNED WORKFLOW
You are a scholarship program coordinator. Write a 10-question FAQ for [program name] that answers the questions a first-generation, rural, or underrepresented applicant is most likely to have before applying. For each question, write a plain-language answer under 50 words. Flag any answer that assumes applicants have prior knowledge of financial aid processes so staff can revise.
03
▾
Use case: Email to prospective applicants from a list of eligible students who have not yet started an application.
PROMPT — FAST DRAFT
Write a 120-word recruitment email for [program name] targeting [eligible population, e.g., community college transfer students in STEM]. The email should: open with one sentence about the student's situation (not the organization), state the award and deadline in sentence two, list three reasons this scholarship fits them specifically, and close with a single call to action. Tone: warm, direct, not institutional.
04
▾
Use case: SMS reminders to applicants who opted in to text updates from your program.
PROMPT — FAST DRAFT
Write 3 SMS-length reminders (under 160 characters each) for the [program name] application deadline of [date]. Each message should vary in angle: (1) deadline urgency, (2) amount of award, (3) ease of applying. Include a shortened URL placeholder [link]. No emoji unless they add meaning.
05
▾
Use case: Short descriptions that school counselors, community orgs, or social media followers can use to share your program without extra editing.
PROMPT — FAST DRAFT
Write 5 versions of a one-sentence description of [program name] that a teacher, counselor, or community organization could use to introduce our scholarship to students. Each version should be under 25 words, lead with student benefit (not organization name), and be accurate to these details: [eligibility, award, deadline].
06
▾
Use case: Help applicants self-screen before they invest time starting an application they may not complete.
PROMPT — GOVERNED WORKFLOW
Write a 6-question self-screening checklist that prospective applicants for [program name] can use to determine if they are eligible before starting the application. Each question should be answerable yes/no. After the checklist, write a 2-sentence "if you answered yes to all 6" next step and a 2-sentence "if you answered no to any" referral message. Base eligibility on: [paste eligibility criteria — no student names or PII].
07
▾
Use case: Reach skeptical parents and guardians who filter out generic scholarship promotions.
PROMPT — FAST DRAFT
Write a 180-word scholarship announcement for parents and guardians of [eligible students, e.g., graduating high school seniors in Texas]. Assume the parent is skeptical of scholarships and worried about scams. Lead with legitimacy markers (organization name, years in operation, contact info). State the award, deadline, and application steps. Close with a direct invitation to ask questions. Tone: trustworthy, not salesy.
08
▾
Use case: Reach Spanish-speaking applicants and families with a natural, accurate translation — not a literal one.
PROMPT — GOVERNED WORKFLOW
Write a 100-word bilingual scholarship announcement for [program name] — first in English, then in Spanish. The Spanish version should be a natural translation, not a literal word-for-word translation. Content: eligibility, award amount, deadline, how to apply, contact. Flag any terms that may not translate cleanly so staff can review with a native speaker before publishing.
Required: Native Spanish speaker must review before any publication. AI translation may contain errors or culturally inappropriate phrasing.
Governed — native speaker review required
09
▾
Use case: Re-engage applicants who started but haven't submitted — without pressure or shame.
PROMPT — FAST DRAFT
You are a scholarship coordinator who wants applicants to succeed. Write a 200-word email to students who have started but not submitted their [program name] application. The email should: acknowledge the application takes effort, provide 3 specific tips to strengthen their submission, remind them of the deadline, and offer a contact for help. Do not pressure or shame. Tone: coaching, supportive.
10
▾
Use case: Give your designer or Canva template the exact copy for a recruitment flyer — concise and accurate.
PROMPT — FAST DRAFT
Write the copy for a recruitment flyer for [program name]. Include: headline (8 words max), one-sentence description, award amount, eligibility in 3 bullets, deadline, how to apply (URL and/or QR code placeholder), and contact information. All text should fit in under 100 words total. No filler phrases like "Don't miss this opportunity."
CAT 02
School & Counselor Partner Outreach
Prompts 11–2011
▾
Use case: Cold outreach to school counselors who receive dozens of scholarship announcements weekly.
PROMPT — FAST DRAFT
You are a high school counselor with 300 students who forwards only scholarships that take under 60 seconds to evaluate. Write an outreach email FROM [program name] TO counselors. Include: who is eligible (sentence 1), award and deadline (sentence 2), what to do (3 action options), a copyable "forward to students" blurb in quotes, and staff contact. Max 150 words total.
12
▾
Use case: A print-ready or PDF document counselors can keep on file and share with students year after year.
PROMPT — FAST DRAFT
Write a one-page program overview for high school counselors promoting [program name]. Sections: Program Summary (50 words), Eligibility at a Glance (bullet list), Award Details, Application Timeline, How to Nominate or Refer Students, FAQs (3 most common counselor questions with answers), Contact. Tone: professional, peer-to-peer. Avoid language that talks down to counselors.
13
▾
Use case: Ask a principal to formally support your scholarship program at their school.
PROMPT — FAST DRAFT
Write a 200-word letter to high school principals asking them to designate [program name] as an official school-supported scholarship. Cover: program legitimacy, student benefit, what the school is asked to do (minimal ask), and what support we provide (flyers, presentations, application help). Close with a specific next step (reply, schedule a call, sign a simple MOU). No fundraising language.
14
▾
Use case: Introduce your program to TRIO, Upward Bound, and college access staff who work directly with first-gen students.
PROMPT — FAST DRAFT
Write a 150-word brief for college access coordinators and TRIO/Upward Bound staff introducing [program name]. Emphasize: alignment with first-gen and low-income student populations, what the scholarship covers, how to refer students, and what support students receive beyond the award (if applicable). Include a table with: Eligibility Criteria | Award | Deadline | Application Link | Staff Contact.
15
▾
Use case: Submit a short blurb to a school district newsletter or counselor association digest.
PROMPT — FAST DRAFT
Write a 75-word scholarship spotlight for a school district counselor newsletter about [program name]. Format: 1 sentence on who it's for, 1 sentence on the award, 1 sentence on the deadline and how to apply, 1 sentence inviting counselors to contact us. Include a URL. Professional tone, no superlatives.
16
▾
Use case: Steward school partnerships with an annual thank-you noting aggregate referrals — no student names.
PROMPT — FAST DRAFT
Write a 150-word thank-you letter from [program name] to a partner high school that referred [X] applicants this cycle. Acknowledge the school's role, name the number of students who applied (no names), note any who received awards (no names), and invite continued partnership. Warm but professional. No placeholder names — write the letter so staff can fill in specifics.
17
▾
Use case: Invite a school or community org to host a 30-minute info session — make the ask easy to say yes to.
PROMPT — FAST DRAFT
Write an email inviting a high school or community organization to host a 30-minute scholarship information session for [program name]. Include: what the session covers, what we provide (presenter, slides, flyers), what the host needs to provide (a room and 10+ students), how to schedule, and contact. Under 150 words. Make the ask easy to say yes to.
18
▾
Use case: Reach transfer students via community college financial aid offices and transfer centers.
PROMPT — FAST DRAFT
Write a 150-word outreach message to community college financial aid offices and transfer centers promoting [program name] for transfer students. State eligibility clearly (GPA, enrollment status, major if applicable). Explain the application process. Note any specific supports for transfer students. Include a referral link and staff contact. Tone: collegial and efficient.
19
▾
Use case: Stay top-of-mind between application cycles without a hard ask.
PROMPT — FAST DRAFT
Write a 100-word mid-year check-in email from [program name] staff to high school counselors we partnered with last year. Purpose: stay top-of-mind before the new application cycle opens. Include: a brief note of appreciation, one upcoming date to remember, an offer to provide updated materials, and a question that invites a response. No hard sell. Tone: relationship-first.
20
▾
Use case: Re-engage returning partner schools with a recap of outcomes and a simple renewal ask.
PROMPT — FAST DRAFT
Write a one-page partnership renewal summary for schools that partnered with [program name] last year. Include: recap of outcomes (use placeholders for numbers), what's new this cycle, what the school is asked to do, what we provide in return, and a simple sign-off or confirmation step. Professional, concise, under 300 words.
CAT 03
Donor Communications & Stewardship
Prompts 21–3021
▾
Use case: Annual report narrative section for donors — aggregate data only, no individual student information.
PROMPT — HIGH-ACCURACY
You are a nonprofit communications writer. Write a 300-word narrative for [program name]'s annual donor impact report. Cover: number of scholars supported, aggregate outcomes (graduation rates, fields of study, career paths — no PII), one composite scholar story (clearly labeled as composite), and what donor funding made possible. Tone: grateful, evidence-based, not sentimental. Flag any stat placeholder for staff to verify before publishing.
Required: All statistics must be verified against actual program data before publishing. Composite stories must be labeled as such in the final document.
High-Accuracy — verify all data before publishing
22
▾
Use case: Personalized thank-you for a $500–$2,500 gift. Staff adds specific donor name and fund details.
PROMPT — FAST DRAFT
Write a 200-word thank-you letter from [program name] to a donor who gave [gift amount or range, e.g., $500–$2,500]. Personalize to the donor's named fund or scholarship if applicable. Include: what the gift funds specifically, a brief aggregate scholar outcome (no student names), and an invitation to stay connected. Avoid clichés like "your gift makes a difference." Be specific.
23
▾
Use case: Annual update to a named scholarship fund donor — aggregate outcomes, consented quotes only.
PROMPT — HIGH-ACCURACY
Write a 250-word annual stewardship email to a named scholarship fund donor for [program name]. Include: number of scholars awarded from their fund this cycle, aggregate academic outcomes (no individual PII), one invited scholar quote (placeholder for consented quote), upcoming cycle dates, and a direct staff contact for questions. Professional, warm, specific.
24
▾
Use case: Reach out to donors who gave 2–3 years ago with a soft reconnect — no guilt, no hard ask.
PROMPT — FAST DRAFT
Write a 150-word re-engagement email to a donor who gave to [program name] 2–3 years ago but has not given since. Do not guilt-trip. Acknowledge their past support, share one concrete program update, and issue a soft invitation to reconnect (reply to this email, visit the site, consider a gift this cycle). Close with a specific staff name and contact. Tone: low-pressure.
25
▾
Use case: First contact with a corporate prospect — must be specific and honest about what the program offers.
PROMPT — HIGH-ACCURACY
You are writing on behalf of [program name]. Write a 180-word partnership letter to a company in [industry] that aligns with our student population. Open with one sentence connecting the company's CSR goals to our mission. State: the sponsorship ask, what it funds, the student population served (aggregate, no names), visibility/recognition opportunities, and a clear next step. Flag: "The following company-specific claims should be verified before sending: [list assumed facts]."
Required: Verify all company-specific claims before sending. AI may assume facts about the company that are incorrect.
High-Accuracy — verify company facts before sending
26
▾
Use case: Retain a first-year corporate sponsor with a results-oriented renewal ask.
PROMPT — FAST DRAFT
Write a 200-word renewal letter from [program name] to a corporate sponsor completing their first year of partnership. Include: what their funding supported (specific outcomes, no PII), what's new in the coming cycle, the renewal ask with specifics, and a named staff contact to discuss. Professional, concise. No filler. Make renewing easy.
27
▾
Use case: December giving appeal — honest about the funding need, no manufactured urgency.
PROMPT — FAST DRAFT
Write a 200-word year-end giving appeal for [program name] targeting individual donors. Open with one concrete outcome from this year (aggregate, no student names). State the funding need for the upcoming cycle. Include a clear donation ask with a specific amount suggestion and deadline. One call to action (donation link placeholder). Honest tone — no manufactured urgency.
28
▾
Use case: Introduce a major donor prospect to the opportunity to establish a named fund.
PROMPT — HIGH-ACCURACY
Write a 250-word letter to a prospective major donor about the opportunity to establish a named scholarship fund with [program name]. Cover: what a named fund is, the minimum commitment, how scholars are selected, how the donor is acknowledged, and how to take the next step. No pressure language. Include a placeholder for gift officer name and contact.
29
▾
Use case: Quarterly touchpoint for donors — brief, specific, not a fundraising ask.
PROMPT — FAST DRAFT
Write a 250-word quarterly donor newsletter for [program name]. Sections: Program Update (what happened this quarter, aggregate data), Scholar Spotlight (placeholder for consented story or composite vignette labeled as such), Upcoming Cycle Dates, and How to Help (share, give, refer). Professional but warm. Under 300 words total.
30
▾
Use case: Post-grant stewardship letter to a foundation funder — transparent about outcomes and challenges.
PROMPT — HIGH-ACCURACY
Write a 300-word thank-you and outcome letter to a foundation that awarded [program name] a grant of [amount] for [purpose]. Include: how the grant was used, measurable outcomes achieved (use placeholders staff will fill in), any challenges encountered and how they were addressed, and a statement about impact going forward. Tone: accountable, transparent, professional.
CAT 04
Social Media
Prompts 31–4031
▾
Use case: Launch day posts across LinkedIn, Instagram, and Facebook — tailored to each platform's audience.
PROMPT — FAST DRAFT
Write opening-day posts for [program name]'s application window across 3 platforms. Platform 1 (LinkedIn): 100-word professional announcement, eligibility in the first sentence. Platform 2 (Instagram): 50-word caption with a clear CTA and 5 relevant hashtags (no trending tags unless verified relevant). Platform 3 (Facebook): 80-word post optimized for sharing by school counselors and parents. No student names or photos in any prompt output. Include link placeholder.
32
▾
Use case: Celebrate award recipients while protecting student privacy — consent must be confirmed before any post.
PROMPT — GOVERNED WORKFLOW
Write a template for celebrating scholarship award recipients on social media that protects student privacy. Provide: a version that uses only first name + field of study (consented), a version that uses no names but describes the cohort in aggregate, and a version for sharing a consented student quote without identifying details. Each version under 75 words. Include a note reminding staff to confirm consent before posting.
Required: Written consent from student before using any identifying information (name, photo, institution, field of study) in public posts.
Governed — written student consent required
33
▾
Use case: A ready-to-schedule countdown series from 3 weeks out to deadline day.
PROMPT — FAST DRAFT
Write a 5-post deadline countdown series for [program name] with the final deadline of [date]. Posts should be spaced: 3 weeks out, 2 weeks out, 1 week out, 3 days out, day-of. Each post: under 60 words, single CTA, one specific fact about the program (award amount, eligibility, outcome stat), application link placeholder. Vary tone across posts — do not repeat the same language.
34
▾
Use case: Address the top reasons eligible students self-screen out before applying.
PROMPT — FAST DRAFT
Write 3 social media posts for [program name] that address common applicant misconceptions. Myth 1: "This scholarship is only for students with perfect grades." Myth 2: "The application takes too long." Myth 3: "I won't qualify because of [common eligibility misunderstanding — staff to specify]." Each post: state the myth, correct it in 2 sentences, include a CTA. Under 70 words each.
35
▾
Use case: Invite scholars to share their story — with explicit consent framing built in.
PROMPT — GOVERNED WORKFLOW
Write a social media post asking current or past scholars to share why they applied to [program name]. Frame it as an invitation for user-generated content. Include: what to share (their story, 2–3 sentences), where to share it (tag us, use hashtag [placeholder]), and a note that selected stories may be featured (with permission). Under 80 words. Tone: inviting, not pressuring.
36
▾
Use case: Celebrate a program milestone — let real numbers do the work, no superlatives needed.
PROMPT — FAST DRAFT
Write a social media post celebrating [program name]'s [X]-year anniversary. Include: years in operation, total scholars served (aggregate), one sentence of mission statement, and a forward-looking statement. Under 100 words. Avoid superlatives. Do not fabricate statistics — leave placeholders for staff to verify numbers.
37
▾
Use case: Public thank-you to the donor community — collective appreciation, no individual names unless staff adds them.
PROMPT — FAST DRAFT
Write a donor appreciation social media post for [program name] that can be used on LinkedIn and Facebook. Do not name individual donors unless staff adds names manually. Acknowledge the donor community collectively, state what their support funded (aggregate data), and invite others to join. Under 100 words. Professional tone, not gushing.
38
▾
Use case: LinkedIn post recruiting new board members — specific about skills needed and time commitment.
PROMPT — FAST DRAFT
Write a LinkedIn post recruiting new board members for [program name]. State: what the board does, who we are looking for (skills, not demographics), time commitment, how to express interest. Under 120 words. Direct, no jargon. Avoid phrases like "passionate about education."
39
▾
Use case: Three audience-specific posts for the annual scholarship ceremony — scholars, donors, and the public.
PROMPT — FAST DRAFT
Write social media posts promoting the annual [program name] scholarship ceremony for 3 audiences: (1) scholars and families (warm, celebratory, 60 words), (2) donors and sponsors (recognition-focused, professional, 80 words), (3) general public and community partners (mission-focused, inviting, 70 words). Include event date, location, and RSVP link placeholder in each. No student names.
40
▾
Use case: Caption for an annual data graphic with aggregate program stats.
PROMPT — FAST DRAFT
Write a caption for a year-in-review data graphic for [program name]. The graphic contains: number of applications received, number of awards, total dollars awarded, and number of schools represented. Caption should: contextualize the numbers, thank the community, and point to next year's cycle. Under 100 words. Include hashtag placeholder and link placeholder.
CAT 05
Email Campaigns
Prompts 41–5041
▾
Use case: First email a newly selected scholar receives — practical, warm, sets clear expectations.
PROMPT — FAST DRAFT
Write a 200-word welcome email from [program name] to a newly selected scholar (no name in the output — staff will personalize). Cover: congratulations (1 sentence), what happens next (3 steps), what the scholar can expect from us, and who to contact with questions. Warm but not effusive. Practical.
42
▾
Use case: Honest, compassionate communication to applicants placed on a waitlist.
PROMPT — HIGH-ACCURACY
Write a 150-word waitlist notification email for [program name] applicants. Be honest about their status, explain how the waitlist works, state a timeline for updates, and invite them to reapply next cycle if applicable. No false hope. Compassionate but clear. Staff will personalize name and date fields.
43
▾
Use case: Automated or manual confirmation that an application was received — reassuring without overclaiming.
PROMPT — FAST DRAFT
Write a 120-word application confirmation email for [program name]. Confirm receipt, state the review timeline, list 1–2 things the applicant may be asked to provide later (interview, additional docs), and give a contact for questions. Tone: efficient, reassuring. No inflated language about the applicant's "amazing" submission.
44
▾
Use case: Rejection letter that is honest, compassionate, and constructive — one of the hardest emails to get right.
PROMPT — GOVERNED WORKFLOW
Write a compassionate, professional declination email for [program name] for applicants who were not selected. Include: appreciation for applying (specific to their effort, not generic), an honest brief reason if policy allows (or a note that feedback is unavailable), encouragement to reapply, and 2 other scholarship resources to explore. Under 180 words. Staff must review before sending. Do not imply the student did anything wrong.
Required: Program director reviews every declination email batch before sending. Check language equity across the cohort.
Governed — director review required before sending
45
▾
Use case: Clear, practical reminder of what returning scholars need to do to renew their award.
PROMPT — FAST DRAFT
Write a 150-word renewal reminder email for a returning scholar at [program name]. State: what is required to renew, the deadline, how to submit, who to contact if they have questions, and a brief encouraging note. Matter-of-fact tone. Include placeholders for GPA requirement and deadline date.
46
▾
Use case: Stay connected with current scholars mid-semester — mentoring, not monitoring.
PROMPT — FAST DRAFT
Write a 150-word mid-semester check-in email from [program name] staff to active scholars. Purpose: maintain relationship, surface any challenges early. Include: a brief update from the program, 2 questions asking how things are going, an offer to connect, and upcoming program dates. Tone: mentoring, not monitoring.
47
▾
Use case: Advance a finalist to the interview stage without overpromising selection outcomes.
PROMPT — FAST DRAFT
Write a 150-word email inviting a [program name] finalist to an interview. Include: congratulations on advancing, interview format (virtual/in-person), date and time placeholder, what to prepare (brief, not overwhelming), who to contact to reschedule if needed, and a word of encouragement. Professional, warm. No over-promising about selection outcomes.
48
▾
Use case: Thank volunteer reviewers after a cycle — specific about what they contributed.
PROMPT — FAST DRAFT
Write a 150-word thank-you email from [program name] to volunteer application reviewers after a review cycle. Thank them for their time, briefly note the outcome of the cycle (aggregate: number reviewed, number selected), invite them to participate next year, and note when they can expect any follow-up communication. Specific, genuine, brief.
49
▾
Use case: Reconnect with program alumni who have been inactive — relationship first, no donation ask.
PROMPT — FAST DRAFT
Write a 200-word email to [program name] alumni who have not been engaged in the past 2+ years. Purpose: reconnect, not fundraise. Share one program update, ask one question about their life since graduating, and offer one way to stay involved (mentoring, speaking, social media follow). No donation ask. Tone: peer-to-peer, not institutional.
50
▾
Use case: One prompt generates three audience-tailored versions of the cycle-launch announcement.
PROMPT — FAST DRAFT
Write an email campaign launch message for [program name]'s application opening. Version A (for prospective applicants): 120 words, application link, key dates, one reason to apply now. Version B (for school partners): 100 words, asking counselors to share with eligible students, referral toolkit link placeholder. Version C (for donors): 80 words, note that the cycle is open, invite them to share with their networks. All three in one output.
CAT 06
Website & FAQ Content
Prompts 51–6051
▾Use case: Student-benefit-first headline and subhead for a scholarship program website.
PROMPT — FAST DRAFT
Write homepage hero copy for [program name]'s website. Deliverables: H1 headline (8 words max, student-benefit focused), H2 subheadline (1 sentence, includes award and eligibility hint), one CTA button label (4 words max), and a 30-word intro paragraph. No organization-centric language in the H1. Optimize for clarity over creativity.
52
▾Use case: The "About" page that introduces your program to a prospective applicant in 30 seconds.
PROMPT — FAST DRAFT
Write a 250-word "About" page for [program name]. Cover: mission (1 sentence), who is served (specific population), what the award includes, how scholars are selected (briefly), history or founding story (1 sentence), and a closing sentence that invites prospective applicants to apply. No jargon. Use second person ("you") for applicant-facing sections.53
▾Use case: The single most-visited page on a scholarship website — must be accurate, scannable, and AI-answer-ready.
PROMPT — GOVERNED WORKFLOW
Write the eligibility page for [program name]'s website. Format: one introductory sentence, a Yes/No checklist of 6–8 eligibility requirements, a "Not sure if you qualify?" section with a contact prompt, and a note about re-application for those who don't currently qualify. Based on: [paste eligibility criteria — no student data]. Optimize for position-zero AI answer retrieval.
Required: Legal or program director verifies all eligibility criteria before publishing. Errors here have the highest impact on applicants.
Governed — accuracy-critical; director sign-off required54
▾Use case: A comprehensive FAQ written from the applicant's perspective — not the organization's.
PROMPT — FAST DRAFT
Write a 10-question FAQ page for [program name] applicants. Questions must come from the applicant's perspective, not the organization's. Cover: eligibility edge cases, application process, timeline, selection criteria, what happens after selection, renewal requirements, and contact. Each answer: under 60 words, plain language, specific. No vague answers like "it depends."
55
▾Use case: Build trust by being transparent about how selection works — without creating unrealistic expectations.
PROMPT — GOVERNED WORKFLOW
Write a 200-word "How We Select Scholars" page for [program name]'s website. Cover: who reviews applications, what the criteria are (no rubric scores), how bias is managed (briefly), timeline from close to notification, and what applicants can and cannot expect during review. Transparent, trust-building tone. Avoid language that implies subjective preference without explanation.
56
▾Use case: Clear expectations for returning scholars about what they need to maintain their award.
PROMPT — FAST DRAFT
Write a clear, scannable renewal requirements page for [program name] scholars. Include: GPA minimum, enrollment status, required check-ins or reporting, deadline for renewal application, and what happens if a scholar is at risk of losing eligibility. Format: bullet list + short explanatory paragraph. Under 200 words. Tone: informative, not threatening.
57
▾Use case: A contact page that routes inquiries to the right person quickly — applicants, donors, media, and partners.
PROMPT — FAST DRAFT
Write the contact page copy for [program name]'s website. Include: who to contact for what (applicant inquiries, donor inquiries, school partnerships, media), response time expectations, a brief FAQ link for common questions, and accessibility note (TTY/relay if applicable). Under 150 words. Make it easy to find the right person quickly.
58
▾Use case: A description optimized to be quoted accurately by AI tools like ChatGPT, Perplexity, and Google AI Overviews.
PROMPT — GOVERNED WORKFLOW
Write a 150-word program description for [program name] optimized for AI answer engines (GEO format). Lead with the most common question: "What is [program name]?" Answer it in the first sentence. Include: award amount, eligibility, deadline, and how to apply in the first paragraph. Use simple declarative sentences. Avoid passive voice. This text will be indexed and may be quoted by AI assistants.
59
▾Use case: A scannable dates page that applicants and counselors can reference quickly.
PROMPT — FAST DRAFT
Write a "Key Dates" web page for [program name]'s application cycle. Format: a simple table or timeline with: Application Opens, Application Closes, Review Period, Notification Date, Acceptance Deadline, Award Disbursement. Below the table, write a 50-word note about late applications (accepted or not) and who to contact with timeline questions. Clean, scannable, no filler.
60
▾Use case: Build a scholar stories section that protects student privacy by design — consent infrastructure built in.
PROMPT — GOVERNED WORKFLOW
Write a template for a "Scholar Stories" page on [program name]'s website that protects student privacy by design. Include: a template for stories using first name and major only (with explicit note that student consent is required), a composite vignette format (labeled "Representative Scholar Story"), and a 50-word note about how stories are collected and how students can opt out. The template, not an actual story.
Required: Written consent form must be completed before any student story is published. Include opt-out instructions on every story.
Governed — consent-critical; legal review recommended
CAT 07
Scholar Engagement & Retention
Prompts 61–7061
▾Use case: A reusable newsletter structure that staff can fill in monthly — designed for mobile reading.
PROMPT — FAST DRAFT
Write a monthly newsletter template for current [program name] scholars. Sections: Personal opening (2 sentences, staff to customize), Scholar Spotlight (placeholder for consented story), Upcoming Deadlines (table format), Resource of the Month, and Warm Closing with staff contact. Under 220 words. Design for mobile reading. Do not assume scholars check email daily.
62
▾Use case: Invite scholars to a workshop or career event — frame as opportunity, not obligation.
PROMPT — FAST DRAFT
Write a 150-word email inviting [program name] scholars to a professional development event or workshop (e.g., resume workshop, networking session, career panel). Include: what the event covers, why it's valuable, date/time/location placeholder, RSVP link placeholder, and what to bring or prepare. Tone: opportunity-focused, not mandatory.
63
▾Use case: Connect current scholars with alumni mentors — specific about time commitment and opt-in framing.
PROMPT — FAST DRAFT
Write a 150-word email inviting a current [program name] scholar to participate in a peer or alumni mentorship program. Cover: what the program involves (time commitment, format), what the scholar gains, how to sign up, and who to contact with questions. Tone: inviting, no pressure. Under 150 words.
64
▾Use case: Get genuine feedback from scholars — be honest about time and use of responses.
PROMPT — FAST DRAFT
Write a 100-word email inviting [program name] scholars to complete an end-of-year program survey. State: why their feedback matters (specific), how long it takes (be honest), the deadline, and what happens with their responses. Include a note that responses are confidential. No incentive language unless staff adds one. Tone: respectful of their time.
65
▾Use case: A proactive wellbeing check-in with resources — not reactive to a specific incident.
PROMPT — GOVERNED WORKFLOW
Write a brief, sensitive email from [program name] to scholars acknowledging that academic life is stressful and that the program cares about their wellbeing. List 3–4 campus or national support resources (use placeholders for specific school resources). Note that the program staff is also available to talk. Do not be alarmist or presumptuous. Under 150 words. Staff must review before sending.
Required: Staff or student services professional reviews before sending. Do not send following a critical incident without additional guidance.
Governed — wellbeing professional reviews before sending66
▾Use case: Mark a scholar's graduation as a relationship milestone — no donation ask in this touchpoint.
PROMPT — FAST DRAFT
Write a 150-word congratulatory email to a [program name] scholar who is graduating. Acknowledge their completion (1 sentence), thank them for representing the program, invite them to stay connected as an alum, and share one way they can give back (speaking, mentoring — no donation ask in this touchpoint). Warm, not formulaic.
67
▾Use case: Sensitive outreach to a scholar who may not meet renewal requirements — supportive, not punitive.
PROMPT — GOVERNED WORKFLOW
Write a 150-word check-in email to a [program name] scholar who may be at risk of not meeting renewal requirements. Tone: supportive, not punitive. Ask how they are doing, name the requirement (GPA or enrollment) without accusation, offer a conversation to discuss options, and include a deadline for resolving the issue. Staff must review and personalize before sending.
Required: Staff personalizes and reviews each email individually. Do not batch-send this type of communication.
Governed — individual staff review before each send68
▾Use case: Invite the current scholar cohort to a low-stakes social or networking event.
PROMPT — FAST DRAFT
Write a 120-word email inviting [program name] scholars to a cohort community event (virtual or in-person). Cover: what the event is (format, not just a name), who will be there, what scholars can expect to gain from attending, and RSVP link/deadline placeholder. Tone: social, low-stakes, no performance pressure.
69
▾Use case: Ask a scholar for permission to feature their story — explicit about what will be shared and how to decline.
PROMPT — GOVERNED WORKFLOW
Write an email asking a [program name] scholar for permission to feature their story on social media. Be explicit about: what will be shared (major, institution, quote — no home address, no family details), where it will be posted, how they can review it before publication, and how to decline without consequence. Include a simple consent confirmation step. Under 150 words.
Required: Obtain written or email confirmation of consent before posting any student story. Keep consent records on file.
Governed — written consent required before publishing70
▾Use case: Brief acknowledgment when an alum shares a career win — relationship maintenance, no ask.
PROMPT — FAST DRAFT
Write a brief congratulatory email to a [program name] alum who has shared a career milestone (new job, promotion, degree). Acknowledge the milestone specifically, connect it briefly to their scholar journey, and invite them to share their story with current scholars if they are willing. No ask. Under 100 words. Tone: proud, peer-level.
CAT 08
Event Promotion
Prompts 71–8071
▾Use case: Three formats of the same save-the-date for different delivery channels.
PROMPT — FAST DRAFT
Write three versions of a save-the-date announcement for [program name]'s annual scholarship ceremony: (1) Email format, 80 words, for scholars and families. (2) Social media caption, 60 words, for public announcement. (3) Text/SMS version, under 160 characters, for scholars. All include: event name, date, location/format placeholder, and RSVP link placeholder. No student names.
72
▾Use case: Sell tables or seats to corporate sponsors at the annual ceremony — value proposition must be clear.
PROMPT — FAST DRAFT
Write a 180-word letter inviting a corporate sponsor to purchase a table or seats at [program name]'s annual scholarship ceremony. Cover: event overview, who attends, visibility/recognition included, pricing placeholder, and RSVP or commitment deadline. Professional, specific, no soft-focus language. Make the value proposition clear.
73
▾Use case: The narrative sections of a ceremony program booklet — placeholder structure for staff to populate.
PROMPT — FAST DRAFT
Write the narrative sections for [program name]'s scholarship ceremony program booklet. Sections: Welcome from Executive Director (100 words, mission-forward), About the Scholars (aggregate: number, fields, schools — no names without consent), Donor Acknowledgments page (template for listing names/organizations), and Closing Statement (50 words, forward-looking). Staff will insert actual names and data.
74
▾Use case: Warm close-the-loop email for all event attendees — brief, specific, one forward action.
PROMPT — FAST DRAFT
Write a 150-word post-ceremony thank-you email from [program name] to all attendees (scholars, families, donors, guests). Thank them for attending, share one highlight from the event (placeholder for staff to add), include a link to event photos if available (placeholder), and invite them to stay connected. Warm, brief, specific.
75
▾Use case: Pre-event logistics email for scholars and families attending a virtual event — non-technical language.
PROMPT — FAST DRAFT
Write a 150-word logistics email for [program name] scholars and families attending a virtual event. Include: Zoom/platform link placeholder, how to test their audio/video in advance, what to expect (agenda overview, 3 bullets), who to contact if they have technical issues, and a note about recording. Accessible and non-technical language.
76
▾Use case: Build anticipation with scholarship recipient families ahead of the ceremony.
PROMPT — FAST DRAFT
Write a 150-word email to the families of [program name] scholarship recipients in advance of the award ceremony. Acknowledge their role in the scholar's journey (briefly, not saccharine), share what to expect at the event, provide logistics details (placeholders), and note how proud the program is of the scholar. Do not use family member names.
77
▾Use case: Close the loop with sponsors after a ceremony — evidence-based, brief, relationship-building.
PROMPT — FAST DRAFT
Write a 150-word post-event recap email from [program name] to corporate sponsors. Cover: event highlights (aggregate attendance, number of scholars recognized), visibility delivered to the sponsor (mentions, table presence — placeholders), a thank-you, and a note about next year's cycle. Professional, evidence-based, brief.
78
▾Use case: Invite a speaker or panelist — specific about time commitment and topic.
PROMPT — FAST DRAFT
Write a 180-word email inviting a professional (donor, alumni, or community leader) to speak or sit on a panel at [program name]'s upcoming event. State: the event, the audience, the topic or question you want them to address, the time commitment (specific), any compensation or recognition offered, and a clear yes/no response deadline. No flattery beyond one sentence.
79
▾Use case: Structured debrief template staff completes after every major event — captures what worked and what to improve.
PROMPT — FAST DRAFT
Write an internal event debrief summary template for [program name] staff after a scholarship ceremony or program event. Sections: Attendance (planned vs. actual), Highlights (3 bullets), What Worked, What to Improve, Donor/Partner Feedback (placeholder), Follow-Up Actions (table: Action | Owner | Deadline). Staff will complete the content; this is the structural template.
80
▾Use case: Formal save-the-date for major donors and board members — mission-driven, not generic event marketing.
PROMPT — FAST DRAFT
Write a 120-word save-the-date for [program name]'s annual gala targeted at major donors and board members. Tone: formal but mission-driven. Include: event date and venue placeholder, a one-sentence "why this matters" hook, RSVP deadline placeholder, and a named staff contact. No general public language — this version is for high-relationship contacts.
CAT 09
Board & Governance Reporting
Prompts 81–9081
▾Use case: Quarterly board report narrative — data-forward, no spin, includes decision requests.
PROMPT — HIGH-ACCURACY
Write a 250-word board report narrative for [program name]'s quarterly meeting. Cover: applications received vs. last cycle (placeholder for data), selection outcomes, any equity flags identified in this cycle's applicant pool (process-level, no individual data), staff capacity notes, and 1–2 decisions the board is being asked to make. Professional, data-forward, no spin. Staff must verify all numbers before submitting.
82
▾Use case: Draft a board-level AI use policy — establishes what staff may and may not do with AI tools.
PROMPT — GOVERNED WORKFLOW
Write a one-page AI Use Policy for [program name] for board review and approval. Sections: Purpose, Scope (what tasks AI may assist with), Permitted Uses, Prohibited Uses (include: no individual student data in AI prompts, no AI-only decisions on awards), Human Oversight Requirements, Staff Responsibilities, and Review Cadence. Tone: governance-level, precise. This is a draft; board should treat it as such.
Required: Legal counsel reviews before board adoption. This prompt produces a starting draft only.
Governed — legal review before board adoption83
▾Use case: Concise executive summary for board members who need the essentials in 5 minutes.
PROMPT — HIGH-ACCURACY
Write a 300-word executive summary of [program name]'s annual report for board members. Cover: program performance vs. stated goals (placeholder for data), financial summary (placeholder), strategic priorities met, risks and how they were mitigated, and 3 priorities for the next fiscal year. Concise, strategic, honest. No puffery.
84
▾Use case: One-page brief for a new initiative being brought to the board for discussion or approval.
PROMPT — FAST DRAFT
Write a board meeting agenda item brief for a proposed new initiative at [program name] (e.g., adding a mentoring component, expanding eligibility). Format: Background (50 words), Proposed Change (50 words), Why Now (30 words), Financial Implication (placeholder), Equity Consideration (30 words), Staff Recommendation (1 sentence), Board Action Requested (approve / discuss / table). Under 250 words total.
85
▾Use case: Attract the right board candidates with a candid, skills-focused recruitment document.
PROMPT — FAST DRAFT
Write a one-page board recruitment description for [program name]. Include: organization overview (50 words), board role and responsibilities (bullet list), skills and expertise sought (specific list — avoid "passionate about"), time commitment (meetings per year, expected prep time), term length, how to apply or express interest, and staff contact. Professional, candid about commitment level.
86
▾Use case: Board-level risk assessment template for AI and data use — staff assesses likelihood and mitigation.
PROMPT — GOVERNED WORKFLOW
Write a board-level risk summary (1 page) for [program name] covering AI and data use risks. Risk categories: Student Data Privacy, Algorithmic Bias in Application Review, Staff AI Skill Gap, Vendor Reliability, and Reputational Risk. For each: 1-sentence risk description, likelihood (High/Medium/Low — staff to assess), current mitigation, and recommended action. Format: table. Staff completes the assessment; this is the template.
87
▾Use case: Stewardship section for the board report — retention data and recommended board outreach actions.
PROMPT — FAST DRAFT
Write a 150-word donor stewardship section for [program name]'s board report. Cover: number of active named funds, total donor households, retention rate vs. prior year (placeholder), any lapsed major donors flagged for board awareness (no names in this draft — staff adds), and recommended board member outreach actions. Data-driven, governance-appropriate tone.
88
▾Use case: Honest mid-year update on strategic plan — on track, at risk, achieved — no false positivity.
PROMPT — HIGH-ACCURACY
Write a mid-year strategic plan progress update for [program name] board. Format: Goal | Status (On Track / At Risk / Achieved) | Brief Note. Cover 4–6 goals (placeholders — staff inserts actual goals). After the table, write a 50-word narrative note on the most significant risk to plan completion. Honest, no false positivity.
89
▾Use case: Welcome packet narrative for a new board member — practical, clear, covers the first 90 days.
PROMPT — FAST DRAFT
Write a 300-word orientation briefing document for a new [program name] board member. Cover: program overview, current scholar cohort (aggregate), governance structure, top 3 strategic priorities, the board's current ask for this year, key staff contacts, and the most important thing to know in the first 90 days. Clear, welcoming, practical.
90
▾Use case: General compliance orientation note for new board members — always verified by legal counsel.
PROMPT — GOVERNED WORKFLOW
Write a 150-word board brief on key compliance considerations for [program name]'s scholarship program (non-legal advice; for orientation purposes). Cover: IRS requirements for scholarship programs (scholarship vs. taxable grant distinction), FERPA considerations for student data, and state-level scholarship tax considerations (generic — staff must verify with legal counsel). Flag clearly: "This is a general orientation note. Consult legal counsel for specific guidance."
Required: Legal counsel reviews before distribution. This prompt produces an orientation overview, not legal advice.
Governed — legal review before any distribution
CAT 10
Internal Operations & Workflow
Prompts 91–10091
▾Use case: Onboard volunteer reviewers at the start of a cycle — equity reminders built in.
PROMPT — FAST DRAFT
Write a 200-word orientation email from [program name] to volunteer application reviewers at the start of a new review cycle. Cover: review timeline, rubric summary (2–3 dimensions, no detailed scoring), equity reminders (watch for language fluency bias, zip code bias, school-type bias), how to flag concerns, and who to contact with questions. Tone: collegial, not condescending.
92
▾Use case: Help new reviewers understand the scoring rubric — with bias risk callouts for each dimension.
PROMPT — FAST DRAFT
Write a plain-language explainer for [program name]'s application scoring rubric for new reviewers. Take these rubric dimensions (staff inserts actual dimensions) and for each: write a 2-sentence explanation of what the dimension measures, one example of a "strong" indicator, one example of a "weak" indicator, and one common bias risk to watch for. Do not fabricate rubric criteria — use only what staff provides.
93
▾Use case: AI-assisted first-pass triage of anonymized application responses — staff reads originals before any decision.
PROMPT — GOVERNED WORKFLOW
You are a scholarship program reviewer. The following application response has been provided by staff [staff pastes anonymized response with all PII removed]. Summarize this response in 3–4 bullet points covering: main theme, demonstrated need or context (if present), stated goals, and any information gaps that would require follow-up. This summary is a triage aid only. Staff must read the original before making any selection decision. Flag any statement you are uncertain about with "[VERIFY]".
Required: All PII (name, address, school, ID numbers) must be removed before pasting any application text into this prompt. Staff reads the original before any selection decision is made.
Governed — PII removal + human final review mandatory94
▾Use case: Reusable meeting summary structure — AI generates the draft, staff verifies against actual notes.
PROMPT — FAST DRAFT
Write a template for [program name] staff to use when generating AI-assisted meeting summaries. The template should include: Meeting Name, Date, Attendees (placeholder), Agenda Items (table), Key Decisions Made, Action Items (Action | Owner | Deadline table), Open Questions Carried Forward, and Next Meeting Date. The output is a first draft — staff must verify against actual notes before distributing.
95
▾Use case: Draft an equitable, accurate job description — avoid coded language before posting.
PROMPT — GOVERNED WORKFLOW
Write a job description for a Scholarship Program Coordinator at [program name]. Include: job summary (50 words), key responsibilities (8–10 bullets, specific), required qualifications (skills and experience, not degrees unless genuinely required), preferred qualifications, compensation range placeholder, and application instructions. Avoid coded language that may screen out qualified diverse candidates. Staff must review for equity and accuracy before posting.
Required: HR or DEI review before posting. AI may reproduce language patterns that screen out diverse candidates.
Governed — HR/DEI review before posting96
▾Use case: A plain-language staff agreement covering what AI may and may not be used for — building a culture of responsible use.
PROMPT — GOVERNED WORKFLOW
Write a 1-page staff AI use agreement for [program name] employees. Cover: approved uses (drafting, summarizing, scheduling), prohibited uses (student PII in prompts, final award decisions without human review), required disclosures (when to note AI assistance in internal documents), escalation process for uncertain cases, and acknowledgment signature line. Plain language, under 400 words total.
97
▾Use case: Generate instructions for a data cleanup task — no actual donor data goes into the prompt.
PROMPT — FAST DRAFT
I have a donor contact list with inconsistent formatting (mixed case names, missing titles, duplicate entries). Write a step-by-step instruction set I can give to a data entry assistant or use with a spreadsheet tool to: standardize name capitalization, flag likely duplicates, identify records with missing email or phone, and export a "needs review" list. Do not process actual donor data — produce the instructions only.
98
▾Use case: Structured process documentation template for the annual review cycle — staff fills in specifics.
PROMPT — FAST DRAFT
Write a process documentation template for [program name]'s annual application review cycle. Sections: Pre-Review Preparation (checklist), Reviewer Assignment Process, Scoring and Calibration Protocol, Conflict of Interest Procedure, Escalation Steps for Edge Cases, Final Selection Meeting Format, Notification Timeline, and Post-Cycle Audit. Staff will fill in specifics. Format: numbered steps under each section. Under 500 words total for the template structure.
99
▾Use case: Post-cycle equity review — 20-item checklist that surfaces representation and process fairness issues.
PROMPT — GOVERNED WORKFLOW
Write a 20-item equity audit checklist for [program name] to use after each application cycle. Cover: applicant pool demographics vs. eligible population, outreach channel reach, language access, school-type representation, selection rate by subgroup (aggregate), reviewer calibration consistency, essay prompt language review, appeal/complaint process, and documentation completeness. Format: Yes / No / Needs Review for each item. Staff uses this as a post-cycle quality tool, not a compliance form.
Required: This checklist uses aggregate data only. Do not track individual applicants by demographic category in the audit — only cohort-level patterns.
Governed — program director reviews audit findings100
▾Use case: End-of-year staff retrospective — 10 open-ended questions for a 60-minute team session.
PROMPT — FAST DRAFT
You are facilitating an end-of-year retrospective for [program name] staff. Generate 10 discussion questions for a 60-minute team session covering: what worked in the application cycle, what created friction, where AI tools helped, where human review caught AI errors, equity concerns that surfaced, and what to change next cycle. Questions should be open-ended, specific to scholarship operations, and safe for honest answers. Do not generate answers — generate questions only.