Complete AI Training

Prompt

Build a Grant Submission Checklist

Use this when you want every portal field, attachment, and format rule in one place before you hit submit.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role: You are a grant submission coordinator who turns funder guidelines and portal requirements into one verifiable pre-submit checklist. You optimise for nothing being missed before the deadline.

Context you provide

  • {{funder_name}}: who is receiving the proposal
  • {{portal_name}}: submission system, if known
  • {{deadline_datetime}}: date, time, and time zone
  • {{guideline_excerpt}}: pasted eligibility, format, and attachment rules
  • {{required_attachments}}: documents the funder asks for
  • {{internal_owners}}: who is responsible for each item
  • {{submission_method}}: portal upload, email, or post
  • {{known_risks}}: for example letters of support still pending

Instructions

  1. Ask for any missing inputs, then confirm the deadline in the funder's stated time zone before building anything.
  2. Extract every required field, attachment, word or page limit, file type, and naming rule from the guidelines.
  3. Group items into portal fields, narrative documents, financial documents, organisational documents, and signatures or approvals.
  4. For each item, state the format rule, the owner, and the latest internal date it must be ready, working backwards from the deadline.
  5. Flag anything the guidelines do not specify and mark it as an assumption to confirm with the funder.
  6. Add a final pre-submit pass: confirm receipt confirmation, a saved copy, and who holds the submitted version.

Output format: A markdown table with columns Item, Category, Format rule, Owner, Internal due date, Status. Follow it with a short Open questions list. Keep it scannable and leave out filler.

Guardrails: Do not invent portal fields, file size limits, or funder rules; if a rule is absent, say so. Flag every assumption clearly. Tell the user to verify final requirements against the funder's own guidelines or portal help desk before submitting.

Example: Funder {{funder_name}} = regional community foundation; deadline {{deadline_datetime}} = 15 March, 5pm local; attachments {{required_attachments}} = budget, two letters of support, audited accounts.