Animal control needs a recurring prompt-driven briefing for emergency ops leadership each morning. Which prompt capability should the admin use?

Animal control should schedule the recurring prompt-driven briefing so emergency ops leadership receives it on a set cadence. Prompt management includes scheduling so approved prompt-driven outputs can run repeatedly without depending on someone remembering to execute the prompt each morning. For municipal emergency operations, a scheduled briefing pattern is how leadership gets consistent situational summaries on time.

Scheduling the briefing prompt template review so leadership receives it on a set cadence fails by concept: it schedules governance review of the template and does not deliver the recurring briefing itself to leadership on a set cadence. Scheduling the briefing team agent workflow so leadership receives it on a set cadence fails because a team agent workflow is separate automation and scheduling it does not deliver the required prompt-driven morning briefing to leadership. Scheduling the briefing prompt approval so leadership receives it on a set cadence fails because it schedules an approval step rather than delivering a fixed morning briefing cadence to leadership.

Exam caveat: AB-900 Domain 3 expects recognition of scheduling prompts as part of managing prompts. Scheduling is distinct from merely saving or sharing a prompt; it addresses recurrence. Do not treat scheduling a prompt template review, scheduling a team agent workflow, or scheduling a prompt approval as substitutes for the scheduling concept.

Operational check: Confirm the briefing prompt is vetted for animal-control emergency content, configure the schedule for the required morning cadence and audience, validate one successful run before relying on it for leadership, monitor failures or empty outputs, and update or pause the schedule when the underlying data sources or on-call roster changes.