A parks planner has a full existing event plan and needs a sponsor one-pager. What should they ask Copilot to do?
Select an answer to reveal the explanation.
Short Explanation
Sponsors want a tight one-pager, not the whole event binder—point Copilot at the existing plan and ask for an audience-specific handout. Keep internal bid details out of that flyer.
Full Explanation
Parks sponsorship outreach needs a concise, audience-specific handout—not the full internal event binder. With a complete existing event plan, the planner should ask Copilot to generate a sponsor one-pager tailored from that plan: public event facts, sponsorship tiers that are already approved, and benefits that appear in the source. That workflow demonstrates grounded repurposing for a new external audience while keeping staffing rosters, vendor bid prices, and other internal details out of the sponsor packet.
Sending sponsors the entire internal staffing roster and vendor bid prices unchanged fails confidentiality and procurement norms; internal cost and personnel data are not sponsor marketing content. Fabricating attendance guarantees that do not appear in the event plan fails accuracy and can create contractual or reputational exposure if sponsors rely on invented numbers. Asking Copilot to replace the event plan with a blank document before drafting removes the grounding source and invites unsupported claims.
Exam caveat: when the stem contrasts a full internal plan with a short sponsor one-pager, the correct move is tailored generation from the existing plan—not dumping internals, inventing guarantees, or wiping the source.
Operational check: point Copilot at the approved event plan, request a one-page sponsor brief limited to public facts and approved tiers, exclude roster/bid fields, have parks leadership review attendance language against documented estimates, then export for sponsor outreach with the plan version noted.