Update your RAID log from weekly meeting notes

Paste the week's meeting notes and the previous week's RAID log into one chat, and ask the AI to propose only the rows it can back with a quoted line from the notes. Then accept or reject each proposed row yourself, and check owners, dates, RAG changes and source quotes before the log goes to anyone.

Steps follow the checks in the AI meeting notes test kit, checked 16 October 2026. The Fernhill office move example is made up.

A RAID log is a project's running list of risks, assumptions, issues and dependencies, one row per item, each with a traffic-light RAG rating. The AI's job here is narrow: compare what was said in the meeting with what the log already says, and show its evidence for every change. In the ChatGPT meeting notes test on 8 October 2026, the tool turned a risk nobody owned into the only action on the page and made a firm decision sound conditional. Those are the slips this prompt is written to catch.

For the weekly status update itself, see Package a weekly status playbook as a Claude Skill.

When nothing changed, or you missed a week

Some meetings won't touch the log. The prompt says so, and every row stays as it was. Write the date you reviewed it at the top of the log so readers can see it was checked, and don't let the AI move due dates or ratings to make the log look current.

If you missed a week, run the prompt once per meeting, oldest first, and update the log after each run so the next one starts from the right baseline. Pasting several weeks of notes at once hides which meeting moved which row, and an older line can end up overruling a newer one. If a meeting has no notes at all, there's nothing to quote. Ask the chair for their record, or leave the gap visible in the log, because no prompt can recover a meeting nobody wrote down.

Check four things before you share the log

Run these against the updated log, which is the version people will read.

• Every owner is a real person the notes show taking or being given the item. Blank owners stay blank until someone agrees to the job.
• Every date matches the meeting record, including any the AI marked [check date], and rows nobody discussed still have their old due dates.
• No RAG rating has gone down without a quoted reason in its source line. Compare the RAG column with the previous log row by row.
• Every new or changed row carries a source quote with its meeting date. A row you can't trace back to the notes goes back to its previous version.