Biz Prompt KitSubmit a use case ↗
← All playbooks
Dots: ongoing work / Editorial adaptation

Catch changed deadlines in a planning channel

Review a defined channel and show which job dates or commitments need an owner's decision.

OpenAI dotsIntermediateOriginal editorial guide

What you’ll produce

A proposed checklist update and a short exception report with message links.

Inputs & connections

  • One approved planning channel and the current project checklist
  • Check frequency, time zone, end date and notification thresholds

A supported connected messaging service and access to the named checklist. Ask the dot to confirm whether scheduling or the requested event monitoring is supported.

Your starting prompt

Replace the bracketed fields. This is our suggested prompt, not a quote from the source.

Review [planning channel] against [project checklist] for changes to agreed deadlines and owners. Cite the exact message behind each proposed change and distinguish a suggestion from a confirmed decision. Prepare a read-only trial report first. Ask for approval before editing the checklist, messaging anyone or activating [schedule, time zone and end date]. Once approved, confirm what was saved and report only meaningful deadline risks, failed checks or decisions that need me.
Open OpenAI dots ↗

How to run it

  1. 01

    Name the exact channel, checklist and changes to watch for.

  2. 02

    Run a trial comparison and review the proposed updates.

  3. 03

    Approve a supported schedule and any limited checklist writes explicitly.

  4. 04

    Confirm the saved settings and inspect the first scheduled result for missed or repeated changes.

KEEP A PERSON IN THE LOOP

Review before you act

Verify that a changed deadline was agreed by the relevant owner and that the schedule uses the intended time zone.

Limitations & success checks

  • Connecting a channel alone does not start monitoring.
  • Event support depends on the connected service; unsupported triggers must not be presented as active.

Measure: Confirmed deadline changes detected, false alerts and checklist updates that need correction.

Sources & attribution

The sources below support the reported example or a tool capability. They do not validate our prompt or prove the outcome in your environment.

Official documentationTasks and memory ↗

Documents saved schedules, supported event monitoring and a planning-channel checklist example. Our trial-report and approval sequence is an editorial adaptation.

Creator / publisher: OpenAI

Editorial review: 2026-10-17. How we label evidence.

FROM A USE CASE TO A WORKING SYSTEM

Have a workflow worth building?

Bring a workflow and the tools your team already uses. Ferociter can help scope the project and build the system.

Talk through your project ↗