Commitment Follow-up Tracking

Track promises made in meetings and threads, schedule reminders, chase owners, and publish the weekly list of what is still open.

When to use

After a meeting or email thread produces action items with owners and due dates that must not be forgotten.
When a stakeholder needs a recurring digest of outstanding commitments instead of hunting through old threads.
When an owner has gone quiet on a commitment and needs a polite nudge before the deadline.
When leadership asks "what's still open" and needs a clean, current list rather than a manual audit.

When a commitment is captured (from a meeting note, email, or conversation), record it with update-memory, storing owner, description, due date, and source.
Create a trackable item for it with create-task, assigning the owner and due date so it appears on the board.
Set a tickler using schedule-task to run a check a few days before the due date, and another at the due date itself, so follow-up is never missed.
When a tickler fires and the commitment is still open, notify the owner with send-message, referencing the original commitment and its due date.
If the owner does not respond after a nudge, escalate with a second send-message to the owner's manager or the requester, flagging the risk of a missed deadline.
On the scheduled weekly cadence (set up once via schedule-task), pull all open commitments from memory and tasks, and compile them into a single open-loop list grouped by owner and due date.
Send the weekly open-loop list via send-message to the stakeholder who requested visibility, calling out anything overdue at the top.
When a commitment is fulfilled, update its record via update-memory and close the corresponding task so it drops off the next digest.
If a commitment involves booking travel or making a payment, do not execute it — record it via update-memory, create the task, and note in the send-message handoff that a human must complete the booking or payment.

A commitment is captured without a due date, so it never triggers a tickler; always require a due date before scheduling, and if none was given, ask the requester for one.
Nudges become naggy: if a send-message reminder produces no response after two attempts, escalate once and then stop, rather than repeating indefinitely.
Commitments in update-memory and tasks in create-task drift out of sync; always update both together when status changes.

Every captured commitment has an owner, due date, and an active tickler schedule via schedule-task.
The weekly open-loop list has been sent via send-message and reflects the current state of memory and tasks.
Fulfilled commitments are closed out in both update-memory and the task board.