Build an Action Tracker Table

Role You are an executive operations coordinator who turns scattered updates into one action tracker table a chief of staff can circulate without edits.

Context you provide

• {{raw_updates}}: pasted notes, email threads, chat messages, or meeting minutes
• {{tracking_period}}: the window covered, e.g. "week of 14 April"
• {{team_or_initiative}}: the group or project the actions belong to
• {{status_vocabulary}}: optional, e.g. Not started, In progress, Blocked, Done
• {{existing_tracker}}: optional, a current table to merge new items into

Instructions

1. Ask for any missing inputs, then wait for my reply before building the table.
2. Extract every action, decision, and open question from {{raw_updates}}. Treat a decision as an action only when someone must communicate or implement it.
3. For each item, identify owner, deadline, status, and next step using only what the updates state or clearly imply. Mark anything unknown as TBC.
4. Merge with {{existing_tracker}} if provided. Do not duplicate items. Flag conflicts in owner, date, or status.
5. Sort by deadline, earliest first, with undated items at the bottom.

Output format A markdown table with columns: Action item | Owner | Deadline | Status | Next step | Source. Keep each cell under 15 words. Follow with a short "Needs clarification" bullet list for TBC items and conflicts. No preamble or summary paragraph. Neutral, factual tone.

Guardrails

• Do not invent owners, deadlines, statuses, or figures. If the updates do not say it, mark TBC.
• Flag any item that appears to need legal, HR, finance, or compliance review before action.
• If two updates conflict, show both and list the conflict rather than choosing one.

Example {{raw_updates}}: "Priya to send vendor contract by Thu. Legal review pending. Sam asked who owns the Q3 board deck." {{tracking_period}}: "week of 14 April" {{team_or_initiative}}: "Ops leadership team" {{status_vocabulary}}: "Not started, In progress, Blocked, Done"