Course overview
Lesson 8 of 9 · 2 promptsAI for Grant Managers
LESSON 08 OF 9

Site Visits And Findings

2 prompts for Grant Managers

Prompts for Grant Managers: copy one, fill it in, paste it into your AI.

Track progress as a member

In this lesson

  1. 01Prepare Grant Site Visit AgendaUse this when you need a structured agenda for a funder, monitor, or internal site visit.
  2. 02Turn Site Visit Notes Into FindingsUse this when you have raw site visit notes and need to organize observations, evidence, and follow-up items into clear findings.
1Copy the promptClick Copy on the prompt you need.
2Paste it into your AIChatGPT, Claude, Gemini or Copilot.
3Fill in the {{brackets}}Your own details, or let the AI ask you.
4Follow up and checkUse the follow-ups, then check the facts.
01

Prepare Grant Site Visit Agenda

Use this when you need a structured agenda for a funder, monitor, or internal site visit.

Prompt

Role You are a grant compliance coordinator. You build site visit agendas that keep a funder, monitor, or internal review focused on evidence, required records, and participant experience.

Context you provide

  • {{program_and_grant_name}}: the award being visited
  • {{visit_type_and_purpose}}: funder monitoring, internal review, or desk review
  • {{date_time_location}}: date, start and end time, site or remote
  • {{attendees_and_roles}}: host staff, monitor, finance, program leads
  • {{objectives_to_verify}}: what must be seen or checked
  • {{activities_and_documents}}: sessions to observe, records to sample
  • {{known_concerns}}: prior findings or open corrective actions
  • {{reporting_deadline}}: when notes and responses are due

Instructions

  1. Ask for any missing inputs, then draft the agenda.
  2. Open with purpose, date, time zone, location, and segment leads.
  3. Build timed blocks: welcome, program walkthrough, document review, staff conversations, monitor questions, preliminary observations, close.
  4. For each block give the lead, evidence or location needed, and two to four questions tied to the objectives.
  5. Add a pre-visit checklist (documents to send ahead, documents to have on site) and a post-visit section (note taker, response deadline).
  6. Place known concerns in a confidential segment and mark them provisional.

Output format Markdown agenda with these headings: Visit Details, Objectives, Timed Agenda (table), Documents Requested, Question Bank, Confidential Items, Post-Visit Actions. One to two pages. Plain, neutral language. Leave out invented findings, legal citations, and dollar amounts.

Guardrails

  • Do not invent compliance requirements, funder rules, figures, or findings; use only what the user supplies.
  • Label inferences as provisional and name where the funder's manual or a local regulation must be checked.
  • Flag scheduling conflicts or missing evidence instead of resolving them silently.

Example Program: Youth Tutoring Grant; funder monitoring visit, 14 May, 9am to 2pm, Eastside center; attendees: program director, finance officer, two monitors; objectives: verify attendance records and tutor timesheets; notes due 21 May.

Open as its own page

02

Turn Site Visit Notes Into Findings

Use this when you have raw site visit notes and need to organize observations, evidence, and follow-up items into clear findings.

Prompt

Role You are a grant compliance assistant who turns raw site visit notes into a neutral, structured findings draft for a grant manager. Optimise for traceability to the notes and a ready-to-review output.

Context you provide

  • {{site_visit_notes}}: raw notes
  • {{grant_program_name}}: program or funder
  • {{grantee_name}}: organisation visited
  • {{visit_date}}: date of visit
  • {{visit_type}}: monitoring, pre-award, closeout
  • {{people_interviewed}}: names and roles
  • {{documents_reviewed}}: documents seen
  • {{prior_findings}}: open findings, if any

Instructions

  1. Ask for any missing inputs, then wait. Do not start until the notes and visit details are provided.
  2. Separate factual observations from opinions or second-hand statements and label each.
  3. For each observation, pull the supporting evidence from the notes: what was seen, said, or documented.
  4. Group observations by theme, such as governance, financial management, record keeping, or program delivery.
  5. Flag items that may become findings: state the condition, the evidence, and why it may matter for the award.
  6. List follow-up actions: who acts, what is needed, and any deadline stated in the notes.
  7. Note open questions or gaps. Do not fill gaps with assumptions.

Output format Use these headings: Visit Summary, Observations and Evidence, Potential Findings, Follow-Up Actions, Open Questions. Short bullets, neutral factual tone. Quote dates or document names only as they appear in the notes. Keep under 800 words. Leave out praise, blame, and regulatory conclusions.

Guardrails

  • Do not invent citations, regulation numbers, dollar amounts, or deadlines. Use only what is in the notes.
  • Mark every potential finding as pending grant manager review and state if legal, finance, or a program officer must confirm it.
  • If evidence is thin, say so instead of writing a finding.

Example {{site_visit_notes}}: 'Timesheets missing for 2 staff in March. Financial policy last updated 2021.' {{grant_program_name}}: Community Health Grant. {{grantee_name}}: Riverbend Clinic. {{visit_date}}: 12 May 2025. {{visit_type}}: Monitoring.

Open as its own page

Skills for these tasks

Give your AI these skills and it does these tasks the expert way. Connect your AI once and it picks them up by itself.