Better Method.ai
Recipe 07

The weekly RSS packet

Grand rounds is not one activity. It is a new session every week: announcement, disclosure reminder, session objective, and eval questions, without inventing a gap you do not have.

What you’re making

One week’s worth of RSS paperwork, in your house wording: a short announcement, a disclosure reminder to the speaker, a session-level objective tied to the series gap, and three evaluation questions.

This is the hospital coordinator’s actual Tuesday. The series file already exists. What does not exist, every week, is the packet for this session. That is the job.

What to have open

The series title, the standing gap, who the learners usually are, and this week’s facts: speaker name and role, topic in their words, date, time, room or link, and whether their disclosure is in.

If you have last week’s announcement, keep it. That is how you get your voice instead of a conference flyer.

Do not paste the content of anyone’s financial relationships. “Disclosure received” or “disclosure outstanding” is enough.

The prompt

Prompt: copy and adapt
You are helping me assemble this week's packet for a regularly scheduled series (RSS). I am the author of record. Draft candidates for me to edit.

SERIES TITLE:
[paste]

STANDING PRACTICE GAP FOR THE SERIES:
[paste]

USUAL LEARNERS:
[specialties, roles, setting]

THIS WEEK:
- Date and time: [paste]
- Location or link: [paste]
- Speaker: [name and role only]
- Topic, in the speaker's words: [paste]
- Disclosure status: [received / outstanding / not yet asked]
- Anything the room needs to know: [parking, virtual login, lunch, none]

HOUSE VOICE:
[paste last week's announcement, or write "none"]

Draft four things.

1. ANNOUNCEMENT. Under 120 words. One session, one ask (come, or add to calendar). No invented CME credit language. If I did not give a credit statement, write [NEEDS: credit designation statement] rather than making one up.

2. DISCLOSURE REMINDER TO THE SPEAKER. Under 90 words. Ask only for the form or the confirmation. Do not discuss the content of any relationship. If status is already "received", write a one-line acknowledgement instead of a chase.

3. SESSION OBJECTIVE. One sentence beginning "After this session, participants will be able to..." Tie it to a specific phrase in the standing gap. If this week's topic does not address the gap, say so in one sentence and do not invent an objective.

4. THREE EVALUATION QUESTIONS. One on the objective, one on whether the session will change practice, one on the format. No leading wording.

Then tell me, separately: what is still missing from an activity file for this one session.

The last line is the useful one. RSS files fail in self-study on missing weekly pieces, not on missing series philosophy.

What good output looks like

The announcement sounds like a note from your office, not a save-the-date. The objective quotes the standing gap. The disclosure email does not mention companies, products, or dollar amounts.

If the topic does not fit the gap, good output refuses the objective. That refusal is the point of the recipe.

How to check it

Gap pass. Put your finger on the series gap and on this week’s topic. If you cannot connect them in one spoken sentence, do not use the objective.

Fact pass. Date, time, room, speaker name, login. Every concrete detail must be one you supplied.

Credit pass. Delete any AMA, ANCC, or joint-accreditation sentence you did not paste in. Credit designation statements are exact. Close is not close enough.

Disclosure pass. The speaker email talks about the process. If it names a company or a relationship, throw it away and write that line yourself.

Where it goes wrong

It writes a new series. Left alone, it will restate the gap, invent a three-year curriculum, and offer you a brochure. You asked for one Tuesday.

It invents credit language. Models have seen thousands of designation statements and will happily mint a plausible one. Never let that reach learners.

It treats RSS like a conference. Grand rounds announcements do not need “we are thrilled to welcome.” Your last week’s note is the fix.

Copilot
A Copilot Notebook can hold the series gap, last week’s announcement, and this week’s facts. Keep speaker disclosure forms out of it.
ChatGPT
A Project can keep the standing series file and house-voice examples. Use an approved workspace. Do not upload disclosure forms.
Claude
A paid Project can keep the series gap and a sample announcement in project knowledge. Same rule: process status only, never the form.