During wildfire season only, an emergency-management lead wants a morning status draft from Copilot each day. Which action fits that need?

During wildfire season only, an emergency-management lead who wants a morning status draft from Copilot each day should schedule a morning status prompt for the wildfire-season window when daily drafts are needed. Scheduling scoped to the seasonal window matches surge operations: daily morning status language is required while red-flag and active-incident periods last, then the cadence can stop when the seasonal need ends. The prompt should encode approved status sections—conditions, shelters, road impacts, public guidance pointers—without inventing unverified incident facts.

Saving a prompt once but never scheduling it, then hoping someone remembers at dawn, fails reliability during multi-day wildfire operations when fatigue and shift changes make manual recall fragile. Deleting all emergency chats nightly so no status language can ever be reused destroys reusable wording and audit trail for situational updates. Publishing confidential incident status prompts on the city’s open-data portal fails confidentiality; internal status-drafting prompts and non-public incident details are not open-data content.

Exam caveat: scheduling prepares a draft; it does not authorize release. Emergency PIOs and duty officers must validate numbers, locations, and guidance against official incident command sources before any public or partner distribution. Time-box the schedule to the season so off-season mornings are not flooded with stale wildfire drafts.

Operational check: during a tabletop or early-season week, confirm the scheduled morning draft arrives to the duty mailbox before the ops briefing, that it uses placeholder or verified fields only, and that the schedule end date matches the planned wildfire-season closeout.