A grant or sponsorship packet for a portable planetarium program should help a funder, administrator, PTA, library, museum, or community partner understand the program clearly enough to ask good questions. It should not invent funding availability, eligibility, award likelihood, tax treatment, sponsor value, purchasing rules, or private budget details.
This checklist is a general planning workflow. Prices, quotes, funder requirements, school approval steps, legal questions, tax questions, insurance needs, purchasing procedures, public-performance rights, accessibility needs, and final approval decisions should come from the operator, host organization, funder, school, venue, insurer, producer, accountant, attorney, qualified advisor, or direct submitted evidence.
What A Funding Packet Can Safely Explain
Describe the program purpose, audience served, grade bands or age ranges, subject areas, visit format, host responsibilities, and the decision questions a sponsor or administrator may need answered.
Keep the language descriptive. Do not promise learning outcomes, funding approval, sponsor visibility, repeat bookings, public impact, community results, or financial return unless a specific approved source supports that claim.
Materials To Gather Before Asking
A useful packet can gather a plain program description, show or topic menu, general setup needs, host preparation checklist, follow-up material examples, operator contact route, and a place for the operator’s current quote or proposal.
Keep private quotes, invoices, student data, donor conversations, school approval chains, budget records, tax identifiers, internal emails, and contact details out of public examples.
- Program summary and audience served.
- Grade band, subject area, or community-program fit.
- General visit format and host role.
- Current quote, invoice, or proposal kept in the private workflow.
- Links to booking, preparation, follow-up, and feedback materials.
- Questions that still need confirmation from the operator, host, funder, or advisor.
Questions Funders Or Administrators May Ask
Funding conversations often need clear answers about who is served, what subject areas are covered, where the visit happens, what the host provides, what permissions or licensing questions require confirmation, and who approves payment.
Frame these as prompts to confirm, not universal requirements. One school, funder, operator, venue, or sponsor practice should not become a public PortaDome rule.
What Not To Put In A Public Example
Do not publish private financial records, donor names, tax IDs, school approval chains, student information, medical or accessibility details, internal messages, contracts, unapproved quotes, contact details, payment details, or security procedures.
Do not list grants, sponsors, deadlines, award amounts, eligibility rules, application requirements, procurement rules, or tax treatment unless those details come from a current source and belong in that specific private or sourced context.
Use The Packet Without Overclaiming
Operators and hosts can adapt the packet into a private funding request, sponsor conversation, administrator memo, PTA discussion, library program pitch, museum education proposal, or community-partner handoff.
The packet should make the decision easier to review. It should not imply that PortaDome can find, qualify, approve, guarantee, broker, or legally structure funding.
Turn Repeated Funding Questions Into Better Planning
Repeated funding questions can inform future Operator Toolkit worksheets, Dome Guide articles, Dispatch topics, outreach follow-ups, and private demand-signal notes.
Label any repeated question by source type and context. Until approved analytics or counters exist, do not present uninstrumented funding questions, search behavior, form activity, or outreach replies as measured market demand.
Useful PortaDome Companions
Pair this checklist with the Operator Toolkit, pricing guide, school booking package guide, marketing-to-schools guide, host booking FAQ, booking confirmation checklist, follow-up materials checklist, and audience question and feedback checklist.