Use it when the project changes between meetings
This responsibility fits a project with named sources, multiple owners and a need to detect changed deadlines, unanswered decisions or conflicting status—not a project that exists mostly in undocumented conversations.
Have ready
- One authoritative task board or project plan.
- The exact collaboration channel or document in scope.
- A known project end date and working time zone.
- The person who can resolve owners, deadlines and commitments.
Stop & check
- A connected channel does not automatically create an event monitor.
- Private context may inform work but is not permission to disclose it.
- A dot-generated register does not replace the authoritative project record.
Copy the project brief
Choose either a fixed review schedule or a supported event trigger. Ask the dot to confirm what it actually saved.
Responsibility: Keep the [project name] decision and deadline register current through [end date]. Approved sources: - [project plan or task board] - [specific Slack/Teams channel, if connected] - [specific project folder or document] Check [schedule] and, where the connected service supports it, watch for [specific event]. Confirm whether the event can actually trigger work; do not assume that connecting a channel creates monitoring. Maintain these fields: decision, owner, due date, current source, status, blocker, and last verified time. Do not invent an owner or deadline. Mark conflicts and missing information as unresolved. Notify me only when a deadline within [number] working days is at risk, two approved sources conflict, an owner is missing, or a decision requires my judgment. Keep routine changes in the register. Draft reminders for my review, but do not send or post them. Do not change owners, deadlines, task status, files, permissions, budgets, or commitments without my explicit approval. Before starting, restate the approved sources, trigger or schedule, notification threshold, end date, delivery location, and actions that require approval.
Require a source-backed register
| Field | Acceptable entry | Reject or flag |
|---|---|---|
| Owner | A named owner supported by the project source | “The team” or an inferred owner |
| Deadline | Date, time zone and source reference | A date copied from an older conflicting message |
| Status | Current state plus last verified time | A confident status with no source |
| Blocker | Specific dependency and decision needed | Vague risk language without a next step |
When approved sources disagree, preserve both references and ask for a decision. Do not silently choose the latest-looking statement.
Actions that remain human decisions
- Changing a deadline, owner, project status or budget.
- Posting a reminder or status update to a team channel.
- Sharing information from a private conversation with a broader audience.
- Editing, moving or deleting a shared document or project record.
Check one sample from each source
If the register drifts
- Reduce the source set to the authoritative project record and one collaboration channel.
- Replace broad monitoring with a fixed schedule until the trigger can be confirmed.
- Require explicit “unknown” values instead of inferred owners or dates.
- Pause the main task, then inspect delegated tasks and Scheduled separately.
How this page was produced
We translated OpenAI's documented schedule, supported-event, context and control model into a project register with narrower disclosure and approval rules. We did not reproduce an authenticated project run, so the page remains Guidance only.
Reviewed October 8, 2026. Connected services differ in supported events and actions. Ask the dot to confirm the trigger it saved and verify consequential information in the project system of record.