Seasonal parks supervisors need the same volunteer-onboarding structure in Copilot each year. What should the parks lead do?
Select an answer to reveal the explanation.
Short Explanation
New seasonal bosses, same onboarding shape—share the prompt. It’s like handing every summer supervisor the same volunteer checklist instead of making them sketch a new one.
Full Explanation
Seasonal parks supervisors who need the same volunteer-onboarding structure in Copilot each year should receive a shared volunteer-onboarding prompt so they can reuse the same structure. Sharing preserves a standard onboarding skeleton—welcome language, training checklist order, safety expectations, timekeeping pointers, and contact paths—across rotating seasonal supervisors. That reduces reinvented onboarding copy every summer and keeps volunteer experience consistent across parks sites.
Forcing each supervisor to invent a completely different onboarding prompt every summer fails standardization and multiplies uneven volunteer communications. Deleting the onboarding prompt at the start of each season before anyone can open it removes the asset precisely when seasonal supervisors need it. Publishing volunteer home addresses inside the shared prompt for faster personalization fails privacy; home addresses are sensitive personal data and do not belong embedded in a shared prompt body for “personalization.”
Exam caveat: a shared onboarding prompt standardizes structure, not the automatic inclusion of volunteer PII. Personalize from authorized roster systems at run time under policy, and update the prompt when risk/safety modules change. Sharing should target seasonal supervisor roles, not the general public.
Operational check: before season start, share the prompt to seasonal supervisor accounts, generate one sample onboarding packet, scrub any address fields from the prompt body, and have the parks lead sign off that the structure matches the current volunteer handbook.