TaskbyTask.Practical AI guides for work
ChatGPT, Claude, Gemini or Copilot · Practical walkthrough

Find the latest agreed decision across meetings and Slack

The call notes say Friday, a Slack thread says Monday, and the launch plan, edited an hour ago, says Wednesday. Before the team plans around any of them, find out which one somebody with authority actually agreed.

Task by Task16 min read + practice
A reviewer compares a clipped current notebook page with a loose proposal while earlier pages remain visible in a fan.

What you'll make

the current agreed position on one decision, with a short source-linked history and a clarification question if one is still needed.

What you'll need

ChatGPT, Claude, Gemini or Copilot in your work account; the relevant meeting notes, complete Slack reply chains and document versions, pasted or attached; a cutoff time; and the name of the person who can agree this decision. Allow fifteen minutes.

Example result.

Current (as of 17 Nov, 16:00 GMT): distributor price list due Monday 23 November.
Proposal: Nadia, #pricing, 17 Nov 11:10. Acceptance: Sam (commercial manager), 11:25.
Superseded: 19 November (original); 20 November (agreed 16 Nov, replaced 17 Nov).
Unresolved: Jo's suggestion of 25 November, 11:40. No acceptance.
Conflict: launch plan DRAFT (edited 13:30) says 25 November; marked unapproved.

1. Name the decision you want to settle

Choose one precise question: the due date for a named deliverable, the agreed reporting frequency, the scope approved for a project. “What happened with the launch?” mixes separate decisions, and the broader the question, the more likely a decision from an adjacent project arrives wearing your project’s clothes.

Gather the passages that set the earlier position, the proposed changes, the replies and any conflicting documents. Keep recognisable names (“Planning call, 16 November”, “Launch plan draft, edited 17 November”) with their dates and status. Include enough surrounding replies to see what each “yes” refers to, and label any summary or missing message as such.

Write down who can agree this decision and how you know. A senior title, repetition or silence doesn’t establish agreement. Then set the cutoff, with a timezone.

Why this works: one decision, one approver and one cutoff give the assistant a question with a checkable answer.

What you should see: a one-line question, the approver’s name, a cutoff and a labelled set of sources.

2. Ask for the current position and its history

Find the latest agreed position on [decision] in these sources, up to [cutoff]. The person who can agree it is [approver].

First state the current position and cite the proposal and the acceptance. If the evidence isn't enough, say what's missing. Then give a short history: earlier positions, accepted replacements, later suggestions nobody accepted, and conflicting documents. Keep any conditions.

Label each position current, superseded, disputed or unresolved. A newer draft, repetition or silence does not replace an agreement. Keep the date a decision was made separate from the date a document was last edited. Cite source names and locations, and flag any source that looks incomplete. Draft one clarification question if needed.

SOURCES:
[sources]

[decision] is your question from step 1; [cutoff] includes the timezone; [approver] is the person and the basis for their authority (or “unknown”); [sources] is the labelled text or attached files.

Why this works: asking for the proposal and the acceptance catches the commonest error, treating “Could we move it?” as “We moved it”. The history makes the conclusion checkable rather than a bare date.

What you should see: one current position with two citations, then a short dated history with a status on each line.

3. Check the chain in both directions

Open the proposal and acceptance the answer cites. Check the deliverable, the date, any conditions and the accepting person’s authority. Then look backwards: does this acceptance replace the earlier decision, or a different deliverable with a similar name?

Look forwards too. Was there a later accepted change before the cutoff? A recently edited file may copy old content or carry a suggestion nobody agreed. If a source is missing, narrow the answer: “latest accepted position in the material we could read” is more honest than “the final decision”.

Why this works: a current position only holds if nothing earlier contradicts it and nothing later replaces it.

What you should see: the cited acceptance confirmed in the original message, and no later accepted change you missed.

4. Resolve what’s left

If a conflict remains, ask the approver a question that names the sources:

The [dated meeting or message] agrees [position], but [document and version] says [different position]. Is that document out of date, or is there a later approved change? Please point me to the confirmation.

Check the recipient and wording before you send it. Keep the reply as a new dated source and update the history without deleting the previous agreement. A current deadline doesn’t tell you the work is done.

Why this works: naming both sources lets the approver answer in one line instead of reconstructing the thread.

What you should see: a short message ready to send, and later a dated answer you can add to the history.

Check the result

  • The current position cites both a proposal and an acceptance by the named approver.
  • No suggestion, draft or repeated mention is labelled current.
  • Every superseded position names the acceptance that replaced it.
  • Dates of decisions and dates of document edits aren’t mixed up.

The usual failure: the newest source wins. A draft edited after the last agreement, or a later suggestion, becomes “the agreed date” because it’s most recent. Spot it when the cited source for the current position is a document rather than a reply from the approver.

Recheck the claimed change from [earlier position] to [later position]. Show the proposal and the explicit acceptance, their dates and who accepted. If any part is missing, correct the status and keep the last supported agreement separately. Do not treat the newest document, repeated wording or silence as approval.

[earlier position] and [later position] are the two dates or decisions the answer linked.

Worked example: four dates, one agreement

Fictional example. Sam, the commercial manager, can agree the deadline for Nadia’s updated distributor price list. The cutoff is 17 November 2026 at 16:00 GMT.

Planning call notes, 16 November:
10:05 Nadia: I'll send the updated distributor price list by Thursday 19 November.
10:20 Nadia: I need to move that to Friday 20 November. OK?
10:22 Sam: Yes, Friday 20 November is fine for the price list.

Stand-up, 17 November, 09:00 GMT:
Sam: the price list is due Friday 20 November.

#pricing thread, 17 November, GMT:
11:10 Nadia: Can I send it Monday 23 November instead? Supplier figures arrive Friday afternoon.
11:25 Sam: Agreed, Monday 23 November.
11:40 Jo: Could we push it to Wednesday 25 November so finance can check?
(No further replies before the cutoff.)

Launch plan DRAFT, edited 17 November 13:30 GMT:
Distributor price list: 25 November. Status: draft, not approved.

The first answer said: “The latest agreed date is 25 November, per the launch plan updated at 13:30.”

  • The failure. The newest source won. The launch plan is a draft, and 25 November is Jo’s suggestion, which nobody with authority accepted.
  • The repair. The repair prompt, from 23 November to 25 November, found Jo’s proposal but no acceptance. It relabelled 25 November as unresolved, kept 23 November as current (Sam, 11:25) and flagged the draft as a conflict, giving the example result at the top of this page.
  • The counterfactual. Remove Sam’s 11:25 reply and the move to 23 November isn’t established. The last supported agreement is 20 November, with an open proposal. That’s the difference between checking a chain and choosing an attractive answer.

The clarification for Sam names the launch plan draft and the 11:25 reply, so Sam can answer without reading the whole thread.

Try it

Task by Task.Explore the example

Recency does not outrank acceptance

Select each event to see which date is agreed at the cutoff.

  1. Planning call
  2. 16 Nov 10:22
  3. 17 Nov 11:25
  4. 17 Nov 11:40
  5. 17 Nov 13:30

Superseded when Sam accepted the move to 20 November.

Cutoff 17 November, 16:00 GMT. The agreed date is 23 November; 25 November is still a proposal.

Task by Task · Illustrative example

Task kit for this job: Download (ZIP) · Reusable instructions

Go deeper

Optional training: Build a ledger for several decisions

When several issues are moving at once, a ledger keeps them apart.

Build a decision ledger from these sources for [named issues]. For each show: earlier position; later evidence; who proposed; who accepted; their authority; current status; source locations; conditions; missing confirmation. Mark an agreement superseded only when you can cite its accepted replacement. Keep later proposals and conflicting drafts separate. Do not count mentions as votes. State the cutoff and which sources you could read.

Read supersession in both directions: does this acceptance replace this decision, or is a later mention only describing history? Has an exception been mistaken for a new rule? Those questions do more work than asking the AI to “double-check everything”.

Optional training: Find the passages with Slack search or a connector

If your workspace is on Slack Business+ or Enterprise+, a question typed into the Slack search bar returns an AI answer at the top of the results, with citations to the messages behind it. It only uses messages you can already see. Treat it as a way to find the thread, then open the full replies and run the checks above; a search answer can quote the suggestion and miss the acceptance.

For pulling meeting transcripts and threads into an assistant through connections, see Prepare a useful brief before a project meeting and Turn a meeting and Slack replies into a useful follow-up.

Optional training: Keep the history useful over time

When new evidence arrives, identify the affected decision, check who agreed it and rerun only those rows. Keep the previous version and the reason for the change. If authority is still unclear, ask the person responsible rather than asking another model to break the tie.

Email chains work with the same pasted-text method: keep dates, senders, quoted-history boundaries and the acceptance itself. A history that shows who agreed what, when, saves the team from reopening settled work.

Sources

Optional analytics

With your permission, Google Analytics uses cookies to measure visits and which guides people read. It stays off until you accept. Use Analytics choices in the footer to change your choice. Rejecting after accepting refreshes this page. Privacy details.